The Toyota Way is less a toolbox and more a habit of thinking: it teaches leaders to slow down, see clearly, and develop people so the organisation keeps improving long after the leader has moved on. This essay unpacks the core ideas, shows how they changed a real governance group I worked with, translates the implications for leadership, and gives practical steps you can use this week.
The core idea
Toyota rests on two interconnected principles: continuous improvement and respect for people. Continuous improvement, or kaizen, means daily, small refinements that compound into meaningful change; respect for people means taking everyone as a thinking contributor and building their capability, not just extracting output. These are not soft extras that sit alongside targets: they shape the questions you ask, the data you trust, and the way you allocate time and attention.
A concrete example
I coached a board of charity governors who were bright, committed, and overloaded. Everything felt urgent, so their meetings were crowded and reactive. We deliberately slowed one discussion and asked people to go and see the work being done on the ground - genchi genbutsu, the practice of going to the actual place to observe. What looked like a resourcing crisis turned out to be duplication: several volunteers were doing overlapping tasks. Once the real problem was visible, the conversation shifted from ‘get me more capacity’ to ‘redesign who does what’, and the group moved from frustration to practical redesign within a single meeting. That change - seeing before deciding, then using a constrained format to capture thinking - was the most Toyota-like part of the work I did with them.
A3 thinking in practice
A3 is the one-page problem-solving discipline Toyota uses to force clarity. On one sheet you state the problem, show the current state, analyse root causes, list countermeasures, and define next steps. The limit matters: it prevents refuge in long reports and compels leaders to make their reasoning visible. With the governors, an A3 stopped meetings circling on symptoms. In one session a confused debate was resolved in thirty minutes once the group committed to writing the issue down, mapping current state, and naming causes. The constraint created discipline; the discipline created focus.
What respect for people really means
Respect for people is often misunderstood as politeness. In Toyota terms it is a practical expectation: people are thoughtful contributors whose judgement you should invite and develop. In the governors’ meetings this changed how quieter members participated. When their observations were taken seriously, the quality of team decisions improved. For leaders this means resisting the urge to supply answers too quickly, asking slightly better questions, and creating space for others to offer precise, actionable observations.
Why continuous improvement is demanding
Kaizen is unglamorous; it is daily and relentless. It forces leaders to accept that most gains are incremental and that capability-building frequently looks like small declines in short-term efficiency while skills develop. With the governors the effect was cumulative: meetings became clearer, shorter, and more purposeful because the expectation of small, regular improvement changed how people prepared and followed up. That rhythm is the leadership work: design the cadence, insist on learning, and protect the space where learning happens.
How to calibrate challenge
Toyota expects improvement to feel slightly uncomfortable. If there is no tension there is usually no learning. The leader’s job is to calibrate that tension: enough stretch to generate growth, not so much that people burn out. Practically, this means keeping close to the work, checking assumptions, and nudging people into tasks that stretch their judgement while giving them the scaffolding to succeed.
Practical steps you can use this week
Go and see: pick one issue your team is debating and commit a leader or pair to spend two hours with the people doing the work this week; return with a one-page observation, not a recommendation.
Try an A3: next time a conversation drifts, stop and complete a one-page problem sheet. Limit it to one side of A3 paper or one slide; force the current-state map and one root cause.
Pause before solving: when someone brings a solution, ask three questions: what is the evidence, who is affected, and what capability would this build or erode?
Make daily small improvements visible: add a two-minute ‘what we improved today’ item to the end of recurring meetings for a fortnight; capture the tiny wins.
Calibrate stretch: for a stretched individual, reduce scope by 20 per cent and add one learning check-in each week; for an under-challenged person, add one small, visible risk they can own.
For coaches: what to look for
Spot patterns not incidents. Coaches should listen for repetitions: the same problem returning with different faces signals a system issue, not a people issue. Ask clients: where have you gone to see the problem? If they have not, make a Go-and-See the next coaching action. Use A3 thinking as a coaching tool: ask your client to produce an A3 between sessions and use it as the basis for challenge and accountability.
Where this sits with Enhanced Leadership
These practices map closely to the themes I explore in Enhanced Leadership: judgement over answers, building capability over chasing outcomes, and designing conditions where better thinking emerges. If you are exploring how to lead through complexity and AI-driven change, these habits provide a human anchor.
One question to leave you with
Where in your organisation are you solving the wrong problem because you have not actually gone to see what is happening?
If this piece has sparked an idea, I would love to hear how you are using structured problem-solving and small, regular improvement in your context.
Until next time, keep leading, keep learning, and keep levelling up!
Follow on LinkedIn - Spotify - YouTube - Apple