From Experimental To Efficient

I have a step-by-step process for learning a new skill or software tool.

Some steps include:

• Open every menu/tab

• Look up explainer videos

• Call support and ask questions

• Tinker around, trying making things and deleting them

 

I don’t know what I’m doing, and generally the more time I spend poking around, the better I will understand the software.

In addition to learning time, the longer I spend writing my first drafts, setting up the software, executing the skill and double-checking my work, the higher quality my work will be.

If I hit a challenge, the longer I think it through rather than giving up, the higher the chance I will solve that problem and know the solution thereafter.

High interest, longer hours and more patience solving issues are all beneficial to me.

But, this perspective is less beneficial once I reach this point:

• I know how to do X or use X tool

• I’m devoting a large portion of my time in this area (it’s driving my results)

 

Now, I need to find ways to be more efficient.

Rather than looking for more to learn, double-check, and tinker with, I need to know where to cut.

Now, spending less time, rather than more, is what I need on order to meet quotas, beat deadlines, and get results.

Once I can get X result in 1 hour, then spending that time watching yet another tutorial video means less results.

If I hit a problem, it’s likely a fringe case I should skip rather than spend hours working through.

Rather than trying everything, I need to only do what I know from experience is necessary to achieve the desired result.

When you are fully capable of executing, the opportunity-cost of second-guessing and double-checking instead of executing matters more than the mistakes you may make while working efficiently.