Product differentiation statement
The product differentiation statement is a single sentence, built on six fixed fields, that says which segment a product exists for, which category the market is to file it under and which alternative it sets itself against. The template comes from Geoffrey Moore, who set it out in Crossing the Chasm. The Agile Extension to the BABOK Guide names it among the exercises of its visioning technique, without giving its form. The sentence is filled in session, one field after another, each defended out loud.
Goal
The product differentiation statement is a sentence built on six prescribed fields: the target segment, that segment's need, the category the offering belongs to, the key benefit, the alternative the segment uses today and the difference that justifies changing. Geoffrey Moore fixed its form and its order in Crossing the Chasm.
The problem addressed is a problem of categorisation. A buyer who meets an offering puts it into a category they already know, then compares it with the category's other occupants and with what they do today for want of anything better. That categorisation happens with or without the team that sells. A description by features leaves every reader to do it, which produces as many positions as there are conversations. The sentence forces the team to choose the category itself and to accept the comparison that comes with it.
Moore treats positioning as a decision. Each of the six fields commits somebody. A sentence that commits on no field passes every review without contradiction and offers nothing anyone can check.
The deliverable is the sentence and the record of the session: who defended which field, which wordings were set aside and on what argument. The Agile Extension to the BABOK Guide cites the exercise among those that feed a visioning session, a session the guide places at the Strategy horizon; its glossary keeps to one line and the body of the text gives neither fields nor template, so the reference form remains Moore's.
Usage
When to use it
- Entry into a market already served: choose the category and the alternative before the first sales pitch is written.
- Visioning session: produce the material the vision statement will be drawn from.
- Diverging descriptions of the product: one shared sentence replaces them.
- A request for a parity feature: the difference field says what can be defended and what merely keeps up.
- A competitor arrives on the segment: read the six fields again and see which have stopped being true.
When not to use it
- Segment and competition still unknown: the session would invent its six answers; run a market analysis first.
- An internal tool with no buyer: nobody arbitrates between two offerings; visioning names the beneficiary and the outcome.
Description
The six fields
The fields are filled in Moore's order and compose a single sentence, which runs to between sixty and a hundred words. Each field carries an answer the team will have to hold in front of a buyer.
For (the segment), who (the need),
the target segment
the unmet need
(the product) is a (the category) that (the benefit).
the box the buyer puts the offering in
the outcome obtained
Unlike (the alternative), our product (the difference).
the habit in place
what justifies the change
Category and alternative, in orange, are contested by name in session.
| Field | The check that rejects a weak answer |
|---|---|
| For (the segment) | Name a company this line excludes. |
| who (the need) | Would the segment describe its need in these words? |
| (the product) is a (the category) | Does this name already appear in the buyer's vocabulary? |
| that (the benefit) | Does the line state an outcome obtained or a feature delivered? |
| Unlike (the alternative) | Is this the segment's current habit or the opponent the team would rather face? |
| our product (the difference) | Can the alternative named say as much? |
Which category does the buyer already recognise?
The category is the field that decides the other five. It fixes the list of offerings the buyer will compare the product with, the vocabulary they will use in front of their management and the budget line the spending will fall on.
Two opposite mistakes lie in wait on this field. An established category makes the offering one more entrant, judged on a feature comparison table where the incumbent has the advantage. A category coined in the room turns up in no search and forces every sales conversation to open with a definition. Moore ties the way out of this dilemma to the segment: a category holds as soon as the segment is narrow enough for the offering to be the obvious answer within it. The check is run outside the room. Three people from the sector are given a one-paragraph description and say which category they attach the product to; the words they use are the category name the market already recognises.
Filling the sentence in session
Six to ten people are enough for two hours: the sponsor, someone who sells, someone who talks to the target segment every week and the team that builds. Each field is written on the wall, read out loud and contested before the group moves to the next. The wordings set aside stay on display with the argument that set them aside, because the category and the alternative come back into discussion a few months later.
The trade-off here is a renunciation: narrowing the segment amounts to writing that other customers are not the target, a commitment that belongs to the sponsor alone. So the rule is set before anyone enters the room: the sponsor decides once the objections have been heard. Without it the segment retreats from field to field and the session comes out with a wording nobody defended. An interview with each participant ahead of the session tells the facilitator who is giving up what.
The guide sets its limitation on the visioning session, which this exercise inherits: the imagination, the diversity and the confidence of the group fix what the session can produce; a statement out of a weak group leads to poor decisions. On a positioning statement the consequence shows quickly: the text is written to hold in front of people who were not in the room.
Three neighbouring statements
A product team may hold three short statements that look alike from a distance.
| Statement | Who it addresses | What it contains | Who owns it |
|---|---|---|---|
| Product differentiation statement | The market: the buyer, sales, the sector analyst | Six prescribed fields, among them a segment, a category and a named alternative | The product team and its sponsor, in session |
| Vision statement | The organisation and the team that delivers | The expected outcome, its beneficiary and the deadline | The sponsor of the initiative |
| Product Goal | The Scrum team | A future state of the product the backlog items work towards; the Scrum Guide attaches no template to it | The Product Owner, in the product backlog |
In a visioning session the template is usually filled first, the vision sentence then drawn from what it contains. The Product Goal follows another route: a team can formulate one without ever having written the other two.
What makes the exercise fail
The segment that is too broad
"For companies that want to save time" excludes nobody, and the five fields that follow then fill themselves without effort because nothing constrains them. The benefit turns generic, the alternative too, the difference no longer holds for want of a shared buying habit to set against it. The check is one request made in session: name a company this line rules out. If nobody finds one, the field is empty however many words it carries.
The flattering alternative
The alternative field readily takes the name of the market leader, which sounds ambitious in session. The alternative the segment uses is often a spreadsheet, manual re-keying, an internal procedure or doing nothing. Writing the leader in its place empties the field: the difference ends up argued against a product the segment does not use, while the habit that loses the deals stays out of reach of the sales pitch.
The invented category
A category name coined in the room reads well and nobody ever searches for it. Where the category does not yet exist, creating it becomes an explicit part of the commercial strategy, with its cost and its deadline.
The sentence written after the solution
When the solution is already settled, the exercise fills in backwards: the category flatters what has been built and the alternative is chosen for being beatable. A field nobody contested has been recorded. A facilitator who crosses the six fields without one objection has run a ratification session; the remedy is set before the session, by charging one named person with contesting the category and the alternative.
AI considerations
What comes ahead of the session lends itself to a language model. From the public pages of a sector it lists the category terms used by buyers and by vendors. It rewrites one field in six forms, which the room puts side by side. It picks out the benefits written as delivered features, a check on form where it is seldom wrong. It then sets the difference field against the backlog and produces the list of items that serve parity alone, a manual sort impracticable across several hundred tickets.
What the model does not replace starts at the segment. Asked about it, the model will produce an acceptable wording without anyone having given up a customer. On competition it produces a plausible list that includes companies the segment never considers; the alternative in place is gathered from sales and in customer interviews. The statement itself sometimes carries an unannounced market entry, a price or a customer's name; those lines are cut from the text before it goes to a public model.
Examples
A software company in the canton of Vaud is preparing to enter the market of fiduciary firms in French-speaking Switzerland. The session first wrote "accounting software" in the category field.
That name put the offering next to suites already installed and already paid for, on a budget line closed for three years: the head of a fiduciary firm would have compared an additional subscription with a licence they renew without thinking. The check outside the room settled it. Three managers of fiduciary firms were given a paragraph of description; two answered "a service that prepares our returns for us", the third "VAT outsourcing". None said "software". The session therefore adopted the category of the preparation and filing service, which moves the comparison towards the hours the firm spends on the period close. The alternative followed: the field had carried the name of the market's main accounting software publisher; it now carries the manual re-keying the three of them had described without being asked.
Product differentiation statement, adopted by the session
For fiduciary firms in French-speaking Switzerland with five to twenty staff that handle the VAT of more than fifty SMEs, who close each quarterly return by re-keying the postings from several accounting packages, Fiduflux is a VAT return preparation and filing service that brings the preparation of a return down from two and a half hours to forty-five minutes. Unlike re-keying into a spreadsheet before filing on the portal of the Federal Tax Administration (FTA), our service reads the postings in the accounting package already installed at the client.
The segment: fiduciary firms with five to twenty staff, which rules out the in-house tax departments of large companies.
The category: a preparation and filing service, which places the spending on the fees line.
The alternative: manual re-keying, the habit in place in the firm today.
Session of 5 August 2026, seven participants. Sponsor: sales management.
The benefit field carries a number the buyer can verify for themselves. A fiduciary firm with 60 VAT mandates produces 240 returns a year, which is 600 hours at two and a half hours each against 180 hours at forty-five minutes: 420 hours freed, to be set against the price of the service, CHF 45 per return, which is CHF 10'800 for that annual volume.
Visualisations
In session the statement is read with its six fields colour-coded, so that each participant finds the one they must contest. The colour serves the session; the sentence circulated afterwards reads straight through, since that is the form in which the market will receive it.
Beside the sentence sit its date, the name of the group that wrote it and the wordings set aside for the category and the alternative. A team that cannot find the options already weighed weighs them again. Where the session also produced a vision statement, the two texts are shown together, the vision sentence below the template.
Cost
| Phase | Level | Justification |
|---|---|---|
| Preparation | Medium | Establishing what the segment does today, the buyers' category vocabulary and the sponsor's positions takes a few days spread over two weeks. |
| Execution | Low | A two-hour session with six to ten people produces a sentence of under a hundred words. |
| Documentation | Low | A dated sentence, the wordings set aside and the name of the group. The cost sits in the re-reading when a competitor or a price moves. |
Tooling
The wall carries the session: one column per field, the cards set aside displayed next to the one adopted. It asks for a room and participants in it; nothing leaves it until someone photographs the wall and transcribes its content.
The collaborative whiteboards (Miro, Mural and their equivalents) replace the wall when the group is spread across several sites and keep the discarded variants within reach of the next revision.
The documentation space (Confluence, SharePoint and their equivalents) carries the dated sentence at the head of the product space, next to the vision statement when both exist.
The backlog tool (Jira, Azure DevOps and their equivalents) displays the difference field where the requests arrive, the one place where the sentence meets the daily trade-off between a parity feature and one that sets the product apart.
That leaves the source that gives the alternative: sales notes, the customer relationship management tool, interview records. Without that source, the "Unlike" field fills with assumptions formed among colleagues.
Sources
- Geoffrey A. Moore, Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers, 3rd edition, Harper Business, 2014: the six-field positioning template, the prescribed order of the fields, positioning treated as a decision to defend and the link between the choice of category and a target segment narrow enough to dominate it.
- IIBA, Agile Extension to the BABOK Guide, §7.24 Visioning: the exercise named among those that feed the visioning session, the one-line definition carried in the glossary and the limitation that rests on the group assembled. §4.7.1 places visioning at the Strategy horizon.
- K. Schwaber and J. Sutherland, The Scrum Guide, 2020, Product Backlog section, Product Goal commitment: the Product Goal as a commitment attached to the product backlog and held by the Product Owner, for the boundary drawn in the description.