The Brief That Stays a Brief
A brief states the result, its constraints and its context; written another way the same information becomes a method document, and the verbs are the giveaway.
Reads as a businessReads as employmentCuts both waysDepends where you are
Four factors, and no total. Every bar is the same length: the side is the claim, the size is not. The heaviest factor in most tests, and the easiest one to give away by accident.
A brief states the result, its constraints and its context. The same information written slightly differently becomes a method document, and the difference is almost entirely in the verbs.
The management distinction in “The Brief That Stays a Brief” matters when software turns a brief into a continuous stream of instructions. Teams considering read this official capability summary for task switching cost should define the outcome being measured, limit access and preserve the contractor’s ability to organise the method where the agreement requires it.
Businesses that learn to write the first kind keep an instrument that businesses writing the second kind have already spent.
For another operational perspective on “The Brief That Stays a Brief”, consult Hive project-management articles. Compare it with the actual statement of work, jurisdiction and supplier relationship before adopting a general practice.
Two versions of the same requirement
Compare these, which ask for the same thing:
The pricing page must load in under two seconds on a mid-range phone on a normal connection, and must still work if the pricing service is down.
Lazy-load the images, cache the pricing response for five minutes, and put a fallback in the template.
The first describes a result and leaves the supplier their judgement. The second is a set of instructions, and if any of them turns out to be wrong, you own the consequence.
The verbs to watch
Briefs that stay briefs tend to use must be, has to, will be judged by, needs to work with. Briefs that have become instructions use use, start with, do, follow, go through.
That is a crude test and it catches most of it. Running a draft brief through it takes two minutes and is the single most useful habit in this section.
Constraints are not instructions
Real constraints exist and belong in the brief: the data cannot leave a particular region, the output has to open in a specific application because that is what the client uses, the work has to interoperate with a system you did not choose.
Write those as properties of the finished thing. "Must run on the existing server estate" is a constraint. "Deploy it to the Frankfurt box" is an instruction about how, and the two are five words apart.
Context the supplier cannot get elsewhere
The part of a brief that earns its keep is everything the supplier could not know: who this is for, what the business is actually trying to achieve, what was tried before and why it failed, what the political sensitivities are.
That is not direction. It is the information that lets somebody exercise judgement well, and leaving it out is the main reason work comes back wrong and buyers conclude they should have been more prescriptive.
What to do with your own strong opinion
Sometimes you know how you want it done and the preference is real. The honest routes are to make it a constraint and say why, or to offer it as a preference the supplier can decline.
"We would rather it used the existing component library, but if there is a reason not to, tell us" is a different document from the same sentence with the second half removed. The second half is what keeps the judgement where you bought it.
The brief that arrives in six messages
Most briefs are not documents at all. They are a conversation, a follow-up, two clarifications and a thread, spread over a week.
Everything in this section still applies, and a single consolidated message at the end — this is what we have agreed the work is — costs five minutes and converts a scatter of instructions into one description. Suppliers almost always welcome it, because it protects them too.
When the brief turns out to be wrong
It will sometimes. The constraint was unnecessary, the standard was unachievable, the context was incomplete.
Rewriting it is normal and the mechanics are in the next article but one. What matters here is that it gets rewritten rather than supplemented by direction, because supplementing by direction is how briefs quietly stop governing anything.
Who writes it
Whoever understands what good looks like, which is usually not the person who owns the budget and not the person who will manage the day-to-day.
Where that person does not exist in the business, the supplier can often write the brief and submit it for agreement. That is a legitimate and common arrangement, and it is considerably better than a brief written badly by somebody who did not want the job.
What it is worth when nothing goes wrong
Nothing visible, which is why it gets skipped. The return arrives entirely in the cases where something goes wrong, and it arrives as the difference between a two-message resolution and an argument in which neither side can point to anything.
Across a year of engagements, a business that writes briefs properly has fewer disputes and resolves the ones it has faster, and almost nobody can attribute that to the afternoons spent writing.