How do we plan a roadmap that keeps the platform healthy too?

You say you want a roadmap that supports the product and keeps the platform healthy. Say what you actually mean: you want to ship fast without paying for it later. That wish is normal. It is also a trap your team sets for itself every sprint. The platform does not break because nobody cared. It breaks because every small choice favored what customers see over what holds the system up. Each choice looked fine alone. Together, they built a slow collapse. You do not need a smarter framework. You need a number, agreed on before the quarter starts, for how much capacity goes to the platform. Then you need to hold that number — even when someone important asks you to bend it.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

Some to learn

1:1 with AureliusWith others (a Pod)

Some one-to-one

Practise with peers

The team needs a simple allocation method to learn, but the real failure is holding the line under pressure, so coaching carries more weight.

How the two dials adapt to you →

What’s really going on

You will not solve this by debating priorities forever. Pick a number — the share of your capacity that goes to platform health — before the quarter begins. Write it down. Defend it when pressure comes. A roadmap that protects the platform is not a document. It is a number you refuse to spend twice.

🔒 What you’ll build togetherUnlock by starting

A moveChoose the number first. Decide, as a pod, what share of each sprint belongs to the platform — write it down before planning begins.

A moveName the one thing you will refuse to build this week because of that number.

A moveWhen a stakeholder pushes for more features, do not debate the number in the room. Say you will discuss it as a pod and return with an answer.

A moveEach quarter, check what you actually spent against what you promised. State the gap out loud — do not call it 'we got busy.'

A moveGive platform health one clear owner who does not also own feature speed. One person cannot judge both fairly.

PractiseThe Capacity Ledger · a Pod of 5 · 30 min

What changes unlock by starting

A number you can point to instead of arguing the same fight every sprint.
Fewer moments where someone quietly skips platform work and hopes no one notices.
A record each quarter of what you promised the platform — and whether you paid it.
Less tension between the people who want speed and the people who want stability, because the terms are written down.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.