When customers start leaving

FOUNDATIONAL · CONSTRUCTED SCENARIO

A company notices that customer retention has declined over the past year. Several teams have ideas about why — but they don't agree on what needs to change.

The situation

The company has historically relied on a strong product and steady customer growth.

Recently, more customers have started leaving after the first year.

Marketing believes the problem is communication.
Sales believes customers are being poorly onboarded.
Customer support sees recurring product issues.
Product believes some customers were never a good fit in the first place.

Leadership decides:

Improve customer retention.

That's the strategy.

But what does it actually mean for the organization to act on it?

Level 0 — Organizational Landscape

The organization already has:

• customer data

• churn statistics

• sales information

• support tickets

• customer interviews

• product usage data

• existing retention initiatives

• departmental assumptions

The first task isn't to choose a retention methodology.

It is to establish:

What do we currently know about why customers leave?

The organization discovers that different teams are working with different pieces of the problem.

Level 1 — Action Plan

The initial action plan might be:

• Increase customer retention by improving onboarding and customer support.

But this immediately raises questions.

Which customers are leaving?

At what point?

Why?

What does "improve onboarding" actually involve?

What outcome would demonstrate that the change worked?

The Action Plan therefore becomes more specific.

Level 2 — Conceptual System

The organization develops a representation of the customer relationship:

Acquisition → Onboarding → Adoption → Value → Renewal

It connects this with:

• customer segments

• product usage

• support interactions

• customer expectations

• value realization

• renewal behaviour

The organization discovers something unexpected:

Customers who churn aren't necessarily experiencing more support problems.

Instead, several high-value customers never reach the product behaviour associated with realizing the expected value.

The problem isn't simply "customer support."

The organization's understanding of the problem has changed.

Level 3 — Operationalization

The organization now needs to change how it works.

For example:

• Sales records customer success criteria during acquisition.

• Customer success tracks whether those criteria are being reached.

• Product receives structured evidence about adoption barriers.

• Marketing adjusts expectations communicated before purchase.

The operational system now supports the action plan.

Level 4 — Capability, Evaluation & Learning

After several months, retention improves for one customer segment but not another.

The organization learns that the original assumption was only partly correct.

That learning becomes part of the New Organizational Landscape.

The next cycle can therefore start from better knowledge.

What this scenario demonstrates

A problem that initially appears to be a departmental execution issue can become a different organizational question once the knowledge surrounding the problem is connected.

Knowledge → Action → Learning → New Knowledge