Planning

“A man without a plan will quickly become banned/canned/overly tanned.”

I hate planning. I also love planning. I love feeling like I can control the outcomes of things, that a plan I’ve written down is exactly how it will play out in reality.

In the tech world, everyone loves “sprinting”. A sprint is a two-week period of a project, with a planning session at the beginning, and a retrospective session at the end.

Most of the time, in my experience, the “value added” hierarchy to the project goes:

doing the hard stuff > talking about what broke / what was learned from doing the hard stuff last time > planning the best way to do hard stuff.

Ideally, a plan is a document that will illuminate problems before they occur, so they can be safely avoided. Some plans are skeletons, others are so full bodied, they take more time to do than the project itself.

The problem is, plans never play out like they should. At best, plans save an equal amount of time on doing the hard thing that they cost to formulate. At worst, the time is entirely sunk because the plan is a steaming pile of garbage.

Whether you are writing a book, learning to fly a plane, or just how to make a burger; get to it. The less thinking and planning, the better, or so I’ve found.