Building account playbooks without bureaucracy
- Define playbooks by lifecycle moment, not binder.
- Apply the minimum-viable-artifact test.
- Tie artifacts to the cadence and retire what isn't used.
The test for any playbook is whether it gets used in a live meeting. So I build the minimum viable artifact for each lifecycle moment — onboarding, QBR, renewal, risk, expansion — each with a trigger, an objective, two or three steps, and an owner. Every artifact is tied to the cadence so it's a working surface, not homework. I start with one high-value play, prove it on real accounts, scale what works, and ruthlessly retire anything that isn't being used.
Lifecycle moments
Handoff, kickoff, onboarding, QBR, renewal, risk, expansion — playbooks map to these, not a binder.
Minimum viable artifact
Trigger + objective + 2-3 steps + owner. If it's not used in a meeting, it doesn't exist.
Success plan vs playbook
Success plan = shared roadmap WITH the client; playbook = internal workflow for delivering it.
Prove then scale
Start with one play (often renewal), prove on real accounts, codify, scale, retire the unused.
- Consistency across AMs without slowing them down.
- Used artifacts compound; unused ones erode trust in the system.
An expansion play turns whitespace into a repeatable team motion.
Lightweight, used playbooks fit a consultancy that resists process theatre.
Your Scrum background — lightweight, iterative, outcome-tied — is exactly the right instinct here.
How do you avoid playbooks becoming bureaucracy?
One rule: a play earns its place only if it's used in a live meeting. Minimum viable artifact per lifecycle moment, tied to the cadence, proven on real accounts, and anything not used gets retired. Structure that makes the team faster, not slower.
“I'd document our best practices and make sure everyone follows the standard process.”
A play earns its place only if it's used in a live meeting. Minimum viable artifact per lifecycle moment — trigger, objective, steps, owner — tied to the cadence so it's a working surface, not homework. Prove one play on real accounts, scale what works, retire what isn't used.
Situation: A previous account-plan template was created but never used.
Move: Diagnose why (too heavy, not tied to a meeting), rebuild as a minimum-viable artifact pulled up in the weekly review.
Outcome: Process that sticks because it's the working surface of a meeting, not extra homework.
Make me design a renewal playbook as a minimum-viable artifact and critique it for bureaucracy.
Open the Tutor (top-right) and paste this prompt, or tap a mode.