Phase 1: Diagnosis (Defining the Problem)
Jumping straight to the first obvious solution usually creates two new problems. You must learn to distinguish between the symptom and the disease, drill down to the root cause, and respect the history of legacy processes before destroying them.
Skill 1: The Einstein Rule
"If I had an hour to solve a problem, I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions." Proper problem framing prevents wasted execution.
Skill 2 & 3: Root Causes & Fences
The 5 Whys: A Toyota framework for drilling past superficial answers.
Chesterton’s Fence: Never tear down a fence until you understand why it was built. Understand the history of a process before proposing to "disrupt" it.
Phase 2: Data & Evidence
"Torture the data long enough, and it will confess to anything." Basic data literacy is mandatory to prevent confirmation bias and to spot manipulated reporting before you base a strategy on it.
Skill 4: When Numbers Lie
Understanding the lethal difference between Correlation and Causation. Just because two trends move together does not mean one causes the other. They are often driven by a hidden third variable.
Skill 5: Overcoming Confirmation Bias
Use the "Steel Man" technique: Actively seek out and construct the strongest possible arguments against your own proposed solution.
Example: Ice cream sales do not cause shark attacks. Both are caused by Summer Heat (The hidden variable).
Phase 3: Solution Design
Once the problem is defined and data is verified, you must design a solution using Skill 6: First Principles Thinking (breaking complex problems down to undeniable truths) and calculating the actual business impact.
Skill 8: Second-Order Thinking
Every action has a consequence (First-Order). Every consequence has a subsequent consequence (Second-Order). Map out the ripple effects so you don't accidentally break another department's workflow.
Fix the Bug
UI Changes
Customer Support Overload
Skill 7: Cost-Benefit Analysis (CBA)
You have a great idea, but is it worth the money and time? Calculate ROI and acknowledge "Opportunity Cost" (what are we not doing because we are doing this?).
Phase 4: Execution & Pitching
A brilliant solution is worthless if you can't sell it or if it fails upon launch. Use Skill 9: The Pre-Mortem to mitigate risks, and Skill 10: The Minto Pyramid to pitch it to busy executives.
Skill 9: The Pre-Mortem
Before launching, assume it is exactly one year later and the project was a catastrophic failure. Why did it fail? Use this pessimistic framework to identify blind spots before you spend any money.
Project X Failed.
Identify all reasons why this hypothetical failure occurred, then build mitigations into today's plan.
Skill 10: The Minto Pyramid
Executives do not want a chronological story of your research. Structure your argument top-down: Ultimate Answer first, Supporting Arguments second, Raw Data last.