By Ryan Richardson · Published 8 October 2026
Knowing which problem you're solving is step 60 (Part IX), the last in this cluster, marked moderate difficulty, almost nobody does this. It's placed last because every earlier diagnostic step in this part feeds into this one decision.
A spike problem wants a very large month; on a chart it looks like a flat baseline with occasional tall peaks, each peak a launch. A floor problem wants to never have a very small one; on a chart it's a jagged line oscillating around a baseline, where the low months are what hurts. Someone chasing a ceiling usually has the first. Most experts who are genuinely good at their own work and bad at being found usually have the second.
A spike machine was built for what turned out to be a floor problem, an expensive way to stay anxious. Most experts good at their work don't lack effort; they lack the back end that turns one good month into a dozen ordinary ones, which is a floor problem wearing the costume of bad luck.
Plot the last twenty-four months before deciding which one applies, and ask out loud, to somebody else, which pattern keeps you up. The honest answer is usually the less exciting one, and it's easier to dodge on paper than when said out loud to another person.
Building spike-oriented infrastructure (a big-launch machine) when the real problem is a floor that needs raising. Mistaking a jagged month-to-month chart for randomness instead of a repeatable low-month pattern worth naming and fixing directly.
| Claim | Value | Source |
|---|---|---|
| Spike problem vs floor problem definitions | spike = wants one very large month; floor = wants to never have a very small one | The Sixty Steps manuscript |
| Who typically has each problem | spike = someone chasing a ceiling; floor = most experts good at their work and bad at being found | The Sixty Steps manuscript |
| Matrix status for this step | Moderate difficulty, almost nobody does this, manual tooling | The Sixty Steps matrix |