Skip to main content

Command Palette

Search for a command to run...

The real KPI problem in platform teams

Updated
2 min read
A
I lead the strategy and delivery of products and systems that solve real problems, support commercial goals and scale across teams and markets. My work spans platform foundations, user-facing experiences, commercial tools and developer products, and I adapt my approach to the needs of each domain. My experience covers early-stage, scale-up and enterprise product environments, combining hands-on delivery with team leadership and award-winning work recognised across several innovative organisations.

Most platform teams rarely struggle because they lack metrics.

They struggle because the metrics they're measured on don't reflect the value they're meant to create.

Adoption, usage, and number of integrations are the most common KPIs. They're easy to track and easy to explain. They're also incomplete.

When platform teams are measured primarily on adoption, a few behaviours follow:

  • Saying yes too often

  • Prioritising short-term uptake over long-term coherence

  • Optimising for volume rather than quality

None of those behaviours are malicious. They're rational responses to the incentives in place.

I worked with a platform team measured on "number of teams onboarded." They hit their target every quarter.

But teams were onboarding to the minimum viable level. Using basic features. Building workarounds for anything complex. The platform was widely adopted and barely trusted.

The metric said success. The reality said otherwise.

The deeper problem is that platform value is mostly indirect.

Good platform work shows up as:

  • Reduced duplication across teams

  • Faster delivery without additional coordination

  • Fewer exceptions and bespoke solutions

These outcomes are harder to measure, slower to materialise, and rarely attributable to a single initiative. When a team ships faster because integration took hours instead of weeks, nobody tags the platform team in the announcement.

So teams fall back to what's legible.

Dashboards that show adoption curves. Quarterly reports on integration counts.

The result is a gap between what the platform is meant to do and what it's rewarded for doing. Over time, the team optimises for the dashboard, not the mission.

The most effective platform KPIs I've seen focus less on activity and more on friction removed:

  • Time saved (integration time drops from 2 weeks to 2 days)

  • Decisions simplified (teams no longer debate authentication approaches)

  • Failures prevented (fewer production incidents caused by inconsistent patterns)

They're imperfect. Some require surveys or estimation. But they align behaviour with intent.

The goal of platform metrics isn't precision.

It's direction.

What you measure is what you optimise for. If you measure adoption, you get volume. If you measure leverage, you get value.