Every engagement we run passes through the same five stages: understand, architect, build, operate, improve. Written down like that it looks like a pipeline, but it works as a loop, and the difference matters more than the stages do.
Why a loop
A pipeline has a final stage. Somewhere on the right-hand side of the diagram sits a box that means “done”, and the whole engagement quietly organises itself around reaching that box. Scope gets negotiated against it and quality gets traded for it, until the handover meeting becomes the finish line and the team that built the system is somewhere else when the system meets its first real month-end.
A loop keeps going. Operating the system feeds improvement, improvement feeds fresh understanding, and the people who designed the system are still in the room when production shows them what it thinks of the design. That changes behaviour at every earlier stage, because you architect differently when you know you will be operating the result, and you build differently when the late-night phone call comes to you.
What each stage is for
Understand exists to stop anyone proposing a tool before the problem is clear: the users, the surrounding systems, the processes, the constraints. Most failed projects fail here, quietly, months before anyone notices.
Architect produces a design that is practical in a specific sense: buildable, and runnable by the team the organisation actually has. An architecture the client cannot operate is a liability with a diagram attached.
Build is incremental on purpose. Working software arrives early, disruption is managed, and assumptions get tested against reality rather than against the specification document.
Operate is where most consultancies leave. We stay accountable for the system in production, well past handover, because production is where the truth lives.
Improve runs on a cadence instead of waiting for a crisis. Operational data and business feedback drive deliberate change, because a system whose only trigger for improvement is a breakage is a system managing its owners.
Why we keep it to five words
Methodologies grow. Left alone, a five-stage loop becomes a nine-stage framework with a certification programme. We keep ours at five because each word is a question we can ask in any meeting: do we understand this, does the design hold, is it built, is it running, is it getting better. Wherever one of those questions has a bad answer, that is where the work is.