Strategic Initiative Charter: Template and How to Write One

Month 14 of an 18-month program

Picture a steering committee, month 14 of an 18-month program. The status slide is green. Milestones met, budget on track. Then someone asks how many customers are using the new system. Nine percent. Someone else asks what number was promised. Nobody knows, because nobody wrote one down. A third person asks who could stop the program. The room goes quiet.

That silence is the charter's fault. Usually because there was no charter, or there was one that described the work and never said what it was for.

A strategic initiative charter is a short document, signed before money moves, that authorizes a piece of work and ties it to one strategic choice. It states the problem with a baseline, the scope, the measures, who decides what, and the conditions under which the work stops. Two pages is typical.

Most people treat the charter as a starting gun. It is more useful to treat it as an exit door you install before anyone is in the building. A charter's real job is to make the initiative stoppable, and the only time you can write the terms of the ending calmly is at the start.

Write the ending while nobody loves the project yet.

What a charter is, and what it is for

The project management world has a precise definition. PMI's PMBOK Guide describes developing a charter as producing a document that “formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities” ¹. The same passage names its key benefit: the charter “provides a direct link between the project and the strategic objectives of the organization” ¹.

Most charters honor the first half and skip the second. They authorize. They rarely link. A strategic initiative charter takes the link seriously: it quotes the strategic choice the work serves, names the measures that will show the choice is paying off, and says who can change course.

The charter decides whether the work should exist and on what terms. The plan, built later by the owner, says how it gets done. A charter stuffed with Gantt charts gets skimmed, and a skimmed charter has not really been signed. For what goes in the plan, see the project plan components.

The template

Copy these eleven fields into a document. The prompt is the question each field must answer. A field you cannot fill is a finding: the initiative is not ready to approve.

Finish with a sign-off line for the sponsor and the owner, the date, and the date of the first formal review.

How to write one

1. Start from the strategy, not the ideaWrite field 3 first. Quote the strategic choice word for word. If the best you can do is a general aim such as “improve customer experience,” the initiative is not yet strategic.
2. Put a number on the problemState the baseline: current cycle time, churn, cost or share, and where the number came from. A problem without a baseline can never be shown to have been solved, which means it can never be shown to have failed either.
3. Draw the scope line twiceList what is in, then list what is out. The out list prevents most later arguments, because it names the work stakeholders will otherwise assume is included.
4. Choose measures that report earlyPair each lagging outcome with a leading driver, so the first review, not the last, can tell whether the bet is working. The KPI page in this series shows how to pair them and how to spot a measure that can be hit without moving the outcome.
5. Write decision rights as a short listName the decisions, not the meetings: changes to scope, spend above a threshold, dates on the critical path, vendor selection. For each, one decider and the people consulted. If the list grows long or contested, choose a decision model deliberately; RACI, RAPID and DACI fail in different ways.
6. Set kill criteria before you startAgree the stop conditions while nobody has sunk anything into the work. Tie each to a measure, a threshold, a date and a named decider.
7. Get it signedThe sponsor signs, the owner signs, and the first review date goes in the calendar the same day.

A filled-in example

The company below is invented. Notice how each field closes off an argument that would otherwise happen in month nine.

Look at the third risk. Sales reps who fear self-service will quietly tell distributors to keep phoning. That risk would never appear on a status slide, but it is the most likely reason the month-6 number comes in low. Naming it in the charter, with an owner, turns a political problem into an assigned one.

Why the kill criteria come first

There is an asymmetry inside every organization. Continuing an initiative requires no decision at all. Stopping one requires a person to stand up in a meeting and argue against work their colleagues have spent a year on. So initiatives continue by default, long after the evidence has turned.

The evidence that this is common is not subtle. In a survey of nearly 8,000 managers in more than 250 companies, Donald Sull and colleagues found that eight in 10 said their companies failed to exit declining businesses or kill unsuccessful initiatives quickly enough ³. Each month of delay also adds to what has been spent, and spent money exerts a pull of its own; the Lexicon entry on the sunk cost fallacy covers the mechanism.

Kill criteria break the asymmetry. Agreed at the start, they turn stopping from an accusation into a scheduled check: the number came in below the line, so the decision we agreed to take is now due. Nobody has to be the villain. When an initiative stops on its kill criteria, the charter has done its job.

Good kill criteria are observable, dated and set in advance: a measure, a threshold, a date and a named decider. Bad ones are vague (“if the initiative is not delivering value”) or land so late that the money is spent before they apply. See kill criteria for the concept.

The case against kill criteria, taken seriously

The strongest objection is that kill criteria kill the wrong things. Real strategic bets often start slowly. Adoption curves bend late. A threshold set at month 6 may stop an initiative that would have been the company's best decision of the decade at month 18. And once teams know a number decides their fate, they will manage the number.

Both points are true. Both are arguments about how to write kill criteria.

• Trigger a decision, not an execution. The criterion says “stop or reshape, and the sponsor decides at the month-6 review.” It forces the conversation. It does not preempt the judgment. A sponsor who continues past a missed threshold should say why, in writing, and set a new line.
• Match the measure to the bet's clock. For a slow-maturing bet, use a learning milestone instead of an outcome threshold: “by month 6, we will know whether distributors' buyers will order online, from a pilot of 10.” The stage-gate process works this way, releasing money in tranches as uncertainty falls.
• Pair every measure with its counter-measure. If the kill line is adoption, also watch order accuracy, so the team cannot hit the line by pushing distributors onto a system that makes mistakes.
• Separate the person from the result. If stopping on the criteria hurts the owner's career, owners will set lines they know they can clear. The fix is cultural and explicit: an initiative that stops cleanly on its own criteria is a well-run initiative.

The alternative to imperfect kill criteria is not patient judgment. It is no criteria, which in practice means the initiative is stopped by a budget crisis, a reorganization or a new CEO, all of which are worse judges than a number you chose with a clear head.

Running a portfolio of charters

One charter disciplines one initiative. A stack of them, laid side by side, disciplines the strategy. Kaplan and Norton argued that when managers use strategic targets to allocate resources and set priorities, “they can undertake and coordinate only those initiatives that move them toward their long-term strategic objectives” ². Field 3 is where that test happens. Read every field 3 in one sitting and two things jump out: links stretched to fit, and strategic choices no initiative serves.

Three second-order problems show up at portfolio scale.

• The cross-unit orphan. An initiative that needs three units to deliver, with an owner in only one of them, stalls on promises nobody else is measured on. The charter's decision rights and resources fields should name the commitments needed from each unit, with a person and a date. The strategy execution page explains why these sideways promises are where most strategies break.
• The protected project. Some initiatives belong to a senior executive's identity. Their charters tend to have soft kill criteria and generous milestones. A portfolio review that applies the same checklist to every charter, published to the whole leadership team, is the cheapest political defense available.
• The capacity illusion. Each charter's resource field looks reasonable alone. Summed, they ask for the same engineers four times. Add up field 10 across the portfolio before approving the last charter, not after.

Before you sign: a review checklist

• Field 3 quotes a strategic choice, not a general aim.
• The problem has a baseline number and a source for it.
• The out-of-scope list names at least three things.
• At least one measure will move within the first quarter.
• Every decision listed has exactly one decider.
• Each milestone has a test of completion, not just a date.
• Each risk has an owner, and the assumptions are written as testable statements.
• Kill criteria name a measure, threshold, date and decider.
• The first review is in the calendar.

Monday morning: take the largest initiative in your portfolio and fill in fields 3, 7 and 11 from what exists today. If you cannot, those gaps are the agenda for the next steering meeting.

A charter that only starts things is a permission slip. The one worth signing also says, in plain numbers and in advance, what would make everyone in the room agree to stop. That sentence is the one nobody will be able to write in month 14.

Questions

What is a project charter?

A project charter is a short document that formally authorizes a project and gives its manager authority to use organizational resources, as PMI's PMBOK Guide describes it. For a strategic initiative, the charter also states which strategic choice the work serves, how success will be measured, who holds which decisions, and the conditions under which the work will stop.

What should a project charter template include?

For a strategic initiative: name, sponsor and owner; the problem with a baseline; the link to strategy; scope in and scope out; outcomes and measures with targets and dates; decision rights; milestones; risks and assumptions; resources; and kill criteria. Add a sign-off line for sponsor and owner and the date of the first formal review.

What are kill criteria in a project charter?

Kill criteria are conditions, agreed before the work starts, that trigger a decision to stop or reshape the initiative. Each names a measure, a threshold, a date and the person who decides. They exist because continuing needs no decision while stopping needs someone to argue against work in progress; setting the terms early turns stopping into a scheduled check.

What is the difference between a project charter and a project plan?

The charter decides whether the work should exist and on what terms: purpose, link to strategy, scope boundaries, measures, decision rights and kill criteria. The plan describes how the work will be done: tasks, schedule, staffing and detailed budget. The charter comes first and is signed by the sponsor; the owner builds the plan within its limits.

Where to go next

• KPI Examples That Track Strategy, Not Activity
• RACI vs. RAPID vs. DACI: Which Decision Model, When
• Strategy Execution: Where It Breaks Between the Offsite and Monday
• Kill Criteria
• Stage-Gate Process
• RAID Log