Principle
A sales playbook that exists as a document and not as a practice is worse than no playbook, because its existence is treated as evidence that the problem it was written to solve has been addressed. The organisation stops looking. The gap remains and is now invisible.
Behaviour
An organisation recognises that its top performers do something the rest of the team does not, and commissions a playbook to codify it. Considerable effort goes into the document. It is thorough, accurate, and describes the methodology correctly. It is distributed, briefly discussed, and stored in a location everybody can name and nobody visits.
Nothing in the operating rhythm of the organisation depends on it. No pipeline review references it. No coaching conversation is structured around it. No onboarding milestone requires demonstrating it. It is a description of how the organisation would like to sell, sitting adjacent to the entirely separate reality of how it sells, and the two do not interact at any point.
Six months later, an executive asks why the team is not multi-threading. Someone produces the playbook, which explicitly instructs reps to multi-thread, and the conversation ends. The document has been used exactly once, to demonstrate that the organisation had already solved a problem it has not solved.
Its existence is treated as evidence that the problem it was written to solve has been addressed. The organisation stops looking.
Evidence
Ask three reps at random to describe, without prompting, one specific thing the playbook instructs them to do that they were not already doing before it existed. The answer is frequently silence, or a description of something that predates the document entirely.
Then examine the operating rhythm for any process that depends on the playbook. Does any pipeline review use its language as the structure of the conversation. Does any onboarding milestone require demonstrating one of its behaviours in a live situation. Does any coaching conversation reference a specific section. Where the answer to all three is no, the document is inert.
Check whether the playbook is ever revised. A living methodology accumulates amendments as reps discover what actually works. A document that has not changed since publication was never used, because use produces friction and friction produces revision.
Psychology
Writing a playbook is enormously satisfying and feels like the solution to the problem it describes. The document is a tangible artefact, it can be shown to a board, and its completion is a discrete event that can be reported. Embedding a playbook is none of these things. It is a slow accumulation of small enforcement decisions made by managers who have many other demands on their attention.
Reps, meanwhile, correctly perceive that no consequence attaches to ignoring the document. Following it requires changing established behaviour in front of live customers, which is uncomfortable and risky in the short term, while ignoring it costs nothing at all. Faced with that trade, reps do what the incentive structure indicates, which is to acknowledge the playbook warmly and continue as before.
Commercial Risk
The existence of documented sales methodology is routinely cited in diligence as evidence of commercial maturity, and it is accepted as such with little examination. An organisation with a comprehensive playbook that nobody follows is indistinguishable, on paper, from one that has genuinely institutionalised its top performers' behaviour, and the two have entirely different scaling characteristics.
The consequence for a post-acquisition plan is that the capability the acquirer believed it was buying, a transferable methodology that new hires can be onboarded into, does not exist. It exists as a document. The knowledge it purports to capture remains in the heads of the handful of people who wrote it, which is precisely the Hero Dependency the playbook was commissioned to resolve.
Embedding a playbook requires only one structural change, which is that some recurring process must depend on it in a way that cannot be satisfied without using it. An onboarding milestone requiring live demonstration, or a pipeline review structured entirely around its language, converts the document from a description into a constraint. Organisations that make this change find the playbook revises itself within two quarters, because contact with reality produces amendment.
Investment Committee Note