Start with the work.
Stay through the result.
Every engagement follows four phases. We use them for process changes, modernization, and custom software. The steps are written down so you know what to expect.
Four phases, in order
Observe
We follow a job from request to completion. We record the handoffs, documents, systems, judgment calls, and exceptions before recommending a change.
Decide
We separate process problems from technology problems, identify what should stay human, and agree on the smallest valuable move. The decision may be to fix, buy, build, or leave the system alone.
Make
We redesign, modernize, or build in the environment where the result will run. You see working material early. We document scope changes and keep new systems away from production until they pass the release checks.
Run
We deploy the work, train the team, monitor the result, and fix defects. We document consequential actions, keep changes reversible, and assign one partner to remain responsible after launch.
Where a person stays in the loop
Every system we ship has a written limit. It handles routine cases and sends uncertain ones to a named person. When judgment is required, the system stops and asks.
The boundary comes from observing the work first. Uncertainty, commitment, money, sensitive data, and consequential decisions stay with people unless the engagement explicitly establishes otherwise.
Everything is filed
We keep a written record of findings, decisions, and changes. Software changes ship as commits, so rollback is routine. Your team keeps the training and handover documents.
When you ask what the system did last Tuesday, the answer is a record, not a recollection.