Friction
Name the friction that sits between interest and a yes
Interest is a meeting on the calendar. A purchase is a risk someone agrees to carry. Friction is everything that makes that agreement feel expensive, political, or unsafe, even when the product demo went well. These patterns are qualitative. They are not a ranked list of “top barriers in the industry,” and the claude standard will not let them pretend to be.
A buyer can admire the product and still refuse the week it would take to defend it internally.
From a stalled-renewal trace, recorded as a scene rather than a score
Four frictions that survive contact with a real deal
Switching cost that is not on the price page
Retraining a night shift, rebuilding a report the board already recognizes, or re-mapping an integration nobody documented. The cost is time and exposure, not a line item your competitor’s calculator shows.
The internal sell
The champion has to translate your language into a reviewer’s language. If that translation needs a number you did not earn, the sell stalls. See buying committees for who receives that translation.
Personal downside
The operator who will be called if the cutoff fails. Interviews on the decision-maker page should ask for this cost in the first person.
The good-enough incumbent
The current tool is clumsy and still covers Tuesday. Observation of that Tuesday, described in touchpoint observation, stops teams from calling every annoyance a buying trigger.
How a pattern becomes visible
You are not hunting a universal barrier. You are hunting a repeat inside your range of traces: the same stall, in different accounts, around the same kind of scene.
- 1. Anchor to a scene. A security review, a budget meeting, a pilot week, a renewal. If the friction has no scene, it is a mood.
- 2. Name the carrier. Which role feels the friction in their own week. “The organization” does not feel anything.
- 3. Separate block from inconvenience. A block stops the purchase or the rollout. An inconvenience is complained about and then worked around.
- 4. Look for the missing artifact. Often the stall is a document that does not exist yet: an exit plan, a data-flow sketch, a rollback note.
- 5. Refuse the fake rank. Three accounts mentioning training is a pattern to investigate, not proof that training is 60 percent of the market’s problem. Coding rules live in pattern synthesis.
Questions teams ask while reading friction notes
Is friction the same as an objection on a call?
No. An objection is a sentence in a meeting. Friction is the cost that sentence is trying to point at. Treat the sentence as a clue and go find the scene, using interviews and, when you can, observation.
Can we publish “the number one reason deals slip”?
Not from this method, and not under the claude standard. You can publish the pattern you saw, the roles involved, and the limit of the range you studied. The evidence page shows the wording that keeps that honesty intact.
Where does friction go in messaging?
Into a positioning line that names the tradeoff a buyer already feels, not into a promise that you will remove every cost. That move is the subject of positioning synthesis. Definitions sit in the glossary.
Turn a named friction into language that does not overclaim
Positioning is the next craft step. Committees explain who has to hear the line. Read both before the sentence ships.