What Gets Measured Gets Done
What Gets Measured Gets Done
Nopadol Rompho
Preface
Simon Sinek makes a particularly interesting point in his book Start With
Why: How Great Leaders Inspire Everyone to Take Action. The author lays
down the three important questions: what, how, and why. Most people only
communicate the “what” and “how,” failing to address the “why.” I could
have written in this preface: “This book is about performance management
(the what); and will present how it is designed and put to good use in
organizations (the how).” Then, this would be an ordinary book about
performance management techniques. However, I’d like to communicate the
“why” first. I am inspired to transform the usual jargon-filled “academic
textbook” into an engaging and comprehensible text. I studied many excellent
research reports that few people manage to get through, and saw many useful
textbooks gather dust on library shelves. My aim is to transform such content
into simple terms that everyone can comprehend, and more importantly,
enjoy.
Through my experience of teaching, writing textbooks, and researching about
performance management made, I realized that people tend to overlook
certain aspects of performance management. Apart from its being engaging
and comprehensible, I hope this book will be a successful knowledge transfer
of such overlooked aspects of performance management.
Acknowledgments
This book could not have been possible without the assistance of many
others. The first person I would like to thank is my wife, because she inspires
me to write. She is also one of the first fans of my Facebook fanpage, and is
usually the first person to tell me that my morning post was difficult to
understand. In addition to her reviews, she also helped consolidate and edit
various articles, gather many files together, and create and format layouts. In
other words, she has been my editor.
Next, I would like to thank my daughter Paan and my son Pun for the moral
support, their smiles and laughter...
I am grateful to my parents for their knowledge and support. I also appreciate
my younger brother’s continuously exchanging thoughts with me.
I thank my research and teaching assistants for gathering the relevant data
and works. I am also grateful to Pat Juthamard, who helped me translate the
Thai version of this book into English.
In addition, I would like to thank the fans of the Performance Measurement
Fanpage for their comments, shares, and likes of my daily 7 am posts. These
have encouraged me to write this book.
Last but not least, I would like to thank you, the readers.
Table of Contents
Chapter 1 Why measure?
Chapter 2 Benefits of performance measurement
Chapter 3 On measurement
Chapter 4 Cautions of performance measurement
Chapter 5 Get to know the system of performance measurement
Chapter 6 Things you should know before creating a performance
measurement system
Chapter 7 Design a performance measurement system
Chapter 8 Create a performance measure
Chapter 9 Set targets and collect data
Chapter 10 Prepare a performance report
Chapter 11 Do not use it if it fails a test
Chapter 12 Implement a performance measurement system
Chapter 13 Put the data from performance measure to good use
Chapter 14 Make your performance management system sustainable
These measures will control and ensure that the procedures would work
smoothly. If a problem occurs, you would be informed and be able to deal
with it right away, which would then lead to organizational success.
Help in day-to-day operations
Apart from devising a strategy, what else do managers do in their lives?
Asking a question like this is asking for trouble. But I do not mean it that
way. On the contrary, I asked that question as a lead-in to the main
responsibility of management and to the how-tos of putting performance
measurement to use. Managers do not spend their time only on formulating a
strategy or creating a long-term vision. They also have to oversee and ensure
that everything is operating effectively and efficiently.
For example, in production control, managers need to make sure that
production runs smoothly, without any problems. But how can a manager
know what’s going on in production? Performance measurement is the tool
that will help the manager find out whether everything is running smoothly or
not. With performance measurement, managers do not need to gather
information from various sources, which is time consuming. In addition,
when performance measures indicate a problem, such as a decline in the
timeliness of production, managers will be immediately notified of the
problem so that they are able to fix it on time. Many performance measures
might even demonstrate the roots of the problems. Generally speaking,
organizational performance measurement is the manager’s right-hand man, as
long as the system implemented is correct and relevant.
Help in organizational development
Besides working on long-term plans and preparing daily reports, managers
have to improve and develop current business processes. Many managers
think “Solving daily problems takes the whole day. How can I have enough
time to improve procedures?” The catch is you are spending time to fix daily
problems because you did not try to improve your process in the first place.
For example, if you never care to improve your production and leave the
machines broken, you would feel anxious that you will not be able to produce
good quality products or produce goods on time. You have to spend your day
seeking for products from somewhere else to be delivered to customers.
Taking a step back to improve the process will definitely be worth your time.
To develop a better process, you have to work harder only once. After that,
you might find that you have more time to work. Performance measurement
will show you what you need to improve, so that you can solve the root cause
of the problem.
However, I have to admit that performance measurement is rarely used for
this purpose. Performance measurement for organizational improvements is
like getting a health checkup. You do not get a checkup because you are sick,
you get it because you are afraid of getting sick, right? If the result shows that
you have certain problems, like high level of cholesterol, you will start to
improve yourself by exercising more or eating a healthy diet. Organizations
need checkups, too. Have you checked the health of your organization yet?
Chapter 6
Things you should know before creating a performance measurement
system
If you have made it to this chapter, by now, you probably want to know how
you can design a good performance measurement system. Wait a little longer,
do not rush it. Before you can design a good system, you need to know what
a “good” system is first. It is like when you want to design a house. Before
you start designing, you have to know what your ideal house is like. So, let’s
take a look at the important factors that you need to know before designing a
performance measurement system.
#1 A performance measurement system must eliminate existing
problems without creating new ones.
I have a story to tell you. A company has a problem delivering its products to
customers on time. To fix this problem, they create a performance measure:
the percentage of late delivery. This performance measure divides the number
of products that could not be delivered on time by total production. If a
customer orders 100 pieces, they produce exactly 100 pieces. However, only
80 pieces are delivered on time, and not the other 20. Hence, the percentage
of late delivery equals 20/100 = 20%. The CEO aims to reduce the
percentage of late delivery to less than 5% within a month. If this goal is
achieved, then he will give out rewards. One month later, it turns out that the
percentage of late delivery is reduced to 2%. However, the company still
receives complaints from their customers about late delivery.
What happened? The company still could not deliver the products of the
same quantity on time even though the percentage of late delivery decreased?
Why? Let’s stop here and take two minutes to think about it.
The answer is that the employees tried improving the percentage of late
delivery, however, such action was not in alignment with what the
organization wants. Do you know what they did? Let’s take a look at the
calculation again. The number of products that could not be delivered on time
is divided by total production. Hence, there are two ways to reduce the
percentage: (1) Reduce the numerator (the number of products that could not
be delivered on time), or (2) Increase the denominator (total production).
Which one do you think is harder? The employees of this company chose
option 2, because option 1 demands hard work. Whereas, with option 2, they
only need to produce more than what the customer orders. In this case, they
produced more than needed. For example, when the customer ordered 100
pieces, they produced 1,000 pieces. And since they did not rush production,
they could manage to produce only 80 pieces on time, while the other 20
were still delayed. Yet, the percentage of late delivery was reduced because
the value of parameters in the equation have changed: 20/1,000 = 2%, instead
of 20/100 = 20%.
This kind of problem occurs because the performance measure creator does
not pay attention to the overall picture, and creates additional problems like
over production. So how can we fix the late delivery problem in this case?
The first method is to adjust the performance measure so that it is aligned
with what we intend to measure. Using the above example, we can calculate
the percentage of late delivery by dividing the number of products that could
not be delivered on time by the number of products the customer ordered,
instead of total production. With this formula, even if the employees produce
more, the performance measure will not be affected. The only way out for
them to reduce late delivery would be to produce and deliver faster.
The second method is to involve other performance measures. For example,
we can include an inventory level measure, so that when the employees
overproduce in order to improve the late delivery percentage, the inventory
level will also increase. When other performance measures are included,
employees would not dare do what the organization does not desire. In this
case, the employees would not overproduce.
The third method is to create a restriction for the performance measure. For
example, we want to reduce the percentage of late delivery and not allow
overproduction. This way, employees will act according to the organization’s
goals. You can see that designing a performance measure is not an easy task.
You have to give careful consideration to it. Otherwise, the performance
measure will become the troublemaker.
Let me give you another example. There is a city with ferry service in the
United Kingdom. The problem is that the ferry captain receives a fixed
salary, so he does not have the motivation to work hard. As a result,
customers begin to complain that the captain is not eager to work. Despite
having full passengers on board, the captain continues to chit chat, and does
not hurry back to pilot the ferry. Once customer complaints reach the ferry
service company, management begins to invent a performance measure that
would solve this problem. The performance measure they come up with is
“the number of trips per day,” because they believe this will make the captain
work harder. Now, I bet everyone is able to guess what’s going to happen
next.
Yes, once you count the number of trips, you will get numbers of trips; “You
get what you measure.” What happens is that the ferry captain does not wait
for passengers to board the ferry, because he knows the more “trips” he
makes, the more rewards he will receive, and he has to achieve the required
number of trips. Hence, waiting for passengers to get on board is a barrier to
his goal. So, customers find that now the captain would not wait for anybody.
Once he had 3-4 passengers on the ferry, he would leave right away. See how
a performance measure that has not been carefully considered can affect an
organization very badly? In the end, this company had to adjust their
performance measure to be based on the revenues received from the trips so
that the goal of the captain and the organization are the same, which is to
generate profit.
Let’s take a look at another example. This happened in a supermarket
somewhere in the United States. The problem with this supermarket was the
long waiting line, especially during prime time. The long waiting line
problem is nothing new. However, customers were particularly dissatisfied
with the sluggish cashiers. As the cashiers were receiving a fixed hourly
wage, they did not have to work fast; no matter if they worked fast or slow,
they would get the same wage. When the cashiers worked slowly, the
customers in line felt dissatisfied because they did not understand why the
cashiers would not work faster, given such a long waiting line. Most of the
time, the cashiers even chit chatted with each other.
To solve this problem, the supermarket’s operation manager set up a
performance measure for cashier performance. This performance measure
focused on the time a cashier spent in servicing a customer. But the problem
was that counting the amount of service time was unfair for the cashiers,
because the cashiers that get to serve the customers who buy few items would
obviously spend less time, and vice versa. Therefore, measuring by dividing
the total service time by the number of purchased items was more rational.
The total service time would start when a cashier begins to scan the first item,
and end when the cashier scans the last item. Then they were able to divide
the total service time by the total number of scanned items. In addition, the
management of this supermarket also found the statistical value of the
performance measure, and defined a goal of spending less time in scanning
an item that rewarded the cashiers.
One week later, the performance measure showed significant improvement;
time spent per item was greatly reduced. Technically, the time spent in the
waiting line should have gotten shorter, right? However, that was not the
case. The time spent in the waiting line got even longer than before. How is
that possible when the checkout time per item is reduced? How come did the
waiting line get longer?
Here’s what happened… The performance measure started measuring when
the first item was scanned, and ended when the last item was scanned. It is
true that the decreased value reflects the reduced amount of time, when
compared to the checkout time of the same quantity of items. However, it
does not reflect the total waiting time. Once this performance measure was
implemented, the cashiers were under the pressure of having to improve the
value (the value had to be reduced). Thus, the cashiers began to take certain
actions to reduce this value. However, these actions became the reason why
the waiting line got longer.
What did the cashiers do? Firstly, when a customer approached the counter
and took items out of her cart, normally the cashier would start scanning the
items right away. However, because of this performance measure, they did
not do that. They would wait until the customer finished unloading the cart,
because they knew that the clock would start ticking when they would begin
to scan the first item. The customer’s unloading her items very slowly was
affecting this performance measure.
Another possible situation in this scenario is when a customer unloads his
cart for the cashier to start scanning, but then he realizes that he forgot
something. In the past, the cashier would continue to scan the other items
while the customer ran to grab the thing he forgot. With this performance
measure in place, the cashier would not do that, because whenever he starts
scanning, the clock starts ticking. If the customer takes a long time, the
cashier’s performance measure would indicate that he is doing a bad job. So,
we would see cashiers standing and waiting for their customers to come back
before starting the scanning process.
Thirdly, what if the customer realizes that he forgot something after the
cashier starts scanning? In this case, the cashier would not be able to prevent
the customer from going back and grabbing something he wants. But at the
same time, the cashier cannot stop scanning, so he has to continue what he’s
doing. But what might happen is that once the cashier finishes scanning, he
might finish the transaction without waiting for the customer to return, not to
prolong his total transaction time. Despite the fact that he might see the
customer already walking back, he would still finish the transaction to stop
the clock, and then start a new transaction once the customer is back at the
counter. Finishing the previous transaction means that the customer has to
pay and sign his credit card for that transaction before the cashier can start
scanning again for the new transaction. Therefore, the waiting time would be
longer.
Now you can see that designing a performance measure is not an easy job. It
is true that in order to reduce waiting times, many actions have to be taken –
from increasing the number of checkout counters to other matters. But what I
am trying to say is that if you design a performance measure without
considering other factors, the performance measure can create new problems
without you even realizing it.
#2 A performance measurement system must explain the performance
gap.
Once you have received your organization’s performance measurement
results, you must ensure that you know what the result means. And more
importantly, you need to know how you can improve it. Normally, you would
receive two values from any performance measure. The first value is the
actual value, and the second one is the expected value. Most of the time,
these two values are different. You might find that the actual value does not
equal the expected (or target) value. The gap between the actual value and the
expected value is called the “performance gap.” It is very important that you
should be able to explain the performance gap once you have a performance
measure in place.
Let me give you an example. Assume that we have a measure called “the
time wasted without creating added value to production.” Of course, we
would want the value to be zero (expected value). However, once we receive
the results, we realize that we have wasted 100 hours without creating any
additional value. The performance gap in this case is 100 hours, or simply
put, there is a 100-hour difference from the desired value. Just reporting the
100 hours would be meaningless for the workers, because they would only
know that they have wasted 100 hours without knowing any of the reasons
behind it.
Hence, a good operational report should contain useful information that can
be utilized in problem solving or further development. Therefore, being able
to explain the difference is very vital. However, it is not necessary to explain
the difference 100% accuracy; 80-90% would do for a start, and later on we
can try to achieve about 95%.
From the aforementioned example, apart from being able to tell the amount
of time wasted, we can also tell that out of those 100 hours, 50 hours were
caused by a broken machine, 30 hours by human error, and 15 hours by the
late delivery of raw materials. Now we can use the result to solve problems. It
is much better than only knowing that we have lost 100 hours, am I right?
#3 A performance measurement system must include sufficient data.
You cannot start your car, so you take it to an auto shop. A technician tells
you that if you let him overhaul your car, he can guarantee that the car will be
able to start. Well, that would leave you with empty pockets. A technician
should rather inspect your car in detail, and identify which systems or parts
don’t perform well, and fix those. That would be a wise move costing much
less than overhauling your car. This problem occurs when your performance
measure is not specific enough. If you only measure input and output, and
nothing in between, you will not know the cause of the problem.
Another example… We have two products, Product A and B, but we measure
the total sales instead of breaking it down to sales of A or B. What could
happen? You might see that the total sales might be stable across time.
Looking at the stable total performance, most people would assume that the
sales of both Product A and B are stable. Yes, it is possible that the
performance of A and B are both unchanged, explaining the total
performance’s remaining constant. However, that might not always be the
case. It is also possible that A’s sales is declining, while B’s is improving.
Yet, when the sales of the two are added up, total sales appears to be
constant.
Same goes for stock market indices. When indices remain constant, it does
not mean that the stock price of every company in the market remains
constant. It is possible that the prices of half of the stocks have increased,
while the other half have decreased. Therefore, we can conclude that
performance measures that are not detailed enough might hide both
opportunities (like the increase in sales of B) and threats (like the decrease in
sales of A). As a result, the organization might miss out on many things.
#4 A performance measurement system must be timely.
Can you remember what you had for dinner yesterday? I think most people
would remember. Let me ask you another question. What did you have for
dinner 15 days ago? Can you remember? Most people would not be able to
remember, unless it was a special occasion like your birthday or the day your
boyfriend or girlfriend broke up with you. Why can’t you remember? I don’t
even have to ask. Who would be able to remember that long ago?
Reporting the results of our performance measures too late reduces their
value, because we cannot remember what had been happening during that
time. Think about it… We get the three-month old value of the percentage of
defects, and we notice that it is higher than usual. Would you be able to
remember what was happening three months ago? Our memory is limited. If
we cannot remember what happened, how can we solve the problem?
To make matters worse, if we only realize the problem of three months ago
just now, we have no idea how much damage was done during the past three
months. This is why I usually compare performance measures to fruits and
vegetables. They can be rotten or expired. If we report the results too late,
they might be useless. Now is the time for the important question. What is
considered “timely” in today’s business world? There is no clear answer to
that. But I can give you a brief answer. Measuring weekly should enable us to
send out reports within the first days of the coming week. Or, if we measure
daily, we should be able to deliver a report by tomorrow. This is what would
be called “timely” in today’s business world.
#5 It takes time to see the results of a performance measurement system.
Have you ever faced a problem in analyzing the results of an organizational
performance measure? Apart from being able to tell if the result is better or
worse, we should also be able to tell what makes it that way. For rational
analysis, we should look at the changes in other performance measures as
well. For example, this month’s customer satisfaction has declined. But why
has it declined? If we observe other performance measures like the rate of
timely delivery, we might find that the rate has decreased. Then we’d know
that the decrease in customer satisfaction is caused by the declining rate of
timely delivery. This would be an easy case to analyze. However, sometimes
analysis could be difficult, because it involves a period of time. What does a
period of time have to do with this? Let me give you another example.
Let’s assume that our sales performance measure is constant or decreasing.
But when we look at other performance measures, we notice that the
advertising expenses have increased. Well, that is puzzling. How can an
increase in advertising expenses make sales decrease? It does not make much
sense, right? In fact, drawing a conclusion like this would be inappropriate,
because we did not consider the period of time it would take for advertising
to create an effect on sales. “A period of time” starts when we begin to adjust
our operations, and ends when an effect is observed throughout a
performance measure “learning cycle.”
Let’s use the same example again. The advertisement that we paid for might
require more than a day or two for it to affect sales. It might even take a
month. Therefore, if you find that your recently launched advertisement
campaign does not affect sales the next day, do not panic. It requires more
time. Thus, you should be aware of the “period of time” when analyzing the
results of performance measures. Simply put, we need to know or estimate
the learning cycle of each performance measure; otherwise, we might make
wrong decisions. In the case of the above example, if we rush things, we
might decide to cancel the advertisement campaign and start to work on
something else without knowing if the advertisement was actually working or
not.
The last concern is what to do about performance measures that have a long
learning cycle. We might end up wasting a lot of money before we find out if
they work or not. Let’s use the same example again. Assume that the learning
cycle of the performance measures for advertisement is one month. Do we
have to air the advertisement for one month? If the learning cycle is very
long, you do not have to wait. If you want to measure using sales, then you
might have to wait a month. But if you are unsure whether the advertisement
works or not, you can try using other performance measures that have shorter
learning cycles. For example, you can measure the number of views of that
advertisement – you should get the result within a week. If we have already
advertised for a week, but no one has seen our advertisement, then you do not
have to wait one month to know for sure that it will not stimulate sales. This
is just an example. You can see that if we really pay attention to our
performance measures, they actually have plenty of uses.
#6 Performance measurement requires consistency.
When should we use organizational performance measurement?
1) When an organization has problems
2) When an organization does not have any problems
That is worth thinking about. Most of the time number one is the case. For
example, you could not deliver goods in time, so you begin to design a
performance measure of late delivery to solve the problem. Or, there is a
problem with production, and you create a performance measure of defects to
deal with the problem. Some people might argue that their organization never
has any problems, until they start to use performance measures, and the
performance measures become the troublemaker. Sometimes that is the case.
The answer to the above question is “all of the above.” Business processes in
organizations are like machines – the processes are repeated over and over.
For example, you produce goods and deliver them to customers, and collect
the money every day. When you stop doing it, it is like you have stopped
doing business. Hence, in order for the processes to operate smoothly, we
need to control them. Therefore, performance measurement is a necessary
tool. But the problem is that many people only use performance measurement
to solve problems. Once the problems have been fixed, they stop using that
performance measure. A risky action...
Let me give you an example. Let’s assume that we have a problem with
production. We are producing a lot of defects. One solution is to create a
performance measure for measuring the percentage of defects so that we
become aware of the problem and find a way to solve it. Yet, once the
problem is solved, we stop using that performance measure. You can guess
what is going to happen next, right? The performance measure is no longer in
place, we lose control, and eventually the problem resurfaces. Many people
would say, “Then, reinstall the performance measure.” Yes, you can start
measuring again, and the problem will be solved again. But if you stop
measuring again, in the end, the same problem will return. Can you guess
what would happen if this persists? Performance measurement would
eventually lose its importance. Even if you start measuring again, the
problem will not be solved. Why? Everyone knows that you will stop
measuring soon, as you always do. It is akin to developing drug resistance.
That is why I always emphasize that you should always measure what’s
important. Inconsistent measurement includes not only data collection, but
also data analysis, data presentation, and implementation.
#7 A performance measurement system must produce comparable
results.
As mentioned earlier, what’s more important than the outcome value of
performance measures is their comparability. It is very difficult to make
good use of outcomes if they cannot be compared. Outcomes that are hard to
compare can cause confusion. For example, if we design “number of defects”
as a performance measure, and find that the “number of defects” has
increased from 100 last month to 200 pieces this month. It seems like the
number of defects is much higher. Also it looks like our production process is
deteriorating. Maybe yes, maybe not. The higher number of defects might not
be caused only by the poor production process, it might also be a result of
more production. The more you produce, the more defects there will be.
Let’s say that last month we only produced 1,000 units, and had 100 defects.
However, this month, we have 200 defects, and produced 10,000 units of
goods. Now we can see that the higher number of defects is not a result of a
low quality production process, but of higher production. If we take a look at
the “defect rate” instead, it was reduced from 10% (100/1,000) to only 2%
(200/10,000). In fact, our production has improved. This is why we usually
create performance measures in ratios or percentages, which is easier to
compare than unit-counts. Be careful when you use unit-counting
performance measures, such as the number of employees who resigned, the
number of defects, etc. to avoid problems like this.
#8 A performance measurement system must not cause unnecessary fear.
Most organizational performance measurement system problems are
“human” problems. Designing an appropriate performance measure, and
considering various relevant factors before creating the measure are both very
vital. However, despite flawless performance measures, problems can still
occur if user attitudes have not been adjusted.
The term “performance measurement” itself makes people feel
uncomfortable. Imagine you are still a student. You probably would not like
these words: "There’s an exam today," "We’re going to have a quiz before
class is dismissed," "I’ll assign you a project to measure your performance.”
These expressions can cause stress. Same goes for work; we would feel the
same way. “If you cannot achieve this KPI, you will be punished.”
These words often create fear and stress, which raises the risk of undesirable
employee behavior, e.g., protesting against all kinds of changes. Sometimes
these fears become the source of false rumors in the organization, such as
"they are going to use KPIs to fire us," "these KPIs are aimed at reducing our
salaries." These rumors can become a barrier to organizational improvement.
Hence, we should deal with these fears before they create problems. Fears
related to performance measurement result from two main reasons:
1) Afraid of being punished, scolded at, embarrassed, etc.
2) Afraid of colleagues getting punished, fired, etc.
Number 1 and 2 can be equally damaging. Therefore, managers have to be
aware of these fears if they plan to implement performance measurement in
their organizations. Fears should be dealt with the right way. Before putting
performance management to use, management needs to inform employees
regarding the rationale and benefits of performance measurement. More
importantly, they should not use performance measurement as a tool to
punish their employees. The enemy of performance measurement is the
organization’s problems, not its employees.
#9 A performance measurement system must not create the “you do it”
culture.
Have you ever heard of a “you do it” organization? A “you do it” culture
implies that employees refuse to do their jobs. This usually is the cause of
failed performance measurement, because no one wants to be responsible for
anything. But who should take care of performance measurement?
“Accountability” is a simple principle; the person who is responsible takes
both the compliments and the blame. Thus, performance measures should be
controlled by an accountable person.
For example, who should be accountable for measuring defects? First, we
should ask ourselves who has the power to control and reduce defects. The
answer is the production department, right? Then the production department
should be accountable for this performance measure.
I have another suggestion about how to select the accountable persons. For
the best result, you should assign only one person or one department to be
accountable for a particular performance measure. The more people involved,
the less accountable a person involved will be. In other words, ‘we are
accountable’ actually means ‘no one is accountable’.
Have you ever noticed that none of the organizational performance measures
receives enough attention? This is because everyone assumes that there will
be a person who is already working on it. So go back and take a look at your
organization’s current performance measures, and ask this simple question:
“Who is accountable for this performance measure?”
#10 A performance measurement system must be correct.
What does it take for an organizational performance measurement system to
be considered as a failure? Many would respond, the system would be
considered a failure if the organization generates less revenue, incurs losses,
or even goes bankrupt. Well, it does not have to be that bad. We can say that
a performance measurement system has failed, when the system is not
accepted and used. This is already considered as a fail. Normally a failed
performance measurement system is caused by these main reasons:
1) The users do not understand the measure, or
2) There is a mistake in the system (e.g., measuring the wrong thing)
If number 1 is the case, then the solution is to train the users on what the
performance measure is, and how to use it. But if number 2 is the case, then
you need to adjust the system. For example, you can design a new
performance measure that is more concise and can better solve the problems.
Introducing a performance measurement into an organization is like teaching
a new language to everyone. We have to inform people as to why they need
to learn the language. Also, we need to hire a knowledgeable instructor of
that particular language in order for everyone to learn the new language the
right way.
The last question is, how can we know that the current performance
measurement system will not fail? Well, we can notice from the decrease in
inquiries or complaints. However, the best proof that can indicate the success
of this system would be seeing everyone benefit from performance
measurement in terms of work development.
#11 A performance measurement system must be “simple” and
“relevant.”
If you want organizational performance measurement to succeed, I have
some tips to give you: make it simple and relevant. Many organizations
invest a lot of money and manpower to design flawless performance
measures and excellent databases. However, no one pays much attention to
these measures. In the end, the performance measurement system fails.
The most common mistake is not making sure that the users understand and
feel that the performance measures put in place and the data they produce is
relevant. Otherwise, no matter how good the performance measure, or how
precise the data might be, no one will utilize it. “Simple” means that we have
to create a performance measure that is easy to understand. Avoid jargons,
and use familiar words that are already a part of the culture. Good
performance measures would not raise questions like “What is it?” In cases
where you cannot avoid jargons, you must explain the language to its
potential users. Do not assume that they would ask if they do not understand.
Most of the time, they will not ask, because they do not want to look less
knowledgable (why didn’t they know such a simple thing?), or maybe they
are just simply too lazy to ask.
Another tip is to be “relevant.” Everyone wants relevant information, right?
A simple example would be Facebook, because Facebook provides tailored
information. Your Facebook page is different from other people’s. And your
friend’s Facebook is also different from other friends’. Yet, everyone still
receives information from friends and acquaintances. This is what makes
Facebook world famous. Sending a report of performance measures to other
people is no different. First, you have to ask yourself if the report is relevant
to them. Marketing department would want information regarding sales, more
than the percentage of defects. If we send the percentage of defects to the
marketing department, it is very likely that they would not use the data.
I have a simple rule that you can use to test the effectiveness and efficiency
of your report. A good report should make readers understand the main
contents in 10 minutes. If it takes longer, it is very likely that they would not
utilize the data, which might indicate that the data is not “simple” or
“relevant” enough.
Chapter 7
Design a performance measurement system
Time flies… You’ve already read six chapters. Now is the time for the
chapter you’ve been waiting for. How can we design a performance
measurement system? Let’s learn how many performance measurement
designs and processes there are, and you will realize that designing a
performance measurement system is not that hard at all.
Let’s learn how to design a performance measurement system.
There are three approaches to designing organizational performance
measurement system:
1) Top-down approach
2) Bottom-up approach
3) Integrated approach
The “top-down” approach is when executive management designs overall
organizational performance measures first, and then performance measures
for each department are created. The advantage of this method is that the
management is already well-aware of the organizational strategy, hence the
designed performance measures would be aligned with the organizational
strategy. In addition, the departmental performance measures would also be
in alignment with the organizational performance measures since they were
all designed by the same person (or the same group of people.) However, the
notable weakness of this approach is that the employees would be
dissatisfied, because they were not involved in the development process.
The second approach is the “bottom-up” approach. This method allows
employees from each department to participate in designing their own
performance measures. After that, the designed performance measures are put
together to create organizational performance measures. The advantage of
this approach is that the employees would believe in the performance
measures, because they were the designers. If they still have doubts in their
own measures, then I do not know what else can be done... On the other end,
the weakness of this method is that it is difficult to consolidate the measures
created by different departments, as they have different directions and not
relevant to the organizational strategy, most of the time.
The last one is the “combined” approach. It begins by having the executive
management design the organizational performance measures, then letting the
employees design their own departmental performance measures. However,
there needs to be a theme that guides departmental performance measures to
be aligned with organizational performance measures. The pros and cons of
this approach fall somewhere between the first and the second approaches’.
Now back to the important question, which approach is the best one? The
answer is, there is no best one. It all depends on the characteristics of each
organization. Take a look at the pros and cons, and you should be able to
select the best one for your organization. Still, the most popular approach is
the top-down approach as it is the easiest way to ensure that the measures fit
the organizational strategy. So, give it a try.
Design a system in four steps
Before I introduce the main steps of designing a system, let’s take a look at
the definition of “organizational performance measurement system” once
again. Organizational performance measurement systems consists of:
1) Performance measure
2) Supporting infrastructure, which is composed of data collection
systems and reporting systems
Therefore, creating a performance measurement system requires the creation
of both the performance measure and the supporting system. We can
conclude that there are four main steps to building a performance
measurement system:
1) Determine what to measure and create a performance measure.
2) Set a target value, and set the data collection system.
3) Design a reporting system.
4) Adjust the system before launch.
If all four steps are properly executed, you will have established your
organization’s performance measurement system. In the next chapter, I will
get into details of each step.
Chapter 8
Create a performance measure
The first important step in designing a performance measurement system is
specifying what you should measure. This is the step that creates a lot of
misunderstandings. The most common one occurs when people brainstorm
on what they should measure, and end up with around 100 performance
measures, calling them all “KPIs.” In fact, the K in KPI is an abbreviation of
“Key,” which means important. Is it even possible to have more than 100
important things? Let’s see how we can select what we have to measure.
“Strategy” comes first.
Another significant factor in designing an organizational performance
measurement system is to understand the organizational strategy, because
the organizational performance measurement will become one of the tools
that transforms strategy into action. Therefore, if we do not know what the
strategy is, then we would not be able to design a performance measurement
system. If you do not know your goals and how to achieve them, of course,
you would have no idea how to measure your success rate. Here’s an
example... Let’s assume that an organization uses a strategy of
differentiation; the performance measures should be the number of new
products, the number of suggestions, and the R&D expenses. Whereas,
another organization that emphasizes a low cost strategy, then the
performance measures should monitor other things, such as the cost per unit
and the number of defects. Different strategies need different performance
measures. Therefore, understanding the strategy should be the top priority,
before designing an organizational performance measurement system.
Consider stakeholder needs.
Another thing that we should not ignore when creating an organizational
performance measurement system is to study the needs of stakeholders. Who
are the “stakeholders” of the organization? Many people would only think of
customers. Yes, customers are stakeholders, however, they are not the only
ones. Stakeholders of an organization include the owner, the management,
business alliances, employees, financial institutions, business partners, the
public sector, as well as the competitors and the society.
Many of you might wonder why competitors are considered as stakeholders.
Let’s take a closer look at the word “stakeholders.” It implies that they must
have gained from or lost something to the organization. What do the
competitors have to gain or lose? Get it? The customers! If they only take our
customers, then they would no longer be our competitors, because we would
be running out of business. Or, if we convert their customers, they are no
longer our competitors, because they would no longer be in the business.
What about the society? How could the society be a stakeholder? Think about
it. If we open an oil refinery in a community area, then of course, we would
need the community’s approval. Otherwise, conflicts can arise. In exchange,
we would need to improve the community’s standard of living.
As you can see, all stakeholders give to and take from our organization. Here
is what is important... To ensure the success of our organization, we need to
satisfy the stakeholders; and in turn, we must gain something back from
them. Therefore, a successful performance measurement must be created by
taking these people and their needs into consideration. We have to study the
needs of stakeholders by conducting a focus group or a survey, and figure out
how many levels of needs there are. We can divide those needs into three
levels: basic quality, performance quality, and excitement quality.
The basic quality concerns what people already expect to have, a must. So,
they usually do not express those needs. Despite the fact that they might not
have mentioned it, do not conclude that they do not want it. For example,
what do you expect the car you are about to purchase to be like in terms of
quality? Nobody would say that they want the car to run, because that is the
basic quality that every car must have.
The second quality is performance quality. This level of quality is clear-cut,
and can be measured. It is the common answers that people give. Let’s use
the same example again. What do you expect a car to be like? You might say
you want a fuel-efficient, powerful, and luxurious car. These are performance
qualities.
The highest level of quality is excitement quality. If we do not ask about this
quality specifically, we would not get the answer, because most people would
not even think of it. For example, what kind of system would you want your
car to have, that you cannot find in today’s cars? Your answer might be
autopilot, hydropower, etc. These things excite us, right? Studying the needs
of stakeholders can make us understand their needs and how to satisfy them,
so that we can design a more precise performance measure.
Create objectives and critical success factors.
Once we know the organizational strategy and have already studied the needs
of stakeholders, we must convert the strategy and stakeholder needs into the
organization’s main objectives. An organization’s main objectives are
answers to the question: “what objectives should be achieved for our
organization to be successful?” For example, objectives of an organization
could be:
1) Generating profit
2) Increasing customer satisfaction
3) Satisfying employees
Setting main objectives will give us a clear direction as to what we want to
achieve. After determining our organization’s main objectives, we should
define our “critical success factor” that will help us achieve those main
objectives. For example, if the main objective is to generate profit, then the
critical success factor would be to increase the number of branches, or to
generate more sales per branch. Simply put, critical success factor is the
cause, and the objective is the effect. However, you should create
organizational performance measures only for very important objectives,
because sub-objectives will emerge by themselves once we have transformed
the main objectives into departmental ones.
Designing performance measures
Let’s take a look at the main steps of designing organizational performance
measures. Mostly, when we talk about organizational performance
measurement, we would brainstorm what we should measure. Brainstorming
is a must, however, it is not the first step. Generally, the process would start
like this:
1) Define business processes, and assign the responsible person in
creating the performance measures for each business process.
2) Arrange a performance measure design training session for those
responsible individuals (in number 1) to set them off on the right
path regarding the proceses and performance measures.
3) Brainstorm to identify the appropriate performance measures. Each
performance measure must be aligned with the main organizational
objectives, as well as the critical success factors.
4) Consolidate all performance measures to establish organizational
performance measures.
It does not sound that difficult, right? Creating performance measures might
take months, or even years if the organization is large and complex.
However, if it is an SME, then these processes can be completed within a few
weeks. So, try to adapt these steps to your organization.
Performance measures must be related to each other.
As mentioned earlier, good performance measures must be aligned with an
organization’s main objectives and critical success factors. But that is not
enough. What I want to add is that once you have designed performance
measures, you must ensure that they are related to each other. Let me draw a
clearer picture. Assume that one of the main objectives is to make employees
happy. In order to make employees happy, we might think that we should
give them proper benefits. Can you see the rationale behind this? When we
offer proper benefits (critical success factor), the employees would be happy
(main objective). There can be more than one critical success factor, for
example, anything apart from benefits).
Now, how can we create a performance measure that would indicate the
happiness of employees, which is the main objective? We might measure
employee happiness by an employee satisfaction score that we could gather
from surveys. But how can we measure proper benefit, which is the critical
success factor? We can measure the percentage of employee benefit
expenses. Once we have created performance measures, we can re-check
whether the two performance measures are related to each other or not. From
the above example, if the percentage of employee benefit expenses has
increased, the employee satisfaction score should increase as well. Generally
speaking, if it makes sense, that means the performance measures work.
However, if it does not make any sense at all, then we should consider
switching to a better performance measure.
Quantitative or qualitative performance measures
This matter will concern the types of measurement mentioned earlier. We can
divide performance measures into two categories: quantitative and
qualitative. Quantitative performance measures can be measured directly
without adhering to human judgment (e.g., production time). Whereas, most
qualitative performance measures cannot be measured directly, because they
usually involve intangible things that require human judgment. This kind of
subjective performance measures usually raise questions.
Let me give you a classic example. I believe that many of you might have
conducted research, and distributed questionnaires to measure customer
satisfaction. If you have not, I believe that you might have completed this
kind of survey as a customer. Let’s take a look at the scale first. The widely-
used scale is 1 to 5, where 1 means the “least” satisfied, and 5 means the
“most” satisfied. Then, the researchers would analyze the data, and draw a
conclusion on whether the customers are “rather satisfied” or “rather
dissatisfied.” No one would ask, “What is the difference between ‘least
satisfied’ and ‘somewhat dissatisfied’?” Or, “What is the difference between
‘most satisfied’ and ‘somewhat satisfied’?” Think about it... Let’s assume
that I am a very rigid person who usually gives low scores. My 2 might mean
that I am “very satisfied” (because I usually assign 1s). However, my friend
is very easygoing. He gives 5s to everyone, unless he is very upset, then he
might give 4s. When we conduct a survey, we simply average the scores
between these two people; even though someone’s 4 might have less value
than another’s 2.
As you can see, measuring intangible things is not easy at all. In order to
reduce bias in performance measurement due to different standards, we
should illustrate “an example of a behavior” instead of just saying least or
most. In surveys that require very precise results, researchers might specify a
behavior corresponding to each scale level. For example, for 5, the most
satisfied, the associated behavior might be, “You are so satisfied that you
have written a letter to the CEO of the organization to express your
satisfaction.” When you see this kind of message, you would know that even
though you are satisfied with the service, you are still not satisfied enough to
write the letter. Then, you will not give a score of 5. For 1, the least satisfied,
an example behavior might be suing the company. So, if you are upset with
the service but not upset enough to sue the company, then you should not
select 1.
This technique can help adjust the standard of each person, because they now
understand the meaning of each score. But of course, as long as we are
human, bias will continue to exist. We cannot completely eliminate bias, but
at least with this technique, we can get a more precise result. The limitation to
this method is time constraint, because surveys like this require details and
time. In order for the respondents to complete the survey, we might need to
give them incentives, which means the investment in data collection would
be higher. You have to consider the trade-off between the result and the
expenses, to see whether it is worth it or not.
Financial or non-financial performance measures
We can look at performance measures from another perspective, and
categorize them into two main categories: financial performance measures
and non-financial performance measures. You can tell these two forms apart
by looking at the unit of measurement. If the unit is monetary, then it is a
financial performance measure. Whereas, if the units are things like the
number of defects or the number of complaints, then the performance
measure is non-financial. Sometimes it could be both; for example, revenues
per employee, where the numerator is financial but the denominator is non-
financial.
You do not need to choose which kind of performance measure is better,
because both of them are used in reality. Naturally, in for-profit
organizations, non-financial performance measures are the leading indicators,
while financial performance measures are the lagging indicators. Since we
should measure both the leading and the lagging indicators, we need both
kinds of performance measures.
Result or process measures
Let’s assume that we want to create a performance measure for a salesperson.
Which performance measure do you think is more appropriate: the number of
sales by that salesperson or the activities of that salesperson that would help
generate more sales (e.g., the number of customer visits, the amount of time
spent in responding to inquiries or addressing complaints, etc.)? Which one is
better?
The problem with the first choice is that sales is difficult to predict, because it
is influenced by various factors. For example, the decrease in the number of
sales might be caused by poor economic conditions; it might not necessarily
imply that the salesperson lacks the necessary skills. And vice versa – an
increase in the number of sales might be due to improving economic
conditions, and might not necessarily be a result of good sales skills. If this is
the case, then why would we use a performance measure that the salesperson
cannot control to measure his skills?
Then, maybe the correct choice is the second one. Just you wait... The second
one measures the activities that the salesperson performs to generate more
sales. This is indeed something that the salesperson can control. However,
what an organization wants is sales, not the number of customer visits. If you
use this measurement, then the salesperson would visit 3-4 customers per
day. What should we do then?
Before I answer this question, let’s take a look at the difference between the
two performance measures. The first measure is an example of a result
performance measure. It emphasizes solely the results, and is very popular in
the West, especially in the US. This measure empowers employees to come
up with their own processes, and measures only the end-result. If the
salespersons say that sales decreased because of the bad economy, the answer
they will get is that the effect of economy will compensate each other when
the economy gets better. It is a random effect, which means it can be good at
one moment and bad the next. So, you do not have to pay attention to it,
because it will eventually cancel each other out.
The second kind of performance measure is called process performance
measure. It puts emphasis on the process, and is more popular in the East,
especially in Japan. The idea behind this performance measure is that one
should be measured based on the things under his control. That is what is
considered as fair. What if the salespersons follow each process, such as
visiting customers frequently, solving problems on time, etc., but sales still
decrease because of poor economic conditions? Should we reward the
salesperson for the decrease in sales? The answer is yes, because had the
salesperson not followed the process, the sales figures might have been even
worse. Therefore, the decrease in sales, in fact, helped the organization
because the salesperson worked his hardest, and followed each process
correctly.
In contrast, if the sales figures of another salesperson increases although he
did not follow the process – he did not visit the customers or correct any
complaints –, despite the increase in his sales, he does not deserve any
rewards, because the increase in sales is not a result of his performance, but
of other factors like a recovering economy.
Now let’s get back to the question: which one is better? That would depend
on the culture and the values of each organization. In reality, we do not have
to choose one; we can use both, because each performance measure has its
own pros and cons. If we use them together, we can get better results.
Tips for creating effective performance measures
There are a few techniques I would like to introduce. You should consider
these eight things if you aim to create good performance measures:
1) Start by studying the main objectives and the critical success factors
of your organization.
2) Try to look beyond financial performance measures.
3) Try to find cause and effect relationships between designed
performance measures.
4) Include both leading and lagging indicators.
5) Include both quantitative and qualitative performance measures.
6) Consider the possibility of acquiring data and the validity of the
created performance measures.
7) Try to acquire information from within and outside the organization.
8) Use simple language and avoid jargon.
Try to include these eight tips in your checklist when you are working on
creating performance measures. Or if you already have performance
measures, then re-check them considering these tips. If you lack one of them,
you can use it to improve your performance measures.
Chapter 9
How to set targets and collect data
There is a saying that goes, “goals are meant to be smashed.” But before we
can smash them, we need goals first. Now let’s see how we can set goals to
create results. Once we have the goals, we will take a look at how we can
collect data for performance measures. Do not forget, “Garbage In, Garbage
Out.” If the input is garbage (meaning it is bad), the output will be garbage.
How to set target values
One of the most challenging parts of performance measurement for me is
setting target values. After a performance measure is designed, the target
value will be the indicator that tells us when we have succeeded. Without
target values, we would be walking aimlessly, without a final destination.
Thus, setting target values is a very important thing.
So let’s talk about the time frame in setting target values. Good target values
require time frames. Normally, we would divide target values into two levels
(or if you want more levels, it is totally up to you): short-term and long-term.
Here is another question without a definite answer: what is considered as
short-term or long-term? In fact, it all depends on the industry, and other
factors. In the past, when we talked about long-term, mostly it would mean
around five years. However, today’s long-term is becoming shorter and
shorter; most of the time, it would mean around three years. Some companies
even consider one year as long-term. All in all, it depends on how fast a
particular industry is changing. For now, I will consider three years as long-
term in examples. When setting target values, we have to think about where
we want to be in the next three years first.
Here is an example so you can get a clearer picture. Our defect ratio is 6,000
ppm (parts per million). How many defects should we have in the next three
years ? We can start by benchmarking with our superiors. Now, there might
be another question: will they give us any information about their practices?
Agreeing on information sharing would be a win-win situation. For example,
if they are willing to share certain practices with us, then we would share our
good practices with them, which is a possible case. Or sometimes we might
benchmark with the companies that are not our competitors. These could be
companies that are operating in other countries and have different target
customers than ours.
Once you receive the information, do not forget that most of the information
will be current. For example, the best of the industry has a current defect ratio
of 2,000 ppm. If we want to be number one in the industry, we have to be
aware of the fact that the industry leader will continue to improve itself as
well. However, it would be harder for them to improve than us, because they
are already the best. Let’s assume that in the next three years, their defect
ratio will be 500 ppm, so we set that value as our target, meaning that our
long-term target regarding defects is 500 ppm. This is how one can retrieve a
long-term target value. However, many people might raise the question,
“Who can I benchmark with if no one is willing to share information with
me?” or “I’m already the best in this, it would be hard for me to benchmark
with someone else” (You are very confident, aren’t you?). Do not panic. If
there is no one for you to compare yourself with, you can set up your own
targets. You can look at past data, and ask your employees to brainstorm on
how much further you can improve in the next three years (long-term target).
In the end, you will have your long-term target.
Now let’s talk about short-term targets. For example, what should the target
be for this year? Let’s say our long-term target is to have a 500 ppm defect
ratio, but our current ratio is 6,000 ppm. Let’s go with the most
straightforward method. If your current defect ratio is 6,000 ppm, and in the
next three years you want it to be 500 ppm, then the ratio needs to be
decreased by 5,500 ppm. Therefore, on (linear) average, we must reduce
5,500/3, or approximately 1,833 ppm, per year. Hence, after the first year, our
defect ratio should be 6,000 – 1,833 = 4,167 ppm, or 4,200 ppm if rounded
up.
However, for the ratio to reflect the reality, maybe we need to consider what
needs to be improved or developed first. Most of the time, the early stage of
improvement is easier than the later stages. If you ever tried to lose weight,
you would deeply understand what I am talking about. In the early stage, you
can lose 2-3 kilograms only by reducing your calory intake. But later on, your
weight just refuses to decrease, and you have to start exercising. Same goes
for performance measures. In the early stage, it would be easy to reduce the
defect ratio, because no matter what you lay your hands on, you can simply
improve it. But in later stages, it would get more and more difficult, because
the obvious problems have already been dealt with. So, in order to reflect
reality, our first year target should be higher than the targets of later years.
This way, we would be able to create short-term targets for each year that is
relevant to the long-term target.
Targets are meant to be adjusted (if necessary).
Should we adjust our target values? Many people are concerned that if they
allow target adjustment once, the target values might lose their reliability.
This is true if we adjust our targets without decent reasons, or if organizations
simply adjust their targets because they want to achieve a certain target value.
In this case, you do not need a target at all, or you can just set a target once
you know the result. In other words, shoot an arrow first, then put the
bullseye where the arrow has landed. You just do not need a target; sound
familiar? But if you do not allow any alterations at all, even if when the
predefined targets are impossible to achieve, then your employees would
have no motivation to work. Well, in such cases, you should allow target
adjustment.
Now the question is in which cases should we allow target alteration? Targets
should be adjusted when important incidents occur. First is when there is a
strategic change. An adjustment in strategy has a direct effect on the target
value of performance measures. For example, if we are making most of our
sales through salespersons, we might set our target value to be an X number
of sales per salesperson. However, if we add more distribution channels later
on (e.g., modern trade channels), that means our sales strategy will change.
At least, we need to take a look at our predefined target value for
salespersons to see whether it is still valid or not.
Next is when there is a change in customer trends. Customer preferences are
ever-changing. Sometimes, change happens very fast, but sometimes only
gradually. For example, in the past, we used cameras to take photos, but now
cameras are replaced with smartphones. Hence, we have to keep our target
values (especially long-term) in check as trends change, to see if they need
any adjustments.
The third incident is when there is an important event that greatly affects the
current situation, such as 9/11, the tsunami in Japan, or wars. These things
will affect our sales and other performance measures. We must review our
targets to see whether or not they are still valid in such cases. Furthermore, if
there is a request to adjust target values, we have to consider why we need
the adjustment, because if we alter our targets without any proper reasons, in
the end, those target values would lose their meaning,
There should be many levels of target values.
Let’s talk about the risks of having “All or Nothing” one-level target values.
Assume that I set a target of 1 million dollars for my salespersons, which will
be rewarded with a three-month bonus plus a trip to Europe. However, if they
cannot achieve it, they will get nothing at all. Is this target exciting and
attractive? Well, if today is the first of January, then maybe yes, I would be
able to motivate almost all of the employees, because everyone wants a three-
month bonus and a trip to Europe. But what if some salespersons have
already achieved one million dollars in sales by June, by the first half of the
year? What would happen to their motivation to work? Of course, their
motivation would decrease, because they have already achieved the target.
There is no need for them to generate more sales, because they’ve already
gotten all of the rewards. If you think about it, these employees who have lost
their motivation are likely to be the company’s top salespersons; otherwise
they would not be able to achieve the target within the first half of the year.
As time passes – July, August, September... – we would lose these
salespersons.
Let’s say it’s October now. How many salespersons do you think would still
be selling this company’s products? Should be less than the beginning of the
year. No, that is not enough... What? There is more? There will be another
group of salespersons who haven’t reached the goal but also have lost their
motivation. These people are the ones who are way behind the target value.
For example, by October, they only manage to generate 300,000 dollars in
sales. They know that if they can only make 300,000 dollar sales in 10
months, they would not be able to achieve one million within three months.
These people would give up, and the company will end up with very few
salespersons by the end of the year. The rest of them are all on vacation.
See how having a one-level target value could be risky? And if that is so,
how can we fix this problem? Let’s see what could happen if we have a
multi-level target value. Will it deal with the problem? And how? Using the
same example, instead of setting the target value to be “All or Nothing,” let’s
have a go with three levels. For example, if they can achieve 800,000 dollars
in sales, they will receive a one-month bonus; one million dollars gets them a
three-month bonus; and 1.5 million dollars gets them a five-month bonus plus
a trip to Europe. This way, if our top salespersons have already achieved the
one million dollars in sales within the first six months, they will not stop
making more sales because there is a higher target waiting for them. Or if it is
reaching the end of the year and some salespersons have only managed to
generate 700,000 dollars in sales, they would not stop, because despite not
being able to get the out-of-reach biggest reward, there are still other smaller
rewards waiting for them.
Multi-level target values motivate more effectively than the one-level target
values. But the thing is, achieving the highest level of target value decreases
motivation. That is correct, and that is why we have to set the highest level to
be challenging but achievable. This will help motivate everyone.
8 techniques for setting target values for performance measures
This is a checklist for those who are about to define target values for their
performance measures:
1) Target values can be adjusted if there is a change in strategy,
customer trends, and circumstances that affect performance
measures.
2) Multi-level target values can motivate employees better than one-
level target values.
3) The highest level of target values should be challenging but
achievable.
4) Target value and rewards should be linked; the harder the target, the
more attractive the reward.
5) Employees should be involved in setting target values, because they
are the ones who will achieve it. If they do not feel like they own the
target value, it would be hard to keep them motivated.
6) Past target values could be useful in setting new target values.
7) If there is no past data (maybe it is a new product), then customer
and expert opinions could be a good source of reference in setting a
new target value.
8) If competitor or industry average value is available, it could be used
as a reference in setting a new target value.
Try adopting these techniques, and they might prove to be very useful.
Garbage in, garbage out
After we have a target, it is time for data collection. Have you ever heard of
“Garbage In, Garbage Out?” Its meaning is very straightforward: bad input =
bad output. It implies that if you have incorrect input, even advanced analysis
and complex mathematics will not help make anything better, because the
result will still be useless. Same goes for performance measurement. If we
have carefully selected the best performance measures, but then we input
incorrect data, the results will be incorrect. It will not matter at all how
excellent our analysis is.
Therefore, information accuracy is one of the most significant factors in the
performance measurement process. First things first. We need to ensure that
the data is correct. Be careful when you ask your employees to punch in the
data, so you do not end up getting a blank sheet of paper. This can mean two
things: (1) Such data does not exist, and (2) The data exists but the employees
refuse to input. Most of the time, number 2 is the case. But how can we
encourage employees to punch in the correct data?
Let me tell you a story. In order to measure the percentage of defect,
production employees have to fill in the number of defects, because they are
the ones who produce defects and know best about it. However, it turns out
that by the end of the day, the company only receives blank papers. There are
two possible cases: (1) There is no defect today, or (2) There are defects like
every other day, but the employees did not fill in the forms. I would suggest
that number 2 is most likely the case, not number 1. If you do not believe me,
then wait for a couple of more days. If number 1 is the case, there should be
some defects on the next day because it is very unlikely that there will be no
defects at all. If this were the case, then there would be no point for us to
create the performance measure in the first place.
Firstly, we need to learn why the employees did not fill in the form. Maybe
they simply do not understand it, or maybe they just do not see the
importance of doing it. Actually, most of the time, it is because of fear. When
employees need to provide information, especially a negative one like
defects, they would naturally be afraid that once management receives the
data, it might be used against them. For example, the management might
reprimand them, reduce their salary, or even fire them. When employees are
afraid, they will not provide true data. This is very important, because if we
receive incorrect data, the performance measure would be useless, no matter
how well it is designed. What we should do is to take away their fear,
especially when what they fear is not even real. We have to inform the
employees that the number of defects is not being collected to serve as a
punishment. We do not collect the data to fire the employees, but rather to
stop defect problems. We have to make them understand that performance
measurement system is the tool that will help management eliminate
problems, not employees.
Data are valuable, do not throw them away.
Have you ever noticed that data collection is not an easy task? Some people
do not want to provide any information, because they are afraid that the
information might come back to hurt them. Some people want to cooperate,
but they do not understand what kind of data is needed. We can say that it
takes “blood and tears” for some organizations to retrieve all the data they
need.
Now let’s assume that we have successfully retrieved all the data. The next
question is, what should we do with it? This is also a vital step. The data that
we have acquired must be arranged and be accessible, because these data
have to go through data processing to be converted into various performance
measure values, which would then be used to create reports. Is data collection
software a must-have? The answer is that it depends on how complex your
organization is. If it is highly complex and is a large organization with a huge
amount of data, then data collection and management software should make
everything easier for you. But for SMEs with few data, MS Access or Excel
should be more than enough. More importantly, it is likely that the data that
is collected during the early stages might not be 100% complete. No matter
how well you prepare, there will still be misunderstandings, incorrect input,
etc. Do not panic. If something is wrong, then fix it. For example, you can
add more explanation to the form. If we just let it be, it could be harmful as
the creditability of the performance measurement system will go down with
it. And once your employees think the system is erroneous, do not expect
them to use the data from the system ever again.
Before getting your hands on data collection
When we plan to measure our organization’s operations, the first thing that
we need to consider is data collection. Many organizations start off by
designing a form for data collection. But hang on... Did you know that most
of the time, the process by which you ask your employees to fill in the data
becomes a barrier in data collection? Sometimes it even results in employees
objecting to the idea of performance measurement.
Why is that so? Because sometimes the form that we use is the same as many
other forms, so it turns out that the employees end up having to fill in the
same data over and over again. So I recommend that you take a look and see
if the data you need is already stored in your database or not. In other words,
talk to your IT department first. If your organization is using an ERP
(Enterprise Resource Planning) system, it is likely that you already have the
data in your database, but it is collected for other purposes. If this is the case,
then cool! You simply need to retrieve the data and analyze it to receive the
performance measurement result that you are looking for. However, do not
expect to have every single data in your database. That would be too much to
expect. Most qualitative performance measures (measurement of feelings and
emotions) are not stored, which brings us to yet another important point. If
you do not have the data, do not abandon the performance measure. The
reason why we come up with a performance measure is not because we
already have data on hand, but because that performance measure is
important. If you do not have the data, then you need to collect it. You can
conduct a survey, an interview, or anything. As long as it is necessary, you
must do it.
What should we do if data is not available?
Sometimes you might find yourself in a situation where you have already
built a performance measure, just to realize later on that you cannot collect
the data. What does “cannot collect the data” mean? You might find out that
some types of data require more investment than your budget allows, or you
might have the budget for it, but the value of the data itself is not worth the
investment. So what should we do? Many people would just give up because
they cannot collect the data. But hold on, do not give up so easily. If you do
not have the data or lack the access, you can try using “surrogate
performance measures.” Surrogate performance measures might not be as
effective as the normal performance measures, but it is better than nothing,
right?
Let me give you an example. Assume that we want to design a customer
satisfaction performance measure by conducting a survey to find the average
satisfaction score. However, we find that each survey will cost quite a lot of
money, and we cannot afford it. So, we should consider a way to measure
other kinds of satisfaction that could substitute for the customer satisfaction
score. We might find other performance measures like the repeated purchase
rate, which may be data we already have. It should be able to reflect customer
satisfaction more or less. This kind of performance measure is what we call
“surrogate performance measure.”
Oh, and one more thing, do not forget external data. Sometimes when we say
we could not collect the data or that data collection requires high investment,
these data might already be collected by external organizations, such as
research institutions, ministries, and other public institutions. Last but not
least, the phrase “unavailable data” is just another obstacle that we have to
overcome.
Source of data
Now let’s get to data collection. From where should we retrieve the data?
Normally, there are four main sources:
1. Electronically stored data
These data may be stored for other purposes - financial data, for instance, are
stored to be used in creating financial reports. Coming across these data is
like finding lost treasure because we do not have to invest anything at all. We
only need to retrieve the data, and can utilize it right away.
2. Data stored on paper
These data may be stored for other purposes as well. However, they might
not have been uploaded to a digital database. For example, we might have the
number of defects stored in monthly production reports. When we want to
use these data for our defect performance measure, we can retrieve them from
monthly reports without having to collect new data.
3. Data that need to be additionally retrieved from a digital platform
If our existing database does not have the data we want, then we have to
collect additional data. My suggestion is, if possible, you should convert the
data into digital format all at once, so that you can skip the punching in
process during which mistakes often arise. An example of this would be
using an employee card scanning system to collect data on absenteeism.
4. Data that need to be additionally retrieved from documents
This is the last source of information. If the first three sources are not
available, collecting data from documents can be your last option. The reason
why I want it to be the last option is because it is time consuming. Your
employees might get so bored of it that they begin to object to the whole
system. But if it really is necessary, then you have to do it – collecting
employee satisfaction scores through a survey, for instance.
It seems like there are two main data collection systems. One is digital
systems, which do not involve any paper documents, and the other is manual
systems, which primarily rely on paper documents. Digital systems are easy
and convenient, but require high investment, especially to build. Manual
systems do not require much investment, but are time consuming and
inconvenient. So organizations have to consider the pros and cons of each
system.
How frequently should data be collected?
This is a very common question. Should we collect data daily, weekly,
monthly, or annually for our performance measures? This question is about
the “frequency” of data collection, which normally depends on two factors:
the cost of data collection, and the changing rate of data.
Regarding the first factor, if each data collection incurs a high cost, then of
course, we will not be able to collect data on a regular basis. Otherwise, our
organization would go bankrupt. For example, if we have to invest one
million dollars each time we collect customer satisfaction data by conducting
a survey, we will not be able to collect the data daily and spend a million
dollars every day. That would be too much to afford, or if we can afford it, it
still would not be worth it.
Regarding the second factor, let’s assume that the cost incurred is not that
high. However, the changing rate of the data is quite low. In this case, we do
not need to collect the data frequently. Let’s say we use online questionnaires
to retrieve employee satisfaction scores. No matter how many times we
collect the data, the cost would not be that high. But still, we would not send
out daily online questionnaires to our employees. Why not? Because
employee satisfaction would not change much over the period of a day.
Hence, collecting data that is unlikely to change frequently would incur
unreasonable costs. Or if it does not incur a high cost, it would still attract
unnecessary annoyance.
On the other hand, if the data is prone to change but we rarely collect it, we
will not be able to see the trend. For example, you would not collect data on
stock prices weekly, right? Because stock prices change every day, or even
by the second. If you collect stock price data on a weekly basis, you will not
be able to see the change in stock prices during the week. Well, it is like
everyone says, “Too much or too little can both be bad.” It is better to be
“just about right.” Now, many of you might still wonder how it’s possible to
know what it means to be “just about right.” I have a suggestion to help you
decide the frequency of data collection for each performance measure.
There is a study that states that we should collect data six times during the
time of change of that performance measure to be able to see the trend
clearly. For example, if we want to see the change in customer satisfaction
over a period of six years, we should collect data annually. However, if we
want to see the change in customer satisfaction over a three-year time period
(because customers change frequently in this industry), then we should
collect data once every six months. And if we participate in a fast-paced
industry, we might want to analyze our customer satisfaction trend over a six-
month time period. This means that we should collect data monthly. I believe
this information should be beneficial for those who plan on collecting data.
So, give it a try.
When should data be collected?
Once we have decided how frequently we are going to collect data, we also
have to decide which day of the week, month, or year we are going to collect
the data. We need to collect accurate data for our performance measure,
which means that the time of data collection is also important. Mistakes
usually occur when selecting the time of data collection. If we choose to
collect data at inappropriate times, we might get incorrect data or data that
does not reflect reality, which means the performance measure will be
incorrect as well. And the rest is history.
Let me give you an example. Assume that we have already decided to collect
customer satisfaction data from customers who use the service of a mall once
a month. Then we ask our employees to distribute customer satisfaction
questionnaires at 11 am on Monday. So, the employees go to the mall to
distribute the questionnaire, and finish at noon. Now, it is time for us to
process customer satisfaction data, analyze it, and make recommendations for
future improvements. Have you noticed the potential mistake? If we only
collect the data on a weekday morning, despite having enough numbers in
our sample, we might only cover a specific group of customers. Plus, they
might not even represent the majority of the mall’s customers. If we collect
data just so we can get it over with, our data would be no different from
garbage, because we could barely use it or could not use it at all.
Who should be the data collector?
This is another common question, because, in many organizations, people try
to evade the responsibility as it means that they have to work more than
usual. Plus such task is very much hated by most people. However, the
answer to this question is not that difficult. Firstly, if the data are already
stored in the database, we would not need anyone to collect them. We simply
have to ask the IT department to retrieve the data from the system, and then
we can process the data right away. However, if such data does not exist and
needs to be collected, the simple solution is to have the ones whose work is
most relevant to that data collect it.
For example, if we have the number of defects designed as a performance
measure, who should be the ones to collect this data? We have to go back and
check to see which department is responsible for creating defects, which
would be none other than the production department. Hence, in this case, the
production department should be the one responsible for collecting the data.
Having the responsibility of data collection does not mean that a particular
department has to be responsible for the results alone. For example, if a
salesperson is responsible for collecting daily sales data, it does not mean that
he has to be held responsible for a decrease in sales. Sometimes the decrease
in sales figures might be a result of poor production quality, bad
advertisement, or many other things. In any case, someone should be
responsible for data collection. Otherwise, you might end up with
“performance measures with no data.”
Cautions of data collection
It takes a lot of effort to acquire data, so we should take good care of the data
collected. We should store it systematically. Even though we might have
already processed and reported the data, we should still not throw them away,
because we will never know when we have to utilize those data again for a
different purpose, or we might even create new performance measures that
require these past data.
The next caution of data collection is about data access restriction. Some data
are sensitive to an organization’s competitiveness such as cost of production.
This is the kind of data that needs access restriction, because the higher the
number of people involved, the higher the risk.
The last caution is computer viruses. I believe everyone has heard of or has
experienced a computer virus before. Our data storage system should be
secure. In addition, we should also back up the data in order to prevent data
losses.
Chapter 10
Prepare a result report
In previous chapters, I discussed system design, target setting, and data
collection. In this chapter, it is time for presenting the collected data. So let’s
take a look at important factors that we should pay attention to.
Do not fall at the last hurdle.
It is a shame that many organizations with good performance measures and
data collection fail towards the end. “Failure” in this case means that no one
utilizes the data. You can even say that the data report has somewhat become
more of a homework that just needs to be handed in. After that, no one knows
nor cares about what happens to it. It is a pity because reporting is one of the
last processes. Designing a good performance measure and collecting
accurate data require a lot of effort. But if it turns out that we fail at reporting,
these processes would literally be worth nothing. Yes, it would be difficult to
create a perfect report during early days. However, 75% is good enough for
me. We can gradually adjust it toward perfection. Most of the time, bad
reports are not a result of failed computer systems or miscalculations, but of
poor understanding of performance measures or processes. So let’s see how
we can create an interesting report of performance measure results.
Prepare a “simple” report.
The first technique I would like to introduce for effective reports is to make
them as simple as possible. Everyone likes the word “simple” – report
creators like it, and so do users. Doing what everyone likes can lead to
success. Think about it, if it takes us weeks to prepare a report, we would not
want to do it, right? Plus, once the report is sent out to employees of each
department, it would take them weeks to finish reading, and understand
everything in the report. Do you think anyone would ever read such a report?
Therefore, the first rule of thumb is to make everything “simple.” We must
have a user-friendly report system. Let me give you an extreme example. If
we can create a report within five minutes, that would be excellent. This is
where a software or an IT system can be a great helper. It would take only a
few minutes for users to understand the report and put it to good use right
away. This is what is called “simplicity.” Easy plus easy equals effortless. If
this does not succeed, then I do not know what else can.
Prepare a “relevant” report.
Now let’s take a look at another technique that could make a report more
interesting. Use a rifle, not a shotgun to hit the target. What does that have
anything to do with result reports? If you love American films, you would be
familiar with how protagonists use a rifle gun. They would place the gun on
their shoulder, which is why this kind of gun is highly accurate and hardly
misses the target. The short gun is the opposite; it’s hit or miss (but most of
the time, miss). Preparing a report is like firing a gun. If you create a report
like you shoot a rifle, your report will hit the target better. A report that is
meant to be sent to the marketing department, should be designed specifically
for the marketing department with relevant marketing data. Likewise, a report
for the production department should be designed specifically for the
production department. This way, users will receive only relevant data.
However, creating a report like you fire a short gun, trying to shoot
everything in sight (e.g., you prepare one big report that contains the data of
every department, then make multiple copies and distribute to everyone in the
organization) is firing blind, expecting everyone to search for the relevant
data on their own. I would say you are expecting too much. Most people
would end up not reading anything in the report. This could be very
heartbreaking for the people who work on preparing the report.
Think of the readers
When preparing a report, you have to ask yourself about who is going to be
reading the report. It is a simple question that people rarely ask themselves. I
have experienced this kind of complaint quite frequently: no one reads result
reports anyway, what should we do? Before jumping right into adjusting the
report, adding more colors and contents, the first question that we should
answer is, “Who will be the readers of this report?” If we can answer this
question, we would know what to do next.
If the report will be sent to the CEO, how much detail do you think you have
to go into? If you have too much detail in the report, do you think the CEO
will read it? What about the report for the CFO? What kind of contents do
you think you should include? It has to be an executive overview instead of
details, right? If the report is meant for head of the department, then you can
add more details because he or she needs the details to solve problems. Or if
you really do not know what that person wants, the easiest way is to ask him
or her. Try this simple technique every time you are sitting in front of a
screen, preparing a report – think of the readers.
Abolish the one-size-fits-all system
The key to creating a good result report system is to decentralize. Do not
stick to the principle of “One Size Fits All,” because it is nearly impossible to
have a form of report that is suitable for every department and every incident.
Creating a standard form of report that does not consider what department the
performance measure is from and the different data needs of departments,
could make the report useless. Meaning, it would be hard to find relevant
data, which would make the report uninteresting.
The public sector often uses this system, because it is easy to create, as they
can simply design a single form for employees to fill in. Sometimes the
employees can only fill a couple of answers in, but have to read through 100
questions to do so. Most of the time, they would fill in “N/A” or “0.” To
make matters worse, those data (that were not needed to be filled in) are
created into tables and graphs. Therfore, the report only contains “N/A”
values. No matter how useful this report could have been, it would still be
dull because relevant data are all obscured by a pool of irrelevant data. So
let’s change how we do things. Let’s prepare a report that contains relevant
data for each particular department. This way, the report would be interesting.
We can even add more details, explanations, and analysis, too. I believe that
most people would be looking forward to read such a report and put it to
good use.
Good news or bad news?
Have you ever noticed that sometimes reports contain good news, but from
time to time they also contain points of failure? Let me give you an example.
Let’s assume that we have two possible ways to report a performance
measurement result: 99% of our products passed quality standards, or 1% of
our products failed quality standards. These two forms are called
conformance reports (99% good quality products) and nonconformance
reports (1% defects). Which one should we use? The answer is that it
depends on the objective of the report. Conformance reports are commonly
used to communicate with people outside the organization, and it portrays the
good side, which would attract customers. Another advantage of this kind of
report is that it sounds positive; it can motivate employees. Everyone loves
good news. However, if reporting is for internal use to make further
improvements, then nonconformance reports are used; 1% defects will be
reported. This kind of report promotes continuous improvement, because if
we say that we are 99% good, most people would perceive that the
performance is already excellent, so there is no need to develop further. So,
try to apply these two forms of reports in your organization.
Using indices in reports
An index is a value that is calculated by taking every performance measure
into account. Let me give you an example. We might have many quality
performance measures. However, to see an overall picture of our
organization’s quality, we need to calculate the index of all performance
measures by adjusting the scores using the same scale. It is not necessary to
give equal importance to each performance measure. We can assign a greater
weight to important performance measures than the less important ones.
Creating an index value can provide an overall direction on a particular
matter. If you cannot picture this, try thinking of the stock market index.
Stock market index was created to act as an indicator of overall market
performance by including every stock price in the market calculations.
However, what you need to be aware of when using the index is that the more
performance measure values included in the index, the lower the variation of
the index would be. So, do not misinterpret the index value. When an index
does not change, it does not always mean that every performance measure
does not alter. When an index is stable, it might be caused by a great increase
in certain performance measures, and a plummet in others. Same goes for the
stock market indices. Stability of the stock market index does not imply that
none of the stocks’ performance changed. It is possible that half of the stock
prices in the market have risen, while the other half have declined.
How to report “confidential” data
There is always a question on whether or not we have to report every single
performance measure to workers. The answer is “we should,” because
otherwise they would not be able to improve. Another top question is, what if
that performance measure is confidential. For example, should we report the
performance measures that can put us at a disadvantage if acquired by our
competitors, such as cost per unit?
Now this question is interesting because there is a risk of competitors
acquiring our data. How can we know if one of our employees has a
girlfriend who works at a competitor company? Or what if one of our
employees switches to a competitor company? Having them sign a contract
might still not be effective because we would never know when our
employees are going to share our confidential data. It would be a little bit too
much to ask them to swear on it. Yet, if we do not report results, performance
measures would be of no use. For example, if we do not report the cost, then
our employees would not know what the cost is, and consequently there
would be no improvement. So, what can we do?
The answer is that we need to report it. However, it is not necessary to report
the actual number. Am I saying that we should report wrong data? Not at all,
but there is a way out. Instead of reporting the actual data, we can report “the
rate of change” of that performance measure. For example, instead of
reporting the cost per unit, we can report the rate of change in cost per unit to
show the percentage of increase or decrease. Or we can utilize the score;
meaning, instead of reporting the cost per unit, we can simply provide the
score. The employees do not need to know how many dollars the score
represents. Rather, they only need to know whether or not the cost has
increased, which should be enough for them to work on improvements.
Another method is to report the index value. We could use a value from any
year as a base value, and set it to 100 - I just made up this number, you would
need to adapt it. If the cost increases by 10% next year, then the index would
be 110. With this method, employees would have enough data for further
improvement while we eliminate the risk of revealing confidential data to
people outside the organization.
How many forms of reporting are there?
When it comes to reporting organizational performance measurement, there
are many forms of reports we can utilize. Let’s start with the most low-tech
and probably the most common one: the paper-based report. This kind of
report does not require high investment, all you need is a computer and a
printer. However, the disadvantage of this method is that it is difficult to
make changes in the future. Let’s say the report’s user needs the data to be in
the form of a table rather than a graph. The user has to contact the report
maker, and the user would never know if he would be able to get in touch
with that person. Plus, we would never know when the report maker would
finish creating the report. Then, there would be one revised version after
another. The user might end up forgetting what data he has asked for in the
meantime.
The next form, paperless reports, do not need to be printed out or bound. The
most common format is a Word document or PDF, which would then be
distributed through email. Users can read the report anywhere as long as they
have a phone or laptop. There is no need to carry the report around, hence it
is more convenient and cost (paper) saving. However, this form of report can
still be difficult to edit.
Another from is a report created through a website. We only have to send a
link to a particular website, together with the login credentials. This kind of
report is getting more popular, because once a report is created, we can
upload it to a website right away. We do not need to type report contents or
send emails to each employee. More importantly, we can adjust the report
automatically, by checking the login history to see which division or
department the users are from. Once we know which department the users are
from, we can choose to display only the data that are relevant to them. In
addition, it would be easier to track download history and to see who never
logs into the system. If the latter is the case, then there is problem.
Another form of performance measurement report – the online report - is a
very good one, because it is both creator and user-friendly. With online
reports, we can simply provide login credentials to users. The users can log
on to the system to see relevant reports. A marketer can see marketing
performance measures, while a financier might see financial performance
measures. What makes it even better is that this form of report allows users to
adjust the reports themselves through filters. Users can select which data they
want displayed on the report, or create their own graphs. Users love this kind
of report, because they can get anything they want in less than 10 seconds.
The creator would be satisfied as well, since he or she does not have to create
new graphs. It is a win-win situation. However, there is one small
disadvantage to this kind of report. It requires investment in software. If you
ask me whether or not it is expensive, I would say it depends on the benefits
you receive from it. If your organization is big and has a lot of data, I would
say the software is worth it.
And here comes the most advanced kind of performance measurement report.
Like online reports, this form requires login credentials from users. When
users log in, they see only the relevant reports, and can adjust the reports
according to their needs. But what’s amazing about this kind of report is that
it offers real-time data – meaning that you can retrieve the data in real-time
and they will always be updated. Let’s assume that we are looking at sales
revenues. Data collection would happen all the time at points of sale. We can
see the graph move all the time, just like the stock market. How’s that? Isn’t
it exciting? I have once joked with my students that it would be pretty
exciting to have a real-time grade report. A real-time board would be set up at
every desk. Whenever the students got bored and paid attention to their phone
instead of listening to me, their grade would gradually reduce. Wouldn’t that
be great?
One company has adopted this system, and found something interesting.
They measured the performance of their call center by allowing the
customers who called in to assess them. Well, it does not sound that
interesting when I put it this way. But here’s the difference. An assessment
system like this is randomized. They did not ask every customer to evaluate
their performance, rather, they only asked some of them. Now a typical
organization would gather this information and analyze it at the end of the
week or month to assess employee performance. But not this company. This
company calculated customer satisfaction right away, and displayed the result
in real-time on their employees’ computer screens, as they responded to
customer questions. What’s even more exciting is that this company used this
performance measure to determine employee bonuses. Can you guess how
the company did that? They finalized their evaluations by the end of every
shift. After every shift, the employees would know whether or not they would
receive a bonus for that day. Customer satisfaction performance measure was
used as a criterion. If the employees could achieve the predefined goal, then
every employee working during that shift would receive a bonus. However, if
they could not achieve it, no one would get a bonus.
Oh, one more thing… The customer satisfaction score displayed on the
employees’ screens an average score that did not belong to anyone in
particular. And that score was used as a bonus criterion. So, how is that? Isn’t
it exciting? However, in the end, this system failed, and the company had to
discontinue it. Before we go any further, let’s think about why this system
might have failed? What could be the reasons behind it? Can you come up
with any? If not, I’ll give you a little more time...
Here’s the answer. Many people might guess that this kind of system would
stress out the employees. Well, that is part of the reason. If anyone gets
measured while they are working, they would stress out. But the main cause
of the failure is that the customers called to complain. But why is that? This
system should benefit the customers because the employees would have to
take good care of customers, right?
Here’s what happened. Many customers called to complain that they had
been experiencing something weird lately. For example, if they made a call
during a certain time, they would get bad responses. Let’s say if they called
around 4 pm, the employees would talk to them impolitely, and did not serve
them well. Sometimes they said that the service was absolutely terrible. But if
they called during other times, the service would be good. They had tried
calling several times, and they still experienced the same thing. What
happened?
First, let’s look back at the real-time measurement system. This system is
good because it can tell the average satisfaction score right away. But there is
a disadvantage to that… Once the employees know the customer satisfaction
score in real-time, they know whether or not they will get a bonus for that
day. So, when it is near the end of the shift - let’s say the shift ends at 4 pm –
each call center employee knows for certain whether they are receiving a
bonus or not, because the score is displayed in real time. If the customer
satisfaction score is far behind the goal, they would know that they would not
be able to make up for the loss in the next 5 minutes. You can guess what
would happen next… Employees do not have to work hard anymore, so it is
unfortunate for the customers who call during that time. This kind of situation
would happen when the customer satisfaction score is way above the goal
near the end of the shift as well. The employees know for certain that they
would get a bonus for today, so let’s just sit back and relax. This is the reason
why this system had failed. It is kind of unexpected, right?
Manual reports vs. electronic reports
So which one is better: paper-based reports, aka. manual systems, or digital
systems that require software? In order to answer this question, we have to
take a look at three factors:
1. The amount of investment you are willing to make
Manual systems barely need any investment at all except for a computer and
a printer. However, in practice they can prove to be difficult to use. Let’s say
the user needs to adjust the graph or request additional information. This
means that you would have to recreate the graph and table, print, and send
out the revised report. If users rarely make extra requests, then it would not
be very difficult. However, if there are a lot of requests, you might have to
hire a team to deal with it, which means higher cost. If you use a digital
system, of course, you would need to invest in software and system
installations; however, it would make everything much easier in the long run,
and users can work on the revisions themselves.
Chapter 11
Do not use it if it fails a test
We should be done with designing a performance measurement system after
we have designed performance measures, collected data, and reported the
results. But for certitude, we should test the system before launch. Testing
would allow us to determine the cause of potential problems so that we can
fix them before starting to use the system. Let’s see what we need to check.
#1 Test the relevancy to strategy.
As I have mentioned earlier, a good performance measurement system
reflects the organization’s strategy. But how can we know whether our
performance measurement system is aligned with the strategy or not? This is
a very interesting question. You can simply put it on trial. If the predefined
strategy gets translated into action, which results in a certain outcome, that
means the system works. If not, then the system does not work. This answer
is not a simple answer, but rather a convenient one. Well, it’s like we build a
car and when a person asks us, “Is this car safe?”, and we simply reply, “Go
on a test drive. If it does not explode, then it’s safe.” This is not a nice reply
at all.
After we have finished designing an organizational performance
measurement system, we should test it. The first test is to see whether the
system is aligned with the organization’s strategy or not. The best way to test
is to take the system to the executive management team, and discuss with
them. They are the ones who develop the strategy, hence they would know
whether the performance measures match their strategy or not. Most of the
time, designing a performance measurement system takes a long time, and
there are many adjustments along the way. Or sometimes there are changes in
the organization’s strategy. Testing ensures that what we measure covers the
key points in the strategy; no more, no less.
#2 Test the validity of the performance measure.
Having tested strategic relevance, the next step is to test the validity of
performance measures. How can we know whether our performance
measures give us the correct values or not? I think this is a very good
question as well. You can try the following methods to check if your
performance measures give the correct results or not.
1) Take a look at important business processes: production, customer
management, etc.; and see if there is any performance measure that
is controlling these procedures. If not, the number of existing
performance measures is not enough.
2) Ask yourself how effectively the existing performance measures
demonstrate the changes in those procedures. Assume a performance
measure determines the % of defects – let’s say if the number of
defects increases, the value of this performance measure would rise
immediately, which shows that the performance measure works.
However, if your performance measures can only show whether
there are defects or not, meaning that you would not be able to tell if
the number of defects have increased, then that performance
measure does not work, because it can only tell that “there are”
defects.
3) Try checking the correctness of the existing performance measures
by collecting data and calculating the results manually. Do not trust
the IT system or software, before you get to compare the results with
your manually calculated number first.
4) Try plugging in made-up numbers to test the system once again. For
example, if you know that the % of defects is calculated by dividing
number of defects by number of produced goods, then key in 10
pieces for defects and 100 pieces for produced goods. The accurate
system should return 10%.
5) Try adjusting the numbers from step 4. For example, instead of
typing in 10 pieces, try keying in 50 pieces (with 100 pieces of
produced goods), and see whether the number changes from 10% to
50% or not. You can do this multiple times to validate.
Try adapting these five suggestions to your organization.
#3 Test data accuracy
Another significant component in creating organizational performance
measurement systems is data accuracy. Before using the system, you have to
ensure that your data is accurate. But how can you be sure of that? You have
to test it first. The easiest way to test is to enter all data into the system, and
examine the result of each performance measure. Strange results might
indicate that there is something wrong with the data. Beware of performance
measure results that show no data; most of the time, this is caused by a
system error, not because there is no data to process.
#4 Test the correctness of reports.
How can we know that our performance measure reporting system is
working? The simplest way to do this is to create a report, and take it to its
users. This might take us some time in the case of paper reports for example,
because we would have to send the report out, and wait for users to read it
before we can ask for their opinions. Or if the reports are digital, we have to
allow the users some time to familiarize themselves with the system, before
asking them for feedback.
I recommend creating an open-ended simple questionnaire that allows users
to express their opinions – what should be improved, for instance – so that we
can use these recommendations to improve our report. It does not sound that
difficult at all, right? If you already have this kind of report in place, have
you ever asked the users for their opinions to see if they like the report or
not? Do not forget – a report without readers is nothing but scrap paper.
#5 Test to see if the system will be put to use.
When we build a performance measurement system, we do not only expect
precise performance measures, usable data, and an interesting report of
results; we also hope that the system will be used in a beneficial manner.
Hence, one of the things we should test, is whether the users have utilized the
performance measure system or not. But how can we test that? A simple
answer to this question is to let the users test the system. If it is a digital one,
then give them usernames and passwords. After a week, you can ask them if
they got to use the system. Or if it is a manual system, ask them how they
utilize the data in their job. If we find out that they get to use the data, then
we can rest easy. But if not, we might need to find “the reasons why,”
otherwise the system would become useless.
#6 Test to see if the system has any other uses.
This is the last topic about testing. Do not stop asking questions, even if you
have received positive user feedback. Do they have any other suggestions?
Or even if the users say the system is useless – do not give up, because
what’s useless to one person might be useful to another. Sometimes a system
designer cannot see how the system can be adapted to other kinds of usage.
So try asking this question, and you might find that the system that you have
is more useful than you thought.
Three questions that need to be answered after testing
Once we finish testing, we might receive suggestions, criticisms, or even
complaints on why we did not do this and that. I think this is very normal. It
is better than not having anyone paying any attention at all. In fact, if you
look on the bright side, those criticisms actually stem from good will. If one
does not care, why would he/she give any suggestions at all, right? But what
should we do? Should we follow what they said, or stand by what we think is
right? If we choose to follow what they said, how much should we
compromise? If we stand by what we think is right, will it seem like we listen
to nobody?
The simple answer to this is that we should take those suggestions into
consideration. If the answers to the following three questions are “yes,” then
you should follow the suggestions. However, if one of the answers is “no,”
then you should not follow the suggestions, and go back and explain your
reasons to the users as to why you did not follow their suggestions. The three
questions are:
1) Does the suggestion have a solid rationale?
2) Is the suggestion practically possible?
3) Do we have enough resources, and is it worth the change?
The first question is “Does the suggestion have solid a rationale?” Well, if
you ask this question, everyone who has given the suggestion would say, “Of
course,” right? But the point of this question is to understand whether or not
there are “enough” reasons to change the current performance measurement
system or not. For example, if there is a suggestion that you should not use a
certain performance measure simply because you have never used it before, it
should not stop you from using it.
The second question: “Is the suggestion practically possible?” Of course,
many people would say that it is possible. But sometimes they think their
suggestions are possible due to a lack of information. A suggestion on
comparing our cost with the competitor’s sounds reasonable. However, it is
nearly impossible for us to know the competitor’s cost, so there is still a
problem with this suggestion.
The last question: “Do we have enough resources and is it worth the
change?” Sometimes suggestions are rational and are possible, but there is a
lack in budget or other resources. For example, conducting a survey on
customer satisfaction instead of just measuring the repurchase rate alone
sounds like a rational and possible suggestion; however, there is a budget
constraint. Hence, we could not conduct the survey.
If you find yourself stuck on any of the three questions, please explain to the
one who gave suggestions that you have already carefully considered the
suggestion, so that he or she could understand the reasons of rejection.
However, if your answers are all “yes,” meaning that the suggestion is
rational, possible, is good value for money, and demands an appropriate
amount of resources, then you should make the adjustment. Do not let your
ego seize the development of your performance measurement system. Do not
forget, Ego = 1/Knowledge.
Chapter 12
Implement a performance measurement system
Having created a performance measurement system, it is now time to
implement it. So let’s see what the key points of this process are.
Designing is hard, but using is harder.
Anyone who has been involved with organizational performance
measurement should agree with the statement above. A performance
measurement system that has not been put to use is nothing but a stack of
blank papers. The first question is, how will the system be put to use? In
general, there are two methods to choose from: apply to the whole
organization at the same time, or apply to one division after another. If your
organization is small, the first choice should be fine. However, if your
organization is large, I would recommend starting with one division first, aka.
a pilot program. An advantage of launching a pilot program is that you can
learn about the system first, because you have no experience in it. You can
limit the damage it could cause, should the system have any errors. You can
utilize what you have learned from the pilot program to improve the system,
and apply the revised version to other divisions of the organization.
Another benefit is that if you do not have a sufficient amount of human
resources, a pilot program would allow you to delegate your human resources
and time efficiently in order to deal with potential problems. Imagine starting
to apply the system to the whole organization at once. Employees would ask
so many questions that we might not be able to answer or deal with them on
time, which might then lead to failure. Lastly, focusing on only one division
could increase the success rate. And once the system has proven to be
successful, it can be set as an example for other divisions, which would make
organization-wide system adoption easier.
Where should we start implementing the system?
Having discussed pilot programs for performance measurement systems, let’s
now talk about where we should start putting the system to use. This is
another interesting question. Normally, we would start where problems occur
the most. Why is that? Starting where the problems occur most often, would
make it easier to identify problems and see the results clearly, after the
problems have been dealt with. Similar to building a software to remove
computer viruses. If we start off by scanning computers that have no viruses,
the results would show that there is no virus. However, users would doubt
whether there really is no virus or the software simply does not work. But if
we scan a computer with many viruses, the software would be able to detect
the viruses so that we can deal with them. Wouldn’t that look more
impressive?
Same goes for performance measurement. We should identify the department
with most problems first, in order for our performance measurement system
to detect problems and recommend solutions. Once the problems have been
solved, other departments would be willing to try out the system. Another
thing is that if we start with a department with many problems, there is more
for us to gain than to lose. If there are already many problems, solving them
should make things better – or simply put, it would be difficult for us to make
things any worse. However, starting with an excellent department would be
more risky, because we would have to make what’s already excellent better -
that can be very difficult. And if things turn out good, employees might still
doubt whether the performance measurement system really helped make
things better or not, because the department was already great before the
system.
The last question is, which department has the most problems? Sometimes
you can answer this question easily by experience. However, if you do not
know the answer, you would have to take a look at the work processes. The
departments with many problems are usually the ones in the latter part of
processes. It does not necessarily mean that those departments are the ones
who create problems – sometimes the problems are accumulated from
previous processes. In the next section, I’ll show you what kinds of concerns
you have to address before putting a performance measurement system to
use.
Point of concern #1: Why should we have a performance measurement
system?
“Why should we have a performance measurement system?” – this question
frequently arises when we implement a performance measurement system in
an organization. There are two answers to this question:
1) Performance measurement tells you the current status of your
organization, whether it is good or bad.
2) Once you know the result, you would know which area you need to
improve.
You lose almost nothing by measuring performance. Although some people
might say that performance measurement is a waste of time, money, and
labor, considering what you could gain from it, most would agree that it is
worth it. Organizational performance measurement is like getting a health
checkup. We have to pay money to get our health checked, but in return, we
get to know how we should adjust our daily routine. I think that is really
worth the money.
Point of concern #2: How can we use a performance measurement
system?
If an organization’s employees have no previous experience with a
performance measurement system but one day their organization makes an
announcement, “We are going to use KPI from now on,” I believe many
employees would be confused and nervous. They would be concerned about
how the KPI is going to affect them. In fact, organizational KPI application is
not as frightening as you might think. Instead, what you should be more
worried about is using it the wrong way. Utilizing a performance
measurement system would affect employees in the following procedures:
1) Employees play a part in the necessary data collection.
2) Collected data are transformed into performance measures.
3) The results will be analyzed to identify problems or opportunities in
order to improve work processes.
4) Employees develop their work processes, and look forward to seeing
the future results of performance measures.
And that actually covers everything. If you did great on everything, your
organization would only flourish. And when your organization flourishes,
your employees would receive rewards, such as bonuses or salary raises. A
win-win situation.
Point of concern #3: Would we get punished if a performance
measurement system is in place?
Before answering this question, I would like to ask you if you’ve ever gotten
your health checked before. Why did you get your health checked? Didn’t
you have to pay for it? Many would simply answer, they did it to know their
health condition, so it is worth the money. If they know that they are healthy,
they would feel at ease and realize that they are living their lives correctly.
And no one would complain, “What a pity. I want to be sick because I’ve
already paid for the checkup.” Also, if there is something wrong with your
health, then you would be able to deal with it right away. For example, if you
know that you have high cholesterol (LDL), you could get on with a healthy
diet and exercise to recover your health, right? But what does this have to do
with organizational performance measurement?
I’ve always compared organizational performance measurement to health
checkups. We measure to improve, not to harm people in our organization.
I always emphasize this point. We have to make everyone understand that
performance measurement is a tool to help management and employees work
together to solve problems. It is not a tool for management to fire employees
- this mindset is very important. If employees’ mindsets suggest otherwise,
then performance measurement will fail.
Point of concern #4: Why does it have to be me?
“Why do you have to measure ‘my’ work results?” “Don’t you trust me
anymore?” These questions are frequently asked when a performance
measurement system is about to be applied in the organization. First things
first. Have you noticed the word “me” in the question? Once there is “me,”
there is “them,” right? Questions stemming from this kind of a mindset marks
the beginning of a conflict. Hence, it is vital to make everyone understand the
rationale before starting to use a performance measurement system. There
should be no “me” or “them.” Performance measurement measures the
“organization.” The main objective is to utilize the results for organizational
development, not to point fingers at and punish someone. Therefore, this
whole thing is not about trust at all. Rather, performance measurement will
point out problems for everyone to see and fix.
Point of concern #5: Why do we have to measure when everything is
already good as is?
“Our organization has been established for 10 years. We didn’t need any
performance measurement. We didn't have any hardship. The profit is good.
Why do we have to measure performance now?” This is probably another
question that employees might ask themselves, or even say it aloud once they
know there will be performance measurement, because they do not feel
comfortable with it. In fact, I think this is a very good question, because it is
an opportunity to register a new mindset in your organization. This is how I
would like to answer this question. The fact that your organization has
survived, and remained profitable for 10 years without performance
measurement is a good thing. However, not facing any hardship without
performance measurement for 10 years does not necessarily mean that you
can survive another 10 years without hardship, right?
Let’s say we meet a 40-year old person who has been recommended to get
his health checked, and he says, “I’ve already lived for 40 years without any
health checkups, and I’m doing just fine. Why do I need a health checkup
now? Why do I have to waste my money?” Not having had any health
checkups for 40 years, and not having any illnesses does not guarantee that
the person will be able to live another 40 years in good health, right? This is
the exact same thing – if we never check our organization’s health through
performance measurement yet our organization remains profitable, it does not
guarantee the organization’s survival in the future. In contrast, it could be
very risky not to measure, since we might have accumulated many problems.
Despite the fact that we are still profitable, it might mean that the problems
are still hidden, the economy is good, the problems are tolerable, or
customers are still fine with waiting for late delivery to arrive. However,
when the economy turns sour, our organization might be the first to fall. If we
were to start using performance measurement at that time, it would be too
late. It is like giving a gravely ill person a health checkup – it is just too late.
Sometimes we might have heard, “We manage to generate profit without
performance measurement. Why do we have to change now?” The above
statement sounds reasonable – if something is already good, why change it?
But the important question is, how do you know that “it’s already good”? If
you do not measure, then you have to use your own judgment. If you use
your own judgment, you are putting your organization in a risky position.
Some people might say, “Just look at the annual profit over the years! How
can you say it’s not good? Yes, making profit is good, but the profit could be
a by-product of positive external factors, such as a good economy or an
expanding market that allows you to sell anything. It could turn out that these
good things are hiding problems. We might have too much inventory,
frequently broken machines, or lazy employees, but they might not have
affected our organization so far because we might have been able to generate
profit regardless.
These problems are like rocks under the water. If the water level is high,
boats would get through very easily. However, if the water level is low, the
rocks would surface, making it difficult for boats to float. Same goes for
organizations. Without performance measurement, we would not know if
there is a problem or not. If we wait until the positive external factors
disappear – poor economy and shrinking market – before identifying the
source of the accumulated problems, it might be too late. Even if you might
believe that your kind of industry would never go bad, still, with performance
measurement, you might be able to generate a much higher profit than
without performance measurement, because performance measurement tells
you what the problems are, so that you can deal with them. Wouldn’t it be
better if you could get rid of the rocks under the water before they could
create any damage to the organization? Performance measurement never
harms anyone - only poor performance measurements do.
Point of concern #6: Why do they have to start with our department?
Will we get to know the result?
There are two other common questions. “Why do they have to start with our
department?” Most of the time, this question arises when we choose a certain
department for a pilot program. The employees are curious as to why it has to
be them. This question can be answered easily. You have to explain to your
employees that, in the end, performance measurement would be applied to
the whole organization, but you choose to start with this department first,
because you can see the success opportunity in this department and this
department can be a leading example for other departments in the
organization.
The other frequently asked question is, “Will we get to know the results of
the performance measures?” It is even easier to answer this question – “Of
course.” If the people who get measured do not get to know the results, then
why are we measuring at all? After all, the people who can improve the work
processes are these same people. If these people do not know the results, then
performance measurement will not create any benefits.
When should we start using it?
Once the system is ready, there will be a question like “Eh, when should we
officially start using it?” Monday, Tuesday, Wednesday, Thursday, Friday, or
maybe Saturday or Sunday? I would like to skip the part about the auspicious
day to launch a system in this book. In fact, prior to saying which day we
should start using the system, we should define what “start using” really
means first. When we apply a performance measurement system in an
organization, in general, we would refer to the “first day of data collection.”
In fact, you can start on any day. But if possible, it should match the cycle of
that particular performance measure’s result report – that would be ideal.
Let me give you an example. If a defect performance measure is collected
monthly, then the first day of data collection should be the first day of the
month. Once we reach the end of the month, we would get a report for the
whole month. However, if we start on the 15th, we would only get results for
half of the month. In addition, we would have to spend more time to explain
why we only have a half-month report for this month, and that for next month
it is going to be a full-month report. This would add to the confusion,
especially during the early days of launching a new system. We would make
things more difficult than they have to be. Another thing we should do is to
communicate the launch date of the system. If most of the employees do not
know anything about the system, it would only make things more
complicated.
Training, training, training
Training should be available during the early stages of performance
measurement implementation. You cannot simply arrange a training session
just to get it over with, as it requires good preparation. The level of success in
training depends on the level of effort in preparation. The more you prepare,
the more likely the training is to yield the best result. In the early stages of
performance measurement system adoption, there will be complications and
questions. The best way to prevent further confusion is to train people.
Training sessions can be arranged using different methods – lectures and
system trials, for instance. Normally, the training instructor is on the system
design team, because he or she knows the system the best. However, if the
system designer does not have good presentation or teaching skills, I would
like to recommend that you hire someone with good basic teaching skills,
and inform him or her with the details of the system. Also, the instructor
should be a specialist in this field. These would ensure the success of the
performance measurement system training.
Why is it so complicated? Why are there so many questions?
During the early days of performance measurement system application, there
will be questions and complaints about why the system is complicated and
why they have a lot of questions. I always reply, “It’s good that they have
questions,” because if no one asks questions and keeps quiet, it is usually a
bad sign showing that no one cares about the system. Therefore, it is good to
receive many questions, because it means that people are actually paying
attention. Furthermore, these questions will help you identify which areas
users are still unclear about, so that you can clarify it for them. If you want
users to have questions, you have to provide contact channels for them. My
suggestion is to provide as many contact channels as possible - phone, email,
chat, or other channels - because the more channels available, the more
convenient it is for employees to ask questions.
If there is a question, there is an answer. During the early stages, it might be
necessary to hold a daily meeting for the team. For example, you can have a
discussion session for asking and answering questions. Or if there are any
suggestions, the team could decide together whether to adjust the
measurement or not. Although you might not end up following the
suggestions in the end, you still have to reply to the people who asked the
questions or gave suggestions to let them know the reasons behind your
decision. Or if you do follow the suggestions, in addition to responding to
them, you have to let every user know that there will be a change. This
method should guarantee success than any other method available.
How can we know if the system succeeds or not?
How can we know if our performance measurement system “succeeds”? We
would know if our employees utilize the performance measurement results in
their jobs. In order for that to happen, performance measurement results have
to reflect the true performance outcome. We have to invest money and labor
for all these to come true. There should be a training session to establish
mutual understanding, answer questions, or even fix problems. The more we
do, the more we gain; the less we do, the less we gain. Well, what if it does
not succeed? We have to take a step back and reevaluate everything to see
what’s wrong. Typical system failures are due to the following four reasons:
1) Management never really pays attention to the system.
This is one of the top reasons, and is the hardest one to solve. Many
managers use performance measurement only because other companies
are using it. They lose interest in performance measurement after a
while, and start seeking other kinds of tools. No system would survive
with a mindset like this.
2) Employees do not understand the information that they receive.
Many organizations have good and beneficial performance measures.
However, due to ineffective communication, employees cannot
comprehend the performance measures. What are they reflecting? For
what can employees use them? In the end, employees do not utilize the
data, which is a shame.
3) Employees receive irrelevant data.
Sometimes they understand the result of performance measures, but they
do not use it because it is not relevant to their jobs. You have to beware
of this. Do not send them the data just to get it over with – you have to
ensure that the data is relevant to their jobs.
4) Employees receive incorrect data.
If the performance measure is good and relevant, but the data is always
incorrect, how can employees utilize it?
These are the four common problems. If you find out that your employees do
not use the performance measurement system, you should go back and take a
look at the reasons why, so that you can fix the problems accordingly.
Signs of acceptance
After implementation, would you like to know how you can tell if the system
is widely accepted or not? The following incidents demonstrate that your
employees have already adopted the performance measurement system into
their jobs:
1) How-to questions about the performance measurement system have
declined.
2) Criticisms regarding the performance measurement have ceased.
3) Employees have requested adjustments to the report format, such as
changing the graph format or asking for additional data.
4) When the report is late, users ask when they will receive it.
Getting everyone to utilize the performance measurement system in their jobs
does not necessarily mean that this system will always be perfect. As a
person who is responsible for organizational performance measurement, you
always have to ask yourself, “Is the data users receive relevant to their jobs?”
and “Is this system still user-friendly?” These questions should allow you to
adjust the system to align with the tasks, and make it sustainably beneficial.
Chapter 13
Put the data from performance measure to good use
There are many organizations that design good performance measurement
systems that is very well-received by their employees. However, it is a shame
that these organizations do not receive much benefit from the performance
measurement system. In fact, it is not completely useless, because they have
analyzed why certain performance measures have increased, while others
decreased. Still, the benefits that they receive is less than what they should
be. This is like buying a convertible car but only driving it to the market and
back. That’s a shame. Now let’s see what benefits you can receive from
analyzing and evaluating a performance measurement system.
Do not rush to analyzing the result.
When we receive the data from a performance measure, the first thing we
normally do is to check if the value has increased or decreased, and why.
Well, that does sound like the thing we should do, right? No! Because that is
jumping to the explanation part, you have to consider the fact that changes in
the value of performance measure are common. Think about the probability,
it is more likely that the value changes than remain static (because there is
only one possibility of the value being stable.)
Do you want to bet with me on whether the stock market index value will be
different on Monday and Friday of this coming week? You probably
wouldn’t bet at all. Because everyone knows that it is nearly impossible for
any stock market index value to remain stable throughout the week. What I
am trying to say is that the value of a performance measure either increases or
decreases. There is a possibility that it might remain stable, but that could
hardly ever happen. What does this have to do with anything? Before you
start analyzing why the performance measure has changed, you should
consider the following characteristics:
1) The change is usual. There is nothing special.
For example, a daily increase or decrease of 5 points in the value of the stock
market index is nothing special, because it would be difficult for the stock
market index value to be totally stable. If there is such a change, do not waste
your time explaining why. Sometimes I notice that some analysts trying to
explain every time there is a change in the stock market index value. For
example, they would say that the stock market index has decreased by 5
points because of poor economic conditions. And the next day, when the
stock market index increases by 5 points, they just say that it indicates a
change in the direction of the economy - there are only good news. Well,
does the economy change every day?
2) There is a change due to a special incident.
This change is abnormal. For example, the stock market index has increased
or decreased by more than 20%. This is this kind of change that you should
take the time to identify the source of, because you normally do not observe
the stock market values increase or decrease by 20% every day.
Try following this suggestion when you have to analyze your organizational
performance measures, and you will be able to manage time and labor
efficiently by choosing to analyze only important matters.
Do not panic because of what you just saw.
Oh my god, our sales declined 30% this quarter! Yes, this might be bad if...
There’s an “if”? The sales have declined by 30%, how can it be good? Of
course, it can. Performance measures will show you things of concern if they
are “abnormal.” Let’s say sales had always increased by 10% every quarter,
but this quarter, sales declined by 30%. Something must have happened. As
the person to analyze the performance measure, you have to identify the
cause. What if it is normal? For example, you are selling a New Year’s card,
and your sales at the beginning of the year have dropped dramatically when
compared to the end of last year. Then you do not have to worry about it,
even if the sales dropped by 30%. If you take a look at past data, and
compare them to the same quarter of previous year, you would see that it is
normal.
Therefore, before you jump right into analyzing the results, I want you to see
if the change is “abnormal” or not. If it is “abnormal,” then start analyzing in
detail. If it is normal, then do not panic, and do not spend time in analyzing
the result - it would be a waste of time.
Correlation is also important.
The following conversation happens in a department that works in analyzing
organizational performance.
Employee 1: "We’re doing good this quarter. Customer satisfaction has
improved."
Employee 2: "Yes, yes. But actually other performance measures have
improved as well."
Employee 1: "True. Employee satisfaction has also improved."
Once this conversation is over, the two employees go back to work. One of
them starts to write an analysis on the increase in customer satisfaction, while
the other writes about the improvement in employee satisfaction. In fact,
there is nothing wrong with that. Each person is doing their job. But what’s
missing is the correlation between the two performance measures if we
analyze them separately.
We do not need to use any advanced statistics. We only have to plot the
customer satisfaction score on the same graph as the employee satisfaction
score. Sometimes, we will get to see a certain pattern. For example, every
time employee satisfaction increases, customer satisfaction increases as well,
or vice versa. Once you see the pattern, performance measure analysis would
be more useful. So instead of analyzing the two performance measures
separately, try analyzing them together – it could change the way you run
your business.
Analyze from many angles.
The following event might have happened at your office.
Boss: “Eh, why do we get so many complaints from customers? Go take a
look at which product model customers complain about the most.”
Subordinate: “Sure thing, boss.”
The subordinate comes back after 10 minutes.
Subordinate: “Model 323.”
Boss: “We should arrange a meeting tomorrow to brainstorm on how we can
improve this model.”
Subordinate: “Great.”
After that, everyone goes back to their desks to work. A week later, a meeting
is held, and model 323 has been improved. Have you noticed anything
strange? If you only skim through it, everything seems to be normal. But if
you look into it in detail, the solution was already there when the boss asked
his first question.
“Go take a look at ‘which product model’ customers complain about the
most.”
The question contains an important assumption: the product model is the
cause of the complaints. Of course, there will always be a product with the
highest number of complaints. So, the company will end up improving that
product model.
I used this example to illustrate that once you have received a performance
measurement result, the first thing you should do is to consider many angles.
You should not ask only which product model has been complained about the
most. You should try to think of other possible causes as well – which factory
produces most of the product with highest number of complaints, or which
dealer has sold most of the product with highest number of complaints?
Analyzing performance measurement results from various angles could
change your perspective on problems. In the end, you will be able to fix the
problem at its root cause.
Do not believe in the correlation right away.
In one of the previous examples, I suggested that you plot two performance
measures on a single graph to see the correlation. In this section, I want to
show you that the correlation might not always be the causation. Why is that?
A correlation between performance measure A and performance measure B
could be due to various reasons.
Firstly, the correlation could be purely coincidental, especially if you did not
collect enough samples. For example, if you plot the height of 2-3 employees
and their salaries, you might find out that the taller the employee, the higher
their salary, which is very unlikely. This kind of situation happens from time
to time; they plot so many graphs that they come across a strange correlation.
For example, they found a correlation between the budget of science, space,
and technology in the USA, and the rate of suicide by hanging or suffocation.
There was a correlation between the number of deaths from drowning in a
pool and the number of movies Nicholas Cage has starred in. There are so
many other examples. But these should be enough to prove that correlations
do not necessarily imply causal relationships.
Secondly, there is another important factor to consider in analyzing
correlations. However, we have not yet included that factor in our analysis.
Let me give you an example. Have you ever noticed that whenever a police is
out directing traffic, there will always be a traffic jam? There is even a belief
that “police creates the traffic jam.” I believe many people have complained
about something like this before, but do not jump to conclusions. Have you
ever noticed that on Sunday morning, when we rarely get to see the police,
there is no traffic? Well, then of course, it must be “the police that cause the
traffic jam.”
If someone counts the number of police seen on the road, and the time it
takes to commute to one’s destination, and plots a graph, we might get to see
a positive correlation between the two – the more police you see, the worse
the traffic. Now, can we draw the conclusion that the police cause traffic
jams? Not yet. According to the findings (assuming enough data were
collected), we might say that the correlation between the police and the traffic
jams is no coincident. However, it is another thing to claim that the police
“cause” traffic jams; this is something we need to be careful of. The
correlation between the two might not be causal. Rather, the correlation
might be caused by a third variable.
Now, it is getting more confusing. The traffic jam might be caused by an
accident; the police might be directing the traffic because of the accident. The
worse the accident, the more police will be out directing traffic to resolve the
situation; and the worse the accident, the worse the traffic jam. But without
the third variable, we could have concluded that the police cause traffic jams.
In fact, if the police hadn’t done their jobs, the traffic might have been even
worse. In addition, the traffic might be a result of other causes such as rain
and flood – and that is why more police might have to come out and work. As
a matter of fact, it might be “the traffic jam that causes the police to come out
and work,”
Therefore, you cannot jump to the conclusion that one performance measure
has an effect on another simply because there is a correlation between the
two. We have to do something extra in order to prove the logic behind the
correlation. The easiest thing you can notice is that the cause must always
come before the effect. Brand awareness performance measure has to
increase before sales performance measure – that “could be considered” as
logical. However, the other way around would be the end of all. If sales were
to increase before brand awareness, we would not be able to conclude that
brand awareness increases sales, as the effect cannot precede the cause.
However, an increase in brand awareness that is followed by an increase in
sales still does not guarantee the causation. That is why I used the phrase
“could be considered.” In order to validate, we have to “make an
experiment.” An experiment would allow us to hold other variables constant,
while changing only one variable that we are interested in, to see if the
change is significant or not.
If we want to see whether advertisements could increase brand awareness or
not, we have to keep other variables constant - do not give a discount or hire
more salespersons, for instance. Then, see if the increased brand awareness
could help generate more sales or not. If you are really going to conduct an
experiment, you have to design it well, because controlling other variables is
not an easy task. However, it is not impossible. Now, I do not want to turn
this book into a research-based book. So, I just want to conclude by saying
that before jumping to conclusions after seeing a correlation, you have to
consider other possible variables that might be the cause first.
Can you hear what KPI is telling you?
Reading this title, many of you might be concerned that something might be
wrong with me. Am I too obsessed with performance measurement that I am
actually talking to it? Not at all. You can relax now. I am just fine. What I
mean is that if we do not carefully analyze the result of a performance
measure, we might miss a lot of things. Let’s take a look. Assume that the
percentage of defect performance measure is as follows:
Round 1: 10%
Round 2: 5%
Round 3: 3%
Round 4: 2.9%
Round 5: 2.85%
If we simply look through it, we might think that our performance is
improving. Moreover, if we only take a look at the values round by round, we
would only be able to conclude that the percentage of defects is gradually
decreasing. However, if we carefully analyze these numbers, we would see
that these performance measure values are trying to tell us something. We
can see that in the first rounds, the amount of decrease is greater. Later on
(round 3 onwards), the numbers are still decreasing but at a much slower rate,
even though same amount of resources or effort is spent.
Why is that? The process that we are trying to improve is reaching its
improvement limit. The process will not improve any further if we keep using
the same method. We need to change the process or come up with new ideas
to see dramatic improvements. This is where many people make mistakes.
They invest their resources and effort on things that are reaching their limit of
improvement. More importantly, the result of the performance measure might
have already told us that, but we just might not have listened. So, go back and
take a look at your performance measure values to see if they are indicating
anything like this.
Do not analyze results separately.
Sometimes when you analyze each performance measure separately, you do
not get anything out of it. Let me give you an example. Let’s say we have
two performance measures: the number of tasks employees can finish per
week and the task error rate (in percentage). Analyzing them separately might
lead to the following conclusions.
The number of tasks employees can finish per week has gradually increased
since the first week of the year until the 10th week. We might conclude that
our employees have worked very hard, which is why the number of tasks
done has continuously increased. The second one, the task error rate, has
remained stable until the 6th week when the error rate has started to gradually
increase. We might conclude that after the 6th week, the error rate started to
increase because our employees began to work negligently. Also, it does not
seem like the rate will decrease anytime soon.
After this analysis, each department would fix their own problem
independently. However, if we analyze performance measure number 1 and 2
together, we might be able to get something useful out of them. During the
first weeks (weeks 1-5), our employees were able to work more. However,
the error rate was low and stable, which means that the employees still did
not work at full capacity. But the important point is about the 6th week when
employees still managed to finish more work. However, working more
always comes with more errors. Or simply put, employees could finish more
work because they reduced the quality of their work. We can imply further
that the true capability of our employees lies upto the 5th week, because
despite the fact that they were able to finish more work after the 5th week,
they did it by compromising quality. This is just an example. Try analyzing
two performance measures together, and you might come across something
even more interesting than siloed results.
Analyze performance measure to identify capacity.
“Can I hire more people?” Many of you might have heard this kind of
complaint before. Most of the time, these complaints have valid reasons.
They really do not have enough people, and need assistance. However, most
of the time, this is not the case. The person who complains the most might
not be the busiest one. Sometimes the one who says nothing is the busiest
one, needing help the most. This person is just too busy that he or she has no
time to complain. What I am trying to say is that sometimes performance
measures could prove something. For example, you can use a performance
measure to test if your department is working at its fullest capacity or not.
Testing something like this with machines would be very easy, because
machines never slack off or complain. With or without an inspector, they
would still work at their highest capacity. Human work capacity, on the other
hand, is more complicated, because people could work fast sometimes and
work slowly at other times – sometimes they are on fire, sometimes
dispirited.
One of the methods to help estimate such outcome is through an appropriate
performance measure. Let’s assume we want to estimate the capacity of a
certain department that mainly uses human labor. We can start off by listing
all of the tasks this department is responsible for. Then, we can estimate the
amount of time needed to finish each task. For example, if our employees
have to contact clients, we would have to estimate how much time they
would need to spend on a client. Let’s say it is approximately 10 minutes
each. After that, we could collect data for a week (5 business days). For
example, if we know that the department contacted 600 customers this week,
we could calculate the amount of time this department spent working, which
is 600 x 10 = 6,000 minutes. Then, we could find the total amount of time.
Let’s say there are five employees in total. Each of them work 40 hours a
week. Hence, the total time would equal 5 x 40 x 60 = 12,000 minutes.
For the last part, we have to find the percentage the employees spent
working, which equals 6,000/12,000 = 50%. We can roughly see that this
department works only half of the time they have. If this department asks for
more people, we would need to ask them why, given such percentage.
Therefore, performance measures could be another good source of
information when it comes to finding out work capacity.
If you change your perspective in analysis, you might see things
differently.
What I am going to write about for this topic is a simple technique that will
make you look at performance measurement results differently. First things
first, each department has their own performance measures. Why is that so?
Most organizations have an organizational structure that is divided into
various departments; the performance measures are correspondingly divided.
So, what is wrong with dividing our organization into different departments?
I have to say that in fact there are some advantages for doing things this way.
We would get to see the performance of the department we work for.
However when you look through the eyes of each department without
involving other departments, this thing called “sub-optimum” can happen.
Sub-optimum is an attempt to make our department’s performance
measurement result look best, without caring about other departments.
Let me give you an example. If our department gets measured in the amount
of time we spend serving a customer, of course, management would want us
to work hard to reduce this number. What could happen is that when a
customer who has complicated problems comes asking for assistance and
although we know exactly how to solve the problems, instead of trying to
immediately solve the problems, we would suggest the customer to contact
another department as we also know that solving the problems would take a
lot of time, which would make our performance measurement results look
bad. Our performance measurement result might end up looking good for our
department, but this is definitely bad for the company.
Therefore, in addition to analyzing the data from the perspective of each
department, we should look at the process. In the case above, we should also
analyze the total time spent from when the customer walks in until the
problem is solved, so that we will be able to see the results from another
perspective. This will definitely help the organization as a whole.
Analyze the result like you are taking a photo.
There is a particularly useful camera function, which I believe many people
have already tried before: zooming. Sometimes we zoom in, sometimes zoom
out. No one always zooms in to get close-up photos. And likewise, no one
always zooms out to capture only tiny humans with the surrounding scenery.
Same goes for performance measurement analysis – we have to both zoom in
and out. Zooming in means to analyze each performance measure in detail,
because sometimes when we only look at the index, we might not get
anything out of it. Just like simple mathematics, when we add up the values
of many performance measures to create an index, the rate of change of that
particular index would gradually decrease. Or simply put, it would remain
stable. However, a stable index does not imply that every performance
measure is stable; some might increase while others decrease. By zooming in,
we would be able to see a much clearer picture.
Management needs to zoom out as well. Zooming out means to look at the
overall picture instead of analyzing each performance measurement value.
There is a saying, “not seeing the forest for the trees.” It explains everything.
To zoom out is to look at the past in order to predict the future of the whole
organization. So, try to adapt my suggestions to your organization, and do not
forget to zoom in and zoom out.
Look at both opportunities and threats.
Let me start off by telling you about two incidents.
Incident 1
Boss: “Why didn’t we reach our sales goal? We’re still 50% short.”
Subordinate: “Because right now, the quality of our product is lower, we’ve
received many customer complaints.”
Boss: “If that’s so, let’s find a solution with the production team.”
Incident 2
Boss: “We did great this time. Look, our sales are 50% higher than the goal.”
Subordinate: “You should treat us to a meal then.”
Boss: “Of course. Tell me when, and we’ll go celebrate.”
These two incidents might seem ordinary at first sight. However, if you
consider the details, you would see that people are only worried when there is
a problem, but never realize potentially missed opportunities. In the first
incident, the company is 50% below the goal. The company might begin to
worry and try to find a solution, which is a good thing that could lead to
improvements. Whereas in the second incident, the company overachieved
the goal by 50%, so they celebrated their success without knowing why the
sales have exceeded the goal so much.
Surpassing the goal by 50% is something to be proud of for sure, but we
should pay careful attention to the rationale behind it in terms of strategic
planning. In this case, the company’s overachievement might simultaneously
indicate that the company might have set the bar too low. Therefore, the
resources that were delegated to achieve the goal was also too low, despite
vast opportunities in the market. If the company were able to set a more
accurate goal, they would have delegated more resources that would have
improved the outcome. Instead of finding the reasons behind bad
performance measurement results, asking why the outcome is highly different
from the goal might give you some useful insights.
Analyzing a pair is better than analyzing an individual.
Sometimes analyzing two performance measures together could give you
interesting data. Here’s an example. Let’s say the value of the quality index
has increased, while the value of productivity index has decreased
(productivity = output/input). In this case, if we analyze the two performance
measures separately, we would not get much useful information out of our
analysis. We might try to find supporting evidence for what we saw. For
example, why has quality improved? Because of this and that… Why has
productivity fallen? Because of this problem and that problem - or something
along these lines.
However, if we analyze both performance measures together, we might find
out that the reason why quality has improved while productivity has fallen is
not because we have fixed the problem at its root cause, but rather because
we have been working on the same tasks repeatedly. We might try to use
better quality control. And once we are able to identify the problem, we
would work on the problem over and over again, until the quality problem is
eliminated, making quality performance measures look better (product return
rate would be reduced, for instance). However, we have added so much input
(such as labor) that it causes productivity (output/input) to decline.
What should we do if we find that quality performance measure has
improved and the quality problem has been dealt with, but still productivity
has not increased at all? Many people have faced this problem before, and
many might wonder why such a thing has happened? If the quality is better
and the problem is eliminated, why doesn’t productivity improve? The reason
is that once the problem has been solved, we would have leftover resources.
We might not have utilized those resources to the organization’s advantage.
Let me give you an example. In the past, there was a problem with our
process, which was why we had to redo everything all the time. It used to
take us 8 hours to manufacture one product, but we solved the problem, and it
only takes us 6 hours now. Is that better? Yes, it is. But now the question is
what did we do with the extra 2 hours? If we don’t do anything, productivity
will not improve.
See how analyzing two performance measures together can make things
much more interesting? Now let’s assume that we find out that both quality
and productivity have improved. What does it mean? It means we are on the
right track. However, it does not mean we could not improve further. We
have to continue to identify if there is anything we have not fully utilized in
production (after solving the quality problem.)
However, discovering that both quality and productivity performance
measures are low, is clearly a bad thing because it shows that we really have
problems. But if we have decent performance measures, we should be able to
identify the source of the problem, and solve it before it could get any worse.
In summary, analyzing two (or more) performance measures at the same time
will help you get a clearer picture – it is obviously better than analyzing each
performance measure individually – “two is better than one.”