Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Fullmer Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Risk
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==The Play Library== In infrastructure, a runbook is a standardized, written response to a known failure mode, so the fix doesn't depend on which engineer happens to be on call. Customer Success mostly still runs on tribal knowledge β the best CSM on the team knows exactly what to do when a champion goes quiet, and nobody else does. The Play Library is that knowledge, written down, so the response doesn't depend on who picks up the account. Every play follows the same shape, so any CSM/TAM/CE can execute one cold: * '''Trigger''' β the specific, observable signal that starts the play * '''Owner''' β the role responsible for running it (see [[CSM vs TAM vs Customer Engineer]]) * '''First 48 hours''' β the concrete first steps, in order * '''Escalation path''' β who gets pulled in, and at what point it becomes a declared incident * '''Success criteria''' β what "resolved" looks like, stated before you start * '''Close-out''' β how the play gets logged, and what feeds [[The Postmortem (Churn and Save Retros)|the postmortem]] if it didn't work Starter plays worth having on day one: * '''Usage Drop Play''' β triggered by a defined percentage decline in core-feature usage over a rolling window * '''Champion Departure Play''' β triggered by a bounced email, a LinkedIn job-change signal, or a support contact from an unrecognized name * '''Support Ticket Spike Play''' β triggered by ticket volume or severity crossing a threshold after a quiet baseline * '''Post-Onboarding Adoption Lag Play''' β triggered by missing the [[Onboard|time-to-first-value target]] * '''Executive Sponsor Silence Play''' β triggered by a defined stretch with no exec-level engagement ahead of a renewal * '''Renewal-at-Risk Play''' β triggered by a health score in the at-risk band inside a defined window before renewal date Judgment doesn't scale past the first few hires, and it doesn't survive attrition. A written play library means consistent response quality across a growing team and β critically β something concrete to improve.
Summary:
Please note that all contributions to Fullmer Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Fullmer Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Risk
(section)
Add topic