Project operations·6 min read
How to write a project brief that prevents pointless revisions
A useful brief is not a polished presentation. It is a short agreement that lets people make decisions without guessing what the project was meant to achieve.
Describe the outcome before the tasks
Start with the change the work should create: what should be different when the project is complete, and for whom? A task list alone lets every participant define success differently.
Choose one simple way to recognize that outcome. It might be a published page, a completed decision, a handoff, or fewer steps in a recurring process.
Name what is outside the work
Write the scope and the exclusions with equal clarity. The second list stops a reasonable request from quietly becoming a different project.
New ideas do not have to be rejected. Decide whether they replace something, belong in a later phase, or need a brief of their own.
- Outcome and audience.
- Expected deliverable or decision.
- Scope and exclusions.
- Owner, reviewers and decision date.
Make decision ownership visible
A list of attendees is not enough. State who prepares the work, who decides, who reviews and who only needs to be informed. Projects often stall because two people assume the other owns the decision.