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 successful resolution look like? How will it be measured?
  • Constraints: What are the boundaries, limitations, or non-negotiables (time, budget, resources)?
  • Actors: Who can influence the outcome or will be impacted by the solution?

2. Structure the Problem

Disaggregate the problem by breaking it down into smaller, manageable parts using logic trees. When structuring, aim for the following principles:

  • Apply the MECE principle (Mutually Exclusive, Collectively Exhaustive) to ensure your sub-problems do not overlap and that no gaps are left behind.
  • Leverage existing analytical frameworks (like financial or operational models) when they serve your specific goal.
  • Focus on structures that generate the deepest insight rather than just neat categorization.

3. Prioritize

You cannot solve everything at once. Identify the critical path by focusing on areas most likely to lead to a major resolution, keeping the Pareto Principle (the 80/20 rule) in mind. Assess each branch based on its potential size of impact and your ability to influence it. Once prioritized, turn your most critical branches into testable hypotheses.

4. Plan the Analysis

Build an explicit workplan to turn your logic trees and hypotheses into action. Your workplan must assign specific analysis tasks and fact-gathering assignments, detailing the exact method, required data, individual responsibilities, and the expected output.

5. Analyze

Execute your workplan to gather facts and test your hypotheses. Always start with simple heuristics—quick thumb-rules and basic math—to see if an idea holds weight. Only deploy advanced analytical tools and complex data techniques when the problem genuinely demands them.

6. Synthesize

Gather your individual findings, test their validity against each other, and assemble them into a logical, cohesive explanation. Move past just summarizing data; your goal here is to answer the ultimate "So What?" to create an action-oriented resolution.

7. Communicate

Develop a compelling storyline from your solutions, linking your final recommendations directly back to your original problem statement. When presenting your results to decision-makers, ensure you:

  • Lead with the answer first (do not make them wait until the conclusion).
  • Organize your arguments using a top-down pyramid structure.
  • Use the SCQA (Situation, Complication, Question, Answer) framework to anchor your main narrative line.
  • Back every conclusion with transparent arguments and solid evidence.

The Power of Iteration

The "One-Day Answer": Problem solving is an iterative loop. At any given moment, you should maintain a "one-day answer"—your absolute best current explanation and recommendation based on whatever information you have right now. This serves as a live baseline that evolves as you learn.

As new insights surface, you must be ready to cycle back: redefine the problem boundary, restructure parts of your logic tree, or run a new analysis method. Whenever possible, work within a team environment; collaborating with others is the single most effective way to challenge assumptions and eliminate cognitive bias during iteration.

Mini Case Study: The 7 Steps in Action

The Problem: The family-owned restaurant "Gia Pizza" has experienced a sudden 25% drop in monthly profit over the past six months.

Step 1: Define the Problem (TOSCA Framework)

  • Trouble: Monthly profit has dropped 25% in the last six months, threatening the business’s survival and the family’s core livelihood.
  • Owner: Dian (the restaurant owner) along with her family.
  • Success criteria: Restore monthly profit back to baseline (or higher) within 3 to 4 months in a sustainable way.
  • Constraints: Extremely limited budget for changes; cannot close the restaurant even for a single day; must retain all existing staff.
  • Actors: Regular and lost customers, staff, suppliers, new competing restaurants nearby, and working family members.

Refined Core Question: What is causing the profit decline at Gia Pizza, and what are the most effective, low-cost actions to reverse it quickly and sustainably?

Step 2: Disaggregate

We break the restaurant's operational reality down into four structural components:

  • Revenue factors: Total number of customer visits, average spending bill per transaction.
  • Cost factors: Food ingredients, labor overhead, utilities, rent.
  • Customer experience: Menu variety, food consistency, speed of service, physical ambiance.
  • External factors: New competitor marketing, location foot traffic, broader market economic trends.

Step 3: Prioritize

Based on initial impact potential, we isolate three critical paths and form a core hypothesis:

  1. Decline in total customer traffic.
  2. Rising raw food ingredient costs.
  3. Menu attractiveness and relevance.

Working Hypothesis: The profit drop is primarily driven by a significant decline in customer traffic due to aggressive new competition and an outdated menu, compounded heavily by unmanaged ingredient cost inflation.

Step 4: Plan the Analysis (2-Week Quick Diagnosis)

The team sets up a rapid workplan to gather facts:

  • Extract and analyze POS sales and invoice cost data from the past 8 months.
  • Observe floor operations and interview family members and staff.
  • Run a brief intercept survey with current customers and call a few lapsed regulars.
  • Conduct a competitive analysis by visiting the new nearby pizza spots.

Step 5: Analyze

The investigation reveals the following clear facts:

  • Daily customer count has fallen by approximately 30% since two trendy competitors opened nearby.
  • Average bill size has dropped slightly because customers are avoiding outdated, high-margin signature dishes.
  • Ingredient purchase costs jumped 18% due to wholesale inflation and a lack of recent supplier price negotiations.
  • The menu has not been updated in over two years, lacking modern options.
  • Marketing efforts are zero; the restaurant relies entirely on old word-of-mouth.

Step 6: Synthesize

The core driver of the profit crisis is top-line revenue erosion: Gia Pizza is losing its customer volume to modern competitors because its menu feels dated. While rising inflation on ingredients makes the situation worse, solving the traffic problem offers far higher leverage than simple cost-cutting. The brand still retains solid local goodwill and high service scores, meaning a revenue turnaround is highly viable.

Step 7: Communicate & Recommend

The Strategic Recommendation: To reverse the 25% profit decline within 90 days, Gia Pizza must immediately launch a revenue-recovery strategy centered on menu modernization and targeted local promotions, while renegotiating raw material costs.

Action Plan:

  1. Revamp the Menu: Cut the bottom 20% slow-moving items and introduce 4 to 5 highly attractive, high-margin modern dishes within 3 weeks.
  2. Launch Volume Promotions: Run a targeted 6-to-8-week value combo promotion to rapidly pull lapsed customers back through the doors.
  3. Supplier Renegotiation: Consolidate purchasing and renegotiate terms with vendors to slash food costs by 8% to 10% without sacrificing quality.
  4. Organic Social Push: Launch a simple, zero-cost Instagram campaign showcasing the new dishes and community promotions.

Next Steps: Finalize the new menu specs by Wednesday, hold supplier meetings on Thursday, and go live with the promotions next weekend.

Comments

Post a Comment

Popular posts from this blog

Problem Solving Manual (1): Table of Contents

Problem Solving Manual: Master Table of Contents About This Book: The Strategic Imperative Welcome to the Problem Solving Manual . This book is a rigorous, practical blueprint designed to bridge the gap between complex analytical problem-solving and real-world execution. Whether you are navigating high-stakes business environments, launching independent entrepreneurial ventures, or engineering a profound personal turnaround, raw willpower and emotional intuition are highly unreliable assets. True momentum is built on structural logic. Across our core operational sections, this volume deconstructs elite problem-solving methodologies—derived from management consulting frameworks and systems engineering—into repeatable, scannable steps. Every page strips away vague corporate jargon, substituting it with concrete tools, logical decision matrices, and quantitative tracking parameters. This digital edition is fully hyperlinked to allow seamles...
Read more

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 ...
Read more

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...
Read more