Problem Solving

Life is a series of problems. Your grades are slipping. Your car won’t start. Your roommate won’t clean up. Your girlfriend is mad. Your boss is demanding. Your budget doesn’t balance.

Most people just react: panic, guess, try random solutions, blame others, or give up. That’s exhausting.

Better approach: learn how to actually solve problems. Not just specific problems, but problems in general. It’s a meta-skill that compounds across every area of your life.

This isn’t about being smarter. It’s about being more systematic. The best problem solvers aren’t geniuses, they just have frameworks.

The Biggest Mistake: Jumping to Solutions

Here’s what most people do when they hit a problem: immediately start trying solutions without understanding what they’re solving.

“My grades are bad” → “I’ll study more”

Except maybe the problem isn’t study time. Maybe it’s:

• You’re studying the wrong material
• You’re not sleeping enough so you can’t retain information
• You’re in the wrong major and deeply unmotivated
• You have ADHD and need treatment
• You’re working 30 hours a week and don’t have time

Studying more doesn’t fix any of those root causes.

The first and most critical step is defining what you’re actually trying to solve.

The Universal Problem-Solving Framework

This works for everything from “why won’t my code compile” to “should I break up with my girlfriend.”

1. Define the Problem

Get specific. “I’m stressed” is not a problem definition, it’s a symptom.

Ask:

• What specifically is wrong?
• When does it happen?
• How do I know it’s a problem?
• What would success look like?

Example: Not “my finances are a mess” but “I overdraft my checking account twice a month because I spend my paycheck in the first week and have no emergency fund.”

2. Break It Down

Big problems are overwhelming. Break them into smaller pieces.

If your car won’t start, that breaks down into:

• Is the battery dead?
• Is there gas in the tank?
• Did the starter fail?
• Is there a fuel pump issue?

Each of those is testable. The big vague “car won’t start” is not.

3. Gather Information

Research. Ask people who’ve solved this before. Google it. Read the manual. Look at data.

Don’t reinvent the wheel. Someone has probably solved your exact problem already.

4. Generate Multiple Solutions

Come up with at least three options. If you only have one solution, you’re not really choosing, you’re just doing the first thing that came to mind.

5. Evaluate Options

List the pros and cons. What are the costs? What are the risks? What’s the time investment?

Sometimes the best solution is expensive or hard. Sometimes it’s surprisingly simple.

6. Test and Implement

Pick the best option and try it. Start small when possible. Test your solution before fully committing.

If you think the problem is your study environment, try studying at the library for a week before you redecorate your entire room.

7. Review and Adjust

Did it work? Why or why not? What did you learn?

Even failed solutions teach you something. Adjust and try again.

Proven Techniques

These are frameworks used by everyone from military commanders to engineers to therapists. They work.

OODA Loop

Developed by fighter pilot John Boyd. It’s how you make decisions faster than your opponent (or faster than your competition, or just faster than your problems compound).

OODA = Observe, Orient, Decide, Act

1. Observe - What’s happening? Gather data.
2. Orient - Analyze based on your experience and context. What does this mean?
3. Decide - Pick a course of action.
4. Act - Do it.

Then loop back to Observe. Did it work? What changed? Adjust.

Example: You’re losing money every month.

• Observe: I overdraft twice a month, spend $400/month eating out, only make $1,800/month after taxes
• Orient: I’m spending more than I make, eating out is the biggest unnecessary expense
• Decide: Cut eating out to $100/month, cook at home
• Act: Meal prep on Sundays, pack lunch every day
• Observe again: I saved $300 this month but I’m miserable and about to quit
• Orient again: I cut too hard too fast, need middle ground
• Decide again: $200/month eating out, 2-3 times a week
• Act again: More sustainable
• Observe again: Still saving $200/month, not miserable

The loop lets you adjust fast instead of committing to a bad plan.

PDCA Cycle

Japanese manufacturing framework for continuous improvement. Toyota uses this.

PDCA = Plan, Do, Check, Act

1. Plan - Identify the problem and create a plan to fix it
2. Do - Implement the plan (often as a small test first)
3. Check - Measure the results. Did it work?
4. Act - If it worked, standardize it. If not, adjust and try again.

This is great for iterative improvement over time.

Example: You want to improve your bench press.

• Plan: Add 5 extra sets of tricep extensions twice a week (weak triceps are limiting you)
• Do: Run it for 4 weeks
• Check: Bench press went up 10 lbs
• Act: Keep the tricep work, now test adding chest flyes

Each cycle makes incremental improvements.

Five Whys

Root cause analysis. Ask “why” five times to dig past the surface problem.

Example:

Problem: My car won’t start.

• Why? The battery is dead.
• Why? The alternator isn’t charging it.
• Why? The alternator belt is broken.
• Why? The belt was old and cracked.
• Why? I never checked it during maintenance.

Real problem: I’m not doing preventative maintenance. Fixing that prevents the problem from happening again. Just jump-starting the car (surface solution) doesn’t fix anything long-term.

Five Whys digs to the root cause.

First Principles Thinking

Don’t accept “because that’s how it’s done.” Break problems down to fundamental truths and rebuild from there.

Elon Musk is famous for this. When he wanted to build rockets, everyone said they cost $65 million. He asked “what are rockets made of?” Aluminum, titanium, copper, carbon fiber. He looked up commodity prices for those materials - about $2 million worth.

The gap between $2M in materials and $65M in rockets is inefficiency, legacy processes, and markup. He decided to build them himself.

How to use it:

1. Identify the problem
2. Break it down to fundamental truths (what do we know for sure?)
3. Rebuild the solution from those truths without assuming inherited wisdom

Example: “College is too expensive, so I’m going into debt.”

• Question the assumption: Do you need college? What do you actually need?
• First principles: I need skills employers will pay for
• Rebuild: Trade school teaches those skills in 2 years for $15k. Military teaches them and pays me. Self-taught + portfolio proves skills with no tuition. Apprenticeships pay while learning.

First principles thinking finds options you didn’t know existed.

Rubber Duck Debugging

Programmers use this. When you’re stuck on a bug, explain your code line-by-line to a rubber duck on your desk.

Sounds stupid. Works constantly.

Why it works: Explaining forces you to articulate your assumptions. Usually halfway through explaining, you realize your mistake.

You don’t need a rubber duck. Use a friend, your dog, a wall, yourself in the mirror.

Example: “I’m broke and I don’t know why.”

Explain it out loud: “I make $2,000 a month. Rent is $800. Car payment is $350. Insurance is $150. Phone is $100. Food is… wait, I’ve been spending $600 on food? That’s 30% of my income. Found the problem.”

Working Backwards

Start with your goal. Then ask “what needs to be true right before I achieve this?” Then work backwards step by step.

Example: Goal - Get an internship at Tesla.

• Right before that: Have an offer from Tesla
• Right before that: Ace the interview
• Right before that: Get the interview
• Right before that: Have a resume they notice
• Right before that: Have projects that demonstrate skills they need
• Right before that: Learn what skills they need
• Right before that: Research Tesla’s engineering stack

Now you have a roadmap. Start at the beginning.

Types of Problems

Not all problems are the same. Your approach should match the problem type.

Technical Problems

Car won’t start. Computer won’t boot. Math homework doesn’t make sense.

Characteristics:

• Usually has a right answer
• Research helps
• Experts exist
• Repeatable solutions

Approach: Gather information, test hypotheses systematically, ask experts.

Interpersonal Problems

Roommate conflict. Girlfriend is upset. Boss is demanding.

Characteristics:

• Multiple valid solutions
• Emotions matter
• Communication is key
• Context-dependent

Approach: Listen first, understand their perspective, find compromise, focus on long-term relationship.

Life Decisions

Which major? Which job? Which city? Should I get married?

Characteristics:

• No single right answer
• Depends on your values
• Long-term consequences
• Trade-offs required

Approach: Clarify your values first, list pros and cons, consider multiple futures, accept uncertainty, make a choice and commit.

When to Ask for Help

You don’t have to solve everything alone. Ask for help when:

1. Someone has solved this before - Don’t reinvent the wheel. If your car is broken, ask a mechanic. If you’re depressed, ask a therapist.
2. You’re stuck after trying multiple approaches - Spinning your wheels for hours is inefficient. Ask.
3. The stakes are high - Legal trouble, health issues, major financial decisions. Get expert help.
4. You’re too emotional to think clearly - Other people have perspective you don’t when you’re in the middle of it.

Asking for help isn’t weakness. It’s efficient. The best problem solvers know when to delegate.

Common Traps

Analysis Paralysis

Overthinking to the point you never act. You research 47 options for the best phone and never buy one.

Solution: Set a decision deadline. “I’ll research for 2 hours, then pick the best option.” Perfect is the enemy of good.

Premature Optimization

Solving edge cases before solving the main problem.

Example: You want to start a YouTube channel. You spend $5,000 on camera gear before recording a single video. Turns out you hate making videos. Expensive lesson.

Solution: Start small. Test with minimal investment. Optimize after you know it works.

Solving Symptoms, Not Root Causes

You keep getting flat tires. You keep patching them. The real problem is you’re driving through a construction zone every day with nails everywhere.

Five Whys prevents this.

Not Learning from Mistakes

You solve the same problem repeatedly because you never figured out why it happened.

Solution: After solving a problem, ask “how do I prevent this from happening again?”

Emotional Decision-Making

You’re angry at your boss so you quit without another job lined up. Three weeks later you’re panicking about rent.

Solution: Make decisions when calm. Sleep on big decisions. Separate emotions from evaluation.

Practice Makes Better

Problem-solving is a skill. You get better with practice.

Start small:

• When your phone is slow, don’t just restart it. Figure out why. Bad app? Memory full? Old OS?
• When you’re bored, figure out why. Not enough stimulation? Avoiding responsibility? Need new hobbies?
• When a friend is upset, figure out what they actually need. Advice? Listening? Distraction?

The more problems you solve systematically, the faster and better you get.

Keep a problem-solving journal:

• What was the problem?
• What solutions did I try?
• What worked?
• What didn’t?
• What did I learn?

Reviewing past problems makes patterns visible.

Summary

Problem-solving isn’t magic. It’s a systematic process you can learn and improve.

Key takeaways:

1. Define the problem before solving it - Most people waste time solving the wrong thing
2. Use proven frameworks - OODA, PDCA, Five Whys, First Principles, Rubber Duck, Working Backwards
3. Match your approach to the problem type - Technical, interpersonal, and life decisions need different handling
4. Ask for help when appropriate - Experts exist for a reason
5. Avoid common traps - Analysis paralysis, premature optimization, solving symptoms
6. Practice deliberately - Keep a journal, review what worked

The best problem solvers aren’t smarter, they’re just more systematic. They have a process. Now you do too.

Start using these frameworks today. Next time something goes wrong, don’t panic and guess. Pick a framework, work through it systematically, and watch how much faster you solve things.