The question behind the idea

I am often asked how I came up with an idea that later became useful to clinical teams. The origin story matters, but it is not the most important part.

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. It eventually led into the development of SCRAM™. But this article is not about a product. It is about the space every useful idea has to move through before it becomes reliable enough to matter.

Innovation is rarely a clean line

The early phase of an idea is unstable. It is not yet a product, a system, a pathway or a recognised solution. It is a piece of discomfort asking to be taken seriously.

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 often judged too early. They are asked to prove themselves before the system has created the conditions in which they can mature.

Uncertainty has to be managed

Uncertainty is not a sign that the idea is weak. It is a sign that the idea is still being tested against 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 keep testing the design against the work.

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.

Feedback makes the idea harder to fool

Early feedback can be uncomfortable because it exposes the gap between the idea in your head and the work as others experience it.

That gap is useful. It is where the design becomes more honest.

A weak idea avoids feedback because it wants to stay intact. A stronger idea uses feedback to become more useful.

Collaborative design is not a softer version of innovation. It is a harder one. It forces the idea to survive contact with practice.

Constraints force focus

Limited time, budget and expertise can stop an idea. They can also sharpen it.

Constraints force a decision: what is the smallest useful version of the idea that can be tested honestly? Not the polished final version. Not the version that impresses a room. The version that teaches you something.

That matters because 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 work.

Purpose helps, but it is not enough

A clear purpose matters. It helps people understand why an idea is worth attention. It keeps the work attached to something more important than novelty.

But purpose alone does not get an idea adopted. It still needs evidence, relationships, testing, iteration, governance, education and trust.

This is where many ideas fail. They have a strong “why”, but no route through the system.

Protect the idea without hiding it

Intellectual property is not the exciting part of innovation, but ignoring it is naïve.

Ideas need exposure to become useful. They also need enough protection to prevent avoidable loss, confusion or misuse. That balance depends on the idea, the partners, the market and the stage of development.

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