Driver Diagrams & Learning Systems
Make your theory of change explicit.
A driver diagram is a one-page picture of how you believe you will reach your aim: the few drivers that have to improve, the change ideas that test them, and the measures that tell you whether it is working. It keeps a portfolio of work connected to the goal instead of drifting into a list of disconnected projects.
Aim → drivers → change ideas → measure
Why this matters to leaders
When leaders can see the theory on one page, reviews change. Instead of asking “what happened to the number,” the team asks “is our theory holding up?” — and the measures are right there to answer it.
What a driver diagram is
A driver diagram connects an aim to the structure of work beneath it. It is built around the IHI Model for Improvement and answers three questions in one view: what are we trying to accomplish, how will we know a change is an improvement, and what changes can we make?
It is a theory, not a project plan. Its job is to make your reasoning visible so it can be tested — and revised — as you learn.
The structure
- 1
Aim
The specific outcome you are trying to improve — including the population, the target, and the timeframe. What are we trying to accomplish, for whom, by how much, and by when?
- 2
Primary drivers
The major system factors that must improve to achieve the aim. Keep these to a handful — the few things that genuinely move the outcome.
- 3
Secondary drivers
More specific contributors underneath a primary driver — actionable enough to point directly at change ideas.
- 4
Change ideas
Specific changes or tests that may influence a driver. Planned experiments and PDSA cycles start here.
- 5
Measures
The linked charts and signals that test whether the theory of change is working — the family of measures for the work.
Linking measures to charts
The power of a driver diagram in Adaptive Flow Studio is that measures are not just labels — they link to the actual charts that test them. Together those charts form a family of measures:
- Outcome measures tied to the aim — is the result improving?
- Process measures tied to the drivers — are the things we believe matter actually changing?
- Balancing measures — is the change causing a problem somewhere else?
Reading them together is what tells you whether a change to a driver is flowing through to the outcome.
From driver logic to action — and learning
A driver diagram points to change ideas; change ideas become small tests of change; and each test ends in a decision. In the Learning Log, every cycle records what was tested, what the data showed, and a clear decision:
- Adopt — it worked; make it the standard.
- Adapt — promising but not there yet; change it and test again.
- Abandon — it did not work; stop and try a different idea.
How leaders should review learning cycles
Leaders do not need to run every cycle — but they should review them. Ask which drivers have active learning, which change ideas have been adopted, and where the diagram has gaps: drivers with no measure, or change ideas with no test. Those gaps are the agenda for the next cycle.