What innovation-specific capacity really means in practice

 

Change doesn’t land simply because people have been “trained”. Training matters, but innovation-specific capacity is about the confidence, ownership, practical understanding, and support people need to use a new system or way of working in real conditions. In this two-part blog, we use the R=MC² change readiness framework to look at what helps change move from implementation to adoption, embedding, and continuous improvement.

Part 1 Introduction

In the first two parts of this readiness series, we looked at motivation and general capacity.

Motivation asks whether people understand the need for change and can see enough value in moving towards it. General capacity asks whether there is enough space, attention and organisational stretch available for change to land well.

This third part looks at the final part of the R=MC² readiness equation: innovation-specific capacity.

In simple terms, this is the practical ability to adopt a specific change. It is the confidence, knowledge, support and shared understanding people need to use a new system, process or way of working well.

It is often mistaken for training.

Training matters, of course. But training is only one part of the story. Innovation-specific capacity is also built through consultation, discovery, co-design, testing, ownership and the way people are supported to make sense of change before it reaches implementation.

In the R=MC² change readiness framework, innovation-specific capacity is the final part of the readiness equation.

Motivation matters. General capacity matters. But even when people understand the value of a change, and even when some space has been created for it, there is still another question to ask:

Can this team realistically learn, adopt, practise and sustain this specific change?

That is the work of innovation-specific capacity.

It is easy to reduce this to training. Has the team been shown the system? Have users attended the sessions? Have the guides been shared? Has the handover taken place?

All of that matters, of course. But in practice, innovation-specific capacity is much wider than training. It is about whether people have enough practical understanding, confidence, support, ownership and contextual knowledge to make the change part of their day-to-day work.

Not just once.

Not just during implementation.

But after the launch, after the consultancy phase, and after the first burst of attention has moved on.

Training is not the same as capacity

Most digital projects include some form of training. That is important, but it is rarely enough on its own.

A team can be trained and still feel unsure. They can attend a session and still not know how the new process fits with real-life exceptions. They can understand the system in principle, but struggle when a customer query, internal handover, reporting need or edge case does not follow the neat route shown in the demo.

This does not mean the training has failed. It means adoption is more complex than instruction.

Innovation-specific capacity grows when people have repeated opportunities to connect the new tool, process or system to the reality of their work. It grows when they can ask questions without feeling exposed. It grows when they understand not only which buttons to press, but why the new way of working has been designed as it has.

That distinction matters.

Because adoption is not the moment someone is shown what to do. Adoption begins when they can do it with enough confidence, context and judgement to keep going.

What this looks like across the CA project arc

We see innovation-specific capacity as something that develops across the full arc of a project, from initial consultation through to adoption and embedding.

In the earliest conversations, we are not only listening for what the client wants to build. We are listening for how ready the organisation is to work differently.

• Who understands the current process?
• Who holds the informal knowledge?
• Where are the workarounds?
• Where does confidence already exist?
• Where might the new solution ask people to learn a different habit, not just use a different tool?

These early signals shape the work that follows.

During discovery and mapping, innovation-specific capacity begins to grow because people start to see the system they are part of. The work becomes visible. Assumptions are tested. Gaps are named. Decisions become clearer. This matters because capability is not only technical. It is also relational and operational.

People need to understand the shape of the change before they can confidently adopt it.

During design and configuration, innovation-specific capacity becomes even more practical. This is where new workflows, automations, data structures, permissions, templates, handovers and reporting routes begin to take shape. At this stage, the question is not simply: can this be built?

• The better question is: can this be lived with?
• Will the process make sense to the people using it?
• Will the system support the way decisions need to be made?
• Will the team know what to do when something does not follow the expected route?
• Will the design reduce friction, or simply move it somewhere less visible?

These questions help protect adoption before the change goes live.

Adoption needs ownership, not dependency

A good implementation should not create long-term dependency on the consultants who helped design it.

That does not mean leaving clients to fend for themselves. It means building confidence and ownership throughout the work, so that by the time adoption begins, the organisation is not simply receiving a finished solution. It has been part of shaping it.

This is why co-design matters.

When people are involved in mapping the current state, testing the future state, naming the exceptions, reviewing the language, and sense-checking how the work will flow, they are not just contributing information. They are building the capacity to understand and own the change.

That ownership is often what separates a system that is technically live from a change that is genuinely embedded.

Without it, teams can become overly reliant on a small number of people. Knowledge sits in individuals rather than in the process. Questions keep returning to the project team. Confidence drops when something unexpected happens.

With stronger innovation-specific capacity, the team has more than access to a system. It has a clearer sense of how to work with it, improve it and keep it useful over time.

Final thought

This is why innovation-specific capacity needs to be considered early, not only when training is being planned.

By the time a system is ready to launch, many of the conditions for adoption have already been shaped. People may have been involved, or they may have been kept at a distance. Informal knowledge may have been surfaced, or it may still sit with a few individuals. Future workflows may have been tested against real scenarios, or they may only have been considered in theory.

These choices matter.

When people are part of shaping the change, they are not just contributing information. They are building understanding, confidence and ownership. That ownership is often what separates a system that is technically live from a change that is genuinely adopted.

Up next

In part two, we will look at how innovation-specific capacity shows up in practice, what warning signs to look for, and how Creative Analysis supports adoption, embedding and continuous improvement through engagement, bespoke training and academy.

If you’re about to start a change programme, or you’re already in one, and you want a simple way to understand what’s shaping innovation-specific capacity in real time, give us a call or use our contact form to book a free consultation.

Blog Contributors: Paula Atherill, Director at Creative Analysis, brings over a decade of hands-on digital transformation experience. Her calm, structured approach helps change land in ways that are practical and sustainable. Sue Mills, Training Director, brings deep expertise in learning design and facilitation, supporting teams to build confidence, capability, and shared ways of working through change. Kristy Lake, Design Ops, brings strategic clarity and an evidence-based approach to readiness. Drawing on the R=MC² formula developed by the Wandersman Center, she helps organisations understand where capacity, motivation, and context align. All three are passionate about exploring where thoughtful design can unlock progress.