Why strong PMs are leaving “feature teams”
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.
Feature teams are where many PMs start, and where a lot of valuable work still happens.
They’re close to users, tightly scoped, and optimised for delivery. When they work well, they move quickly and ship tangible improvements.
So when strong PMs leave feature teams, it’s rarely because the work is beneath them.
It’s usually because the leverage changes.
Feature teams tend to optimise for local outcomes:
Shipping features
Improving a specific flow
Moving a narrow set of metrics
At a certain point, strong PMs start to notice that the biggest constraints on impact sit outside the feature boundary:
Platform limitations
Organisational dependencies
Inconsistent foundations across teams
No matter how well the feature performs, the ceiling remains.
Leaving feature teams is often about seeking work where:
Decisions have longer time horizons
Small changes unlock value for multiple teams
Impact compounds rather than resets each quarter
This shift can feel counterintuitive. Platform, enablement, or system-level work is usually less visible. Success is indirect. Progress can look slow.
But for PMs optimising for leverage, that trade-off is worth it.
It’s not an indictment of feature teams. They’re essential.
It’s a recognition that as judgement matures, the problems worth solving often move upstream, closer to the system itself.
Feature teams optimise locally. Platforms optimise structurally.
Sometimes the biggest impact comes from stepping back.