Prefer listening over reading? 🎧 Listen (AI-Generated Audio Version)

When Growth Stops, Platforms Have to Earn Their Place

Platform teams were built for growth, ship faster and scale further. However, when growth stops, the question “How fast can we ship?” changes to “What does this cost us and who would notice if we turned it off?”

Most product thinking still assumes the first question. Roadmaps, team structures and the way we pitch platform investment all come from a time when the business was expanding and speed was the scarce resource. In companies that are flat or shrinking, that assumption quietly stops being true.

When Nobody Is Buying Speed

In a growth company, the platform team’s pitch is simple. Teams can build faster, onboard faster and scale without rebuilding the foundations. Everyone is short of time, so speed sells itself.

In a company that is not growing, nobody is buying speed. The people reviewing your budget are asking different questions, e.g. “What does this cost?”, “What breaks if we switch it off?”, “Which of these platforms are we paying for twice?”

I have found that the same platform can look essential in the first setting and like an expensive habit in the second. Nothing about the technology changed. The only thing that changed was what the organisation values.

Treat Adoption as Retention

What I have seen is that in companies that are not in growth phase, it helps to treat the platforms as products that have customers and can lose them. In that case, adoption is retention. If teams can route around you, they will, and in a company under cost pressure they will do it faster, because they are being asked to justify every dependency they carry.

This can be a useful discipline because it removes the safety net of a mandate. If teams use your platform only because they are required to, high adoption tells you nothing. If they would keep using it when they are free to leave, because it makes their hardest workflow easier, that is real evidence of its value.

Pick One Painful Workflow

In a growth phase, a comprehensive platform roadmap can be a sensible bet. Capabilities that nobody needs today may be needed next year and there is budget to cover the gap.

Without growth, that same roadmap will probably die in the budget review. A better approach is to pick one painful workflow and make it ten times better. For example, if provisioning an environment takes days and involves three approvals, fixing that one journey is easier to defend than a plan to modernise everything.

In flat or shrinking companies, one visible win gives you credibility, while a broad roadmap gives the reviewer a long list of things to cut.

Price the Impact

“Developer satisfaction is up” will not survive the CFO and while it may well be true, it is not a unit the business budgets in.

The platform’s value needs to be expressed in hours saved and dollars avoided. For example, capture how many teams use it, how much time it saves each of them and what would it cost to replace. That can be a conversation a finance leader can take part in. It will also force an honest look at whether the value is real, which is a benefit in itself.

Count What You Retire

Throughout my consulting career I have seen that most organisations run more platforms than they need and no one is paid to kill them. Every team that built something useful during the growth years still maintains it and each of those things has a running cost, a security surface, an on-call rota and so on.

If we only count what we launch, we reward addition. However, a platform team that wants to be taken seriously in a flat year should also report what it has retired, merged or simplified, with the cost that came out. It’s worth noting that retirement needs an owner and a target, otherwise it will never happen.

The PM’s Job Changes

In a growth company, the product manager’s central question is “what should we build next?”. When growth slows, the job changes and the question becomes “what should we stop building?”.

That is usually harder, because stopping has no launch and no celebration, and someone usually depends on the thing being stopped. It requires evidence about who uses what, honest conversations with those users and the judgement to say no.

Every platform capability that nobody uses still makes the platform harder to understand, harder to support and slower to change. In a growth phase the tax is easy to ignore, but in a flat year it shows up in every conversation about cost.

Conclusion

Growth forgives a lot, such as overlapping platforms, features that never found users and investments justified by a future that arrived late or not at all. But when growth slows, the forgiveness ends.

For platform teams, it is a chance to be judged on something harder and more honest than speed. The teams that can show what their platforms cost, what they save and what would break without them will be the ones still standing.

Growth lets you add. A flat year asks you to prove what deserves to stay.