← Patterns

Effectiveness Over Efficiency

Core Concept

“There is nothing so useless as doing efficiently that which should not be done at all.” — Peter Drucker

Efficiency is doing things right. Effectiveness is doing the right things. In a world of constraints — limited time, limited hands, limited compute — the distinction is mostly academic, because scarcity forces you to choose. You can’t be inefficient because there isn’t enough to waste.

In a world of collapsed constraints, the distinction becomes existential. When agents can do anything, the question shifts from “how fast?” to “should we at all?” The agentic era removes the natural forcing function that made organizations choose. This is the trap.

The Agentic Amplification

When an agent can spin up a project in minutes, write the code, test it, deploy it — the cost of doing the wrong thing drops to near zero in the moment. But the systemic costs don’t drop: attention fragmentation, maintenance burden, decision fatigue, organizational confusion about what matters.

Full utilization of agents is the new full utilization of people. DeMarco proved that maximizing human utilization kills adaptability. The same applies to maximizing agent utilization — it fills every gap with something, whether or not that something matters.

Diagnostic Questions

Ask yourself (or your organization) regularly:

1. “If we couldn’t do this at all, what would happen?” If the answer is “not much” — stop doing it, no matter how efficiently you do it.
2. “Are we confusing activity with progress?” Agents make activity trivially cheap. Activity is not progress.
3. “Would we start this today?” The sunk cost of agent-generated work is ~zero, so this question should be easy. In practice, it isn’t — we feel invested in anything that exists.
4. “What are we NOT doing because we’re doing this?” Even with agents, attention is finite. Every task an agent does consumes your attention for review, integration, decision-making.

The Paradox of Abundance

Scarcity made us efficient. Abundance requires us to be effective. But effectiveness is harder than efficiency because:

• Efficiency has clear metrics (speed, cost, throughput)
• Effectiveness requires judgment (what matters, what doesn’t)
• Efficiency feels productive (look at all this output!)
• Effectiveness sometimes feels like doing nothing (I chose NOT to build that)

The hardest thing in an age of agents is saying no to something an agent could easily do.

Related Patterns

• Debt-Forgiveness-Economics — Policy-scale example: forgiveness is administratively efficient but economically ineffective (doesn’t fix the pricing dysfunction that created the debt).
• Doorman-Fallacy — Takeaway #4 explicitly names this distinction. The Doorman Fallacy is what happens when you optimize for efficiency (remove the doorman) at the cost of effectiveness (lose everything the doorman actually did).
• Parallel-Projects-Sequential-Tasks — The execution-level version: parallelism has costs. This is the strategic-level version: some tasks shouldn’t exist.
• Busy-vs-Productive — The personal-scale version. “Being busy is not the same as being productive.”
• Right-Problem-Leverage — 100x productivity comes from choosing the right problems, not solving faster. Drucker’s insight applied to engineering.
• Augmentation-Over-Automation — The design philosophy version: don’t automate everything, augment the human’s judgment about what to do.

Cross-References

• Parallel-Projects-Sequential-Tasks — execution-level counterpart
• Doorman-Fallacy — efficiency-vs-effectiveness in role design