The brief is the most important artifact

A clear brief beats a smart team. A muddled brief defeats a great one.

The brief is where the project actually gets decided. By the time the team is building, eighty percent of the outcome is locked in. The brief set it.

Most briefs are bad. They're aspirations, not constraints. They list what we'd love to have without naming the trade-offs we're willing to make. They name the goal without naming the user. They name the user without naming the job.

The result is a team building five different things in parallel because the brief gave permission for any of them.

A good brief has five parts:

The user, named specifically. Not "professionals." Not "small businesses." A specific person with a specific job to be done. If you can't name them, you're not ready.

The job, in their language. What are they trying to accomplish? Phrased the way they would phrase it, not the way you would.

The constraint, stated upfront. What can't change? What's the budget? The deadline? The dependencies? Brief without constraints is wishful thinking.

The trade-off, made explicit. What are we choosing to be bad at so we can be great at the thing that matters? Every product is a trade-off; the brief has to name it.

The success criteria, falsifiable. How will we know in six months if this worked? If you can't write the answer in one sentence, you haven't designed for outcome.

A brief like this is uncomfortable to write because it forces decisions you'd rather defer. That's the value.

The team building from a five-part brief produces something specific. The team building from a vibe produces five things and ships none.

Write the brief before you write the code.

It's the cheapest leverage in operating.