The Architecture of Improvement

Every improvement tool has three parts: a visible structure, an interaction practice, and a development system. Companies like Toyota design and implement all three together. Most organisations install the first and hope the other two follow.

The development system is what sits outside and above the manager-form interaction. It’s the organisational architecture that builds capability in using forms and patterns — not just in one team but across the enterprise, not just this year but cumulatively over time. Toyota designs different development systems for each organisational layer. Group Leaders develop through the Floor Management Development System. Supervisors develop through On-Job Development structures. Managers develop through cross-functional committee participation. Each layer has its own form-pattern-development triad, deliberately designed to build the specific capabilities that layer needs.

This is the leg most Western organisations don’t know is missing. They install forms. The better ones also develop patterns — coaching leaders in how to use the tools. But almost none design the development system that integrates form and pattern across the organisation and builds capability cumulatively. Without it, good practice in one team doesn’t transfer. Capability doesn’t compound. The organisation depends on individual champions rather than architectural capability.

The form is the visible structure — the management board, the A3 template, the daily stand-up format, the KPI review meeting. Forms are documentable, transferable, and easy to install. When an organisation benchmarks Toyota or sends people on a lean study mission, they bring back forms: “We need visual management boards.” “We need A3 problem-solving.” “We need daily huddles.” The forms go up. The rollout looks successful.

The pattern is the structured interaction between the manager and the form. It’s how a team leader uses the management board in a fifteen-minute coaching conversation — not reading the numbers but asking what the numbers reveal about yesterday’s process. It’s how an A3 gets developed through catch-ball dialogue — not filled in at a desk and presented, but shaped through successive conversations that test the thinking. The pattern is what makes the form a working instrument rather than a wall decoration.

Without the pattern, you get compliance without insight. People update the board because they’re required to. The stand-up happens because it’s scheduled. The A3 gets completed because it’s mandated. The forms are alive in appearance and dead in practice. This is the most common outcome of improvement programs worldwide — and it’s invisible to anyone measuring whether the tools are “in place.”

When you assess any improvement tool in your organisation, ask three questions: Does it have a visible structure? Does it have a defined interaction practice that makes the structure work? And does it sit within a development system that builds capability across teams and over time? If you’re missing the third — and most organisations are — you’ve found the reason nothing connects.

Want to Dive Even Deeper?

opt

1

Back to the Drawing Board

Thinking with Meg and Barry

opt

2

Designing Continuous Improvement

For teams ready to rebuild improvement from foundations

Online

Workshop

opt

3

Process Design

Designing the connections between teams and functions

Online

Workshop

opt

4

OAC Phase 1: Work Compression

For individual Leaders wanting to start from their own desk

Executive

Program