Template

Implementation Plan Template for Services Engagements

The eight-artifact implementation plan an engagement manager produces in week one. Workstream map, decision rights, acceptance criteria, assumption ledger, and more, in one workbook.

An eight-artifact workbook plus the phase-and-gate plan, each tab prompted cell by cell.

A real implementation plan is eight artifacts produced in week one, not a Gantt chart. This workbook gives you all eight as prompted tabs: the workstream map, decision rights matrix, per-workstream acceptance criteria, assumption ledger, integration map, change control protocol, cadence schedule, and close-out plan. The timeline document is the byproduct you assemble on Monday of week two, once these inputs are real.

What's inside

  • All eight artifacts as prompted tabs, produced in week one so the timeline becomes a byproduct, not the plan.
  • The phase-and-gate table from the article, pre-filled with a prompt in every cell.
  • A decision rights matrix that routes a change request to the right approver in hours, not weeks.
  • An assumption ledger that turns 'you missed the date' into 'the test-data assumption was wrong, and here is what that cost.'

Related reading

The Kickoff Meeting Is the Easy Part
Delivery

The Kickoff Meeting Is the Easy Part

See it running on your firm's data

15-minute working demo. No slides. Bring an engagement you actually scoped.

FAQ

Three things must be resolved before the client joins the call: the EM and PM must agree the scope is deliverable as written, the architect or technical lead must have confirmed there is no ambiguity on the core technical approach, and internal alignment on margin and resourcing must be complete.

Most kickoff failures are prep failures. The meeting itself is straightforward: scope walkthrough, introductions, next steps. What derails engagements is sending those questions into the kickoff instead of resolving them before it. If the PM finds problems in the SOW on the Monday she's onboarded, and the kickoff is Thursday, the project is already behind. Pre-kickoff is where the project is won or lost.

The three structural fixes: cap senior delivery staff utilization at 75 to 80% so they have time to actually scope work before it closes, require a paid Phase 0 discovery on any engagement with novel technical or client risk, and give the Engagement Manager written authority to commit scope and price without multi-department review.

Scope creep rarely starts when the client asks for one more thing. It starts when the team had four hours to scope work that needed four days. The change order is a symptom. The root cause is a scope that went out before discovery finished: either because the team was too busy to scope it properly or because sales had to close the deal before the discovery was done.

When the original scope assumption has broken in a way the customer will not contract around, when the team is burning hours with no path to delivery, or when the relationship has deteriorated past honest conversation. The EM raises it with a written recommendation. A firm where EMs cannot say this without career risk is one where bad engagements run long.