A plant decides to build a new assembly cell. The kickoff has thirty slides, a budget and a target date. Six months later the sponsor, the production manager and the software team each describe a different project.
Most projects do not fail on technology. They fail because nobody wrote down what success means before the work started.
Seven sections, one test each
A charter answers seven questions on no more than two pages:
- Purpose: why the project exists, in two sentences, from the view of the user.
- Objectives: three to five results with a value and a date. “Cell runs at 62 seconds cycle time and 98 percent first pass yield by 30 June 2027.”
- Scope: what is in and what is out, as two lists.
- Deliverables: what is handed over at the end.
- Constraints: budget, fixed dates, standards to follow.
- Organization: sponsor, project manager, core team.
- Acceptance: criteria and the person who accepts.
The test for each section is simple. Could someone check it at the end without a discussion? “Improve productivity” fails. “Reduce assembly time per unit from 9 to 7 minutes” passes.
Write the out of scope list first
The most expensive sentence in a project is “we assumed that was included.” It appears in month five, when the budget is committed.
Write the out of scope list in week one and make it as concrete as the in scope list. “Changes to the existing cells of family A” and “series support after six weeks from start of production” are typical entries. Read the list aloud in the kickoff. Silence is not agreement, so ask each lead to confirm it.
Authority belongs in the charter
A charter also says what the project manager may decide alone. A common rule: changes up to 5 percent of the budget and two weeks of the schedule within the project, everything above with the sponsor.
Without that line, every decision travels up the hierarchy and the project waits.
Signed, not just presented
The charter is finished when the sponsor signs it. Signing forces the last questions: is the budget really approved, are the named people really released by their managers, is the end date a wish or a commitment?
Store the signed version as the baseline. When the scope changes later, the change is visible against a document everybody agreed to.
The charter is short on purpose. If the project cannot be described on two pages, it is not understood yet, and no schedule will fix that.