The "Problem Solver"

Chapter 8: The Pivot Point

Knowing when to stay the course and when to change tracks.

​There is a fine line between persistence and stubbornness. Persistence is working through a difficult patch because you believe in the outcome; stubbornness is doing the same thing over and over again while expecting different results.

​In this chapter, we learn how to identify the Pivot Point: the exact moment when the data tells you that your current solution is no longer the best path forward.

​The Sunk Cost Fallacy

​The biggest enemy of a successful pivot is the Sunk Cost Fallacy. This is the psychological urge to keep investing in a failing plan just because you’ve already spent so much time, money, or emotional energy on it.

​Your brain says: "I can't stop now, I've worked on this for six months!"

The Problem Solver says: "The last six months are gone regardless. Is this the best use of the next six minutes?"

​The "Dead Horse" Test

​How do you know if you are just in a "dip" (a temporary struggle) or if you are riding a "dead horse" (a solution that will never work)? Use these three criteria:

​Diminishing Returns: Are you putting in twice the effort for half the results compared to last month?

​External Shifts: Has the environment changed? (e.g., A new competitor arrived, the technology became obsolete, or the root cause you identified in Chapter 3 shifted).

​The "Day One" Question: If you were starting this project today, with everything you know now, would you choose this same path? If the answer is "No," you are overdue for a pivot.

​How to Pivot Without Panicking

​A pivot isn’t a failure; it’s an adjustment based on new data. When you decide to change tracks, follow the Pivot Framework:

​Keep the Goal, Change the Method: If your goal is "Financial Freedom," and your "Real Estate" plan is failing, you don't give up on freedom—you pivot to a different vehicle, like "E-commerce."

​Cannibalize Your Progress: Look at what you built. Which parts of your failed plan can be used in the new one? (Refer back to Resource Mapping in Chapter 7).

​Communicate the "Why": If you are working with a team (Chapter 6), explain the data that led to the pivot. A pivot with an explanation is a strategy; a pivot without one is just chaos.

​The Pivot Audit:

Look at your current project. On a scale of 1–10, how much do you believe the current "Method" will lead to the "Goal"? If you are below a 6, it’s time to run the "Day One" Question.

​Next Step: Once you've successfully pivoted and solved the issue, your job isn't done. In Chapter 9, we look at Building the Shield—how to ensure the problem never comes back to haunt you.