Your company wants innovation. As long as nothing changes.

The project has a budget. A team. A sponsor. The pilot works and the first users are interested.

Then comes the move into day-to-day operations. Sales would have a new offer to sell. IT, an integration to maintain. Support, requests to handle. The project might even take customers away from an existing offer.

Suddenly, not everyone agrees.

The company agreed to fund an experiment. It did not necessarily agree to the consequences of its success.

A priority that fits into nobody’s roadmap

For the innovation team, launching is the logical next step. For the other teams, it is a request they did not choose.

Their targets are set. So are their deadlines. Taking on the project means delaying something else, without knowing whether management will accept the delay.

A manager can believe in the product and refuse to spend time on it. They will be judged on the results already promised. If the new project succeeds, the credit might go to the innovation team.

The company approves the launch without revising the teams’ commitments. The time the project needs is already going somewhere else.

Everyone supports the project. Nobody makes room for it.

The people “resisting” are sometimes doing their jobs

This gets called resistance to change. The operational teams are supposedly too attached to their habits. Yet no decision has allowed them to change priorities.

Legal sees new risks. The manager of an existing offer sees a threat to sales. The project does not remove those responsibilities. That also explains their reservations.

Rules and approval processes protect the existing business. They are its corporate antibodies, and a new offer can run into them. The teams applying those rules then look like opponents of the project. But who decided to give this new business priority?

Without that decision, everyone keeps defending what they are paid to deliver.

From pilot to scale, the organisation is put to the test

A pilot sometimes benefits from a dedicated team, exceptional access and closely supported users. It operates alongside the usual organisation, under conditions that may not last.

Moving beyond the pilot brings the product into the company’s everyday operations. It is sold, delivered and maintained. That commits budgets and teams, beyond the technology and the volumes involved.

The pilot tests an offer. Scaling tests the organisation that will run it.

The pilot’s exceptions come to an end. Who takes over the project team’s work, and with what budget? Which activity gives up time or resources? Behind these questions are work to allocate and power to share.

“Support isn’t ready” may simply mean that nobody will take over the requests the project team handles today.

“The risk is too high” is a reminder that the person presenting the results is not always the person who will answer for an incident.

“This competes with our current offer” puts two managers up against incompatible targets.

Some objections expose an offer that is too costly or too risky. A good pilot does not justify every launch. Others bring out the cost of change, which was missing from the project until now.

A sponsor without decisions leaves priorities untouched

A sponsor can defend the project in a committee without securing the priority or budget it needs to launch.

That support becomes concrete when another project is delayed, a budget is granted or a target is revised. The company then accepts a change to its plans.

Otherwise, the project is simply added to the teams’ workload. The innovation team hears “you have our support”. The others hear “your commitments stay the same”.

The sponsor does not always have the authority to decide. Budgets and priorities may be set higher up. Their influence then depends on securing a decision at that level.

The organisation chart does not tell the whole story. A team with no formal veto can block the launch if nobody can replace it. A leader’s enthusiasm alone does not change the teams’ work schedule.

I tried to make these tensions tangible in the Innovation Protection Framework. The starting point is simple: what the launch changes for each person the project depends on. That helps explain both support and reservations.

Four possible futures. None leaves everything intact.

Growing alongside the company allows the project to build its own organisation. The company gives it autonomy that its usual activities do not have. It may later become a spin-off and attract outside investors.

Joining the existing offers changes the roadmap of the team taking over the project. The innovation team sometimes loses its autonomy. It, too, may resist the integration.

Staying small means keeping a useful activity without the growth originally announced. The company funds its operations and revises its ambitions.

Stopping the project frees up resources but closes off a possibility. The product works; its prospects no longer justify the investment. Some knowledge or technology survives it.

A fifth situation avoids the decision: the project remains officially supported, with no growth, no handover and no shutdown. It keeps a team occupied and feeds presentations, as long as it disrupts no existing priority.

The prototype has changed. The company has yet to decide to change anything.