TOPIC 02 OF 08

Audience and perspective

Choose a useful viewpoint

PLAIN-LANGUAGE IDEA

Describe who the output is for and, when useful, the perspective the system should apply. ‘Review this as an accessibility specialist’ can focus attention. Treat role prompting as a lens, not proof that the system has real expertise, identity, or authority.

SEE IT IN A SITUATION

Review this signup flow from the perspective of a first-time screen-reader user. Identify obstacles, but do not claim that the review replaces user testing.

DO NOT MISS THIS

Broad personas can reproduce stereotypes. Prefer relevant needs, constraints, and expertise criteria over invented demographic characters.

TRY THIS NOW

Name the real audience, what they already know, what they need, and the perspective that would reveal blind spots.

CONNECTED LANDMARKS

a-useful-requestA useful request bias-and-representationBias and representation

← PreviousNext idea →

TAKEAWAY TOOL

The Request Brief

Use this when a task deserves more than a quick question. Leave a field empty when it does not help; never add sensitive information merely to complete the template.

01Goal
What should the work help you create or decide?
02Audience & perspective
Who is it for, and which viewpoint reveals useful criteria?
03Context
What minimum background and sources change the answer?
04Boundaries
What must it use, avoid, protect, or leave to a person?
05Output
Which structure makes the result easy to inspect?
06Example & tone
What does good look and sound like?
07Evidence
How should uncertainty, sources, and missing facts appear?
08Human checkpoint
Who verifies, edits, approves, or acts?

◉

Important topics change.

Environmental impact, copyright, privacy, security, and EU obligations require dated sources and context. The Atlas teaches durable decision habits and clearly separates them from legal or professional advice.