Clarifying platform ownership during rapid growth

Context

The company had grown quickly. What started as a focused product team had expanded into several overlapping streams, each with its own priorities and stakeholders.

The platform underpinning all of it had no clear owner. Everyone depended on it. No one was responsible for it.

The problem

The main issues identified were:

Platform decisions were made reactively, driven by whichever team had the most urgent need
Ownership was assumed rather than assigned, leading to gaps and duplication
Technical debt was accumulating faster than it could be managed
New initiatives were slowed by unclear dependencies and unstated constraints

Progress was being made in individual streams, but the organisation was losing coherence.

Everyone depended on the platform. That was exactly why informal ownership was no longer enough.

My contribution

My role included:

Mapping the platform's actual dependencies and decision points across teams
Facilitating a process to define and agree platform ownership
Working with leadership to establish a lightweight governance model
Acting as interim product lead for the platform while a permanent structure was put in place
Supporting the transition to the new model without disrupting ongoing delivery

Outcome

The work resulted in:

A named platform owner with a clear mandate
Documented ownership boundaries that teams could reference
A prioritisation process that accounted for platform health alongside feature delivery
Reduced back-and-forth between teams on cross-cutting decisions

Responsibility only became real when authority, boundaries, and trade-offs could be named in the same sentence.

Reflection

The technical problems were largely understood. What was missing was a shared agreement on who had the authority and responsibility to act on them.

That kind of clarity is harder to establish than it sounds. It requires people to accept constraints as well as authority, and that often takes time and careful facilitation.