Begin with a reader’s task
A topic is not yet a reason to publish. Identify the question a reader brings and the situation in which they will use the answer. “An article about editing” becomes more specific when the task is “Help a small team decide which kind of edit its draft needs”.
Define what belongs on the page
Write a short scope statement and a few boundaries. List the questions the piece will answer and the questions it will leave for another resource. This protects the draft from collecting loosely related material simply because it shares a keyword.
Plan the evidence before the claims
List the facts that require checking, the examples you can create yourself and the sources you need to consult. Distinguish an illustrative example from an account of a real customer or experiment. If the subject requires professional expertise, decide how that expertise will be obtained and attributed.
Choose a structure that matches the task
A comparison may need a table. A procedure may need ordered steps. An explanation may need a worked example before a list of exceptions. Choose the structure for the reader’s use, rather than filling the same set of headings on every page.
Set a useful completion check
A brief should say how the draft will be assessed: the central question is answered, material claims are supported, limitations are visible, and the reader has a clear next step. A word count can be a practical constraint. It is not proof that a page has done its job.
AN ORIGINAL WORKED EXAMPLE
Weak completion rule
Reach 1,500 words and include the keyword ten times.
Useful completion rule
Explain the decision, compare the relevant options fairly and give enough evidence for the reader to understand the recommendation.
ONE THING TO TRY
Write a one-page brief with audience, question, scope, evidence, structure and completion checks.
Build a revision planProject credit: Human Readers. No named human or expert review is claimed for this launch guide.
Report a factual or editorial issue ↗