In a hurry?
Skip the introductory part and scroll down to the section Inefficiency Benchmarks and follow instructions.
In each of my posts, I have shown how work can be done more efficiently.
You probably already knew a method of doing it.
I am highlighting the best, fastest, smartest method. That is called Efficiency.
The problem is that there are millions of business activities we perform and there are thousands of features. I cannot help you with every activity you perform.
The question is, as an individual, how do you detect your inefficiency?
The solution: Self-Audit
The solution is simple. YOU must start detecting your own inefficiencies – while you work.
How to do that? By a simple process of SELF-AUDIT.
Start noticing how you work and think about what are the exact steps you are taking.
Usually, while working with Office tools, we do not notice the actual steps. We have been using it for years. So things happen automatically.
Self-Audit means consciously noticing the activities you perform. Click, Right click, Keyboard shortcut, mouse movement, repetition, Undo… everything.
Initially it will require some proactive effort. But soon it will become a habit.
Next problem: How to find if my method is inefficient?
This is a tough question to answer. Because, in most cases you know only ONE method of performing the activity or task.
Office allows you to perform most activities in many different ways. You found one method which worked for you and you stick to it lifelong.
How did you find that particular method? Most probably by trial and error.
Even if you found that method from documentation or research, there is a good chance that Microsoft has added more features to make it simpler. You have not taken any extra effort to find a better approach because your existing method is working anyway.
This is what I called Active Inefficiency!
If you know only one method, how can you say it is good or bad? Efficient or Inefficient?
You have nothing to compare it with. No benchmark.
The method which was best on day one may be the worst way of doing it today.
Here are simple benchmarks to tell you whether your method is inefficient or efficient.
These may sound arcane at first. But just try these for next few days. I will post more explanatory articles later.
Repetition = Inefficiency
This is obvious. But still we continue to do many repetitive activities instead of trying to find a better way.
Struggle = Inefficiency
If you are struggling and fighting with the software to get something done, then it is definitely not the right way – even if it eventually works.
Feeling that you are helping Office rather than Office is helping you
You try something. It works but it does not work elegantly. Are you trying to help Office? If yes then STOP IMMEDIATELY.
Remember that Office is created to help us. Not the other way.
So if you are faced with a situation where you are helping Office do its job, that means you are not communicating correctly with the software. Stop and try to find a way of communicating correctly.
Hands in active use but brain is idling
Content is important. Not formatting. But most of us spend disproportionately more time on formatting Word and PowerPoint documents. That is inefficiency. Content comes from brain. Formatting comes from hands. So an imbalance between usage of hands v/s brain indicates inefficiency.
Small data = less time, Large / Complex data = exponentially more time
This is a corollary to repetition. Even if you use an inefficient method few times, it does not matter. But if the data becomes bigger, that inefficiency is going to take inordinate amount of your time. This is a sure way of detecting inefficient approach.
Undo = Inefficiency
If you made a mistake and pressed UNDO, then it is absolutely fine.
But in reality, we often use UNDO because you tried to do something (intentionally) and what happened was not what you expected. Therefore, to repair the damage we use UNDO. This type of UNDO usage is a sure indicator of inefficiency.
In this case UNDO is telling you that you don’t know how to do!
Again it is time to discard your current method and find a better one.
Try these benchmarks while working in the next few days. Post your feedback as comments.
In future articles, I will cover examples so that you can relate to it better.