Your customer, pinned.
Also called: Customer persona · Buyer profile · Ideal customer profile · Target user
A specific, named portrait of the one person the product is for, built from real evidence, not a demographic bracket or a guess.
One real buyer, named and evidenced, not a demographic bracket. A good persona settles arguments: you ask what they would do, not what “users” want. Build it from interviews and observation, then keep it in front of every later decision.
What a customer persona is
A customer persona is a specific portrait of the one person the product is for, drawn from evidence. “Home bakers aged 30 to 55” is not a persona; it is a demographic bracket. “A serious weekend baker in a cold Victorian kitchen who has binned three overnight proves this winter” is. The first describes a market. The second describes a person you can picture making a decision.
In my experience the persona earns its keep the moment an argument starts. Two features are on the table and the team is split. You stop asking what “users” want, which is unanswerable, and ask what this one named person would do, which usually is. The persona does not have opinions of its own; it just makes the team’s assumptions visible enough to test.
Why teams get this wrong
- They invent it. A persona built from the team’s imagination just reflects the team. It has to come from people you actually spoke to.
- They make it flattering. The fictional buyer who loves everything you planned to build is worse than useless; it launders your bias as research.
- They make it too broad. “Anyone who bakes” cannot help you choose between two designs. One sharp person can.
The proofing-box buyer
The clearest way to pin a persona is to fill it in for a real person you met, not a composite. Here is the one that came out of the proofing box’s customer interviews, so you can see the level of detail that makes a persona useful rather than decorative.
Notice what the persona is not. It is not “people who like bread”. It is one person, in one kind of kitchen, with one recurring failure, who has already tried the obvious fixes. That is specific enough to argue with.
Weak persona vs strong persona
The same buyer, framed two ways. The weak version feels safe and tells you nothing. The strong version is uncomfortable and immediately useful.
- “Home bakers, 30–55, who care about quality.”
- “Foodies who like gadgets.”
- “People who want better bread.”
- Built from what the team assumed, not from interviews.
- A three-year baker in a cold kitchen, failing one prove in three.
- Has already tried the oven light and a heat mat.
- Wants a steady 26°C with no app and no ritual.
- Drawn from twelve real conversations, with quotes.
The weak persona could describe half the country, so it settles no argument. The strong one is narrow enough that you can ask, of any feature, “would they actually use this?”, and get a real answer.
How it fits the bigger picture
Customer Persona is activity 02.10.03 in the framework, in Stage 02 Discover. It builds on the value goals set at the start of Discover, and feeds the market context enquiry and, later, Stage 04 Evaluate, where the persona is the yardstick the commercial case is measured against.
What it can do
It turns “the market” into one person the whole team can picture, which makes design and scope arguments quick to settle. It also keeps you honest: a feature that the named buyer would not use has to justify itself loudly.
What it can’t do
It can’t validate demand on its own. The persona is a sharp hypothesis about who the buyer is; the market context enquiry and Stage 04 Evaluate test whether enough of those people exist and will pay. A persona built from too few conversations is just a confident guess.
See the full 10-stage process →
Try it yourself
Pull up the last five people you spoke to who have the problem. Write one of them up as a single named person: their kitchen, their week, the exact moment the problem bites, and what they have already tried to fix it. Use real quotes where you have them. If you cannot fill it in without inventing, you have not done enough interviews yet, and that is the finding.
Want a structured first pass? The Free Sprint walks you through who the buyer is as part of its early questions. Start the Free Sprint →
Your persona checklist
Project notes: the buyer behind the box
▸ From the notebook · optional reading
How Dan and Anna pinned the proofing-box buyer from twelve kitchen-table conversations, and the quote that decided the no-app call.
3 min read · click to open
We started with a flattering sketch: “keen home bakers who love kit”. It would have justified anything. So we parked it and went and talked to twelve actual bakers, most through the Sourdough School community, a few in their own kitchens around Stockport and Manchester.
What the conversations changed
The age range turned out to be irrelevant; the kitchen was everything. Almost everyone described the same thing: a cold room, an overnight prove that worked in summer and failed in winter, and a drawer of half-measures. One baker walked us through her oven-light routine, checking it twice before bed, and said the line we kept coming back to: “I just want to set it and trust it.”
That sentence did more than any spec meeting. It killed the companion app on the spot. An app is the opposite of “set it and trust it”: it adds a screen, a pairing step, a thing to charge. The persona, once it was a real person and not a bracket, simply would not have used it.
Where the persona earned its keep
When the £149 price came up, the fear in the room was that it was too high. I asked the obvious question: would the woman with the oven-light routine pay it? Every interview pointed the same way. She had already spent more than that on flour she had binned over two winters, and on a stand mixer she used less. The premium ceramic finish, which we nearly cut to save cost, was the thing that made it counter-worthy rather than another gadget shoved in a cupboard.
The persona did not make those decisions. It just meant we were arguing about a person we had actually met, instead of a market we had imagined.
— Discover stage, project notes, 2026
— Next in Discover → Market context enquiry