Project Charter · Kickoff
Project Charter & Kickoff
What is a project charter?
- A document that formally approves the launch and grants authority
- Out-of-scope items and manager authority are the core
- Kickoff is where you align on success criteria
Writing a project charter doesn’t just add one more document; it changes who you argue with. Without a charter, four months in, when someone says “Wasn’t that included originally?”, the PM has to answer from memory. With a charter, that question becomes a matter of opening section 3 together, and the conclusion shifts from whether it’s in scope to whether to seek approval for an amendment. A charter moves the dispute from people to a document, so what actually gives it force is not how complete the content is but who signed it.
A charter is not a business plan or a proposal. A plan persuades people to do something; a charter gives permission to do it. It also differs from a WBS or an execution plan: those cover “how,” while a charter covers “how far.” Two to three A4 pages is enough; the longer it gets, the less anyone reads it, and the weaker its approval. What it must include is the change criteria. Put them in numbers, such as “changes beyond 2 weeks of schedule or 10% of budget require sponsor re-approval,” and the charter stops being a paper read once at launch and becomes a baseline you refer to throughout the project. The signature line should carry not the PM but someone who can actually commit budget and people.
A kickoff is not for pleasantries; it is where you force misunderstandings into the open. Block 60–90 minutes, put the charter on screen, and read it one item at a time. Ask each attendee to say in one sentence, “If this project succeeds, what will be different in six months?” and you will usually hear three or four different answers. A mismatch surfaced in that room costs far less to resolve than the same mismatch surfacing midway through the project.
The most common failure in practice is a PM writing the charter alone, emailing it around, and, when no one replies, treating it as approved. This document takes effect only when it goes through the approval line and is signed. Another is leaving out-of-scope items blank for fear of seeming unhelpful. Items such as migrating past data, training business users, and standardizing other departments’ forms, if not written down, are all read as “obviously included” and get piled on with no added staffing. A charter that goes into a cabinet right after kickoff is no better. A charter that doesn’t reflect changes becomes, six months later, a paper no one accepts as a reference.
John KimInstructor John Kim, CEO of Nanum Consulting and author of “B2B Marketing Design”
Kwangdong MinExpert in business models, revenue models, and market researchThe Project Management Body of Knowledge (PMBOK) defines it as the document that formally approves a project and gives the project manager authority, and treats it as the key deliverable of the initiating process group. Most project management methodologies since have a similar kickoff document.
Company A, an auto-parts manufacturer with 480 employees and KRW 120 billion (≈ US$89,780,000) in annual sales, is restarting its warehouse management system (WMS) rollout. Two years earlier, the same initiative dragged on for six months before being dropped. This time the budget was KRW 580 million (≈ US$433,900) and the timeline eight months. The biggest risk was that the logistics, production, and IT teams each expected something different. (Hypothetical example)
- The IT manager wrote a two-page A4 draft charter, then raised the approval line to the logistics executive director for a signature, because the last project had stalled for lack of a decision-maker.
- Three items were explicitly listed as out of scope: production results reporting, a supplier portal, and migrating three years of historical inventory. The production manager confirmed, “So ours goes into phase two,” and expectations were settled.
- The PM’s authority was also written in numbers: schedule adjustments within 2 weeks and spending up to KRW 30 million (≈ US$22,400) were the PM’s call alone, and anything beyond that needed the executive director’s re-approval.
- In a 90-minute kickoff, nine attendees each said in one sentence “what will change eight months from now.” The answers split across inventory accuracy, shipping lead time, and month-end closing workload, so the team narrowed the success criterion to 98% inventory accuracy.
- By the month-8 launch, of 11 scope change requests, only 4 were accepted under the charter and 7 were pushed to phase two. The delay stayed at 2 weeks, and inventory accuracy rose from 91% to 97.6%.