From an unclear request to a reader-task brief
4 min read
Lesson objectives
- Turn a vague request into a reader-task brief with evidence and acceptance tests.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A professional assignment may begin with “improve the help page.” That is an aspiration, not a deliverable or a reader task. Before drafting a title, identify who reaches the page, what they are trying to do at that moment, which product or process evidence is available, and what they should be able to do after reading. Without those answers, “good writing” becomes a matter of taste and the document cannot be tested against its purpose. We call the result a reader-task brief. It is a working artifact, not a professional licensing standard.
Record six connected fields: intended reader, situation, task to complete, authorized source of truth, document boundary, and observable acceptance criterion. “Users” is too broad to guide a writer. “A reception worker submitting a first record-correction request through the organization’s portal” reveals likely prior knowledge, vocabulary, and required steps. Separate the organization’s goal, such as reducing calls, from the reader’s task, such as choosing an attachment. A page may contribute to fewer calls, but a successful attachment task does not by itself prove call volume fell. Measure that organizational outcome separately. Do not promise an effect that the brief cannot establish.
Collect source materials before fixing claims. A product owner may hold an approved release specification, the support team may have an old article, and a colleague may describe a change that has not shipped. Combining all three into one page would create a misleading hybrid. Record each source’s version, date, and the claims it can support. Where they conflict, put a bounded question to the decision owner: “Which version will readers actually use, and is the proposed change released?” You can design the page structure and write stable sections while the answer is pending. You cannot responsibly publish a procedure that depends on the disputed detail. The writer identifies and escalates the conflict rather than making a guess look official.
Make acceptance criteria observable. “A clear page” tells a reviewer little. “A reception worker finds the attachments field, selects the document for their case, and recognizes from the confirmation message that the request was sent” describes a test. Add a factual check: every field name and document state must match the interface version that will accompany publication. Include at least one failure case when the task has exceptions. A happy path may work while a reader with no attachment gets stranded. Test task completion with a person using a comparable interface; verify factual accuracy against the authorized source. These checks answer different questions.
In the handoff, distinguish facts, assumptions, and open decisions. For example: “Reader: new reception worker; basis: team request; confirm with service owner.” Do not silently promote an audience assumption into a settled fact. Rank unresolved questions by consequence. Uncertainty about a decorative button differs from uncertainty about an eligibility rule that could lead readers to submit the wrong request. If a high-impact question blocks a truthful instruction, hold that instruction while finishing the verifiable parts. The brief then defines both the work and the boundary of the writer’s authority.
Lesson summary
Turn a vague request into a reader-task brief with evidence and acceptance tests.