Building a Product Organisation
Turning ad-hoc delivery into a product discipline.
Summary
Establishing clear ownership, discovery and prioritisation so that product, design and engineering could work as one system rather than three handoffs.
Context
As the product surface grew, decisions were being made quickly but not always deliberately. Ownership was informal, prioritisation lived in people’s heads, and collaboration between product, design and development depended on who happened to be talking.
The challenge
Introduce enough structure to make decisions clear and repeatable — without turning a fast, capable team into a slow, ceremony-heavy one.
My role
- Shaping the product operating model and ways of working
- Defining ownership boundaries and decision rights
- Designing discovery and prioritisation processes
- Coaching the collaboration between Product, Design and Development
Approach
Make ownership explicit
Established clear product ownership so every meaningful area had someone accountable for its direction, not just its delivery.
Build a discovery habit
Introduced lightweight discovery so problems were understood and validated before engineering effort was committed — separating the requested feature from the underlying need.
Prioritise in the open
Replaced implicit prioritisation with a shared, visible approach weighing impact, effort, risk and strategic alignment, so trade-offs could be discussed rather than assumed.
Structure the portfolio
Introduced structured product portfolio management so the whole body of work could be seen, compared and sequenced as a system.
Key decisions
Clarity over ceremony
Chose the lightest process that removed the ambiguity — deliberately avoiding heavyweight frameworks that would have slowed the team more than they helped.
Roles, not gates
Framed ownership as accountability for outcomes rather than approval gates, keeping momentum while adding direction.
Outcome
- →A shared operating model where product ownership, discovery and prioritisation are explicit rather than tribal.
- →Tighter collaboration between Product, Design and Development, with fewer decisions relitigated after the fact.
- →A portfolio that can be reasoned about as a whole, not just a list of in-flight tickets.
What I learned
Organisational structure is a product in its own right. The goal is never process for its own sake — it is the smallest amount of structure that reliably produces clarity, and it has to be maintained like anything else you ship.
Next case study — 02
SIMInsights
Want to talk through a problem like this? Get in touch