Reviewing churn cases without blaming individual account managers

Reconstruct the customer's decision and the team's knowledge before a lost account. Ask what could have been recognised or changed, including constraints outside the account manager's control. Close with an evidence-based action, an explicit unknown, or a decision that no programme change is justified.

Fix the case boundary

Identify the service or contract line that ended, the decision date, and whether the customer left entirely or reduced scope. Gather the customer's own explanation where available, keeping it distinct from an internal category such as “poor adoption”. If no reason was given, record that gap rather than filling it with a colleague's guess.

Choose a period before the decision in which the team could realistically have acted. Reconstruct the goal, product-use evidence, support history, commitments, stakeholder changes, and commercial steps as they stood then. Notes written after the loss may help explain it but must not appear in an earlier snapshot.

Reconstruct decisions, not personalities

Build a timeline of what the customer needed, what the team observed, what each person understood at the time, what was decided, and what happened next. Invite the account manager and relevant support, product, or commercial owners to correct it. Ask what information, authority, or route to help was missing at each decision point.

For a hypothetical approvals customer, the record might show extra training arranged while users could not complete an approval. Ask whether the obstacle was visible, whether the manager could request technical investigation, and who owned the customer update. The sequence does not establish that training caused the loss or that one manager could have fixed the problem.

A review without blame can still record a missed handoff or unfulfilled commitment. Describe what happened accurately, examine the conditions that allowed it, and assign corrective work. Address any separate performance concern through the appropriate management process.

Test several explanations

Compare the customer-confirmed reason with product experience, service response, changed priorities, and commercial terms. Preserve conflicts in the evidence. A customer might have experienced a serious service problem but ended the contract because its project closed.

Before calling a finding a pattern, compare the case with similar retained and lost accounts. One loss can reveal a serious failure without showing how common it is. Look for the same task and obstacle, including cases where the team resolved it.

Close with a learning decision

Write a short conclusion: the confirmed reason, other supported contributors, unknowns, the earliest actionable signal, and any proposed change with an owner. The change might be a clearer escalation route, a product investigation, a corrected handoff, or further evidence gathering. Set a point for the owner to report back.