The 15-minute innovation audit any product owner can run this week

Your innovation pipeline is full. Your roadmap looks impressive. Your stakeholders are excited.

So why does nothing actually ship?

I have run this same audit with product owners at Disney, American Express, and NatWest. Every time, the same pattern emerges. The problem is not the ideas. It is not the budget. It is the invisible friction between decision and delivery.

Here is a 15-minute diagnostic that will show you exactly where your innovation efforts are getting stuck.

The three-layer audit

Innovation fails at three predictable points. Most organisations obsess over layer one and ignore layers two and three entirely.

Layer 1: The idea pipeline

Pull up your current innovation backlog. Count how many projects have been "in progress" for more than six months. Now count how many have shipped meaningful features to real users in the last quarter.

If the ratio is worse than 3:1, you have an execution problem, not an idea problem. Stop adding more initiatives to the pile.

I worked with one financial services team that had 47 "innovation projects" running simultaneously. Exactly two had reached customers. The rest were trapped in endless refinement loops.

Layer 2: The decision architecture

Map your approval process for a typical innovation project. Write down every person who needs to say yes before you can test something with real users.

Count the handoffs. If it is more than four, you have built innovation quicksand.

At ING, we discovered that getting approval for a simple prototype required 11 different stakeholder sign-offs. The most innovative ideas died waiting for the eleventh person to respond to email.

The fix was creating innovation "safe zones" where small bets (under €10k, under four weeks) could run without climbing the approval ladder.

Layer 3: The fear tax

This is where most audits stop. Big mistake.

Ask your team this question: "What happens to someone who champions an innovation that fails?"

If the answer involves performance reviews, budget cuts, or "learning experiences," you have found your real innovation blocker.

Fear creates conservative behaviour. Conservative behaviour kills innovation. The maths is that simple.

Three fixes you can implement this week

1. The two-week rule

Any innovation project that cannot show user feedback within two weeks gets paused. Not cancelled. Paused until someone can define a smaller first step.

This forces teams to think in testable increments rather than grand unveilings. It surfaces the real friction points fast.

One product owner I worked with applied this rule to a "revolutionary" checkout flow that had been in development for eight months. Within two weeks, they had a clickable prototype testing three core assumptions. They learned more in that fortnight than in the previous eight months of planning.

2. The innovation budget firewall

Ring-fence 20% of your development capacity for projects that might fail. Make it untouchable by quarterly planning cycles or urgent feature requests.

The key word is "might." If you know it will work, it is not innovation. It is optimisation.

Track learning velocity, not delivery velocity. Celebrate fast failures as much as slow successes.

3. The failure CV

Start a shared document where team members log their innovation failures and what they learned. Make it visible. Reference it in team meetings.

This does two things. It normalises failure as part of the process. And it prevents teams from making the same mistakes twice.

At NASA, they call this a "lessons learned database." It is not buried in some corporate repository. It sits on the desktop of every project manager.

What you will discover

Running this audit will reveal that your innovation problem is not what you think it is.

It is rarely about having better ideas. It is about creating conditions where good ideas can survive contact with your organisation.

Most product owners focus on the front end of innovation. Better brainstorms. Cleaner roadmaps. Shinier presentations.

The real work happens in the messy middle. Where decisions get made. Where teams choose safe over significant. Where good intentions meet organisational reality.

Fix the system, not the symptoms.

Innovation dies in the gap between what we decide to do and what we actually ship.