Why Greatness Cannot Be Planned

The Problem With Over-Planning for Excellence

I spent years watching teams try to engineer outstanding results through increasingly detailed plans. Quarterly OKRs, milestone maps, risk matrices, scenario planning — the whole apparatus. And almost without exception, the outcomes were mediocre. Not bad. Just average. The most successful people and organizations I've worked with shared a trait that had nothing to do with planning rigor. The core issue is that planning assumes the future is knowable. It isn't. When you lock yourself into a detailed roadmap, you become committed to a specific version of success that may no longer be optimal once conditions shift. This is What I Mean By Why Greatness Cannot Be Planned, and it applies whether you're building a product, growing a business, or developing a skill.

Why Greatness Cannot Be Planned

Planning optimizes for predictability. Greatness emerges from adaptability. These are opposing objectives. A plan tells you what to do when things go right. It barely prepares you for when things go wrong, which is almost always in ways you didn't anticipate. The plan becomes a comfort object you hold onto while the environment changes around you. I ran into this head-on in 2019 when my team was building a data pipeline for a logistics client. We had a six-month plan with weekly milestones. Everything looked clean on paper. Then the client's legacy system threw three undocumented data formats at us during month two that weren't in any specification document. Our plan had zero contingency for that. We ended up scrapping the original architecture and rebuilding around a streaming approach that was never in any roadmap. The delivered system was genuinely good — better than what we would have built following the plan. But it only happened because we stopped trying to force the plan to work and accepted that the real problem looked nothing like what we'd planned for. The workaround I used was simple and unpleasant. I told the client we needed to pause for two weeks and redesign. That meant burning through budget without deliverables to show for it. Leadership hated it. But it was the only move that didn't produce a mediocre result built on a foundation that couldn't handle reality.

Here's the part most people miss. The opposite of planning isn't chaos. It's something more specific — you invest in building sensing capacity instead of prediction capacity. A sensing system tells you when conditions have shifted. A prediction system pretends it already knows what will shift and where. Prediction creates confidence. Sensing creates responsiveness. One of those actually serves you when something unexpected happens.

What Actually Works Instead

The framework I use starts with defining the problem space rather than the solution space. Most planning fails because it locks in a solution before understanding the constraints well enough. When I can't fully define the problem upfront, which is common, I build small probes — minimal experiments that reveal information about the real constraints. Each probe costs less than a week of work. After three or four probes, the actual problem usually looks different from what the plan described. I then set directional targets instead of milestone deadlines. A directional target says "move toward X type of outcome" without specifying the exact path. This keeps the team orienting correctly without requiring false precision about how to get there. The difference sounds subtle but it changes daily behavior. Milestone deadlines make people optimize for status reporting. Directional targets make people optimize for information gathering and course correction. There's a practical mechanism for this that I found useful. When building complex systems, I allocate about twenty percent of capacity to unplanned work. Not emergency firefighting — I mean actual exploration and iteration on unknown paths. Without that allocation, the team has no room to pursue discoveries that emerge during execution. They absorb all unexpected learning into the existing plan, which means they keep executing the wrong plan faster.

Common Mistakes People Make

The first mistake is confusing thorough planning with actual preparation. You can spend three months researching and still be unprepared for what shows up. Preparation means building the ability to respond, not building a document that describes what you hope will happen. The second mistake is believing that if you just gather enough data, you can predict the future. You can't. The data you gather is always from the past. Past data predicts past patterns, not novel conditions. That gap between past patterns and future novelty is where most plans die. A more subtle error is over-instrumenting your process. I've seen teams install dashboards, retrospectives, and status meetings for every planning artifact they produce. This creates the illusion of control. The dashboards report on lagging indicators — what already happened. They don't surface leading signals about what's about to break. By the time the dashboard turns red, the window for an easy pivot has closed. I learned to look for signal decay instead — the moment when the metrics that once predicted outcomes stop predicting them. That's usually the first real warning sign, and it appears before any dashboard color changes.

When Planning Actually Helps

I'm not saying planning is useless. It works well in narrow contexts where the environment is stable and the feedback loops are short. Routine manufacturing, compliance workflows, and repetitive operational tasks all benefit from detailed plans because the cost of deviation is predictable and contained. In those domains, planning is a efficiency tool, not a greatness tool. Greatness — meaning outcomes that exceed the baseline of what competent execution produces — requires an element that planning cannot generate. That element is serendipity channeled through prepared judgment. You can prepare the judgment. You can create conditions where lucky breaks are more likely. You cannot plan the break itself. The people and teams I've seen achieve remarkable results all share a pattern. They maintain strong directional intent, they run many small probes, they kill failing approaches quickly without ego, and they reinvest the results into the next probe. The trajectory is intentional. The path is not. The plan is a compass, not a map. There is a difference that matters more than most planners admit.

One more thing that nobody likes to hear. This approach produces worse results than a plan in the short term, usually. Because the plan gives people something concrete to execute, and execution feels like progress. The probing approach feels slow and uncertain until it isn't. You need tolerance for that discomfort phase, which most organizations don't have. If you're looking for a guaranteed method to achieve greatness, this isn't it. There isn't one.