The Case Against Efficiency
Optimization can save time and resources, yet a life with no slack may become brittle, joyless, and unable to welcome surprise.
Efficiency is a real good when it removes needless effort. A reliable train, a clear form, or a tool that takes over repetitive work can return attention to people and problems that deserve it.
Imagine a neighborhood shop that uses online ordering to reduce checkout queues. If the system also removes the only way for a customer to ask for help, the shorter line is a genuine gain for some people and a new barrier for others. Efficiency has to be judged against the service it is meant to provide.
The trouble begins when efficiency stops being a means and becomes the only test. A schedule with no spare minutes may look productive until a late bus, a sick child, or an unexpected conversation makes the whole day fail.
Resilience often depends on capacity that appears wasteful in calm conditions: a backup supplier, a free afternoon, an extra staff member, or a walk without a destination. Those reserves have a cost, but they can keep a small disruption from becoming a crisis.
Optimization can also narrow what we notice. If a hobby is judged by output, a friendship by convenience, or reading by speed, the measurable result may improve while the original pleasure quietly disappears.
Still, inefficiency is not automatically humane. Long waits, duplicated paperwork, and preventable waste burden people with the least time and power. Some streamlining is a matter of access and fairness, not a devotion to productivity.
A reserve can look idle because its value is easiest to see during a disruption. A spare caregiver shift, for example, costs money on a quiet day but may let the team handle illness without unsafe workloads. The question is not whether slack is free; it is whether its protection is worth its carrying cost.
The useful distinction is between friction that protects something valuable and friction that merely blocks it. A pause before sending an angry message can be wise; a needless approval chain that delays a basic service is not the same kind of pause.
Consider a household that plans every evening down to the minute. The routine may help with meals and care, but leaving one evening open can make room for a neighbor, a repair, or simply rest without turning every surprise into a scheduling failure.
The evidence for a particular efficiency claim should be local. Ask what time or resource was actually saved, who received that saving, what new costs appeared, and whether the system still works when demand or circumstances change.
A practical inquiry lens is to track both throughput and slack. Count completed tasks, but also notice error recovery, human discretion, unplanned learning, and whether people can absorb an ordinary setback without sacrificing health or dignity.
Which parts of your life should be streamlined, and which deserve enough slack to remain resilient and surprising?