Guide

Product brief template, built on what customers said.

A product brief is one page that says which customer problem you are solving, how you know it is real, what you will and will not do, and how much time it is worth. Copy the template below. Fill in the evidence first, from your calls, then make the decision.

Updated

Brief · worth six weeks

Reports customers can share without redoing them

9 companies, 7 without being asked.

What is a product brief?

It is the page someone reads before they build. It explains the problem and the bet you are making on it, and leaves the how to the people doing the work. Whoever picks it up should be able to start without asking you anything.

This template has two halves. The first half is evidence: what customers said and how many of them said it. Nobody edits that half to fit the plan. The second half is your decision, and it is yours to argue about.

The template

Plain text, so it pastes into Notion, Google Docs, Linear or an email as it is.

# Brief: [the change, in one line]

## The problem, in their words
"[Exact sentence]" [company, type of call, date]
"[Exact sentence]" [company, type of call, date]
"[Exact sentence]" [company, type of call, date]
The pattern behind them: [one sentence]

## Who has it
[N] companies raised it, [N] of them without being asked.
[Who they are, if it matters: plan, size, role]

## What we are doing
[The change, in a few sentences. What the customer will notice.]

## What we are not doing
[The obvious extras, ruled out by name.]

## Constraints
[What must not change or break.]

## Done looks like
[What we will see that tells us it worked.]

## Time it’s worth
[A day / a week / two weeks / six weeks]

What does a filled-in brief look like?

Here is one from a made-up team. Every company and quote in it is an example.

Brief · six weeks

Every report gets a status its reporter can see

The problem, in their words

  • "I reported it in March and I don't know if anyone read it." Ostrom, success call, 4 Sep
  • "We stopped reporting things. It goes into a hole." Caldera Retail, renewal call, 18 Sep
  • "Can you at least tell me it's on a list somewhere?" Northvale Systems, onboarding call, 2 Oct

The pattern behind them: people report problems and never hear back, so they stop reporting.

Who has it

8 companies raised it, 7 of them without being asked. Mostly the person who looks after the tool day to day, not the buyer.

What we are doing

Every report gets a status the person who filed it can see, and they hear when it changes.

What we are not doing

No public roadmap. No voting on reports. No dates promised in the status.

Constraints

Support keeps working in the tool they use today. Nobody gets more email than one message per change.

Done looks like

Reports per active customer stop falling. Nobody asks "did anyone read this?" on a call for a month.

Time it’s worth

Six weeks.

How do you fill in each part?

PartWhat goes in it
The problem, in their wordsThree quotes from three different companies, word for word. Then one sentence on what sits underneath them.
Who has itHow many companies, not how many mentions, and how many raised it without being asked.
What we are doingThe change, as the customer will notice it. A few sentences, no screens.
What we are not doingThe extras someone will suggest, ruled out by name.
ConstraintsWhat must not change or break.
Done looks likeSomething you can see or count afterwards.
Time it is worthA day, a week, two weeks or six. How much this is worth, not how long it will take.

The idea comes from Basecamp's book Shape Up: you decide what the problem is worth before anyone estimates it. If the work does not fit, cut the scope, never the evidence.

Counting companies rather than mentions is the part most teams skip. The guide How to hear your customers explains why it changes which problems make it into a brief at all.

When do you need a PRD instead?

A product requirements document lists what the finished thing must do, often down to fields and edge cases. You need one when the people building cannot ask you questions: an outside agency, a regulated product that needs a paper trail, or several teams that must agree on the same details.

For a team that sits together and can talk, a brief is usually enough. Start with the brief anyway. A PRD written without the evidence half tends to specify the wrong thing very precisely.

What makes a brief go wrong?

  • A feature request in the problem slot. "Customers want a status page" is someone's guess at a fix. Write what they are struggling with instead.
  • Paraphrased quotes. They lose how strongly something was said, and they drift towards what you already believed.
  • No "not doing". The scope grows quietly until it no longer fits the time it was worth.
  • An estimate instead of a limit. An estimate grows with the work. Deciding what it is worth tells the team when to stop and cut.

Can the evidence half write itself?

Collecting the quotes and the count is the slow part: finding three good sentences, checking they came from different companies, and counting who raised it without being asked.

Ordagrann reads the customer calls you record in Granola, groups every problem and request into themes, counts how many companies raised each one, and turns a theme into a one-page brief your team can build from. The evidence half is filled in from the theme and locked, and you write the decision half. Whoever builds opens it with a link, no account needed.

Get started

Works with Granola Business. Any other transcript can be pasted in.