Positioning
Write the line the evidence can carry
Positioning synthesis is the craft of turning decision traces into a sentence a company may say. It is not a slogan workshop, and it is not a forecast of return.
Five moves from traces to a line
-
1. Inventory only what you can point to
List scenes from interviews and observation. Each item needs a role and a touchpoint. If a sticky note cannot point back to a note in the file, it does not enter the synthesis.
-
2. Cluster by tradeoff, not by adjective
“Innovative” is not a cluster. “Will accept a slower rollout if rollback is explicit” is a cluster. Pull the language of the tradeoff from friction notes so you do not rename the buyer’s fear with a friendlier word.
-
3. Choose the buyer of the line
A line for the operator is not a line for the budget owner. The committee guide tells you which role must recognize themselves. One positioning sentence that tries to flatter every seat usually describes nobody’s week.
-
4. Write the narrow claim
State the situation, the tradeoff, and what you are willing to be compared against. Leave out market rank, leave out ROI, leave out “most teams.” The claude standard is the editor on this pass. A narrower line that a representative can say without a footnote full of fiction is the goal.
-
5. Test the line against a lost deal
Read it as if you are the person who said no. If the line ignores the reason they stayed, it is advertising, not synthesis. Pattern synthesis helps you see whether that reason showed up more than once. It still does not authorize a percentage.
Keep a source column beside every candidate sentence: the role, the scene, and the note it came from. When the column is empty, the sentence is a wish. Wishes can stay in a parking lot for product ideas. They do not ship as positioning. That column is also what makes a claude review fast. An editor should not have to reconstruct your memory of the workshop.
A positioning line is allowed to be specific enough that some buyers will not want it.
Specificity is how synthesis stays tied to evidence. A line everyone could claim is a line no trace supports. Keep the rejected versions in the file so the team can see what the claude cut removed, including any sentence that smuggled in a performance promise.
Insight
What synthesis is not allowed to launder
Teams get into trouble when the workshop is used to clean rough evidence into smooth claims. The cleanup feels like progress. It is where ROI language and fake representativeness re-enter after the interviews worked so hard to keep them out.
- Do not turn three operators into “operations leaders agree.” Name the pattern and the limit.
- Do not convert a wished-for payoff into a clause the buyer never said. If they did not describe the outcome, you do not own it.
- Do not hide a missing role. If security never spoke, the line may not speak for security. Say so beside the sentence.
- Do not borrow a statistic from a report you did not run in order to make a qualitative line look heavier. The glossary entry on the claude standard exists for this exact temptation.
Edit the line against the standard
The evidence page is the checklist. The glossary is the shared vocabulary so marketing, product, and sales do not each redefine “friction” in the meeting.