The brief is the most expensive document in software
The most expensive document in software is the one nobody wrote: the brief. A brief is a short description of the task and the context. Not a spec, not a prototype β just enough to explain what is needed and why. It tak
The most expensive document in software is the one nobody wrote: the brief.
A brief is a short description of the task and the context. Not a spec, not a prototype β just enough to explain what is needed and why. It takes an evening, and it saves weeks, because every misunderstanding it prevents would otherwise surface after the first demo.
The minimum that unblocks everything
You do not need a 40-page document. Four things are enough:
- The problem in one paragraph. Not "we need an app" but "drivers photograph 8 angles of a car, managers review each set, and today it happens in a WhatsApp group".
- Who does what today, and how long it takes. As-is beats to-be every time.
- What success looks like. One metric: fewer rejections, faster handover, fewer phone calls.
- What is definitely out of scope. The most useful section, and usually the shortest.
Brief, spec, prototype: what is the difference
- Brief β short description of the task and context. Written by the client, to explain what is needed.
- Spec (scope document) β an agreement on scope and acceptance criteria. Agreed by both sides, to fix the work and how it will be accepted.
- Prototype β the visual logic of the screens. Usually made by the contractor, to agree on how it looks and behaves.
Skipping the spec is how "we agreed verbally" turns into an argument about the invoice.
How to describe a scenario
Bad: "the app should let the manager approve photos".
Good: "the manager opens the request, sees 8 photos with labels, approves or rejects with a comment; a rejected set returns to the driver with the comment visible; the driver sees the list of rejected angles".
The difference is not detail for its own sake β it is that the second version can be estimated, built and tested.
What is usually unnecessary
- Page-by-page descriptions of screens that do not exist yet;
- Colour choices and fonts (that is design work, not scope);
- A 50-page technical specification written by someone who will not build it;
- Feature lists copied from competitors' pricing pages.
Checklist of a good brief
- [ ] There is a goal and a success metric;
- [ ] Users and their context are described;
- [ ] There are 3β7 scenarios with a result each;
- [ ] It states what is included and what is not;
- [ ] Integrations and constraints are listed;
- [ ] Acceptance criteria are defined;
- [ ] Examples or references are attached;
- [ ] It is clear how scope changes are recorded.
If you have these eight points, the estimate becomes accurate and the project stops drifting. If you do not, the contractor will write them for you β and charge for the guessing.
Cross-post. Full version: How to write a brief that saves you money. Related: how to estimate a project and what an MVP is.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.