Scaling product is more about unlearning than adding
I lead the strategy and delivery of products and systems that solve real problems, support commercial goals and scale across teams and markets. My work spans platform foundations, user-facing experiences, commercial tools and developer products, and I adapt my approach to the needs of each domain. I focus on maturing complex systems, improving the experience for both users and developers and strengthening the foundations that make products reliable, scalable and easy to build on. I care about clarity, good judgement and creating the processes and environments that help teams deliver consistent, long-term impact. My experience covers early-stage, scale-up and enterprise product environments, combining hands-on delivery with team leadership and award-winning work recognised across several innovation competitions.
When teams think about scaling, the instinct is to add.
More process. More roles. More tools. More frameworks.
Some of that is necessary.
But in my experience, the hardest part of scaling product isn't adding. It's unlearning.
Practices that worked at small scale become liabilities at larger scale:
Informal decision-making stops scaling
Heroic individual effort creates hidden risk
Speed without structure turns into rework
I worked with a team that had scaled from 5 to 40 people. They were proud of their "no meetings" culture. Decisions happened fast in Slack. Everyone just figured it out.
At 5 people, that worked. At 40, it was chaos. Decisions were made in threads nobody saw. Context was lost. Teams duplicated work because nobody knew what others were doing.
The fix wasn't adding meetings for the sake of it. It was recognising that "no meetings" had become a liability, not an asset. They needed to unlearn the habit that got them here.
Unlearning is uncomfortable because it challenges identity.
Teams are proud of what got them here. "We move fast." "We don't do bureaucracy." "We trust people to figure it out."
Letting go of those habits can feel like admitting they were wrong, even when they were simply right for a different phase.
Another reason unlearning is hard is that the costs are delayed.
You don't feel the impact immediately. Things still work, until they don't. By the time friction is visible, behaviours are already embedded.
Scaling product well often requires:
Making implicit decisions explicit
Replacing individual judgement with shared principles
Trading speed in one area for leverage across many
Accepting that what felt like freedom now feels like chaos
None of that looks like progress in the short term.
But it creates room for growth that doesn't collapse under its own weight.
For me, the biggest scaling shifts came not from adding new mechanisms, but from letting go of habits that no longer served the system.
Growth isn't just building new muscle. It's shedding what no longer fits.