The fog of innovation

The question behind the idea

People often ask where an idea came from. That story can matter, but it is not usually the part that decides whether the idea survives.

The more useful question is what happens after the idea appears. How does something small survive the fog between a clinical friction point and a tested change in practice?

That question is where many useful improvements begin. Not with a grand invention, but with a repeated friction point that refuses to disappear.

In my own work, that question sat around emergency airway preparation. The issue was not simply to create something new. It was whether preparation could be designed so there was less searching, less avoidable variation and less cognitive load at the point where delay and small errors can carry serious consequence.

When the idea is still fragile

In the early phase, ideas are fragile. They are vulnerable to influence before they have been tested against the conditions they are meant to improve.

That influence can be useful. Feedback, constraint and challenge can make an idea stronger. But the same period can also dilute the idea, distort it, or stop it before its value has been understood.

At that stage, the idea is not yet a product, system, pathway or recognised solution. It is an early signal that something in the work needs closer attention.

That is the fog of innovation. You can see enough to move, but not enough to be certain. The path changes as the idea meets users, constraints, budgets, prototypes, governance, scepticism and real-world use.

The danger is that fragile ideas are judged too early. They are asked to prove themselves before there is a safe route to test, shape and learn from them.

Uncertainty has to be managed

Uncertainty is not proof that an idea is weak. It is usually a sign that the idea is still being tested by reality.

Useful innovation usually has to answer several questions at once:

• Is the problem real or just personally irritating?
• Does the idea reduce work or simply move the burden elsewhere?
• Can it be tested safely without over-claiming its value?
• Who needs to be involved before the idea is allowed to grow?

The answer is not to pretend the uncertainty has gone. The answer is to make the route visible enough to keep learning safely.

The hidden no

In organisations, new ideas are not always rejected directly. More often, they are absorbed into delay.

“Yes, but…” can sound constructive. Sometimes it is. But it can also be a quiet no: a way of keeping an idea in permanent discussion without ever creating the conditions to test it.

A healthier design culture does not approve every idea. That would be reckless. But it does make the route visible. It shows what evidence is needed, who can authorise a test, how risk will be controlled, and what would make the idea worth stopping.

Without that route, useful friction points remain trapped inside conversations.

Friction points are design data

Every team has friction points. Some are obvious: missing equipment, unclear ownership, repeated work-arounds. Others are quieter: variation in layout, avoidable decisions, uncertainty about who is doing what, or equipment that is present but not immediately usable.

Not every friction point becomes a major innovation. Most should not. But repeated friction is data. It tells you where the system is asking people to compensate.

The real opportunity is not always to invent something new. Sometimes it is to see the existing work clearly enough to remove avoidable load, unnecessary variation and small points of friction that make the work harder than it needs to be.

Feedback makes the idea harder to fool

Early feedback can be uncomfortable because it shows the distance between the idea as you imagined it and the work as other people experience it.

That distance matters. It shows where the idea is still carrying assumptions, where it adds load, and where it may not yet fit the conditions it is meant to improve.

Useful feedback should not simply protect the original idea. It should make the idea harder to fool. It should expose what needs to change before the design is trusted any further.

That is why collaborative design is not the easy version of innovation. Done properly, it is more demanding. It asks the idea to survive contact with practice, not just approval in a room.

From interest to use

Early support for an idea can be misleading. People may recognise the problem, agree with the direction, and still not be ready to change how the work is done.

That is where constraint becomes useful. Limited time, money, attention and trust force the question that matters: what is the smallest version of this idea that can be tested honestly?

Not the polished version. Not the version that wins the meeting. The version that shows whether the idea can survive contact with real users, real conditions and real consequences.

Broad ideas are easy to admire and hard to implement. Focused ideas are easier to test, easier to improve, and easier to stop if they do not make the work better.

Purpose still needs a route

A clear purpose helps. It gives people a reason to care and keeps the work attached to something more important than novelty.

But a strong reason is not enough. An idea still has to move through evidence, relationships, testing, iteration, governance, education and trust.

This is where many ideas stall. People may understand the “why” and still have no clear way to test the idea, approve it, support it, or make it part of normal work.

The two resources below are included because they speak to different parts of that problem: why people care, and why early support does not automatically become routine use.

Protect the idea without hiding it

Early ideas need contact with the real world. They need feedback, challenge and exposure to the people who understand the work.

But exposure without any protection is risky. An idea can be diluted, misused, copied badly, or pulled away from the problem it was trying to solve.

The balance is to protect enough to keep the idea viable, but not so much that it never learns from the world it is meant to improve.