Question Assumptions - Build from Fundamentals

Instead of copying what others do, break problems down to their most basic truths.

Student Example

Analogy Thinking: "Everyone studies late at night, so I should too."

First Principles: Ask foundational questions:

• When do I actually focus best?
• What does research say about sleep and memory?
• What's the actual goal? (Knowledge retention, not just hours spent)

Conclusion: Study when YOUR brain works best, not when others study.

Professional Example

Analogy: "Competitors use this feature, so we should too."

First Principles:

• What problem are we trying to solve?
• What do our specific customers need?
• What resources and capabilities do we have?

Conclusion: Build what solves YOUR customers' problems, not a copy of competitors.

The Process

1. Identify the problem or goal
2. Break it down to fundamental truths
3. Rebuild the solution from those truths
4. Ignore "how it's always been done"

Why It Matters

First principles thinking leads to innovation. Copying leads to commoditization.

Every Action Has Consequences, and Those Have Consequences

Most people stop at first-order thinking (immediate results). Winners think second and third-order.

Student Example

Decision: Skip class to finish an assignment

First-Order Effect: Assignment gets done (good!)

Second-Order Effect: Miss important lecture material

Third-Order Effect: Struggle on exam, spend more time studying later, more stress

Outcome: Short-term gain, long-term pain.

Professional Example

Decision: Automate customer support to cut costs

First-Order: Save $100K annually (good!)

Second-Order: Customers frustrated with automated responses

Third-Order: Customer churn increases, negative reviews spread

Fourth-Order: Lost revenue exceeds the $100K saved

Outcome: Penny wise, pound foolish.

How to Practice

Before making a decision, ask:

• "And then what?"
• "And then what?"
• "And then what?"

Keep asking until you've mapped out the ripple effects.

The Skill

The best decisions optimize for second and third-order effects, not just immediate outcomes.

Instead of "How Do I Succeed?" Ask "How Would I Definitely Fail?"

Inversion helps you identify and avoid critical mistakes.

Student Example

Traditional Question: "How do I get an A in this course?"

Inverted Question: "How would I definitely fail this course?"

Inverted Answers:

• Never attend class
• Skip all assignments
• Don't study for exams
• Ignore the syllabus

Action: Make sure you NEVER do these things. Success follows.

Professional Example

Traditional: "How do we make this project succeed?"

Inverted: "How would this project definitely fail?"

Inverted Answers:

• Unclear requirements
• No stakeholder buy-in
• Unrealistic timeline
• Poor communication

Action: Build safeguards against each failure mode.

Why Inversion Works

• Failures are often easier to identify than successes
• Avoiding disaster is sometimes more important than chasing perfection
• It reveals blind spots in planning

Application

Before starting any major endeavor, spend time on "pre-mortem": assume it failed, and work backwards to why.

Keep Asking "Why?" to Find the Real Problem

Surface-level symptoms often hide deeper root causes. The Five Whys technique helps you dig deeper.

The Method

Start with a problem. Ask "Why did this happen?" Then ask "Why?" about that answer. Repeat five times.

Example: Failed Product Launch

Problem: Product launch failed.

Why? Marketing campaign didn't reach target audience. Why? We used the wrong channels. Why? We didn't research where our audience spends time. Why? We skipped customer research to save time. Why? Project was rushed due to unrealistic deadlines.

Root Cause: Unrealistic project timeline forced shortcuts that doomed the launch.

The Insight

Fixing "marketing channels" (third layer) treats symptoms. Fixing "project timeline management" (fifth layer) prevents future failures.

When to Use

• Post-mortems on failures
• Recurring problems
• When quick fixes don't stick
• Before assigning blame

Important Note

Sometimes you hit the root in 3 whys, sometimes it takes 7. The number "five" is a guideline, not a rule. Stop when you've found a root cause you can actually address.

Most Decisions Involve Uncertainty - Embrace It

Absolute certainty is rare. Learn to think in probabilities and confidence levels.

The Shift

Old Thinking: "This will definitely work."

Probabilistic Thinking: "Based on available data, there's an 80% confidence this will work, with these known risks..."

Why It Matters

1. Honesty: Acknowledges uncertainty
2. Better Decisions: Forces you to identify risks
3. Adaptability: You're prepared when the 20% happens

How to Apply It

Student Example: "I'm 90% confident I'll finish this project on time, assuming no major obstacles. The 10% risk factors are: unexpected bugs, sick days, or scope changes."

Professional Example: "This marketing strategy has a 70% chance of increasing conversions by 20%, based on pilot data. Risk factors include: seasonal variations, competitor responses, and budget constraints."

The Framework

1. State your confidence level (60%? 80%? 95%?)
2. Identify what would need to be true for the higher probability
3. List the main risk factors
4. Plan for the scenarios where you're wrong

Calibration

Track your predictions. If you're right 80% of the time when you say "80% confident," you're well-calibrated. If not, adjust.