Rebuild enablement as a living knowledge system (L6)
Static decks and quarterly trainings are replaced by a maintained source of truth that feeds reps, agents, the website, and support from the same content. Enablement stops producing artifacts and starts owning a system.
The steps
- 01
One source, many surfaces
Tool: Notion
Positioning, objection handling, and proof points live once and are published into the assistant, the website, and support macros. No parallel decks. Owner: enablement plus product marketing. Pitfall: a slide library that drifts from the source within one quarter. DoD: each claim exists in exactly one place with a named owner.
- 02
Every claim carries evidence and an expiry date
Tool: Manual
Proof points get a source and a review date. Expired claims are hidden automatically rather than quietly repeated on calls. Owner: product marketing. DoD: no live claim is past its review date.
- 03
Feed the system from the field, continuously
Tool: Gong
New objections detected on calls open a content task the same week. The loop from field to content is measured in days, not quarters. Owner: enablement. DoD: median time from new objection detected to approved answer is under ten business days.
- 04
Retire the quarterly training ritual
Tool: Manual
Replace the all-hands enablement session with short in-flow updates. Keep one live session per quarter for practice only. Owner: enablement leadership. DoD: the calendar reflects the change and rep-facing time is measured.
Tools in this playbook
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.
