Skip to main content
← All posts Essay

The Wall on Day 200: When Plans Don't Go to Plan

Sometimes things don't go to plan

The wall on day 200

You don't usually find out the thing won't work on day one. You find out on day 200, after you've told everyone what you're building, after the money's in, after the shape of it is fixed in your head. That's the part nobody warns you about.

The wall doesn't show up early because the wall isn't visible early. A sketch doesn't have a regulator. A pitch deck doesn't have an insurance underwriter. A brainstorm doesn't have a clause buried in a provincial statute that says no, actually, you can't structure it the way you drew it on the whiteboard. The constraints that kill the original plan are mostly the kind that only reveal themselves once the thing is real enough to bump into them.

So you bump into them on day 200, not day one. That's not a personal failing. That's how building works.

The interesting question isn't why the wall is there. The wall is almost always there for a reason — legalities, insurance, market reality, a structural thing about the model that nobody could have priced in until you were close enough to see it. The question is: why did it take you 200 days to look?

That one's worth sitting with.

Most of us — and I include myself — get heads-down once a thing has shape. You set the direction, you start building, and the daily work is so demanding that looking up feels indulgent. Every hour you spend re-examining whether you're still building the right thing is an hour you didn't spend building. There's a whole genre of advice that tells you that's exactly the point: the people who make it are the ones who put their head down and don't look up. Just keep going.

I think that's wrong. Or — to be fair to it — I think it's right about effort and wrong about navigation. Keeping your head down is how you cover ground; looking up is how you make sure the ground you're covering still leads somewhere. Both are work. The trouble is that one of them feels like work and the other feels like doubt.

Here's the honest part. You can't pre-mortem every constraint. You won't catch all of them up front. The legal thing, the insurance thing, the partner who pulls out, the regulation that changes between you signing the lease and you opening the doors — there's a real category of risk that only shows up once you're close enough to it for it to matter. Trying to anticipate all of it would mean never starting.

So the move isn't "see around every corner." The move is build in moments where you stop and check.

A checkpoint is not a strategy session. It's not a board meeting. It's not a pivot. It's a much smaller thing — a built-in habit of asking, every so often, the questions you were too busy to ask yesterday. Is this still the thing? Is the thing still possible? Has anything I assumed three months ago turned out not to be true?

That's it. That's the whole technique. The reason it's worth doing isn't that it'll save you from every wall — it won't. The reason is that when you do hit the wall, you'll have hit it sooner, with less sunk in, and with more options on the table than the day-200 version of you would have had.

Because here's what sunk cost does. It makes you bad at the gut check. Once you've put a year into a thing, the question "is this still right?" stops being a clean question and starts being a question about you — about whether the year was wasted, about whether you were wrong, about whether you're the kind of person who finishes what you start. None of that is the actual question. But it feels like the actual question, and that's enough to make you stop asking.

Checkpoints are how you ask before sunk cost gets a vote.

When the wall does show up — and it will — there's a part nobody talks about either, which is that you have to let yourself grieve the thing you thought you were building. Not for long. Not melodramatically. But you can't skip it. If you try to jump straight from "this won't work" to "here's the new plan," you'll make the new plan with one hand still gripping the old one, and the new plan will be the old plan in a slightly different costume. Give it an afternoon. A walk. A bad night's sleep. Then come back.

And then you do the work. You scope the options — and the options usually suck. One costs too much. One changes the model so much you're not sure it's still your model. One is the obvious answer but you don't like it. One you haven't thought of yet. You won't get to take all the time you'd like to choose between them; quick decisions are part of the job. But the decisions are better when you've already been doing checkpoints — because you're not making them from a standing start. You've been looking up the whole time.

The lesson from the wall isn't "be more careful." You were careful. The lesson is: build in the looking up. Make it small. Make it regular. Make it cost you an hour, not a year.

So here's the gut check. Two questions, that's all.

What have I been working around instead of looking at?

If I were starting today, knowing what I know now, would I build the same thing?

You don't have to like the answers. You just have to know them. Because the wall on day 200 isn't actually the failure — the failure is the 199 days you spent not asking.

You're going to find out the thing won't work the way you thought it would. That part isn't optional. The only thing that's optional is when.