Platform Capabilities Model

πŸ“– Introduction

When I first started building internal platforms, I approached it as a technical problemβ€”pick the right tools, wire them together, and developers would be productive. But after several iterations, I realized that successful platform engineering requires a more holistic view. Technology is just one piece; you also need investment, adoption, governance, and continuous measurement.

Microsoft's Platform Engineering Capabilities Model provides a structured framework for assessing and building platform maturity. It's helped me identify gaps in our platform strategy that pure technical thinking would have missed.


🎯 The Six Capabilities

spinner

Overview

Capability
Focus
Key Question

Investment

Resources, budget, strategy

How committed is the organization?

Adoption

Onboarding, documentation, support

How easy is it to use the platform?

Governance

Policies, compliance, standards

How do we ensure safety and consistency?

Provisioning & Management

Infrastructure, automation

How do we deliver platform capabilities?

Interfaces

APIs, portals, CLI tools

How do users interact with the platform?

Measurement & Feedback

Metrics, iteration, improvement

How do we know if we're succeeding?


πŸ’° Capability 1: Investment

What It Covers

Investment isn't just about moneyβ€”it's about organizational commitment to platform engineering as a strategic initiative.

Maturity Levels

Investment Patterns

Pattern
Description
Indicators

Grassroots

Bottom-up, developer-driven

Limited funding, part-time contributors

Strategic

Top-down, leadership-driven

Dedicated budget, full-time team

Hybrid

Mix of both

Project funding + platform budget


πŸ“ˆ Capability 2: Adoption

What It Covers

The best platform is useless if developers don't use it. Adoption focuses on making the platform accessible, understandable, and valuable.

Adoption Funnel

spinner

Adoption Metrics

Adoption Best Practices

  1. Documentation - Clear, searchable, up-to-date

  2. Onboarding - Guided first experience

  3. Support - Dedicated Slack channel, office hours

  4. Champions Program - Identify and empower advocates

  5. Feedback Loops - Regular surveys, user interviews


πŸ”’ Capability 3: Governance

What It Covers

Governance ensures the platform maintains security, compliance, and consistency while still enabling developer autonomy.

Governance Model

spinner

Policy as Code


βš™οΈ Capability 4: Provisioning & Management

What It Covers

How the platform delivers infrastructure, services, and resources to consumers.

Provisioning Patterns

spinner

Infrastructure Abstraction


πŸ–₯️ Capability 5: Interfaces

What It Covers

How developers interact with the platformβ€”APIs, portals, CLI tools, and IDE integrations.

Interface Types

spinner

CLI Design


πŸ“Š Capability 6: Measurement & Feedback

What It Covers

How you measure platform success and continuously improve based on feedback.

Key Metrics Categories

spinner

Metrics Implementation


🎯 Maturity Assessment

Self-Assessment Template

Capability
Level 1
Level 2
Level 3
Level 4
Level 5

Investment

No dedicated team

Part-time contributors

Dedicated team, limited budget

Full team, multi-year roadmap

Strategic investment, executive visibility

Adoption

Grassroots use

Some documentation

Onboarding program

Champions program

Self-sustaining growth

Governance

Ad-hoc policies

Some automation

Policy as code

Continuous compliance

Proactive governance

Provisioning

Manual processes

Scripts

Self-service some resources

Full self-service

Intelligent automation

Interfaces

CLI only

Portal prototype

Full portal

Multi-interface

Integrated ecosystem

Measurement

No metrics

Basic usage stats

KPIs defined

Continuous measurement

Predictive insights


βœ… Action Items

After assessing your capabilities:

  1. Identify gaps - Where are you weakest?

  2. Prioritize - What will have the biggest impact?

  3. Set targets - Define measurable goals for each capability

  4. Create roadmap - Plan incremental improvements

  5. Measure progress - Track advancement over time


πŸ”— What's Next?

In Article 8: Developer Portals with Backstage, we'll explore how to build a developer portal using Spotify's Backstage, implementing software catalogs, templates, and plugins.


πŸ“š References

Last updated