Who owns the change that adoption requires?

An innovation can have a clear clinical purpose and still be difficult to introduce into everyday practice. Someone has to request it, interpret its output, communicate the result and take responsibility for what happens next. Each step belongs to a working service with existing pressures and priorities.

Consider a hypothetical diagnostic solution that helps inform a treatment decision. Its introduction might change the sequence of appointments, require additional review or create a new conversation between a laboratory and a clinical team. A compelling value proposition does not assign responsibility for those activities.

One useful starting point is to follow a single case through the proposed pathway. At each handover, ask who acts, what information they need and what would prevent the next step from happening. Include the people who will do the work. Their practical concerns can reveal requirements that remain invisible in a launch plan.

The aim is to distinguish the capabilities already available from those that need to be created. Training may address one gap. A revised escalation process, a change in scheduling or a clear agreement between services may address another. Some constraints may require a different initial use case.

Ownership also needs to continue after introduction. A named person should be able to identify where the pathway stalls and bring the relevant teams together to resolve it. Otherwise, each function may complete its own task while the overall process remains unreliable.

For leaders, a useful adoption review therefore goes beyond interest in the technology. It asks whether the organization can describe the change in practice, identify who owns it and explain how the change will be supported.

A question to take into the next review: Which new activity does adoption depend on, and who has agreed to own it?