Read on Twitter
""23 things I didn't learn in college / grad school":
#19:
Bias toward action. Use milestones.
.
#19:
Bias toward action. Use milestones.
.
One of my favorites, because I tend to dream a lot, think endlessly, compose essays or theorems or documents in my head, keep seven browser tabs open to buy a $20 thing.
The main reason not to overthink things but start doing something is to get feedback.
The feedback can be internal (you find gaps in your thinking) or from others (a colleague who gives a counterexample) or the environment (a clever idea that doesn't work).
The feedback can be internal (you find gaps in your thinking) or from others (a colleague who gives a counterexample) or the environment (a clever idea that doesn't work).
A common reason for "analysis paralysis" is lack of clarity about a large nebulous body of work. If that happens, try to define a few milestones -- either in the core of the work, or if you're hopelessly stuck, on the periphery.
But be concrete so you can see progress.
But be concrete so you can see progress.
Concrete milestones lead to reusable artifacts. They often find value in their own right.
My favorite technique to overcome overthinking a large project plan or complex presentation is to write out the "API"s for the parts This forces me to examine the assumptions we make about the parts.
Milestone one is usually a list of tweet-length descriptions of the units.
