Most product management content focuses on startups and scale-ups. The advice is about finding product-market fit, shipping fast, and learning from early users. But what happens when the product already has product-market fit, millions of users, and a revenue engine that works? What does product management look like when the organisation is mature?

At PR_D_CT DAY 2025 in Ghent, Pieter Vanhove from Microsoft brought a perspective that is rarely heard at product conferences in Belgium: what it means to manage product at one of the largest technology companies in the world. His talk explored the unique challenges of product management in a mature organisation, where the stakes of every decision are amplified by the sheer scale of the user base and the complexity of the technical estate.

For an audience accustomed to hearing about scrappy startups and lean experimentation, Pieter's talk was a necessary counterweight. It showed that product management at maturity is not less demanding than product management at a startup. It is demanding in fundamentally different ways.

slideshow

Original Presentation Slides

Download the slides from this talk as presented at the gathering.

The Unique Challenges of the Maturity Stage

Pieter begins by defining what maturity means in a product context. It is not simply about age or revenue. A mature product has an established user base with deeply embedded workflows, a complex technical architecture with years of accumulated decisions, and a business model where incremental improvements generate more predictable revenue than bold bets.

At Microsoft, this maturity creates a specific set of challenges that product managers must navigate daily. Every change affects millions of users. Every deprecation triggers enterprise support tickets. Every new feature must integrate with an ecosystem of products, APIs, and partner solutions that has been built over decades.

“In a startup, your biggest risk is building something nobody wants. In a mature product, your biggest risk is breaking something that millions of people depend on every day.”

- Pieter Vanhove

Pieter argues that this asymmetry of risk fundamentally changes how product managers must think. In a startup, speed and learning are paramount. In a mature organisation, reliability and backward compatibility carry equal weight alongside innovation. The product manager's job is not to choose between these priorities but to find ways to pursue both simultaneously.

Driving Innovation Within Constraints

The central question Pieter addresses is one that many product managers in established companies wrestle with: how do you innovate when the constraints of the existing product, the existing customers, and the existing architecture are so heavy? His answer is counterintuitive: the constraints are not obstacles to innovation. They are the raw material of innovation.

Constraint as creative fuel: the requirement to maintain backward compatibility forces product teams to find more elegant solutions rather than simply starting from scratch

Enterprise empathy: understanding the workflows that enterprises have built on top of your platform creates innovation opportunities that greenfield competitors cannot see

Security as a feature differentiator: at Microsoft scale, security and compliance are not tax. They are competitive advantages that drive purchasing decisions

Platform thinking: mature products innovate most effectively by enabling others to build on top of them rather than trying to build everything internally

infoThe platform leverage effect

Pieter shares that at Microsoft, the most impactful product decisions are often not about building new features but about exposing new capabilities through APIs and integrations. When your platform serves millions of users, enabling a thousand developers to build on it creates more value than any single feature your team could ship.

He illustrates this with examples from his own work, showing how product decisions that appeared conservative from the outside were actually bold strategic moves when viewed through the lens of platform impact and ecosystem value.

Navigating Stakeholder Complexity at Scale

One dimension of mature product management that Pieter explores in depth is stakeholder complexity. In a startup, the product manager might need buy-in from a founder and a tech lead. At Microsoft, a significant product decision might require alignment across multiple product groups, legal review across jurisdictions, enterprise customer advisory boards, partner ecosystem considerations, and regulatory compliance teams.

The security-first prioritisation framework

Pieter describes a situation where his team needed to balance a feature that customers were demanding against a security improvement that no customer had asked for but that the security team had identified as critical. Rather than framing this as a trade-off, they integrated the security improvement into the feature itself, shipping both as a single release. The lesson: at maturity, the best product decisions are the ones that satisfy multiple stakeholders simultaneously rather than forcing a zero-sum choice.

He argues that the ability to navigate this stakeholder complexity is what separates effective product managers in mature organisations from those who struggle. It is not about politics or compromise. It is about finding the solution geometry that serves the most important needs of the most important stakeholders without creating unacceptable trade-offs for anyone else.

lightbulbInfluence without authority at scale

The PM mantra of influence without authority takes on a different meaning in a mature organisation. At a startup you are influencing a dozen people you see every day. At Microsoft scale you are influencing teams across geographies and time zones who may never meet you in person. Written communication, clear decision frameworks, and institutional credibility become your primary tools.

What Every Product Manager Can Learn from Maturity

Pieter closes by connecting the lessons of mature product management back to the broader audience. He argues that even product managers at startups and scale-ups can benefit from thinking about maturity challenges early, because the habits they build now will determine how effectively they can operate when their products reach that stage.

check_circleBuild backward compatibility thinking into your architecture decisions from day one, because it is cheaper to design for it than to retrofit it

check_circleStart treating security as a product feature rather than a technical requirement. Customers will eventually demand it

check_circleDevelop your written communication skills: as organisations grow, the ability to persuade through documents becomes more valuable than the ability to persuade through conversation

check_circleThink about platform potential early. The most valuable products are the ones that enable others to create value on top of them

The talk strikes a chord with the Belgian product community, where many companies are transitioning from growth-stage thinking to maturity-stage challenges. Pieter's perspective from Microsoft provides a clear picture of what that future looks like and how to prepare for it.

Product Management in the Maturity Stage

Original Presentation Slides

The Unique Challenges of the Maturity Stage

Driving Innovation Within Constraints

infoThe platform leverage effect

Navigating Stakeholder Complexity at Scale

The security-first prioritisation framework

lightbulbInfluence without authority at scale

What Every Product Manager Can Learn from Maturity

This article is for Consortium members

Key Takeaways

Related Editorials

Product Management in the Scaling Stage

Security-by-Design: Making Security a Product Feature