Stop Replacing What You Have Not Learned to Fix

I have been watching the rise of the right-to-repair movement with great interest. The European Union adopted new rules in 2024 to promote the repair of goods, with member states expected to apply them from 31 July 2026. One of the shifts is beautifully simple: when consumers choose repair instead of replacement under the legal guarantee, they receive an extra year of legal guarantee. (European Commission)

New EU rules for smartphones and tablets also started applying from 20 June 2025, bringing repairability, durability, battery life, energy efficiency, spare parts, and resistance to dust, water, and accidental drops closer to the surface of the customer decision. For the first time, products in those categories must display a repairability score from A to E. (Energy Efficient Products)

That stayed with me. Not because I suddenly want to spend my weekends lovingly disassembling a toaster while wearing safety goggles and muttering, “They do not build them like they used to,” although there is a version of me in a shed somewhere who would absolutely enjoy the drama. It stayed with me because repair is becoming visible again.

For a long time, the modern economy trained us to replace rather than repair. The cracked screen, the tired appliance, the outdated device, the failing part. When something became inconvenient, we were encouraged to discard it, upgrade it, outsource it, or start again with something shinier.

And then, quietly but firmly, the repair question returned. Why was this designed to fail? Why is the broken part so difficult to reach? Why is the manual unavailable? Why does fixing cost almost as much as buying new? Who benefits when repair becomes too hard? This is not only a consumer question. It is an organisational one.

Then when I turned these questions closer to home I can see that many workplaces have developed the same habit. When something breaks, they replace the tool, restructure the team, rebrand the programme, change the dashboard, launch a new initiative, rename the process, move the problem to another department, and call it transformation.

The same problem returns later, usually wearing a better outfit. This is the fifth idea in The Human Comeback Files. The future is not less human. It is more deliberately human. And a deliberately human organisation cannot only be good at launching new things. It has to become good at repairing what its own systems keep breaking.

The Same Problem Returning Is a Message

The recurring problem is rarely just a recurring problem. It is the system asking to be understood.

That repeated customer contact, the one everyone has learned to sigh at, is a message. The workaround that has become part of daily survival is a message. The escalation path people use because the official route is too slow is a message. The spreadsheet someone built because the system cannot show the right thing is a message. The customer complaint that keeps coming back in different words is a message.

Organisations often treat these signals as irritations. They become queue pressure, backlog noise, customer frustration, employee resistance, operational complexity, or “one of those things.” But repeated friction is not background music. It is evidence.

Something is asking for attention. Something has not been designed well enough. Something was never properly owned. Something was patched when it needed repair. Something has been normalised because everyone got used to carrying it.

The danger is that repetition dulls curiosity. The first time a problem appears, people notice. The tenth time, people manage. The hundredth time, people build a workaround and stop expecting anything to change. That is when a defect becomes culture.

Replacement Feels Easier Than Responsibility

Replacement has a seductive cleanliness to it. A new system. A new platform. A new framework. A new operating model. A new transformation programme. A new dashboard glowing with newborn innocence.

Newness gives the organisation a temporary sense of escape. It allows everyone to step away from the awkward evidence of what did not work before. There is energy in a launch. There are slides. There is language. There may even be a logo if things have become serious.

There are times when replacement is absolutely necessary. Some tools no longer fit the work. Some structures were built for a world that has moved on. Some policies should be retired with a small ceremony, a thank-you note, and possibly a biscuit.

The problem begins when replacement becomes a way of avoiding learning.

A team that could not listen properly before will not magically listen because the feedback tool has changed. A culture that punished honesty will not become transparent because the survey has a new interface. A process that never addressed root cause will not improve because the tracker moved to a prettier dashboard.

People have seen too many replacements pretending to be repairs. That is why the next new thing is so often met with polite optimism and private eye-rolling. Employees are not always resistant to change. Sometimes they are simply carrying organisational memory. They remember the tool that was meant to save time but created extra admin. The programme that launched with urgency and then dissolved into silence. The process that was “fixed” three times without touching the reason it failed.

Fresh starts are attractive because they forgive the organisation for not learning. Repair does not offer that comfort. Repair asks what happened. Why it happened. Repair asks why it was allowed to continue. And what needs to change so the same injury is not reopened every Monday by a different team.

Rescue Is Fast. Recovery Is Slower. Repair Changes the Future

This is where time matters. In customer experience, we often celebrate rescue because rescue is visible. A customer is upset, a frontline professional steps in, the issue is escalated, a refund is processed, a workaround is found, a manager approves something, and the moment is saved.

Rescue gets the customer out of the river. Recovery helps them breathe again. Repair walks upstream and asks who keeps knocking people off the bridge. Those are different kinds of work.

Rescue is immediate. It protects the person in front of you. It matters deeply. Anyone who has ever calmed a furious customer, saved a failing delivery, corrected a billing error, or pulled a broken case back from disaster knows that rescue is skilled work. It requires judgement, composure, and speed.

Recovery is the next layer. It restores confidence. It rebuilds trust. It gives the customer, employee, team, or leader a way back into relationship with the system after something has gone wrong.

Repair goes further upstream. It changes the condition that made rescue necessary. It studies the policy, handoff, tool, metric, training gap, ownership blur, unclear input, poor process design, or incentive that caused the failure to repeat.

The person who saves the day gets applause. The person who quietly redesigns the process so the day no longer needs saving may get a line in a project update and a sandwich in a workshop. That is part of the problem.

Rescue feels heroic. Repair feels slow. Rescue has drama. Repair has method. Rescue creates stories people remember. Repair creates problems people stop having. A healthy organisation needs all three: rescue, recovery, and repair. The danger is when rescue becomes the operating model.

The MacGyver Problem

Every organisation has a few MacGyvers. The person who knows which spreadsheet still works. Who knows which inbox actually gets answered. Who can unlock the stuck case, interpret the ancient policy, find the missing approval, calm the difficult stakeholder, and get the thing through the system with a paperclip, a password reset, and the weary calm of someone who has seen the beast before. These people are gold. They are also diagnostic evidence. The danger begins when the organisation starts treating MacGyver as the operating model.

A clever workaround can be a beautiful thing in the moment. It gets the customer helped. It protects the team. It keeps the wheels moving when the official route has fallen into a ditch and is pretending to be a strategic pause. But if the same workaround is needed every week, the organisation should stop admiring the ingenuity and start inspecting the cause.

Honestly workarounds is my greatest pet-peeve. I get on that horse and start firing off shots like it is the wild west; Why does this need a workaround? Why does only one person know how to fix it? Why is the official route too slow, too unclear, or too weak? Why has survival knowledge not become system knowledge? Why is the person closest to the problem carrying the repair without authority to change the design?

When skilled people repeatedly compensate for broken systems, the organisation may mistake their capability for system health. The customer is helped, the metric survives, the escalation closes, and the machine keeps running. But somewhere underneath, the crack remains. And eventually even MacGyver gets tired.

Six Sigma Was Always a Repair Discipline

This is where Six Sigma enters quietly, wearing practical shoes and carrying a clipboard that has seen things. At its best, continuous improvement is disciplined repair. It is the refusal to accept recurring defects as personality traits of the organisation.

DMAIC is a repair story. Define the problem clearly. Measure what is actually happening. Analyse why it keeps happening. Improve the system. Control the gains so the repair holds.

That last part matters. A quick fix may rescue the moment. It does not prove the system has changed. A goodwill voucher may calm the customer. It does not change the machine that produced the complaint. An apology may be necessary. It does not repair the process unless something learns from it. Repair is not a vibe. It is a method.

Real repair has a little Dr House energy. It mistrusts the first diagnosis. It asks why the obvious answer feels too convenient. It keeps poking until the pattern confesses.

“Training issue” may be true, but it is often the lazy diagnosis. Was the process unclear? Was the input poor? Was the tool unreliable? Was the policy designed too far from the customer? Did the metric reward the wrong behaviour? Did ownership disappear at the handoff? Did the customer need get misunderstood from the start?

Root cause analysis is not glamorous. Neither is opening the cupboard under the sink to find the leak. But if the floor keeps getting wet, eventually someone has to stop buying prettier towels. That is repair thinking.

Repair Is How Corporate Systems Heal

I know the word “healing” can make a corporate room twitch. It sounds suspiciously like someone is about to dim the lights and bring out a singing bowl. But systems do heal, or they do not. And I would venture to state that a system that keeps reopening the same wound is not resilient. It is untreated.

Corporate healing is not soft mist and motivational quotes. It is what happens when a defect is named, the cause is examined, the affected people are heard, the system changes, the repair is tested, and the learning is retained. That is healing with a hard edge.

It means the frontline no longer has to absorb the same anger caused by the same flaw. Customers stop being handed apologies for problems that should have been repaired three versions ago. Managers stop translating the same broken promise into a temporary workaround. It means leadership stops mistaking movement for progress.

Healing also requires memory. An organisation that cannot remember what it learned will keep staging the same crisis with new actors. Repairable organisations build memory into the system. They do not let lessons evaporate after the post-mortem. They do not allow known defects to become folklore. Or rely on one experienced person to hold the whole map in their head. They create ways for learning to survive the meeting.

Why Repair Fails Inside Organisations

Repair fails for reasons that are painfully human.

Repair creates evidence. Once you inspect the crack, someone may ask why it was ignored for so long.

Repair threatens comfort. A problem living between teams can remain polite and unresolved for years until someone asks who owns the join.

Repair is less glamorous than launch. A new tool photographs better than a fixed handoff.

Repair competes with speed culture. People are rewarded for moving quickly, not for stopping long enough to understand why the same thing keeps breaking.

Repair exposes design debt. The temporary workaround that lasted three years becomes harder to laugh off once someone writes it down.

Repair is politically awkward. The root cause may sit inside a leadership decision, a metric, a budget constraint, or a policy nobody wants to revisit.

Repair simply has no owner. Everyone agrees the issue is real, but no one has the mandate, time, or incentive to fix it properly.

And sometimes the organisation has become addicted to rescue. There is emotional reward in being the person, team, or department that saves the day. Repair changes the story. It removes the recurring crisis, which means it also removes the recurring hero moment.

That is why repair requires maturity. It asks people to care more about the problem disappearing than about being praised for managing it.

Repair Is a Trust Strategy

Trust grows when people see that the organisation learns from what went wrong. Repair tells people: we noticed, we understood, we acted, and we will not make you carry this again if we can help it. That matters.

Repair also changes the emotional contract inside the organisation. It tells the frontline that their observations matter. It tells customers that their complaints were not merely processed. It tells leaders that improvement is not only ambition, but maintenance. It tells the business that care is expressed through design, not only tone.

There is something deeply human about repair.

To repair is to refuse disposal as the first instinct. It says this thing has value. This relationship has value. This process can be made better. This team is worth listening to. This customer pain point deserves more than another apology.

Repair is respect.

What Deliberately Human Organisations Do Differently

Deliberately human organisations build repair into the operating rhythm.

They make recurring pain visible before it becomes folklore. Repeat contacts, workarounds, escalations, exceptions, and recurring complaints are treated as signals worth studying.

They separate containment from correction. Containment protects the customer today. Correction changes the system so tomorrow’s customer does not meet the same failure.

They protect the people who raise defects. When employees fear blame, they hide the crack until it becomes structural.

They build repair loops into governance. Significant service failures need routes into process review, product design, policy clarification, training, technology improvement, or ownership redesign.

They make the cost of non-repair visible. How many hours are spent explaining the same issue? How many contacts are generated by one poor handoff? How much emotional labour is being used to compensate for unclear design?

They treat process tools as living instruments. SIPOC, DMAIC, root cause analysis, control plans, and customer journey maps should help people see where repair is needed and whether the repair holds.

They celebrate prevention, not only rescue.

That last one may be the hardest.

Because prevention is quiet. The customer does not know what almost went wrong. The executive does not always see the incident that never happened. The team may not get a dramatic story to tell. But the absence of recurring pain is one of the cleanest forms of progress.

That is the shift. From workaround to redesign. From launch excitement to learning discipline. From crisis applause to prevention pride. From shiny replacement to structural care.

The Repair Question Is for Everyone

The question for this article is simple: What keeps breaking here? What keeps breaking? And perhaps the even better question is: Why are we still making people recover from this? Let that one sit in the room for a while.

The right-to-repair movement challenges a world that became too comfortable with disposal. It asks us to design products that can be opened, understood, maintained, and restored.

Organisations need the same challenge. Build processes that can be examined. Systems that can be questioned. Policies that can be improved. Metrics that can be challenged when they distort behaviour. Customer journeys that can be repaired before frustration becomes loyalty loss. Cultures where naming the crack is treated as care, not complaint. The comeback story of work will not be written only by organisations that launch the most impressive new tools. It will be written by those that learn how to repair with discipline, humility, and speed.

Because the future is more deliberately human. And perhaps the next great organisational advantage will belong to the company that learns quickly from what breaks. Repair is not a step backwards. It is how a system proves it is still alive.

So, what keeps breaking in your organisation?