All insights
Operations

The handover is the system.

Field note6 min readMustafa Mujahid

The deliverable that matters in an Implement engagement is not the running workflow on day 60. It's the workflow your team is still running on day 180, without us.

Most consultancies treat handover as a closing milestone. We treat it as the architecture. Everything we build is built to be operated by someone else, and that "someone else" is on the calls from week one.

What handover actually means

A handover is not a Loom video and a Slack channel. A handover is a working operator who can run the workflow on a Tuesday morning when something breaks. To get there, the workflow has to ship with four things:

  • An SOP the operator wrote with us. Not a doc we delivered, a doc the operator drafted and we corrected. Forces every assumption to surface.
  • An eval rubric the operator agreed to. "Good output looks like this. Bad output looks like that." Gives the operator a way to know when the system has drifted, before the problem reaches the customer.
  • An off-switch they've used. Not just documented, actually flipped, in a dry run. The first time you pull the plug should not be in production.
  • A monthly check-in for the first quarter. Not retainer scope creep, a 30-minute review against the eval rubric. We come back, the operator runs us through what changed, we adjust.

Why most handovers fail

The pilot was built around the consultant. They held the prompt. They knew the brittle integration. They were the system. When they leave, the team inherits a tool nobody actually knows how to operate.

Three weeks later, the workflow has drifted. Six weeks later, the team is doing it manually again. Three months later, the AI tool is technically still on, but it's a ghost.

The fix is not a better deliverable doc. The fix is to build the engagement so the operator's hands are on the keyboard from week three.

How we run it

By week three, the operator is reviewing every output. By week six, they're triaging the edge cases without us. By week eight, we're running dry-run handovers, the operator runs the workflow, we observe, we fix the gaps in the SOP. By week ten, the formal handover is a formality, because the operator has been operating for a month already.

The goal of the engagement is to make ourselves unnecessary. If you still need us on day 91, we did our job badly.

That sounds like a bad pitch for a consultancy. It's actually how we get hired for the next workflow.

Related field notes

All insights
Strategy

Why most AI pilots stall at month four.

The pattern is consistent: a strong PoC, a quiet handover, no owner. The system limps along until the next reorg quietly buries it.

Governance

The off-switch is part of the design.

You should be able to turn the model off in under five minutes and revert to the manual workflow without losing data.

Implementation

Human-in-the-loop, without the drag.

Approval steps that don't slow the workflow to a crawl. Be honest about which decisions actually need a human.

Trust the transition.

A 30-minute fit call. No deck. We'll tell you whether AI is the right move, honestly.

Book a fit call
Book a fit call