The Iteration-First Approach to Getting Stuff Done
You know how most people plan out their entire career, or project, or business before actually starting? Yeah, that doesn't work. The original quote is from a Spanish poet named Antonio Machado, and it basically says there is no path until you walk it. People treat it like a motivational poster, but in practice it's a methodology for how to actually ship things when you don't have all the information. Here's the straightforward version. Instead of trying to figure out the complete strategy upfront, you take a small step, see what happens, adjust based on what you learned, and then take another step. It sounds obvious until you're sitting in front of a whiteboard with twelve sticky notes trying to predict the next three years of market conditions. You can't. Nobody can reliably. What works is moving, getting feedback, and correcting course faster than everyone else. I spent probably four years working in product management at a mid-size SaaS company, and our biggest win came from applying this literally. We had a feature request from our largest enterprise client that required a completely new integration workflow. The old approach would have been six months of requirements gathering, design, engineering, and testing before anyone saw a prototype. Instead, we built a rough clickable wireframe in two days, showed it to five customers, got yelled at by three of them about edge cases we hadn't considered, went back and adjusted, built a basic prototype in a week, tested it with ten users, found the actual friction points, and iterated again. We shipped the real thing in ten weeks instead of six months, and it was closer to what people actually needed because we'd stopped guessing.
Why Planning Everything Is a Trap
Most people fall into the planning fallacy. You think if you just document the next steps clearly enough, the future will cooperate. It won't. The world changes, stakeholders change their minds, your assumptions were wrong, technology shifts. Every hour you spend writing a perfect plan is an hour you're not getting real-world data. The counter-intuitive part that most people miss is that taking action before you feel ready actually produces more clarity than thinking does. Not always, but often enough that it's worth the risk. When you sit and plan, you're working from your current knowledge state, which is incomplete. When you act, you create new information. Problems reveal themselves that you couldn't have predicted. Solutions become visible that weren't in your original model. I hit a real wall with this approach once when I was trying to validate a new content strategy for a client. I kept iterating on blog topics and headlines based on early performance data, but the metrics were noisy and each test had a tiny sample size. After about eight weeks of small experiments that were going nowhere, I realized the problem wasn't the iteration speed, it was that I didn't have a clear success metric to measure against. I switched from optimizing for engagement to optimizing for a specific conversion action, and suddenly the data became useful. The lesson wasn't that iteration doesn't work, it's that you need a frame of reference before the iteration tells you anything.
When This Approach Breaks Down
This isn't a universal solution. There are situations where the "just start walking" mentality will get you in serious trouble. If you're building medical equipment, you need thorough upfront planning and regulatory compliance. If you're launching a rocket, you don't get to iterate after ignition. If your decisions involve other people's money or safety, you can't learn your way through it casually. The method also fails when you lack a feedback loop. Walking without direction just means you're wandering. The key difference between iteration and randomness is that iteration has a return step where you evaluate what happened. If you're acting but never stopping to assess, you're not using this methodology, you're just being reactive. Set up clear checkpoints. Measure something real at each one. Adjust or double down based on evidence, not hope.
Get the Full Details
The Practical Step-by-Step
Start by identifying your smallest possible first step. Not the first milestone, the first action. Something you can do in a day or two that gets you out of the planning phase. Then do it. After that, gather real feedback from the situation, not from people who haven't actually interacted with your work. Use that feedback to make one or two specific adjustments. Repeat. Track what changed and why so the next round builds on actual learning rather than starting fresh each time. The process usually cuts your first draft time significantly compared to traditional planning-heavy approaches, especially on projects where requirements are unclear or likely to shift. I'd estimate roughly a 40 to 60 percent reduction in time spent before you have something concrete to show, though that depends heavily on how clear your end goal is and how fast you can get feedback. People often confuse this with not caring about the destination. It's not that. The direction matters, you just accept that the path to get there isn't drawn until you start moving. Stay loose on the steps, firm on the goal. That distinction is what separates people who use this method from people who justwing it.
