Posts

Problem Solving Manual (9): Master Case Study

The Master Case Study: The Complete Problem-Solving Lifecycle of Gian Context & Background: A Real Life Turnaround To fully anchor the 7-step problem-solving methodology, we explore the personal case of Gian, a professional in his late 20s. Gian is highly organized and naturally ambitious, but spending years within a stable, comfortable corporate role gradually dulled his drive, slipping him into a deep lifestyle comfort zone. When an unexpected corporate layoff struck, the sudden shock triggered depression and a complete loss of direction. For several weeks, Gian found himself living without a purpose—sleeping all day, staying up all night playing video games, isolating himself from friends, and avoiding his family. Recognizing that he was wasting a pivotal period of his life, Gian decided to stand up and systematically apply the exact problem-solving principles he mastered to map out an ironclad path forward. He holds no current in...

Problem Solving Manual (8): Synthesize & Communicate

Steps 6 & 7: Synthesize and Communicate Step 6: Synthesize (Answering the "So What?") Synthesis is not a summary. A summary merely repeats the facts you found; a synthesis assembles individual analytical pieces to extract a higher-level insight that answers the ultimate question: "So What?" Your mode of reasoning must evolve as you move through this stage. You shift from looking backward at past implications toward looking forward at reasons to drive action. For example, consider this synthesis progression: The Summary: Data shows customer traffic is down 30% and ingredient prices are up 18%. The "So What?" Synthesis: Traffic erosion to modern competitors is our primary problem. Therefore, we must aggressively act on top-line revenue recovery through product and marketing updates first, rather than relying on pure operational cost-cutting. A great sy...

Problem Solving Manual (7): Analyze

Step 5: Analyze The Architecture of Objective Analysis The analysis stage is the bedrock of objectivity in problem solving. Its primary purpose is to determine the exact scale or magnitude (how influential a variable is) and the direction (increasing or decreasing) of the problem's core levers. By substituting vague opinions with hard data, analysis either confirms or disconfirms the hypotheses generated during disaggregation. In our Gia Pizza baseline case, establishing the magnitude and direction of key levers prevents the team from executing wrong solutions: Customer Traffic: –30% (Largest negative lever—Primary Core Problem) Food Ingredient Costs: +18% (Medium negative lever—Secondary Friction) Average Transaction Bill: –8% (Small negative lever—Minor Symptom) Promotion Potential: +25% to +40% possible volume uplift (Biggest positive recovery lever) ...

Problem Solving Manual (6): Prioritize & Plan

Steps 3 & 4: Prioritize and Plan the Analysis Step 3: Prioritization (Pruning the Logic Tree) A comprehensive logic tree maps every possible factor, but you cannot chase every branch. Prioritization is the deliberate act of pruning your logic tree—cutting away the low-leverage branches to focus your limited time and energy on what truly moves the needle. The Solution Prioritization Matrix To determine which branches to keep and which to cut, evaluate each sub-problem or candidate solution against two primary dimensions: Potential Scale of Impact: How much will solving this specific branch contribute to the ultimate success criteria? Ability to Influence: Do we possess the operational power, capital, and authority to change this variable, or is it completely out of our control? In the case of Gia Pizza, we deprioritize uncontrollable macroeconomic trends or rent fluctuati...

Problem Solving Manual (5): Disaggregate

Step 2: Disaggregate The Purpose of Disaggregation Disaggregation is the process of breaking a complex problem down into its component parts to find the specific levers of solution. By mapping the entire problem space, you can identify the critical path —the specific branches of the problem that hold the highest leverage and yield the most impactful resolutions. The primary tool for this step is the logic tree . To ensure your logic tree is structurally sound, aim for your branches to be MECE (Mutually Exclusive, Collectively Exhaustive). This means your sub-categories should not overlap, and when taken together, they must cover the entire problem space with no gaps left behind. Types of Logic Trees Great problem solvers do not rely on just one type of tree; they build and iterate on multiple structures to discover which perspective yields the deepest operational insights. 1. Deductive Logic Trees ...

Problem Solving Manual (4): Define

Step 1: Define the Problem The Architecture of a Problem Statement A problem well-stated is a problem half-solved. To build a rigorous definition that prevents wasted resources, we look deeply at each component of the TOSCA framework, examining how to push beyond vague issues into actionable clarity. Deep Dive: The TOSCA Components 1. Trouble The trouble is the fundamental gap between an observation (what is actually happening) and an aspiration (what we want to happen). To be useful, trouble must never be vague; it requires strict specificity. For example, instead of stating "sales are down," a precise definition states: "Gia Pizza has experienced a 25% drop in monthly profit over the past six months." Specificity anchors the entire project team to an objective reality. 2. Owner The owner is the individual or core group whose job it is to take care of the troubl...

Problem Solving Manual (3): Quick Start Guide

Quick Start Guide The 7-Step Problem-Solving Process The 7-Step process is a systematic, universal framework designed to solve nearly any type of problem. It is both comprehensive and highly iterative. You do not need perfect data to begin; you can run through a complete cycle at any time using the information currently at hand. As you gather more data and your understanding deepens, you simply repeat and refine the steps. Summary of the 7 Steps 1. Define the Problem Before rushing to find solutions, you must ensure the problem is clearly and explicitly defined. A weak problem statement leads to wasted effort. To build a sharp, unshakeable definition, use the TOSCA framework: Trouble: What is the core symptom or pain point triggering this need? Owner: Who is responsible for making the final decision or solving this? Success criteria: What does a succes...