Every fast-growing CS team eventually builds a playbook, and every playbook eventually meets a customer it wasn't written for. The tension between running a repeatable process and staying flexible enough to actually serve the account in front of you only gets sharper as headcount grows. This session brings together CS leaders working through where standardization genuinely helps a team scale, and where it quietly starts working against the outcomes it was meant to protect, covering how they decide what belongs in a playbook, what should stay a judgment call, and how to keep both from collapsing into either chaos or box-ticking. What this session will cover: - Where standardized playbooks help a growing team and where they start to hurt - How to decide what should be documented process versus CSM judgment - How to keep consistency from turning into box-ticking that customers can feel - What signals suggest a playbook needs revisiting rather than reinforcing