WORKSPACE / READING

Define a project before the task list.

A short scope keeps a team from confusing activity with progress. It should be readable without a planning tool.

Editorial team ·

NOTE 01

Start with a change in the world

Write the outcome as something a reader, colleague or visitor could observe. “Improve the help centre” is too broad to guide a choice. “A new reader can find the setup steps from the homepage” identifies a situation and a result. Note the current friction separately: people may need to search several headings or repeat a question. Keeping the problem distinct from the solution leaves room to discover that a clearer link matters more than another document.

NOTE 02

Name the boundary

Decide what the project will leave untouched. The boundary may be a supported browser, an existing storage format or the fact that no user account will be created. These details belong near the outcome because they change what counts as an acceptable implementation. A useful scope also explains who can approve a departure from it. Without that distinction, a reasonable suggestion can become an accidental commitment, and the original work becomes difficult to finish.

NOTE 03

Give completion a visible test

Turn the desired result into a small observation. Ask someone unfamiliar with the material to locate the guide, perform the described task and explain the next step. Record which part caused hesitation instead of scoring the person. If a software feature is involved, include the error path: a missing item should lead to an understandable message. Passing a test means that behaviour was observed; it does not prove that every reader will have the same experience.

NOTE 04

Keep changes to scope deliberate

New information is useful, but it should not silently rewrite the objective. Put proposed additions in a short decision note and ask whether they correct a mistaken assumption or merely suggest future work. Keep the first scope visible while making that judgement. When the work ships, compare the outcome with the initial description rather than the number of tasks completed. If the goal moved, explain the reason. This leaves a record that another reader can follow.

Further reading

Continue with the guides index, or explore the overview for the wider context. Try the method on a small unfinished task before using it for a larger project. Keep the original explanation next to the revised one, and record which decision became clearer. A useful note should remain understandable to someone who was not present for the discussion.