How to write a brief your vendor can’t misunderstand

Most late projects don’t start with bad development — they start with a bad brief.

Structure of a good brief

1. Goal in business numbers — what improves, and by how much.
2. Current state — processes, systems, data.
3. Target state — how it will work after hand-over.
4. Acceptance criteria — measurable and verifiable.
5. Out of scope — as important as what’s in.

A brief is a contract of understanding. The more precise, the cheaper the project.