When a Better Plan Becomes a Way to Stall

The first move should give you something to work with

Sometimes the next version of the plan is just a nicer way to stall. I like planning. I do it for a living, and I think there's real value in knowing what you're trying to accomplish before you start throwing time and money at it. But a useful habit can also become a convenient place to hide.

That can be difficult to recognize when you're a capable person. You know how to compare options, build a spreadsheet, ask good questions, and make a case. Preparation looks responsible. It feels responsible. And if you've got kids, a career, and people depending on you, being responsible is hardly something you want to argue against.

Preparation has a comfortable side

The question I have to ask is whether the next round of preparation will change what I do. Sometimes the answer is yes. There's a number I need, a requirement I haven't checked, or a conversation that could change the decision. Other times, I already know the next step. I just don't particularly want to take it.

Writing a book keeps bringing that distinction into view. The outline helps me see where the ideas belong. But a thousand rough words give me something the outline can't: a page I can read, question, cut, and improve. Until the page exists, I'm mostly evaluating what I think I'll be able to say.

There's something uncomfortable about that transition. An idea in my head can stay pretty impressive. Once I put it on paper, I get to discover the paragraph that makes no sense and the explanation that sounds much better in conversation. That's useful information, even if I'd rather have written a great first draft.

What will the first move tell you

In product work, I can spend time organizing what I believe customers need. Eventually I have to ask them. A conversation may confirm the assumption, complicate it, or reveal that I've been solving the wrong problem. The value of making contact is that the answer comes from somewhere outside my own thinking.

The same thing happens with personal decisions. If I'm considering a move, a call with someone who lives there might tell me more than another evening of browsing listings. If a relationship needs a difficult conversation, asking for twenty minutes is a real first step. Neither action settles the entire question. Each gives me something to respond to.

This is why I don't think every decision needs a weeklong business plan to get started. Some decisions need careful planning because the cost of getting them wrong is high. But there are plenty of smaller, reversible steps that help me find out what the larger plan should include. I can take one of those before I feel fully prepared.

Give the move a finish line

I like a seventy-two-hour move because it puts a short boundary around the question. Within the next three days, what can I actually finish that will move this out of my head? The timeframe isn't magic. It's just close enough that I have to deal with the calendar I have, instead of borrowing time from some imaginary future week.

The sentence is simple: Within 72 hours, I will finish ___ so I can learn ___. Write a rough page so I can see where the explanation breaks down. Contact three people so I can find out whether the problem I've identified is familiar to them. Complete a short workout so I can learn whether that time of day fits my routine. The useful part is naming both the action and what it will tell me.

The finish line matters. 'Work on the book' can expand to fill an evening without producing a page. 'Write 500 rough words about one idea' gives me a stopping point. 'Get healthier' is a direction. 'Take a twenty-minute walk tomorrow morning' is something I can do. A small action doesn't solve the whole problem, but it gives the day a concrete task.

Let the attempt change the plan

Once I've done it, I need to look at what happened. Maybe the step was too large. Maybe the feedback changes the next step. Maybe the first attempt failed and I need to pause, regroup, or take a different approach. Action is more useful when I'm willing to learn from the result instead of treating persistence as an obligation to keep doing the same thing.

I also try to be honest about what got in the way. A real constraint may mean I need to redesign the step. If I was waiting for someone else's answer, I may need to follow up. If I simply didn't want to send the message, another spreadsheet probably wasn't going to help. Those are different problems, and they deserve different responses.

Action, in the Blueprint, is the point where the decision becomes behavior. There should be something I can point to afterward, even if it's small or rough. You can revise a first attempt. You can't revise the one you keep imagining. That's the part I'm trying to remember when I reach for the outline again instead of writing the next page.