What to Learn from a Mid-Size Implementation Charter, Six Months Later
Most charters get filed after launch. A short retrospective on a mid-size implementation charter — what to harvest, and what makes the next one better.
The charter you signed in January is a teaching artifact in July
A charter that survives a project unchanged is rare. A charter that's marked up after delivery is gold.
Most implementation charters get filed and forgotten the day a project ships. The most underused source of organizational learning in a mid-size company is the gap between the charter you signed and the project you delivered. Pulling that gap apart, six months on, takes about an hour and pays back across the next three projects.
This is a light retrospective practice. It is not a postmortem; the project is over, and assigning blame is no longer useful. It's a forward-looking exercise dressed up as a backward-looking one.
- T+6 monthsReread the charterPull up the original signed charter. Read it without notes for ten minutes.
- +30 minsMark every driftAnnotate inclusions, exclusions, and assumptions: which held, which broke, which got quietly replaced.
- +30 minsWrite three patternsFrom the marks, write three sentences: 'We consistently underestimated X. We consistently overestimated Y. We were silently wrong about Z.'
- T+6 months, +1 dayInsert into next charterTake those three sentences into the next initiation. Each should produce a new exclusion, a new assumption test, or a new decision-rights clause.
What to look for, specifically
For mid-size implementation projects, three patterns tend to repeat:
- Stakeholder lists were too short. The signed charter typically names sponsors and decision-makers, but the people who actually blocked or accelerated the project rarely appeared on the original list. Mark them up.
- Assumptions about other teams' capacity were optimistic. If your charter assumed two days a week of input from another team, mark whether you got it. The answer is usually no.
- Exclusions were undersigned. Look at exclusions and check which got absorbed back into the project. Each absorbed exclusion is a charter authoring failure, not an execution failure.
These three patterns alone, applied to the next charter, materially reduce expansion in the next project.
Charter retrospective output
0 / 4- Marked-up copy of the original charter, kept with the project archive
- Three sentences naming the strongest drift patterns
- One concrete change to the standard charter template — added field, sharper exclusion language, or different sign-off process
- A note in the next project's charter draft pointing back to this retrospective
If you do this once, you've improved one charter. If you do this on three consecutive projects and aggregate the patterns, you've improved how your organization initiates projects — which is a far rarer outcome than improving any individual one. For the prospective baseline this builds against, see the enterprise charter template, and for the active corrective when retrospect isn't enough, see rebuilding a charter mid-flight.