I've been thinking about Kaizen, and about why a word usually translated as "continuous improvement" feels so different from what it often becomes in practice. I much prefer its simpler meaning: change for the better.

That small shift in language changes the question we ask. It moves us from "how do we do more?" to "what would actually make this better for the people doing the work and the people receiving care?"

I'm something of an organisational nerd! I trained as a nurse, and much of my working life has sat between clinical education and organisational development. I have taught clinical skills, helped teams change how they work, and watched good ideas succeed or fail for reasons that had little to do with the idea itself.

Process and purpose

Kaizen is written 改善 in Japanese, and a useful English rendering is "change for the better". Over the years I have challenged, discussed and explored the phrase "continuous improvement". Badly deployed, it can feel like relentless activity: another audit, another initiative, another thing added to a full day. That is not a criticism of the people who use it, and it is not a rejection of W. Edwards Deming, whose work I value. His learning cycle, Plan, Do, Study, Act, is a discipline of curiosity rather than a treadmill.

Continuous improvement is a process. Change for the better is the purpose.

If we lose sight of the purpose, the process becomes the point. Improvement that exhausts people is not improvement, however many boxes it ticks.

Improvement that creates capacity

Change does not have to mean doing more. Sometimes it means making something simpler, giving people better tools, making better use of the expertise already in the room, or creating the conditions for the people closest to practice to improve it themselves.

The same thinking applies to technology, including AI. Technology multiplies whatever we point it at. The design question is what we choose to multiply.

Multiply what helps. Reduce what drains.

Engineering, clinical learning and organisational change

Good engineering and good clinical education share a habit: both start by watching how things really work. Japanese manufacturing has a long tradition of attention to detail, to the person using the tool and to the small refinements that accumulate. That heritage is part of what interests me in our developing collaboration with Nipro, a Japanese medical technology company. Throughout this article, the views about Kaizen and change are my own interpretation. They are not statements made on behalf of Nipro, and Nipro does not own or endorse HALO.

A well-designed device still has to be understood, practised and trusted by the person holding it. That is why device change is never only a product decision. If you would like to read more about that, see The Last Mile of Innovation and NHS Product-Change Readiness.

What this looks like in HALO

HALO is VeinTrain's practical system for supporting learning and organisational change in vascular access. It is built around a few beliefs:

• Meet people where they are. Practice differs between wards, shifts, departments and specialties, and learning has to reach all of them, including the nights and weekends that are easy to overlook.
• Observe before designing. We learn what is really happening before we decide what should change.
• Co-design, learn and adapt. Local teams shape the work, and the work changes as we learn.
• Measure what matters. Attendance at training is not an outcome. Meaningful measures look at confidence, competence, practice and patient experience.

Three lines sum up how I think about it:

We don't cascade training. We develop the people who lead change.

We don't reward perfection. We recognise learning.

People closest to practice already hold much of the expertise. Our job is to support them to lead, and to connect them to the development that already exists rather than creating yet another programme. You can read how this works for local champions in From evidence to practice, and how learning, competency and leadership connect in What SISPeC teaches us.

A question to take back to your team

Next time an improvement idea arrives, try asking: will this create capacity or consume it? Who closest to the work has been involved? How will we know it has made things better, and for whom?

If the answers point to change for the better, keep going. If not, simplify.

Sarah Phillips is the founder of VeinTrain and a nurse and organisational development consultant.