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
The Postmortem (Churn and Save Retros)
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!
Part of [[The Playbook]]. This is the page that turns everything else here from a one-time setup into an actual system. Without it, [[Observability (Customer Health Scoring)|health scores]] go stale, [[The Play Library|plays]] never improve, and the same account failure mode repeats with a different customer's name on it every quarter. ==Blameless, and mean it== The point of a postmortem is not to find who missed the signal β it's to find what the system missed, because a person will always be the last link in a chain of things the system should have caught earlier. A postmortem culture that assigns blame teaches CSMs to hide problems until they're unrecoverable, which produces exactly the surprise churn the whole system exists to prevent. ==Run one after every [[Incident Response for At-Risk Accounts|incident]], win or loss== * '''Timeline''' β what happened, in order, from first available signal to close * '''Root cause, not proximate cause''' β "the champion left" is proximate; "we had no relationship with anyone else at the account" is the root cause, and it's the one worth fixing * '''What the health score caught or missed''' β did the signal fire in time, or did the score need an input it didn't have * '''What the play caught or missed''' β did the matching play exist, did it trigger correctly, did the owner follow it * '''What changes as a result''' β a new play, an adjusted trigger threshold, a new [[Observability (Customer Health Scoring)|health score]] input, a revised [[SLOs for Customer Outcomes|SLO]]. A postmortem with no resulting change didn't do its job. ==Don't skip the wins== Most CS orgs only postmortem the losses. That means the org only ever learns what fails, never what specifically worked β so a save that happened because one CSM improvised something clever never becomes a documented play, and the next CSM who hits the same signal starts from zero again. Review saves with the same rigor as churns; the output is a new entry in [[The Play Library]] instead of a fix to an existing one. ==Where the output goes== Every postmortem should produce at least one concrete edit to another page in [[The Playbook]] β that's the test for whether it was worth running. If a postmortem's conclusion is "nothing to change," either the incident really was a one-off, or the review wasn't dug into deeply enough. [[Category:Customer Success Manager]] [[Category:Customer Engineering]]
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
The Postmortem (Churn and Save Retros)
Add topic