A Project Charter defines the business case, problem, goal, scope, roles, timeline, benefits, and governance for an improvement project.
Definition
A Project Charter is the authorization and alignment document for a Lean Six Sigma, Kaizen, or operational improvement project. It clarifies why the project matters, what problem will be solved, what is in and out of scope, who owns the work, what target is expected, and how success will be measured.
A strong charter prevents vague projects from becoming broad activity lists. It gives the team a practical contract with the sponsor.
History
Project charters come from project management practice and were adapted heavily into Six Sigma deployments. DMAIC projects in particular use charters to connect improvement work to business priorities, financial validation, customer impact, and phase-gate review.
When to Use
Use a Project Charter before starting a DMAIC project, Kaizen event, cross-functional improvement, cost-reduction project, customer complaint initiative, or process redesign effort. It is most valuable when multiple stakeholders must agree on problem, scope, resources, and expected outcomes.
Step-by-Step
- State the business case and customer impact.
- Define the problem with data, timeframe, location, and magnitude.
- Set a measurable goal without prescribing the solution.
- Define scope boundaries, constraints, and assumptions.
- Identify sponsor, process owner, team members, and decision makers.
- Estimate benefits, costs, risks, and timeline.
- Agree on phase reviews, communication, and escalation rules.
- Review and revise the charter as facts improve.
Examples
- Quality: Reduce final inspection defects on a product family by 40 percent within six months.
- Service: Cut invoice correction cycle time from ten days to four days.
- Maintenance: Reduce unplanned downtime on a critical line through failure-mode analysis.
Common Pitfalls
- Writing a solution instead of a problem statement.
- Vague goals that cannot be measured.
- Scope that includes too many processes or sites.
- No sponsor authority or process-owner commitment.
- Unvalidated savings assumptions.
- Failure to update the charter when project learning changes direction.