How to
How to write a new product development brief
A brief for a consumer product specifies the problem worth solving, not the product. Here is what belongs in one.
A brief specifies the problem, not the product
The most common mistake in a new product development brief is to write down the answer. "We need a high-protein breakfast bar" is a solution wearing the clothes of a brief. It closes the question before the team has opened it. A good brief holds the problem open: it says what job needs doing and for whom, and leaves the team room to find the sharpest way to do it.
This matters because the brief is the single point everything downstream traces back to. If it names a product, every later decision is really just decoration on a choice already made. If it names a problem, the concept, the positioning and the design each have something real to be measured against.
What belongs in a consumer product brief
The job to be done
The consumer problem, stated as a job people are trying to get done. Not "launch in the electrolyte category" but "help people who train early feel ready without a stimulant crash." The job is the spine of the brief; everything else hangs off it.
The consumer
Who specifically has this job, described as a person in a moment rather than a segment. A brief that says "health-conscious millennials" has not narrowed anything. A brief that says "the person who has quietly given up on their skincare routine because it stopped working" has given the team someone to build for.
The tension and the insight
What the consumer feels about the job today, and the truth underneath it. The insight is the part of the brief that makes the team lean in. It is worth spending most of the brief's effort here, because a sharp insight does more to shape good work than any amount of instruction.
The constraints
The real boundaries: where it must sit commercially, what the business can and cannot make, any non-negotiables of channel, format or margin. Constraints are not the enemy of creativity in a brief; they are what stop the team solving a different, easier problem than the one that matters.
The ambition, and what success looks like
How big this is meant to be, and how you will know it worked. A brief for an incremental line extension and a brief for a category-defining bet should not read the same, because they call for different work. Say which one this is.
A note on the term
Write "new product development brief" or "consumer product brief," not "product brief" on its own. In most professional contexts a bare product brief means a software product requirements document, which is a different artefact for a different audience. The distinction is not pedantry; it changes who the brief is for and what a good one contains.
The test of a good brief
A good brief is short, and it survives being handed to someone who was not in the meeting. If they can produce work you did not anticipate but immediately recognise as right, the brief did its job. If everything they produce is either an obvious restatement of the brief or a departure from it, the brief was either too closed or too vague. The next step from a finished brief is turning it into a concept.
Common questions
What is a new product development brief?
A short document that tells a team what consumer problem to solve, for whom, and within what constraints, so everything they produce traces back to one agreed intent. It specifies the problem worth solving rather than the product itself.
What should a consumer product brief include?
The job to be done, the specific consumer, the tension and the insight underneath it, the real constraints, and the ambition with a clear picture of what success looks like. The insight usually deserves the most effort, because it shapes good work more than instruction does.
What is the difference between a product brief and a new product development brief?
A bare "product brief" in most professional settings means a software product requirements document, aimed at engineering. A new product development brief, or consumer product brief, is about a physical or consumer product and specifies a consumer problem, not a set of features. Use the fuller term to avoid the wrong audience and the wrong template.
How long should a product development brief be?
Short. A brief that runs to many pages has usually started specifying the product. The discipline is to hold the problem open on a single page, with a sharp insight, so the team has room to find the best answer rather than execute a decision already made.
Run this on your own idea
Bring a rough idea or a brief. Bampot works it up into the concept, the strategy and the briefs to build it. The first one is free.
Try a brief, free