Analyse, execute, review

We do not try to finish it all at once. Small pieces go into real use on a short cycle, and what happens next is decided from what actually gets used.

Review feeds straight back into analysis. The loop does not finish, it keeps turning.

Analyse

The stage where the problem gets redefined. We look past the feature that was requested to the reason it was requested.

Watching the work and interviewing the people doing it
Reading the existing data and records
Agreeing what is in scope and what is not

Execute

Build the smallest useful piece and put it into real use. Nothing waits for the whole thing to be finished.

Core flow first
Trial run on real data
Feedback from the floor folded straight back in

Review

We check the record for whether it is actually used. Features nobody opens get removed, not defended.

Usage records and handling times
Manual steps that are still left
Scope for the next cycle

Principles

Unused is the same as absent

Progress is judged on usage records, not on a count of delivered features.

The data is yours

Your operating data and content are your assets, kept in a form you can export at any time.

Written down, not remembered

Procedure belongs in the document and on the screen, not in someone's head.

Nothing switched on that cannot be switched off

Irreversible changes are flagged in advance and only made once approved.

Send an enquiry