State the Outcome and Audience

Work through the explanation, apply it to the example, and complete the quick check before continuing.

Start with the change you need

A topic is not an outcome.

Topic:

Customer service.

Task:

Draft a one-page guide that helps new support staff recognise when a complaint must be escalated.

The task tells us what should exist and what it should help someone do.

Write an observable outcome

A useful outcome names:

• The deliverable: email, table, summary, comparison, plan, or checklist.
• The purpose: inform, prepare, compare, decide, revise, or explain.
• The success condition: what the result must allow the reader or reviewer to do.

Weak:

Make this better.

Stronger:

Rewrite this notice so residents can identify the collection date, accepted items, and contact route within one minute.

The stronger version can be reviewed. We can check whether those details are present and easy to find.

Name the real audience

Audience affects vocabulary, detail, examples, tone, and assumed knowledge.

Compare:

• A short explanation for a first-time customer.
• A technical note for the engineers maintaining the system.
• A decision brief for a manager who has five minutes.

All three may concern the same system. They should not receive the same explanation.

State what the audience already knows and what they need next. Avoid invented labels such as make it professional when a more useful description is available.

For example:

Audience: department managers who understand the current process but do not know the proposed software. They need the main benefits, costs, risks, and unresolved questions before a meeting.

Purpose is not tone

Tone describes how writing sounds: calm, direct, formal, friendly, or reassuring.

Purpose describes what the writing must accomplish.

Use a friendly tone cannot replace tell registered learners what to bring and where to arrive.

Worked example

Vague request:

Explain password safety.

Outcome and audience:

Create a 250-word onboarding note for new office staff. Help them recognise three unsafe password practices and know where to report a suspected account problem. Assume no security background. The note is general awareness material, not incident-response instructions.

Now the task has a deliverable, purpose, audience, assumed knowledge, and boundary.

Remember

• A topic is not an outcome.
• Name the deliverable, purpose, and success condition.
• Describe the audience’s knowledge and need.
• Tone supports the outcome; it does not define it.

Next, we will decide what information the system may use.