Efficiency vs. Effectiveness: Why the Difference Matters

Efficiency vs effectiveness comes down to two different questions about the same piece of work. Efficiency asks how much time, money and effort the work used for what it produced. Effectiveness asks whether it achieved what it was meant to achieve. The 2015 edition of ISO 9000, the international vocabulary for quality management, defines efficiency as the relationship between the result achieved and the resources used, and effectiveness as the extent to which planned activities are realized and planned results are achieved.¹ A team can be excellent at one and poor at the other, which is why the difference matters. Clearing your inbox in an hour is efficient; it is effective only if the replies settle what they needed to settle.

Efficiency vs effectiveness: what is the difference?

Efficiency is about cost per result: how little input it takes to produce a given output. Effectiveness is about the result itself: whether the planned outcome happened. The International Organisation of Supreme Audit Institutions (INTOSAI), in the principles it sets for performance audits of public bodies, splits the two in the same place: efficiency is getting the most from the available resources, effectiveness is meeting the objectives set.²

The two answer different questions, so they fail in different ways. An efficient process can churn out the wrong thing cheaply. An effective process can reach the goal while wasting half its budget on the way. Knowing one score tells you nothing about the other. (ISO published a revised ISO 9000 in 2026; the wording quoted here is from the 2015 edition.)

Take a customer support team. If it closes 50 tickets a day per agent, that is an efficiency figure (an illustrative one). If customers come back with the same problem a week later, the team is not effective, however fast it closes tickets. Now flip it: a team that solves every problem for good but needs three people on each call is effective and inefficient.

So whenever someone says a process “works”, ask which of the two they mean. “It’s quick” and “it gets the result” are different claims, and each needs its own evidence. A process improvement project should name which of the two it is trying to raise before anyone starts redrawing steps.

Can you be efficient but not effective? The four combinations

Yes. Because efficiency and effectiveness measure different things, any piece of work sits in one of four combinations: efficient and effective, effective but inefficient, efficient but ineffective, or neither. ISO 9000’s definitions make the split plain: one compares results with resources, the other compares results with plans.¹

1. Efficient and effective: the right result, for few resources
2. Effective but inefficient: the right result, at too high a cost
3. Efficient but ineffective: cheap and fast, aimed at the wrong result
4. Neither: costly and aimed at the wrong result

Here are examples from a team and from one person’s week, all invented for illustration:

• Efficient and effective. A payroll team pays everyone correctly and on time with a short, automated checklist. Personally: you prepare a presentation in two focused hours, and it persuades the people it was meant to persuade.
• Effective but inefficient. The same payroll is correct and on time, but only because three people double-check every line by hand on a weekend. Personally: the presentation lands, after twenty hours of rewriting slides nobody looked at.
• Efficient but ineffective. A sales team sends 500 cold emails a day through a slick template to people who will never buy. Personally: you clear your inbox to zero by lunchtime and leave the proposal that mattered untouched.
• Neither. Nobody reads the monthly report, yet compiling it eats two days.

The middle two combinations are the ones an improvement effort can fix, and they need opposite fixes. Effective but inefficient work needs a better method: fewer handoffs, less checking, simpler tools. Efficient but ineffective work needs a different target, and no amount of speed will fix it.

Who said “efficiency is doing things right”? Drucker, in three steps

The management writer Peter Drucker developed the distinction over a decade, and the famous one-line version is the last step, not the first. Quote Investigator, which traces sayings to their earliest printed source, finds the contrast in Drucker’s May 1963 Harvard Business Review article “Managing for Business Effectiveness”, which spoke of the confusion between effectiveness and efficiency.³

In his 1967 book The Effective Executive, Drucker linked the idea to whether the work is manual or knowledge work. For manual work, he wrote, efficiency is enough: the ability to do things right. A manual worker’s output can be judged by its quantity and quality, like a pair of shoes; for the knowledge worker, he wrote, productivity means effectiveness, the ability to get the right things done.⁴ The crisp line most people quote, that efficiency is concerned with doing things right and effectiveness is doing the right things, appears in his 1974 book Management: Tasks, Responsibilities, Practices.³

The wording drifted after that. A related saying, that management is doing things right while leadership is doing the right things, is linked to the leadership writer Warren Bennis: a 1985 book credited him with a version of it, and Stephen Covey’s 1989 bestseller attributed it to both Drucker and Bennis.³ That is a claim about leaders and managers, which Drucker’s pairing of two measures of work was not.

Myth

Drucker wrote 'efficiency is doing things right; effectiveness is doing the right things' in The Effective Executive.

Fact

The 1967 book contrasts the ability to do things right with the ability to get the right things done. The two-sentence line appears in his 1974 book Management.

Drucker did not dismiss efficiency; his argument was that in work where you choose your own tasks, picking the right task is the harder and more valuable skill.

Which is more important, efficiency or effectiveness?

Effectiveness comes first, because efficiency only has value when it is applied to the right work. Drucker made this the starting point of his 1999 article on knowledge-worker productivity: the central question, he wrote, is “What is the task?”, while in manual work the task is given and the only question is how to do it.⁵

His examples are familiar to anyone in an office. A nurse, he noted, largely decides whether to spend time at the patient’s bed or on paperwork, and engineers are pulled off their task to write reports and attend meetings. Nothing in the work forces the right choice, so people can be busy and efficient all day on the wrong things.⁵

Controlled experiments suggest how easily that happens when people pick their next task.

The study

Moderate evidence

Online workers took the worse-paid task more often when it looked urgent, in a 2018 experiment

In an online experiment, workers picked between two brief typing tasks, and one paid a few cents less. About a third chose the cheaper task when it was set to expire sooner than the other; roughly one in ten chose it when both shared the same deadline. Once workers were reminded of each task’s pay just before choosing, the deadline version and the plain one showed no clear difference.⁶

The 2018 paper by Zhu, Yang and Hsee reports five experiments, run in a lab and online, in which people chose between tasks within a single session for prizes such as chocolates, cents or gift cards, so they show which way choices lean, not what the lean costs in a real job. The authors call it the mere urgency effect.⁶ An extensive, independent replicationreplication: Running a study again with fresh data and the same method, to see whether the original result comes back. A finding that fails to replicate is not automatically wrong, but it stops being something you can lean on.Full entry in the glossary from a UK team at Nottingham, published in 2026, again detected the effect in every test designed to rule out other causes, although adding those controls weakened it.⁷

Before you pick the next task, say out loud what each option is worth, not just when it is due. The Eisenhower matrix sorts tasks by the same two questions, urgency and importance; our guide to the Eisenhower matrix and the pull of urgency covers it in full.

Efficiency still matters once the direction is right. A correct, on-time payroll that eats every weekend is not sustainable, and freed time is what pays for the next improvement. Be careful with labels, though. Michael Porter’s “operational effectiveness”, from a 1996 Harvard Business Review article, means performing similar activities better than rivals, which he says includes but is not limited to efficiency; he adds that improving it is necessary but is not strategy.⁸ Different writers use the same word for different things, so ask which meaning is in play.

How do you measure efficiency and effectiveness?

Efficiency is measured as a ratio of output to input; effectiveness is measured as results against a goal set in advance. The OECD describes productivity statistics, a familiar family of efficiency measures, as describing how efficiently an economy turns inputs such as labor and capital into output.⁹ ISO 9000 ties effectiveness to planned results, so it is hard to measure unless someone wrote the goal down first.¹

An illustrative accounts-payable team shows the difference. Four people process 400 invoices a week, so efficiency is 100 invoices per person per week; automating data entry might raise it. The goal, though, is to pay suppliers correctly and on time, so effectiveness is the share of invoices paid correctly by their due date against a target the team sets, say 95 percent. A team can raise the first number while the second falls, for example by rushing approvals and paying more invoices late or wrong.

That is why one number is never enough. Pair every efficiency measure with an effectiveness measure for the same work, and read them together:

• Calls handled per hour, with the share of problems solved on the first contact.
• Features shipped per sprint, with the share that customers use.
• Hours spent on a report, with the number of decisions it informed.

A single measure that becomes a target invites gaming, a risk explored in our piece on Goodhart’s law and team metrics that backfire. A pair is harder to game, because improving one at the other’s expense shows up straight away.

The trap: perfecting work that should not be done at all

The most expensive efficiency mistake is improving a process that should not exist. Drucker put it bluntly in his 1963 article, in a line Quote Investigator confirms:¹⁰

There is surely nothing quite so useless as doing with great efficiency what should not be done at all.

The trap is easy to fall into because efficiency work feels productive and shows up in the numbers. Automating the monthly report that nobody reads cuts the hours spent on it and still produces nothing of value. A faster approval step for a purchase that needs no approval only speeds up something that should not happen.

In his 1999 article, Drucker’s remedy was to put a few plain questions to the people doing the work: what is your task, what should it be, what should you contribute, and what hampers you and should be eliminated.⁵ Those are questions about effectiveness, and they come before any question about speed. Once the work has earned its place, tools such as value-stream mapping show where its time goes.

Some processes will fail the first two questions. Stopping one saves all of its cost, which no speed-up can match.

The bottom line

Check effectiveness first, because making the wrong work faster only produces the wrong result sooner. Then track one efficiency measure and one effectiveness measure for the same work, so a gain in one never hides a loss in the other.