Expertise · Project unclear or stuck

Innovating under uncertainty

Identify the critical priorities and get an unclear or stalled project moving again, without locking in the wrong solution too early.

Talk to an expert See the approach

Project unclear or stuck

This is for you if…

The project moves forward, but the areas of uncertainty remain wide open.
Every meeting adds questions instead of reducing risk.
The specification rests on hypotheses that have not been tested yet.
Several options coexist and none stands out.
The topic has been stuck for months.

The problem

Trying to execute when you still need to learn

In early phases, the real risk is not a lack of structure: it is building a structure too early around the wrong hypotheses. Innovating under uncertainty does not mean moving at random. It means making the solution definable before executing it, by separating three zones.

What we know

An intention, a field problem, known constraints. They give a direction, not yet a solution.

What we assume

A clean enough signal, feasible miniaturisation, simple integration… Some assumptions can kill the project.

What we don't know

The open questions. They only become a problem if nobody tackles them at the right time.

Our approach

How we move forward

A progressive start: tight framing, a short evidence-driven iteration, a quick decision on what comes next.

State the intention
Clarify the problem and the ambition, without pretending to know the solution already.
Identify the critical hypotheses
Spot those that could undermine the project and that evidence can settle early.
Loop fast
Build short learning loops: one test, one measurement, one decision.
Decide and stabilise
Organise milestones around decisions, then gradually stabilise the specification.

The specification is not always the starting point. It can become the outcome of a structured exploration.

What you get

Your critical hypotheses, written down and ranked
A first test that settles the riskiest one, with its measurement
A reasoned decision, and the specification that follows from it

Our method in detail

Where do you stand? Take the "Technological uncertainty" self-assessment: 12 questions, 5 minutes, and a detailed analysis straight away.

Take the self-assessment

FAQ

Frequently asked questions

Can an innovation project start without a specification?

Yes, as long as the absence of a specification is not confused with the absence of method. The project needs a clear intention, a map of the unknowns, critical hypotheses to test and decision criteria. The specification is then built from what is learned.

What is the first step when innovating under uncertainty?

Separating what you know, what you assume and what you don't know. This reveals the critical hypotheses: those that could undermine the project's viability if they turn out to be wrong.

How do you avoid locking in the wrong solution too early?

By structuring the project around evidence rather than deliverables. Before choosing a technology or an architecture, we test the hypotheses behind that choice: performance, robustness, integration, cost, use, industrialisation.

How do you know whether an uncertainty is a priority?

It is a priority if it could undermine the project's viability and if evidence can be produced relatively early. Critical uncertainties come before secondary optimisations, even when they are less comfortable to test.

Can we start without launching a heavy or high-profile programme?

Yes. We favour progressive starts: tight framing, a short evidence-driven iteration, a quick decision on what comes next. You make real progress with a controlled level of commitment.