Problem Solving Manual (4): Define

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 trouble and make the final call on solutions. When a problem is complex and spans multiple departments, it is often best to frame the analytical thinking from the perspective of a single, primary owner at the highest relevant level of the organization.

Crucially, you must account for the owner's underlying values and non-negotiables. If the owner's personal or corporate values dictate that they absolutely will not lay off employees or compromise consumer trust, any solution that suggests firing staff to cut costs is a non-starter. Understanding these values early saves weeks of misaligned work.

3. Success Criteria

Success criteria outline exactly what a successful resolution looks like, including a hard deadline. This component must be specific, measurable, and highly accurate. Rather than saying "we want to make more money soon," define it mathematically: "Recover 100% of the lost profit within 3 to 4 months."

Defining success sets the scale of aspiration, which dictates how rigorous and radical the problem-solving effort must be:

Low Aspiration: Recovering only 70% of lost profit might just require minor cost-cutting.
Medium Aspiration: Recovering 100% of lost profit might require a partial menu revamp and a supplier re-negotiation.
High Aspiration: Pushing to exceed historical profits by 20% would demand a complete business model transformation or geographic expansion.

4. Constraints

Constraints are the concrete boundaries and hard limits placed on your problem-solving canvas. They fall into three distinct categories:

Constraints on the success criteria: Hard quality requirements that the outcome must respect (e.g., "Must restore profit margins without sacrificing raw food ingredient quality.")
Constraints on the solution: Strategic paths or execution methods that are completely off the table due to capital or positioning (e.g., "Cannot compete on price with massive corporate restaurant chains; cannot relocate the physical storefront; cannot implement any solution costing more than 20 million IDR.")
Constraints on the problem-solving process: Structural limits on your timeline and resources (e.g., "The complete, data-backed action plan must be finalized within exactly 2 weeks.")

5. Actors

Actors are the internal and external stakeholders who hold a vested interest in the situation or possess the power to influence your results. Mapping these actors via a Power-Interest Matrix ensures you manage organizational politics and operational friction proactively.

Taking Gia Pizza as our operational baseline, the matrix maps out like this:

Stakeholder Segment	High Interest	Low Interest
High Power	Dian & Family (Owners) Strategy: Manage closely. They hold total decision authority and their livelihood is at stake.	Key Wholesale Suppliers Strategy: Keep satisfied. They hold the power over your ingredient costs, but your internal restaurant crisis doesn't alter their core business model.
Low Power	Loyal Customers & Kitchen Staff Strategy: Keep informed and protected. They are highly impacted by operational changes but don't hold executive signing power.	General Street Passersby Strategy: Monitor passively. They represent potential future traffic but currently have no skin in the game.

Advanced Framing Techniques

Challenging the Thesis with Counterfactuals

Great problem solvers do not accept initial narratives blindly. They rigorously stress-test their problem definitions using counterfactuals and antithetical reasoning to uncover hidden biases before building logic trees.

The Antithesis: Force yourself to argue the exact opposite assumption. "What if the 25% profit drop is actually NOT caused by the new competitors down the street, but by a recent, unnoticed slide in our own kitchen's food quality?"
The Counterfactual: Isolate variables across time. "If those two new competitor restaurants had never opened up across the street, would Gia Pizza's profits still have dropped over the last six months due to broader economic inflation?"

Porpoising into Data

Do not stay cooped up in pure abstract strategy for too long. Effective definition requires you to "porpoise"—dipping rapidly down into quick, accessible pools of data to check your initial assumptions, and then surfacing back up to refine and sharpen your problem statement based on what you saw.

Empathizing with Human-Centric Design

When a problem is highly complex, unpredictable, and deeply intertwined with the human experience, pure spreadsheet data is not enough. You must actively deploy empathy and design-thinking methodologies to understand the emotional realities of your actors.

Immersive Observation: Step out from behind the manager's desk. Conduct brief, structured interviews and observe 20 regular customers in real-time. This reveals insights data aggregations miss: "Many regular diners state the menu feels old and boring; they crave modern flavor profiles, and admit they are drawn to the competitor's highly photogenic, Instagram-friendly plating."
Become the Customer: Undergo the complete service process yourself end-to-end. Walk through the front door as an anonymous diner, wait for a table, order off your own menu, evaluate the pacing of the kitchen staff, and pay the final bill. Experiencing the system's friction firsthand exposes the real operational bugs holding your business back.

nugistic