The engagement ends, the final readout is delivered, and we move on. Within sixty days, the slides sit in a SharePoint folder nobody revisits and the roadmap becomes a snapshot of what was true in week ten, one that nobody updates because the people who built it are gone. The question that separates lasting value from a temporary burst of clarity is: what will your team be able to do independently on day one after we’re gone?
Three Layers of Residue
Most firms deliver only the first of three layers that a consulting engagement can leave behind.
Templates are the most common: a workstream charter template, a decision log format. These are reusable structures that encode a way of thinking about the problem. A good charter template forces the team to define scope, dependencies, and success criteria every time they start a new workstream, even without us in the room. But templates are limited; they tell the team what to fill in, not how to facilitate the conversation that produces the content.
Exercise designs are more valuable. An exercise design is the capability to run a process. When we leave behind the design for a pre-mortem session (i.e., the question framing, the silent writing protocol, the prioritization method, the synthesis process), your team can run their own pre-mortem six months later without calling anyone. Exercise designs transfer the facilitator’s craft to the organization.
Operating models are the real product. An operating model is the set of meetings, roles, decision rights, and escalation paths that keep a program coordinated over time. When designed well, it answers every question the team will face in the first ninety days: when do we meet, who decides, how do we escalate, how do we update the roadmap, how do we know if we’re on track.
Templates Are Easy to Deliver, but the Deeper Layers Require Co-Design
Templates are tangible and make good appendices in final readout decks. Exercise designs require documenting the full process for running each exercise: how to set it up, how to frame the question, manage the discussion, and synthesize. This documentation is labor-intensive and doesn’t look impressive on a slide.
Operating models require even more. They have to be co-designed with the client’s team during the engagement, tested during the engagement, and adjusted based on what works. We can’t hand over an operating model in a final readout the way we hand over a slide deck; your team has to have lived inside the operating rhythm for several weeks before the engagement ends.
A Capability Transfer Artifact Makes the Residue Explicit
In the final step of the engagement, the handoff, a specific artifact makes the residue explicit. The capability transfer document lists every template and exercise design the engagement is leaving behind, plus the operating rhythms that keep the work running. For each one, it identifies:
- Who on your team has been trained to run it, and when they practiced during the engagement
- What support they might need in the first quarter
This artifact forces a conversation that most engagements avoid: is the team actually equipped to operate independently? If the answer is no, it’s better to discover that in week eleven than in month four when nobody can figure out how to update the roadmap.
The Ninety-Day Mark Reveals Whether the Engagement Worked
The real test of a consulting engagement is what happens at the ninety-day mark. Is the team still running the operating rhythm? Can the program lead facilitate a roadmap update without calling us back? If the answer is yes, the engagement delivered lasting capability. If the answer is no, it produced a set of artifacts aging in a shared drive, and the organization is running the same way it ran before anyone was hired.
