Innovation isn't about having brilliant ideas. It's about having the discipline to question the way things are done. Most teams operate on inherited assumptions — "that's how it's always worked" — without ever testing whether those assumptions still hold. Real innovation starts with a simple question: "Why do we do it this way?"
The best innovations I've been part of weren't moonshots. They were moments where someone said "what if we just... didn't do that?" Removing a step from an onboarding flow. Replacing a weekly meeting with an async update. Using AI to handle what three people were doing manually. Small changes that compound into transformative results.
"Innovation is less about adding something new and more about removing something old."
Innovation requires a safe environment for experimentation. Teams that punish failed experiments stop trying. Teams that celebrate learning — even from failures — keep finding breakthroughs. The product manager's job is to create that safety while maintaining accountability for outcomes.
There's a tension between innovation and reliability, and that tension is healthy. You don't innovate on your deployment pipeline during a critical release. You don't experiment with payment flows without guardrails. The art is knowing where to be creative and where to be conservative — and having the structure to do both deliberately.
In Practice
- — Every quarter, audit one "sacred" process — the thing nobody questions — and test if it still earns its place.
- — Rapid prototyping sessions where "what if?" ideas get built in hours, not debated in meetings.
- — Failed experiments get documented and shared — the learning is the deliverable, not the success.