Sometimes, short-term results don’t tell the whole story.
How many times have you gone down a rabbit hole of programming, just to find out that the feature you added wasn’t needed, or that your approach didn’t work? Typically, we don’t know what implementation is needed until we can see our first attempts at a solution. The short-term gains shown during early attempts aren’t telling us how the end product is going to look or perform.
Have you ever tried a diet that helps you lose weight in the near-term, but you either end up feeling like crap, or gaining it all back? I wonder what the research says about health expectancy for people who stick with fad diets, lose weight, feel great, but then die early…
How many trips to the gym does it take before you start to see the health benefits? You have to stick it out long enough to find out.
Do you know of any companies that like to focus on quarterly earnings, all the while ruining their reputation, losing customers, and failing in the long run? Sometimes, doing the right thing and, taking some early losses can set you up for success later.
One of the reasons we say that hindsight is 20/20 is because we can’t predict the future far enough in advance. If our short-term goals were indications of how things ultimately turn out, we wouldn’t have to worry so much about hindsight.