Approach
How we think about improvement
A few principles that shape every piece of work, whether we are writing code or facilitating a session.

Real work beats exercises
Teams learn fastest on the problems they actually have. Simulations have their place, but improvement sticks when it is practised on the next real backlog item.
The team decides
We offer options and experience. The team chooses what to try and owns its agreements. Changes imposed from outside rarely survive the first busy week.
Small steps, quickly
One or two changes tried for a fortnight beat a dozen recommendations in a report. We would rather see a small improvement used than a large one admired.
Psychological safety is practical
People admit problems when it is safe to do so. We keep sessions about the work and the system, never about blaming individuals.
Follow up honestly
We check in after a few weeks. If something did not stick, that is useful information, and we say so plainly.
Software quality is team quality
Clean code, good tests and smooth releases are outcomes of how people work together. That is why we do both kinds of work.