INNOVATION

Why good ideas fail to scale

Large organisations rarely suffer from a shortage of ideas. The harder problem is creating a credible path from an interesting idea to an adopted product or business capability.

Innovation is often discussed as though it were a single activity. In reality, the capabilities required to discover an opportunity are very different from those required to scale it.

Early on, ambiguity is useful. Teams explore problems, test assumptions, talk to users and experiment quickly. Later, ambiguity becomes expensive. The initiative needs ownership, architecture, funding, integration, adoption and a clear business model.

Stage one: is the problem worth solving?

The first task is not building a solution. It is proving that a meaningful problem exists.

Who experiences it? How is it handled today? What is the operational or commercial consequence? Is the pain significant enough for users to change behaviour?

At this stage, learning matters more than financial precision. A small experiment can be more valuable than a polished business case built on weak assumptions.

Stage two: does the solution actually work?

A proof of concept should reduce uncertainty. It tests whether a proposed solution can solve the problem under realistic conditions and which assumptions still need validation.

This is where technology teams, operational experts and users need to work closely together. A technically successful pilot that does not fit the process is not a successful innovation.

Stage three: can it become a product?

The move from PoC to MVP is one of the most difficult transitions.

Suddenly, questions that could be postponed during experimentation become unavoidable: Who owns the product? Which systems must it integrate with? What is the minimum reliable experience? How will users access it? Who pays to build and run it? What business value should it generate?

This is also the point where innovation teams need to become comfortable with much more rigorous economics. Cost, revenue, recurring savings, ROI and adoption are not constraints on innovation; they are what allow a good idea to survive.

Stage four: adoption is part of the product

Even a strong solution can fail if the organisation treats go-live as the finish line.

Users need to understand why the new way is better. Processes may need to change. Commercial teams may need a proposition they can explain. Operations may need new responsibilities. Management needs evidence that the solution is creating value.

Scaling therefore requires product management, communication and change capabilities that are often absent from the original innovation team.

Innovation needs a bridge between exploration and execution

The organisations that consistently innovate well create an explicit bridge between these two worlds.

They protect early experimentation from excessive bureaucracy, but progressively introduce stronger ownership, architecture, governance and business metrics as an initiative matures. They know when to stop projects that are not learning fast enough, and when to mobilise the broader organisation behind projects that are.

That is ultimately how I think about innovation: not as an ideas function, but as a disciplined way to move from uncertainty toward scalable business value.