Everyday-life content begins with noticing, not stereotyping. Record a specific situation, friction, phrase, or small win; identify what it may reveal about a defined audience; then shape a useful angle. One observation proves one moment—not how “Pakistanis” behave.

You will build a seven-day observation log and ten respectful angles. Each angle will carry a source observation, creative lens, and consent or privacy decision.

// concept

Build a Seven-Day Observation Log

Keep the log in Notes, a spreadsheet, or a paper notebook. Capture moments while fresh, but do not secretly record people. Write what happened before interpreting it.

Field	Useful entry	Entry to reject
Situation	“Gulshan apartment: comparing two electricity-bill line items”	“Pakistan problems”
Literal observation	“Two labels were checked before comparing the total”	“People never understand bills”
Friction or small win	“Highlights made comparison easier”	“Poor people struggle”
Exact phrase	Your own or a consented, redacted “location pin bhej dein”	A copied private voice note
Evidence	“My note, 18 July; no account number”	A face, CNIC, phone number, or transaction ID
Permission	`self`, `written yes`, `anonymise`, or `do not use`	Blank

Be narrow enough to picture, not narrow enough to identify. “Gulshan electricity-bill comparison on a phone” can produce an explainer; “Pakistan problems” produces a complaint. Describe the task or decision, not a home, face, or account.

Notice a situation (the task), a frustration (where it slows), or a small win (a workaround). An empty row is better than an invented anecdote.

// concept

Convert an Observation Through Four Lenses

Use this chain:

// prompt — copy me1 line

literal observation → possible audience insight → creative lens → content angle

An insight is an explanation to test, not a national truth. Write “This may help apartment residents comparing bills on a phone,” not “Pakistanis do not understand electricity.” Then choose a lens:

Lens	Question	Angle shape
How-to	What small task can I demonstrate?	“A walkthrough for…”
Myth-bust	What assumption can evidence correct?	“What this assumption misses…”
Cost-reveal	Which components can I show without inventing prices?	“Before comparing totals…”
Story	Can I narrate my own change?	“What changed when I tried…”

For cost-reveal, show components and verify any tariff or fee against the current official source on publication day. For story, use your experience, obtain written permission, or label a non-identifying composite; do not borrow someone’s private moment.

This prompt turns logged material into options without asking AI to invent “local colour”:

// template — copy me15 lines

You are an editorial angle assistant. Use only the observations inside <log>.
For each observation:
1. Separate the literal observation from a possible insight.
2. Draft one how-to, myth-bust, cost-reveal, and story angle.
3. State what must be verified before publication.
4. Flag any person, phrase, location, face, document, or private detail that needs consent,
   redaction, or removal.

Do not generalise from one moment to Pakistan, a city, class, gender, ethnicity, language,
religion, or profession. Do not add anecdotes, quotes, prices, hardship, or cultural details.
Return a table: observation | cautious insight | lens | angle | evidence needed | safety action.

<log>
[Paste only your redacted observation rows here.]
</log>

// concept

Run the Cliché and Dignity Checks

Chai, rishta, load-shedding, cricket, and traffic become cliché wells when the reference is the entire joke. Apply the subversion test: remove the familiar symbol. If the angle collapses, replace it with a task or decision. “When chai fixes every deadline” collapses; “How I batch captions during a scheduled power window” teaches a workflow.

Next ask whether someone’s poverty, identity, accent, body, home, job, or private frustration is entertainment. Would the angle survive if they saw it? Did they approve this use and channel? Permission to take a photo is not permission for a brand campaign.

Bad sample—exploitation: “Watch this struggling rider teach privileged customers gratitude.” It assigns an identity, turns hardship into spectacle, and claims a lesson the person never gave.

Respectful fix: “A checklist I use to make delivery instructions easier: correct map pin, reachable phone, landmark, and gate note.” The creator teaches their own behaviour. No rider is filmed, quoted, or made responsible for a moral message.

// worked_example

Worked Example

This is a hypothetical sample, not reported research or a result. A Karachi home-based seller has removed customer names, numbers, addresses, and order details.

Sample observation	Cautious insight	Lens	Draft angle
A redacted WhatsApp query asks for delivery cost although the caption contains it	Important buying information may be hard to scan on a phone	How-to	“Put delivery city, charge source, and cutoff in three scannable lines”
The creator compares the current electricity bill with a saved screenshot	A side-by-side visual may make line-item comparison easier	Cost-reveal	“How I compare two bills without showing an account number”
A recipient asks “location pin bhej dein” after receiving a typed address	A pin plus landmark may reduce clarification messages	Myth-bust	“Why a full typed address may still be an incomplete delivery instruction”

The prompt wrongly returns, “Every Pakistani customer ignores captions.” That turns one sample into a stereotype. The fix is: “On a small screen, delivery information may be difficult to scan; test a three-line information block.” This proposes a test without blaming all customers.

The creator then expands the same log into this sample set of ten angles:

How-to: make a three-line delivery-information block for a WhatsApp catalog post.
Cost-reveal: list delivery-cost inputs to verify before quoting a total.
Story: compare the creator’s dense caption with their scannable rewrite.
Myth-bust: show why an address and map pin solve different delivery needs.
How-to: redact a message screenshot before use.
Cost-reveal: build a bill comparison with fabricated numbers labelled “sample.”
Story: show the creator’s offline reference workflow for an outage.
Myth-bust: test “Roman Urdu is always more relatable” with one segment.
How-to: turn consented product questions into a five-card FAQ without quotations.
Story: document the creator’s week of improvements without universalising them.

Before publishing, check the platform’s current privacy, originality, AI-disclosure, and commercial-content rules on its official help page.

// failure_cases

Failure Cases to Diagnose

6 cases to diagnose

The observation is already a judgement
“Lahoris are…” is a stereotype, not a log entry. Replace it with a dated, literal action you personally observed.
The angle mines hardship
If poverty, occupation, disability, gender, ethnicity, or accent supplies the entertainment, discard the angle; do not merely anonymise it.
A cliché carries the whole post
Remove chai, rishta, traffic, or cricket. If no useful idea survives, return to the task or friction in the log.
One moment becomes a national claim
Change “Pakistanis prefer…” to a hypothesis for a named segment and test it with content or first-party research.
Consent is vague
“They said it was okay” is insufficient for an identifiable customer story. Record the asset, channel, purpose, and approval in writing—or do not publish.
Redaction is cosmetic
A blurred face beside a phone number, school badge, vehicle plate, QR code, or unique location can still identify someone. Crop or replace the asset.

// pakistan_angle

Pakistan Angle

Pakistan is not one content persona. A Roman-Urdu caption tested with Karachi online shoppers says nothing about Pashto-speaking viewers in Khyber Pakhtunkhwa or English-first professionals in Islamabad. Keep city, language, age, device, and buying context attached. Religion, politics, sect, ethnicity, and provincial identity are not “relatable” decoration; using them needs a clear editorial reason and reliable sources.

WhatsApp commerce can expose phone numbers, profile photos, home addresses, location pins, JazzCash or easypaisa references, and voice notes. Do not paste these into AI or publish the screenshot. With permission, re-type the minimum redacted phrase or paraphrase the question. Never use a CNIC, utility account number, student card, prescription, or payment confirmation as visual texture.

Plan around Pakistani connectivity instead of making load-shedding a punchline. Keep the log offline, compress references, and batch uploads when power and data are stable. Your workflow can be useful content; a neighbour’s difficult moment is not automatically yours to film.

// hands_on

Hands-On Exercise

6 steps

Build one week of observations into ten respectful angles.

Create a log with the six fields from the first table.
For seven days, record at least one situation, frustration, or small win you directly notice. Leave identifying details out.
Mark every row self, written yes, anonymise, or do not use; remove every do not use row from the AI input.
Write one cautious insight for each usable observation. Ban “Pakistanis,” “everyone,” and city-wide claims unless you have appropriate evidence.
Apply the four lenses. Use the prompt to expand options, then keep ten angles you can actually source and produce.
Run the cliché-subversion and dignity checks. Record one evidence need and one safety action beside every angle.

// completion_rubric

Completion Rubric

5 checks — tick as you verify

0/5

// sources

Sources

3 official sources — check every claim yourself

// check_yourself

Check yourself

4 questions · answers and options are taken word-for-word from this course

0/4

1 / 4 · diagnose
Your work shows this failure mode: “The observation is already a judgement.” The lesson describes it like this: ““Lahoris are…” is a stereotype, not a log entry.” What does the lesson tell you to do about it?