Most leadership and product teams believe they understand their customers. They look at:

• performance dashboards
• customer journey maps
• defined target segments or personas

Yet when performance shifts — positively or negatively — one gap becomes apparent:
Leadership can observe change, but struggles to explain it. Metrics evolve, initiatives launch, experiences are optimised —
but the link between action, customer behaviour, and outcome remains blurred.

Why this gap persists — even in data-driven organisations

Most organisations are not lacking customer insight. They are rich in perspectives, tools, and expertise. The challenge lies elsewhere. Customer understanding is distributed across functions, artefacts, and meetings. Each perspective answers a different question — and does so convincingly on its own. But leadership decisions are rarely made within one perspective. They require trade-offs, prioritisation, and an understanding of impact across customers and time.

When these perspectives are not connected, organisations optimise in parallel:

• product teams improve flows
• marketing refines targeting
• analytics reports movement and goal achievement

What is missing is a shared, explainable view that allows leadership to understand how actions translate into customer behaviour — and how that behaviour translates into business outcomes (see also Sabine’s post on the connection of UX with the Sales perspective). Without this connection, leadership sees change — but lacks strategic leverage.

A familiar executive situation

Example: In a large consumer organisation, a core KPI looks stable — for example, new customer sales. Several initiatives were launched in parallel — product, marketing, experience. Each team can point to positive signals. Yet weeks later, growth slows and churn edges up. No single action explains it, no clear cause emerges. Leadership sees movement — but cannot explain which decisions affected which customers, and why.

What leadership lacks in these situations is not insight, but causality: the ability to link actions to customer behaviour and business outcomes.

Causality in customer decisions emerges only when three familiar perspectives are connected:

• a view on what is happening (analytics)
• a view on who it is happening to (user types)
• a view on where and how it happens (customer journeys)

Each perspective is necessary. Only together do they become actionable.

What leadership can do differently

Regaining control does not require new tools or another transformation programme. In most organisations, the necessary perspectives already exist. What changes is how they are connected and used in decision-making.

1. Make customer journeys explicit per user type

Instead of assuming one “typical” customer path, distinguish where different customer groups follow the same journey — and where they diverge.

This immediately reveals:

• where improvements help some customers but hurt others
• what uplift can be expected from which customer group

For leadership, this turns abstract experience discussions into explicit prioritisation choices (and Sales will also be interested).

2. Anchor journeys in business-relevant metrics

Customer journeys become actionable when they are connected to outcomes that matter at leadership level — not just experience scores.

This means:

• embedding metrics like conversion, churn, support calls, or retention directly into journey views
• observing how these metrics change over time, before and after decisions

Journeys stop being explanatory artefacts and become instruments for steering and control.

3. Make user types visible in analytics

This is typically the most demanding — and most consequential — step. Making user types visible in analytics means translating conceptual customer distinctions into observable behavioural patterns. This is rarely available out of the box and often requires deliberate analytical work, alignment on definitions, and careful handling of privacy constraints.

• Entry Patterns: For example, one user type may predominantly enter through organic search, while another is more likely to arrive via campaigns or referrals.
• Usage sequences: Some user types reliably move quickly into detailed functionality, while others spend more time in overview or orientation states before acting.
• Context signals: Device choice, timing, or usage context often correlate strongly with underlying needs and constraints.

Identifying such patterns requires exploratory analysis, iteration, and often collaboration between product, analytics, and domain experts. It also requires conscious decisions about how far to go, given regulatory and organisational boundaries.

Once user types become observable, analytics can answer why numbers change — not just that they do.

What improves once these perspectives are connected

When these steps are in place, leadership gains something rare: the ability to reason causally about customer decisions. Concretely, this changes how decisions are made and evaluated:

• Initiatives can be assessed by which customers they affected, not just overall averages
• Trade-offs become visible early, not after KPIs disappoint
• Discussions shift from opinions to explainable effects over time

Leadership no longer asks: “Did this work?” but instead: “For whom did this work — and at what cost?”

This is the point where customer understanding turns into strategic leverage: not because uncertainty disappears, but because decisions become explainable, testable, and steerable.

You don’t gain control by collecting more insight. You gain it by connecting what you already know into a causal picture. That is what turns customer understanding from observation into leadership actionability.

And you can even turn this understanding into a company-wide business driver.

The first steps are often the most important ones. If you can show the power of connected customer data to stakeholders, adoption and integration will be much easier. And this is less about methods and more about change — in how decisions are prepared and discussed. We will go deeper into that topic in upcoming articles.

Happy to exchange experiences!

Contact us

Featured Image: Cockpit of Tupolev Tu-22M3 by Wikimedia