Essay · Systems Thinking

Redundancy Is a Kindness

Autumn 2026 · Reading time · 16 minutes

The most efficient system is not the leanest one. It is the one that leaves room for a person to be a person and still have the work move forward without her.

A generation of operating advice has taught owners to strip slack out of every process, because slack looks like waste. On paper, this is defensible. In practice, it produces businesses whose only defense against a single person having a bad week is that person deciding not to have one. Redundancy, correctly understood, is not inefficiency. It is the design choice that allows the people inside the enterprise to be human without the enterprise punishing them for it. A working owner who understands this stops treating her systems as machines to be tightened and starts treating them as habitats that need spare capacity to remain livable.

What slack is actually for

Slack is what allows a system to absorb the truth of the day. Someone will be sick. Someone will lose a parent. Someone will simply be flat for a week for reasons that have nothing to do with the work. A system built to run at exactly its stated capacity treats every one of those human moments as an incident. A system built with a little intentional slack treats those same moments as unremarkable, because the coverage was there before it was needed. The savings from running tight look real on a spreadsheet. The costs of running tight show up in turnover, in silent resentment, in the specific brittleness that only reveals itself the first Monday after a small crisis, and those costs never make it back to the spreadsheet where the savings were calculated.

A working owner learns to price the second cost as carefully as the first. She keeps a private note of every moment the slack she designed in absorbed a shock the tighter version would have amplified. Over a year the note becomes a quiet argument for the design. Over a decade it becomes the reason her business is still standing while equally talented competitors, who ran leaner on the same day she did, are not.

Automation changed the shape of redundancy

Redundancy used to mean an extra person. It still can, and often should. But automation and AI have widened the palette in a way that owners are still adjusting to. A model that can draft the standard reply is a backup for the person who usually drafts it. A workflow that can run without the manager on that day is a backup for the manager. A tool that can hold a customer conversation for the twelve minutes it takes for a human to arrive is a backup for the human. These are not replacements. They are second layers, and they have quietly turned redundancy from a headcount question into a design question.

The owner who reads the moment correctly builds redundancy in two layers at once. She keeps human backup for the parts of the work that require judgment and warmth. She keeps tool backup for the parts of the work that require only execution. The mistake is to try to use tool backup for the judgment layer, or human backup for the pure execution layer. Both misapplications produce the same result, which is a system that is redundant on paper and fragile in practice. The right layering makes both the humans and the tools do what each is uniquely good at, and the enterprise becomes forgiving in exactly the places it needs to be.

Kindness as an engineering criterion

Calling redundancy a kindness is not sentimental. It is precise. Every system in a business is used by a person. That person has good weeks and hard weeks. She has a mother who might be ill. She has a child who might be having a moment. She has her own body that will occasionally refuse to cooperate on a day the calendar had other plans for. A system that assumes she will always be at full capacity is not neutral. It is quietly punitive, because on the day she is not, the system will exact a cost from her that no one designed on purpose. Building slack in is a decision the owner makes on behalf of every future person who will interact with the system, most of whom she will never meet.

An owner who understands this begins to treat kindness as an engineering criterion, on par with cost and speed. The system that produces the same output at the same cost, but with room for the humans inside it to be human, is the better system, and the difference will show up in retention, in judgment, in the small acts of discretion that only a person who feels held will offer freely. None of that appears on a dashboard, and all of it decides the ceiling of the business.

Two failure modes

The first failure mode is the owner who confuses lean with excellent. She strips every buffer, celebrates the resulting efficiency, and treats the first hard week as a personnel problem rather than a design problem. Her team learns that being human is inconvenient to the plan, and the ones who can leave, leave. The ones who stay develop the habit of hiding their humanity from the system, which produces a workforce that looks compliant and is quietly disengaged. Efficiency numbers look excellent for a period. The exit interviews are more revealing.

The second failure mode is the owner who confuses slack with generosity. She builds so much redundancy that no one is ever slightly stretched, and the work develops the slow tempo of a place where nothing is quite urgent. Standards drift downward without anyone naming it. The kindness becomes indulgence, and the team begins to resent the lack of edge because good people want to be part of something excellent, not merely something comfortable. The right amount of slack is enough to absorb reality, not enough to erase pressure altogether.

The redundancy the owner needs

The last redundancy an owner tends to build is for herself, and it is often the most important. Every role in the business, including the owner's, should have at least a partial backup. A trusted second who can hold a decision for a day. A written record of how the owner thinks about recurring questions, so someone else can approximate her judgment when she is unavailable. A tool that can carry standard correspondence in her voice for the hours she is not at her desk. These are not admissions of weakness. They are acts of stewardship. An owner without any backup is an owner who has quietly bet the enterprise on her own continuous availability, which is a bet no serious system should ever have to make.

Building her own backup also teaches the owner something useful, which is how to describe her own judgment in words other people, and other tools, can follow. That description clarifies her thinking in ways that nothing else does. Owners who write their own operating notes end up with better judgment, not because writing is magic but because the act of describing forces the kind of precision that muddy thinking cannot survive.

What the working owner actually does

A working owner walks through her systems once a quarter with a single question. Which of these would fail if the person or the tool that carries it took a week off, and would that failure be visible or invisible. She writes the answers honestly. She then chooses one or two of the fragile ones and builds the second layer. She resists the urge to fix all of them at once, because a system with too many parallel changes becomes its own kind of fragile. She protects the pace of the redesign the way she protects the pace of the business.

Redundancy as kindness is what allows an enterprise to hold its shape while the humans inside it live their actual lives. It is a design choice, not a personality trait, and it can be made by any owner who is willing to look at her systems as habitats rather than as machines. The business that emerges from that choice is more forgiving to work in and more durable to build, and its owner will find, quietly, that the people who stay are the ones who felt held by the design itself.