Joel Cuevas

Wait and See

Reading: 1 minute — Updated on: 2026

Some of the most expensive work I've ever done was preparing for things that never happened. Building flexibility into systems for use cases that didn't show up, learning skills "just in case," planning around scenarios that played out completely differently. By the time the real problem arrived — if it did — half the prep was wrong and the rest had quietly gone stale.

It happens everywhere outside of work too. Couples rehearsing fights that never happen. Parents planning their kid's life around a path the kid never takes. Whole weekends spent worrying about a meeting that turns out fine.

The pull to over-prepare is strong because it feels responsible. Building for the future, thinking ahead, being ready. But the real problem in front of you is messy and unclear. The imagined one has a clean shape, which makes it tempting to solve that one first.

Future-you will know things current-you doesn't. New context, different constraints. Decisions made in advance, with worse information, usually have to be redone anyway — and now you're stuck unwinding work nobody asked for in the first place.

This doesn't mean ignoring everything until it's on fire. There's a difference between deferring and neglecting. If something is clearly coming, prepare. But if it might come, in some shape you can't predict, the cheapest move is usually to wait. Solve the real thing in front of you well, and trust that you'll handle the next thing when it actually arrives.

The simpler version of anything tends to age better. Less to maintain, less to undo, less rope to trip over. When in doubt, do the smallest thing that works and see what happens. The need will tell you what to do next, much better than your prediction of it would.

It feels like preparation buys control. Most of the time, it just adds luggage you'll drag into a future that won't look like the one you planned for.


From the Shelf Wait Before You Add


Related Notes While You're Here

Go back to the homepage