Problem Solving Manual (6): Prioritize & Plan

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 fluctuations. Instead, we heavily prioritize the total customer count, because it sits at the intersection of high impact and high internal control.

Applying the Pareto Principle

Issue prioritization relies heavily on the Pareto Principle (the 80/20 rule). In any complex challenge, roughly 20% of the root causes drive 80% of the negative symptoms. Conversely, 20% of your strategic actions will generate 80% of your profit recovery. Prioritization forces you to identify and isolate these "vital few" high-leverage initiatives—such as a combined menu refresh and local promotion—while letting go of the trivial many.

Step 4: Plan the Analysis (Building the Workplan)

A gold-standard rule of elite problem solving is this: never start analyzing data until your hypotheses are firmly formed. Unguided data mining is a massive time sink. The workplan translates your prioritized hypotheses into specific, time-bound tasks.

1. Knock-Out Analysis

Before designing long-term data collection tasks, run a "knock-out analysis" on your critical hypotheses. This means testing your boundaries early to immediately eliminate solutions that violate hard constraints. For example, if a hypothesis suggests completely shutting down operations for a two-week interior remodel, your knock-out check immediately kills the idea because it violates the absolute constraint of keeping the doors open daily and capping expenses at 20 million IDR.

2. Dummying the Expected Output

Before gathering data, draw out your expected results. Create "dummy charts"—empty graphs with rough layouts, mock tables, and placeholder structures. Visualizing the final output tells you exactly what data you actually need to fetch and prevents you from gathering useless information.

3. Clear Operational Mechanics

A professional workplan must be highly explicit. It maps every single hypothesis to a data gathering task, assigns a specific person within the team, establishes a firm deadline, and defines the expected artifact. This document must be constantly revised as early insights alter your direction.

The Core Elements of an Iteration Loop

Formulating Strong Hypotheses

When drafting your workplan, ensure your hypotheses are stated as strong, definitive claims rather than vague themes. Write "Customer volume dropped 30% because our pricing is uncompetitive relative to new entries," instead of "Let's look at competitor pricing." A strong, bold claim is much easier to stress-test, challenge, and cleanly disprove with data.

The "One-Day Answer" Structure

To maintain absolute clarity during rapid iteration, the team must anchor their current progress using a standardized three-part framework:

Situation: The objective, unchanging baseline reality of the client or business.
Observations / Complications: The critical triggers, data points, or competitive dynamics that are breaking the system.
Implications / Resolutions: The immediate, high-leverage actions required to bridge the gap.

Cognitive Biases in Problem Solving

Even with a structured framework, human teams are highly prone to psychological traps. Recognizing these core biases is essential to prevent flawed data interpretation:

Confirmation Bias: The tendency to look only for data that validates your pre-existing beliefs while ignoring conflicting evidence.
Example: A consultant is convinced that Instagram marketing is the magic cure. They obsessively track the 5 younger customers who mentioned seeing a post, while completely ignoring data from 50 older neighborhood regulars who do not even own smartphones.
Anchoring Bias: Getting over-indexed or emotionally stuck on the very first piece of data you discover.
Example: Finding an invoice showing wholesale chicken prices jumped 18%, and immediately blaming the entire 25% profit collapse on chicken costs—failing to see that the broader problem is a massive drop in total foot traffic across all menu items.
Loss Aversion Bias: The psychological tendency to fear a loss far more than valuing an equivalent gain.
Example: Dian flatly refuses to remove a historical recipe from the menu that only sells once a week. He hates the feeling of "losing" an original family item, ignoring the fact that keeping its specialized ingredients fresh is quietly bleeding cash.
Availability Bias: Overestimating the weight of a problem based entirely on a highly recent, vivid, or dramatic event rather than long-term statistical trends.
Example: A floor manager panics and says, "The new competitor is completely destroying us because I saw a massive line outside their door last Friday night!"—even though a look at the data shows their weekday lunch traffic is completely dead.
Overoptimism Bias: Holding unrealistic expectations about how easy a solution is to execute or how fast it will yield results.
Example: Assuming that publishing a single organic Instagram post will instantly cause an immediate 30% surge in premium weekend dinner bookings.

Mitigating Bias Through Team Dynamics

To stay agile and realistic, you must remain highly flexible. When hard data contradicts a hypothesis, a great problem solver abandons the hypothesis immediately, using the insight to hunt for breakthrough thinking rather than settle for safe, incremental improvements.

The Equal Team Safeguard: The single most effective defense against cognitive bias is building a diverse team made up of individuals with entirely different mental models. However, structure alone is not enough; the team must foster a culture of radical equality where flat hierarchies are the norm. Team members must feel safe to aggressively challenge ideas, question senior assumptions, and pressure-test facts without fear of friction.

nugistic