Most improvement programmes fail not because people lack commitment or capability, but because nobody designed the programme itself. An organisation selects a methodology — lean, six sigma, agile, TPM — trains people in its tools, launches activities, measures early wins, and then watches momentum decay.
he programme runs across six sessions over seven weeks, with pre-work that grounds participants in the fundamentals of different improvement methodologies before the first session begins. Each session is forty-five minutes of facilitated discussion built on online content that participants review at their own pace during the week. The format is deliberately compact — theory and practical application delivered in small, manageable portions rather than intensive multi-day workshops that produce insight overload and implementation paralysis. Sessions are recorded and accessible on the learning management system alongside key point charts and workbooks, so that learning continues between sessions rather than waiting for the next one.
The six sessions follow a deliberate sequence. You begin with the strategic question — selecting the right methodology for your context and creating a deployment strategy that fits your organisational reality. From there you move into the planning work that most programmes skip: gaining genuine buy-in at all levels through detailed planning that connects improvement activity to what people actually care about. The middle sessions address the practical architecture of implementation — activity types, implementation steps, and the measurement systems that make the rate of change visible rather than assumed.
Within twelve months the programme has become one more layer in the organisation’s accumulated history of initiatives that started strong and faded quietly. The tools were sound. The people were willing. What was missing was the design of how the programme would enter the organisation, build supporters, sustain momentum through the inevitable resistance, and embed itself into the management system so that improvement persists beyond the initial enthusiasm.
Designing for Continuous Improvement addresses this gap directly. It is not a course about improvement tools — it assumes you have tools or can acquire them. It is a course about the architecture of deployment: how to design an improvement programme so that it works within the reality of your organisation rather than against it. The distinction matters. Most training teaches you what to do. This programme teaches you how to design the conditions under which what you do actually sticks.
The programme closes with the two disciplines that determine whether improvement persists: the cycles of reflection and adaptation that improve the improvement programme itself, and the embedding of change into the workplace management system so that gains become the new standard rather than a temporary deviation from old habits.
The programme also builds networks. Participants learn from each other’s deployment challenges and contexts, creating peer relationships that continue beyond the formal sessions. This is deliberate — improvement is rarely a solitary endeavour, and the people who sustain change over years are almost always connected to others doing the same work in different environments. The course creates those connections as an integral part of the learning design, not as an afterthought.
This programme is available in both standard and AI-embedded versions. The AI-embedded version provides participants with a configured thinking partner that supports deployment design work between sessions — helping them think through stakeholder analysis, plan communication strategies, design measurement systems, and pressure-test their deployment architecture against the realities of their specific organisational context.
Course Overview
This is an Online Workshop that is delivered twice a year in February 2026 and April 2026 – additional by request.
session
1
Strategy
Why structured thinking matters and where A3 fits in the architecture of work. The relationship between SDCA (maintain) and PDCA (improve). Why you cannot improve what you cannot first stabilise.
session
2
Planning
Designing your work for clarity and learning the A3 format. Peer review of work systems. Building quality into each step through judgment criteria. Where standards exist versus working from memory. The A3 as communication tool.
session
3
Follow-up
Communication, consensus-building, and the rhythm of work. Visualisation principles. The tatakidai concept: presenting draft work for feedback. Nemawashi: building consensus before decisions. Horenso: the ongoing communication rhythm.
session
4
Results Analysis
Monitoring process and results, understanding gaps. Leading versus lagging indicators. Quantitative and qualitative measures. Gap analysis: when is a gap a problem to solve versus a paradox to navigate?
session
5
Discovery
Finding problems worth solving and exposing them properly. Problem selection criteria. Authority check: where do causes live? Stratification before root cause analysis. Distinguishing symptoms from causes. Gemba observation.
session
6
Capability
Building ongoing practice and developing others. On-job development principles. The teaching-learning cycle. Building A3 thinking into daily management. From Event to Setting to Vision: the developmental progression. Personal practice planning.