Why programs without charters drift on scope
Three months into every program, someone asks "is X in scope?" and the team has three different answers. By month six, the program has accreted four adjacent initiatives nobody formally approved but everyone is somehow committed to. By the end, you're well over budget and the success metric has shifted twice.
A charter doesn't prevent this by being wordy. It prevents it by being explicit about what's NOT in scope. That's the conversation people avoid in kickoff because it feels combative. It's also the most useful 30 minutes you'll spend on the program.
"A charter without an out-of-scope section is a wishlist."
This template structures the kickoff to force the hard conversations early. The cheat sheet covers how to facilitate it without the sponsor checking out at slide 4.
Program charter vs project charter
Most templates online are project charters dressed up. They cover one workstream, one delivery date, one team. That's a project charter. It's a useful artifact for a single delivery effort, but it's not what you want for a program.
A program charter is broader and longer-lived. It governs multiple related projects under one strategic outcome, often spans multiple quarters or years, has an executive sponsor (not a delivery manager), and explicitly defines the boundary between this program and the adjacent ones it will be confused with. The charter is the artifact you point to in a steering committee when someone proposes adding a sixth workstream that doesn't belong.
Three things a program charter has that a project charter usually doesn't:
- Out-of-scope statement. Explicit list of what this program will NOT do. Often longer than the in-scope list.
- Governance model. Who decides what at which forum. Steering committee composition, decision rights, escalation path.
- Success metrics that aren't delivery metrics. "Ship by Q3" is a project goal. "Reduce customer time-to-onboard by 40%" is a program goal. The charter binds the program to the outcome, not the deliverable.
This template is built for the program-level conversation. If you only need a project charter, the format will feel heavy.
The 7 sections that prevent scope creep
The template walks through these in order. Each one forces a specific conversation at kickoff that's much harder to have in month four.
- Strategic outcome. One sentence on the business result this program delivers. If you can't write it, you don't have a program.
- In-scope. The workstreams and deliverables this program will produce.
- Out-of-scope. The adjacent initiatives that look like this program but aren't. This is where most charters fail.
- Stakeholders & RACI. Sponsor, decision-makers, contributors, informed. Names, not roles.
- Success metrics. Outcome metrics, not delivery metrics. Targets, not directions.
- Constraints & assumptions. The conditions under which this scope is achievable. When an assumption breaks, the charter triggers a re-baseline conversation.
- Governance. Steering committee, cadence, decision rights, escalation path. The forum that will use this charter to make decisions.
Pair the charter with a RAID log for ongoing risk and dependency tracking, and a weekly status report for the rhythm that keeps the program on the charter's intended path.
