Step 9 marks the end of the engagement and the beginning of the program’s independent life. On paper, it’s administrative: decision log, capability transfer, open items, success criteria. In practice, it’s the most emotionally loaded step in the methodology, because the client team has been working alongside our consulting team for twelve weeks, and those people are now leaving.
The handoff produces four artifacts that sustain the program
The handoff step produces four artifacts, each serving a different function:
- The decision log captures every decision made during the engagement: who made it, when, and what it resolved. When questions arise in month four about why a scope boundary was drawn a particular way, the decision log provides the answer. Without it, institutional memory depends on people who may rotate or leave.
- The open items list captures everything identified during the engagement but not resolved: unresolved dependencies and deferred decisions, plus flagged risks without mitigation plans. Most engagements surface more open items than they resolve, because the work reveals issues that existed before we arrived. The list makes incomplete work visible and assigns ownership for each item.
- The capability transfer artifact documents what the client team can now do that they could not do before. This is a list of capabilities, not deliverables: the team can run a cross-functional planning process, facilitate a pre-mortem, build and maintain a constraints calendar, and make governance decisions using the operating model without external facilitation. The question of what stays after the consultants leave is answered here.
- Post-engagement success criteria define what good looks like in the months after. These are operational checkpoints: the operating rhythm sustains through at least two full cycles, the risk register is updated monthly, the roadmap is revised quarterly, and cross-functional dependencies are tracked in the cadence the engagement established. If the operating rhythm sustains through three cycles, the capability transfer worked; if the risk register has new entries three months later, the team internalized the discipline.
A well-designed handoff addresses anxiety without reinforcing it
The final weeks of an engagement often produce anxiety in the client team, and that anxiety is about the absence of the people rather than the quality of the deliverables. Over twelve weeks, our consulting team became part of the operating rhythm. We facilitated sessions and built artifacts while holding the cross-functional view. This concern is a signal that the working relationship was real and that the program depends on the capabilities the engagement built. The design challenge is to address the anxiety without reinforcing it. A handoff framed as “here is everything we did and you need to keep doing it” reinforces dependency; a handoff framed as “here is what you can now do” transfers ownership. The second emotional risk is a drop in energy. The engagement had momentum: weekly sessions and visible progress. A decision log and an open items list can feel like the energy leaving the room. If the handoff is designed as an administrative closeout, the team leaves the final readout feeling like the engagement ended with paperwork. How the closing lands depends on whether the handoff is designed as a graduation or an ending.
The handoff readout showcases what the client team accomplished
The handoff readout should center on what the team built. Our names should barely appear; the client is the protagonist. The readout follows two sections:
- What the program team built together and what capabilities transferred. This section walks through the major artifacts (i.e., the program architecture, the roadmap, the operating model, and the risk register) and frames each one as the team’s output, using language like “the team identified” and “the group decided.” It names each new capability and attributes it to the team’s work during the engagement. The template library that should outlast the engagement is part of this transfer.
- What happens next. Post-engagement success criteria with specific dates and owners: the first independent operating rhythm cycle, the first quarterly roadmap review, the first monthly risk register update. Each milestone has an owner and a date, so the readout ends with forward momentum rather than a retrospective.
In most engagement readouts, we present. In the handoff readout, we facilitate while client team members present their own sections. Disease area leads present workstream outcomes; the program lead presents the operating model and cross-functional governance cadence; the executive sponsor presents the success criteria. When the client team presents, they demonstrate the capability transfer in real time, and the room sees the team operating independently before we’ve left. The readout structure matters because it determines whether leadership sees the handoff as a conclusion or as a launch. A well-designed handoff comes down to the specifics: artifacts that document what happened, capabilities the team can name, and next milestones with owners and dates. When those pieces are in place, the program does not depend on whether anyone remembers what the consulting team said. It depends on whether the client team can do what the engagement taught them to do, and the handoff readout is their first opportunity to prove they can.
