1.3.1 Building a Business Case & Project Charter

Building a Business Case & Project Charter Purpose of a Business Case and Project Charter A strong business case and project charter align improvement work with organizational priorities and create a clear, shared understanding of what the project will achieve. - The business case explains why the project should be done. - The project charter defines what the project will do, how, and with what boundaries. Together they: - Link the project to strategic goals. - Quantify the impact of the problem and expected benefits. - Clarify scope, timeline, and high-level plan. - Establish how success will be measured. - Provide a basis for stakeholder agreement and support. --- Foundations of the Business Case Problem Recognition and Context The business case starts with clear recognition of a performance gap. - Current condition: Briefly describe what is happening now in measurable terms. - Desired condition: Describe the target or requirement (internal goal, customer expectation, regulatory standard). - Gap: Clarify the difference between current and desired performance. Focus on facts, not solutions. At this stage, do not commit to a specific fix; demonstrate that a significant, well-defined problem exists. Strategic Alignment The business case must show how the project supports organizational priorities. - Link to strategic objectives such as: - Cost reduction - Revenue growth - Customer satisfaction - Compliance and risk reduction - Quality and reliability - Identify which key performance indicators (KPIs) will be affected. - Explain how the project supports: - Voice of the Customer (VOC) needs - Voice of the Business (VOB) requirements Alignment improves the likelihood of sponsorship, resources, and sustained interest. Quantifying the Problem and Opportunity A credible business case quantifies both the current loss and the potential gain. - Problem quantification may include: - Defect rates - Rework or scrap - Cycle time or lead time - Waiting time - Error rates - Service failures or complaints - Financial impacts typically include: - Direct costs (labor, materials, rework, warranty) - Indirect costs (delays, missed revenue, capacity loss) - Risk costs (penalties, legal exposure, brand damage) Use simple, transparent calculations: - Estimate current annual loss due to the problem. - Estimate realistic improvement (for example, a 20–40% reduction in key defects or delays). - Translate expected improvement into annual financial impact. Be conservative and base estimates on credible data, not speculation. Risk, Urgency, and Timing A persuasive business case explains why the problem must be addressed now. - Risks of inaction: - Increasing costs - Competitive disadvantage - Escalating customer dissatisfaction - Compliance or safety exposure - Time sensitivity: - Regulatory deadlines - Seasonal or market windows - Capacity constraints impacting planned growth Clarifying urgency helps decision-makers prioritize among competing initiatives. --- Core Elements of a Project Charter The project charter transforms the business case into a structured, executable project definition. It typically includes: - Problem Statement - Goal Statement - Project Scope - Business Case (brief, refined) - High-Level Timeline and Milestones - Team and Stakeholders - Constraints and Assumptions - High-Level Risks and Dependencies - Primary Metrics (Y) and Key Inputs (X’s, initially high level) Problem Statement The problem statement precisely describes the current issue without prescribing solutions. Effective problem statements are: - Specific: Focused on a defined process, product, or service. - Measurable: Include quantitative data (baseline performance). - Time-bounded: Refer to a clear period. - Non-judgmental: Neutral language, no blame. Example structure: - “From [start date] to [end date], [process] has experienced [issue], resulting in [impact metric] averaging [value and units], compared to the required [target or standard].” Avoid: - Mentioning root causes or solutions. - Vague language such as “often,” “usually,” or “many.” Goal Statement The goal statement defines the desired improvement and time frame. Strong goal statements are: - Outcome-focused: Centered on the primary performance measure (Y). - Quantified: Specify target level or percentage improvement. - Time-bound: Include a completion date. - Realistic: Achievable with selected scope and resources. Example structure: - “Reduce [metric] from [current value] to [target value] by [date], while maintaining or improving [critical related metric].” Include any guardrail metrics that must not worsen (for example, do not increase cost while reducing cycle time). Project Scope Scope defines what is inside and outside the project boundaries. Good scoping prevents “boiling the ocean” and scope creep. Define: - In-scope: - Processes, departments, products, sites, or customer segments included. - Time period of data and operations. - Out-of-scope: - Areas explicitly excluded to keep work focused. Use scope to: - Limit the problem to a manageable segment. - Ensure data access and process ownership are clear. - Align expectations with stakeholders and sponsors. When helpful, a simple high-level process view (start and end points) can clarify scope in words: - “From receipt of customer order to shipment confirmation email” vs. - “From initial marketing contact through customer payment collection.” Business Case (Charter Version) The charter restates a concise version of the business case tailored to the project definition. Include: - Brief description of the operational problem. - Key metrics currently at risk. - Estimated financial benefit or other quantified value upon success. - Link to strategic objectives and customer impact. This ensures every team member understands why the project matters. High-Level Timeline and Milestones The charter sets expectations for project pace and key checkpoints. Define: - Overall expected project duration. - Major phases and target completion dates. - Critical milestones, such as: - Completion of baseline data collection - Approval of analysis and recommendations - Implementation start and completion - Verification of benefits Timelines should be aggressive but realistic, considering data needs and stakeholder availability. Team and Stakeholder Definition The charter clarifies who is involved and how. Identify: - Sponsor: Person providing resources, removing barriers, and accepting results. - Process owner(s): Individuals responsible for the process in scope. - Core team members: Representatives from functions directly involved in the process or strongly affected by it. - Key stakeholders: Customers, suppliers, or support functions whose engagement is critical. Specify: - Expected time commitment for core team members. - Decision rights where appropriate (who approves changes, who is consulted). This reduces conflict later about authority and responsibilities. Constraints and Assumptions Constraints and assumptions define the conditions under which the project will operate. - Constraints: - Budget limits - Technology fixed during project - Mandatory compliance requirements - Policy or contractual constraints - Assumptions: - Data is accessible and reliable. - Current staffing levels remain stable. - Planned organizational changes will not remove core resources mid-project. Clearly documenting these: - Makes risks more visible. - Guides solution development within realistic boundaries. - Helps explain timeline and scope choices. High-Level Risks and Dependencies The charter summarises known risks and dependencies that could affect the project. - Risks may include: - Resistance to process changes - Competing initiatives consuming shared resources - Uncertain data quality - Possible changes in regulations or market conditions - Dependencies may include: - Availability of subject-matter experts - IT or engineering changes - Vendor actions or approvals For key risks, identify: - Likely impact on timeline, cost, or quality. - Early ideas for mitigation or contingency. --- Linking the Business Case to Project Metrics Primary Output Metric (Y) Every charter must identify the main performance measure that will define success. - Choose a single primary Y that: - Clearly reflects the core problem. - Can be accurately measured. - Is meaningful to customers or the business. - Typical examples: - Defect rate (DPMO, DPU, percentage defective) - Cycle time, lead time, or on-time performance - Cost per unit or per transaction - First-pass yield - Complaint rate The primary Y should be directly connected to the quantified business impact. Supporting Metrics and Trade-Offs Supporting metrics provide a complete view of project impact and guard against sub-optimization. - Supporting outcome metrics: - Related quality or service indicators affected by the main Y. - Process metrics: - Intermediate measures that reflect performance at key process steps. - Risk or compliance metrics: - Indicators that must not degrade as improvements are made. Define: - Which metrics must improve. - Which must be maintained or prevented from worsening (guardrails). Explicitly note major potential trade-offs, such as: - Reducing cycle time without increasing error rates. - Reducing cost without harming customer satisfaction. --- Crafting a Strong Problem and Goal Pair Common Pitfalls in Problem Statements Avoid: - Vagueness: “Our process is slow” instead of measured cycle times. - Solution bias: “We need a new system” rather than describing the performance issue. - Blame: “Operators do not follow procedures.” - Over-breadth: Trying to cover many processes or products in one statement. A refined problem statement focuses only on what can be measured and improved within the defined scope. Refining Goals for Clarity and Feasibility Check each goal against: - Relevance: Does it directly address the problem statement? - Measurement: Can progress be tracked with available data? - Feasibility: Is the target realistically achievable within the timeline and constraints? - Balance: Have secondary metrics been considered so that improvements do not cause hidden damage? If necessary, start with a range or minimum target and tighten later when baseline data and variation are better understood. --- Developing the Initial Project Plan from the Charter High-Level Work Plan The charter does not contain a full detailed plan, but it should outline a high-level structure to: - Gather and validate baseline data. - Understand the current process and variation. - Identify potential causes and prioritize them. - Develop, test, and implement solutions. - Validate and track benefits. This high-level path ensures the project remains disciplined and evidence-based. Review and Approval of the Charter Charter review and approval translate the document into a shared commitment. Key actions: - Present the business case, problem, and goal to the sponsor and key stakeholders. - Verify that: - Scope is acceptable and aligned with strategy. - Benefits justify the investment and effort. - Constraints and risks are understood and tolerated. - Agree on: - Decision-making structure. - Reporting cadence. - Criteria for success and closure. Only after this agreement should the project proceed into deeper analysis and solution work. --- Maintaining and Updating the Charter Charter as a Living Document As data is collected and analysis progresses, understanding of the problem may evolve. The charter must remain aligned with reality. Update the charter when: - Baseline measures differ significantly from initial estimates. - Scope must be narrowed or adjusted to stay feasible. - Goals are refined based on better data. - New constraints or risks emerge. - Stakeholder structure changes. Maintain version control and ensure all key stakeholders are aware of meaningful changes. Controlling Scope Changes Uncontrolled scope expansion can undermine timelines, benefits, and clarity. To manage scope: - Evaluate proposed additions against: - Strategic alignment. - Business case impact. - Resource and time availability. - If new areas are essential: - Consider splitting into separate projects. - Revisit goals, timeline, and resources formally. - Update charter and obtain renewed approval where needed. Disciplined scope control preserves project focus and credibility. --- Summary A well-constructed business case and project charter ensure that improvement work addresses important, quantifiable organizational problems in a focused and disciplined way. - The business case defines why the project matters by: - Describing the performance gap. - Quantifying operational and financial impact. - Demonstrating strategic alignment and urgency. - The project charter defines how the project will proceed by: - Stating a precise problem and measurable goal. - Setting clear scope, boundaries, and timeline. - Identifying metrics, stakeholders, constraints, risks, and dependencies. Treat the charter as a living agreement that is reviewed, refined, and maintained throughout the project. Mastering the creation and use of a robust business case and project charter is essential for launching improvement projects that are strategically aligned, measurable, and capable of delivering sustained benefits.