Course-aligned practice for D31-D36 Context Template Seed. This page uses the previous and next artifacts to keep the practice connected.
Part 2 | D31-D36 Context Template Seed | normal
Define audience fields that control reader, concern, tone, detail level, and adaptation rule.
A teammate says: “The template works, but it gives the same answer for manager, teammate, and customer.”
It sounds like tone adjustment. The trap is that audience fields define reader role, prior knowledge, evidence depth, and action.
“Audience: formal, friendly, or casual.”
The weak version contains formal, friendly, casual, no reader role, no action needed.
Manager, teammate, customer, or reviewer.
What they already know.
What they should do after reading.
Use this rule before filling the build table. The goal is a reusable context asset, not another one-off prompt.
Manager, teammate, customer, or reviewer.
What they already know.
What they should do after reading.
A finance analyst prepares the same budget variance explanation for CFO, department manager, and project owner. Each reader needs different detail and tone.
Define audience fields that control reader, concern, tone, detail level, and adaptation rule.
Using one generic explanation for every stakeholder and forcing the reader to translate it.
The same analysis is too technical for sales and too vague for an executive. Audience fields define reader concern, detail level, tone, and decision need.
Which audience field should be added first?
Received: D34 background_fields.md
Hands off: D36 use_case_fields.md
Redline: Do not export audience fields without naming the reader and what that reader needs to decide.
Before building the artifact, decide what the template should make easier to review.
This is not a generic sample. It is filled for Day 35: Audience Fields.
| No. | Audience | What they care about | Tone/detail need | Misread risk | Adaptation rule | Evidence used | Readiness |
|---|---|---|---|---|---|---|---|
1 | Department manager | Whether overspend needs immediate action | Direct, short, include variance amount and next action | May think finance is blaming the team | State cause, action owner, and decision needed | Budget variance sheet + manager request | Ready for D36 |
The response changes from information dump to useful decision support.
Detailed API explanation sent to sales lead
Reader concern: renewal risk; detail level: business impact, no API internals.
Core path: complete three rows. Deep path: complete three rows. Blank required fields create export warnings.
| No. | Audience | What they care about | Tone/detail need | Misread risk | Adaptation rule | Evidence used | Readiness |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 |
Optional but recommended: Use this pass to find the context/template field that would fail reuse, confuse a teammate, or hide a review need before export.
Weak row: Audience: friendly customer tone.
Repair move: Add reader role, prior knowledge, evidence depth, and action.
Better row: Audience: support manager; knows escalation; needs evidence and decision options before approving reply.
Choose the field you would be comfortable carrying into the next day.
Choose the field most likely to fail reuse or need review.
Sentence starter: The weak row is weak because ___. I will repair it by adding ___ before using AI.
This file is today’s work receipt. It should show which context/template field can be reused tomorrow, not just that you filled a table.
What this artifact proves: This file proves you can make audience fields operational rather than cosmetic.
Weak export: Audience: friendly customer tone.
Good export: Audience: support manager; knows escalation; needs evidence and decision options before approving reply.
Click Generate Markdown to create audience_fields.md.
Continue with a day-specific practice example.