The short version
- Positioning projects fail because the framework is too big to finish, so it becomes a workstream and gets deprioritised.
- Five days: pull raw material, name the incumbent, audit differentiation, write the sentence, pressure test with people who will push back.
- Cross out every capability a competitor could also claim. What remains is short and often uncomfortable, and that is the finding.
- Positioning is a hypothesis, not a discovery. The returns come from testing it in market, so a slow process delays the only thing that produces signal.
Positioning projects fail for a boring reason. The framework is too big to finish, so it becomes a workstream, and workstreams get deprioritised when a quarter goes badly.
The version below takes a week. It is smaller than the canonical frameworks on purpose. A finished decision beats a thorough process that stalls in week six.
| Day | Work | Output |
|---|---|---|
| One | Pull closed-won, closed-lost and support notes | The buyer’s actual vocabulary |
| Two | Name the incumbent behaviour and its cost | What you really compete with |
| Three | Differentiation audit, cross out anything a competitor can claim | The short honest list |
| Four | Write five versions of the sentence, read aloud | One sentence |
| Five | Pressure test with two salespeople and one customer | A cut, not an addition |
Day one: pull the raw material
Three sources, nothing new commissioned. Closed-won notes from the last twenty deals. Closed-lost notes from the last twenty. Support tickets from the last quarter, skimmed for the phrases customers use when frustrated.
You are not analysing yet. You are collecting the buyer’s actual vocabulary, and this comes first because every positioning exercise that starts in a workshop room ends up written in internal language.
Day two: name the incumbent
Write down what the buyer does today if they do not buy you. Be concrete: a named spreadsheet, a specific contractor arrangement, a competitor plus a workaround. Then write what it costs them, in their words, from yesterday’s notes.
Most companies skip this and position against the category. You do not compete with the category. You compete with the specific thing the buyer would otherwise keep doing, and that thing is usually not a competitor. Getting this wrong is the third failure mode in positioning statement examples that hold up.
Day three: the differentiation audit
List every capability you would put on a website. Next to each, write the name of a competitor who could also claim it. Cross out every line that has a name next to it.
What remains is short and often uncomfortable. Sometimes nothing remains, which is itself the finding: your differentiation is in service, speed, price or focus rather than product. That is fine. It just needs saying out loud so the messaging stops pretending otherwise.
Cross out everything a competitor could also say. What survives is your positioning, and it is usually shorter than the leadership team expects.
Day four: write the sentence
One sentence. Buyer, incumbent behaviour, the specific thing you do instead. No adjectives that cannot be checked. If a claim cannot be falsified, it is decoration.
Write five versions. Read them aloud. Four will die on contact with your own voice.
Day five: pressure test with people who will push back
Not the leadership team. Two salespeople and one customer.
Salespeople will tell you which clause dies on a call, because they have watched it die. The customer will tell you whether the incumbent framing is right, which is the part most likely to be wrong and the most expensive to get wrong.
Take the notes and cut. Do not add. Every positioning document I have seen grow after this stage got worse, because each addition was somebody’s reasonable concern and the sentence absorbed all of them.
What you have at the end, and what you do not
You have a sentence, a named incumbent, a short list of real differentiators, and the buyer’s vocabulary in a document. That is enough to rewrite a homepage, brief a writer, and fix a sales deck.
You do not have a forty-page positioning document, a persona set with fictional names, or a messaging matrix by segment. Those are useful later, at a size where segments genuinely diverge. Building them in week one is how the project stops being finishable.
Why is a week enough?
Positioning is a hypothesis, not a discovery. You cannot verify it in a room. The value comes from putting it into the market and watching what happens to reply rates and call length, which means the cost of a slow process is not just salary time, it is the delay before you get real signal.
Every long positioning project I have been near produced a better document and a worse outcome than a short one, because the short one was in market four months earlier. Where the sentence goes next is covered in what a go-to-market plan actually contains.
Frequently asked questions
How long should a positioning project take?
One week for the core decisions. Positioning is a hypothesis rather than a discovery, so value comes from testing it in market and watching reply rates and call length, not from refining it on paper. Long projects produce a better document and a worse outcome because they delay real signal by months.
What is the first step in a positioning framework?
Pull raw material you already have: closed-won notes from the last twenty deals, closed-lost notes from the last twenty, and a quarter of support tickets skimmed for the phrases customers use when frustrated. You are collecting the buyer's vocabulary before anyone opens a workshop deck.
How do you identify real differentiation?
List every capability you would put on a website, then write the name of a competitor who could also claim it beside each one. Cross out every line with a name next to it. What remains is your differentiation, and sometimes nothing remains, which means you compete on service, speed, price or focus.
Who should be in a positioning workshop?
For the pressure test, two salespeople and one customer rather than the leadership team. Salespeople will tell you which clause dies on a call. The customer will tell you whether the incumbent framing is right, which is the part most likely to be wrong.
What deliverables come out of a positioning project?
A sentence, a named incumbent, a short list of real differentiators, and the buyer's vocabulary captured in a document. That is enough to rewrite a homepage, brief a writer and fix a sales deck. Persona sets and messaging matrices by segment come later, at a size where segments genuinely diverge.
Why do positioning projects stall?
Because the scope is set to the canonical frameworks, which are built for companies with a research team. A workstream gets deprioritised the moment a quarter goes badly. A finished decision beats a thorough process that stops in week six.
Sources
- Chua Network delivery data across 8 client accounts (internal fact bank)
