Brief
also called project brief
A short document defining objective, audience, constraints and success measures.
The short document that starts the work properly.
What It Is
You will find Brief in the Execution layer, alongside the rest of Process. Stated plainly: a short document defining objective, audience, constraints and success measures.
It is a repeatable structure, which means it only pays off when it is actually followed through instead of quoted. Once it is defined that clearly, arguments about it usually stop.
How It's Used
In practice, Brief shows up in project delivery, scheduling and the handover between people doing the work. It is usually discussed together with Content Brief, Discovery and Scope. The practical test is whether anyone can follow it without the person who wrote it in the room.
Why It Matters
Brief is one of those items that only becomes visible when it is missing. When it is unclear, work still happens — it just happens twice. It is worth pinning down before anyone builds on top of it.
Think of a recipe. Follow the steps and you get a predictable result. The short document that starts the work properly.
Termshift™
How the meaning shifts depending on who is using it, and where.
Practitioners use Brief as shorthand and expect no explanation — a short document defining objective, audience, constraints and success measures.
Outside the industry, most people would just say: the short document that starts the work properly.
The Bottom Line
If you only keep one thing about Brief: the short document that starts the work properly. Everything after that is detail.