To achieve regulatory conformance is it better to unambiguously document every process step, or to leave the job to the operator and inspect the final outcome for conformance? Andrew and Julian did neither! A quality problem forced this issue, and they created a step-wise review practice that worked well in Operations. “Say, Do, Prove” is a short description of it, and the parallel with Agile’s “Acceptance Test Driven Development” is hard to miss.
The same “Say, Do, Prove” accountability was applied to administrative functions, revealing that some cells were handling their autonomy and freedom much better than others. Efforts to address this problem eventually led Andrew and Julian to divide under-performing cells even further until they each contained one person.
Optional Reading to do:
500%: How Two Pioneers Transformed Productivity – The First Truly Self-Leading Organisation
Chapter 7, 8, 9
Sub-topics in the Chapters:
- Devolving all the bureaucratic functions into the cells
- Shifting the quality emphasis from process to outcome
- Introducing an overarching philosophy (Requirement; Say, Do, Prove)
- Introducing ‘Recipes for everything’
- Importance of Audit
- Documenting our new Organisational Model
