How do I build a roadmap that grows the product without wrecking the platform?

You say you want a roadmap that supports the product while keeping the platform healthy. That sounds reasonable. It is also a way to avoid choosing. Here is what is really happening. Every feature request pulls time from the platform. Every hour spent on the platform is an hour the product does not grow. You know this. You have known it for months. What you lack is not knowledge — it is the nerve to put a number on it and say no to someone's face. This is not about finding the perfect balance. There is no perfect balance, only a decision you make and defend. The work in front of you is to decide, write it down, and hold the line when people push.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

Some to learn

1:1 with AureliusWith others (a Pod)

Mostly you & the coach

A little with peers

The trade-offs are already known to you; what moves the needle is deciding on a number, writing it down, and defending it — so guidance leads, with just enough structure to make the decision concrete.

How the two dials adapt to you →

What’s really going on

You cannot serve two masters by accident. Choose, in writing, how much time goes to new features and how much to platform health — then defend that split in every planning meeting. A roadmap without a stated ratio is not a roadmap. It is a wish.

🔒 What you’ll build togetherUnlock by starting

A moveWrite down the split now: what percent of this quarter goes to features, what percent to platform work. A number, not a feeling.

A moveName the platform work in product terms — what breaks, when, and who it costs — not 'technical debt.'

A movePut the split in front of whoever can override it. Make them say yes or no in writing.

A moveReview the ratio every month. Change it on purpose, not by drift.

A moveWhen someone asks for a feature that breaks the ratio, ask them what they will cut to pay for it.

What changes unlock by starting

A written roadmap with a stated ratio between feature work and platform work.
A record of who agreed to that ratio, so blame does not land only on you.
Fewer silent trade-offs — every cut becomes a decision, not an accident.
A platform that does not quietly rot while everyone celebrates new features.

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.