An Open Letter to Systems That Call This Efficient

A fictional repair technician watches usable appliances disappear into a disposal cage because replacement is easier to authorize than repair. Addressing the system that calls this efficient, she examines the conflict between short reporting periods and long useful lives, asking what a responsible institution should preserve rather than simply process faster.

An Open Letter to Systems That Call This Efficient printed in dark serif lettering on vintage parchment.

Dear system that has made it easier to throw something away than to mend it,

The kettle was still warm when it arrived on my bench. Someone from the staff kitchen had brought it downstairs because its lid would no longer close securely. I recognized the model and knew that our stockroom once carried a replacement part for it. I also knew that the revised maintenance procedure required me to request a quotation before ordering any component that was not on our approved list. A new kettle, however, could be purchased directly from the catalogue. My supervisor looked at the clock and told me to put the old one in the disposal cage.

I work in an imagined maintenance workshop serving several office buildings. The kettle, its owners, and the purchasing arrangements described in this letter are fictional. I am not offering instructions for repairing electrical equipment. I want to ask what happens when the duration of an administrative transaction becomes more important than the duration of the thing being purchased.

For much of my working life, the workshop was a place where objects arrived with stories attached to them. A chair had begun wobbling during a meeting. A drawer had jammed while someone was looking for a document. A lamp had stopped working beside a desk where an employee preferred to read by its light. We assessed each item, determined whether it could be repaired safely, and recommended replacement when it could not. The work was sometimes unremarkable, but it required attention to the particular circumstances of an object.

The organization had reasons to change the arrangement. Repair requests could remain open for weeks while staff waited for parts. Estimates were inconsistent, and equipment with recurring defects sometimes absorbed more labor than a replacement would have cost. Managers wanted predictable expenditure and fewer delays. I welcomed the prospect of better records. I had spent too many mornings searching for the history of an item whose previous repairs were recorded on scraps of paper.

The new system introduced standardized replacement options and target times for closing requests. The catalogue was useful. Essential items could be obtained quickly, and employees no longer had to negotiate with several suppliers for an ordinary purchase. But the comparison between repair and replacement began taking place inside two administrative processes of very different lengths. One required investigation, documentation, and approval. The other required selection from a list.

A technician could spend half an afternoon determining whether a damaged object was worth repairing. The request would remain open while an estimate was considered. If the same technician recommended replacement, the request might move through the system within minutes. Both decisions were permitted. Only one regularly improved the department’s performance figures.

I thought of the kind of efficiency that excludes important parts of the work it claims to improve. The purchasing report recorded the speed with which an employee received a functioning replacement. That was a valid concern. But the report did not capture the remaining useful life of the discarded item or the resources consumed in producing and delivering another. We had made a perfectly legitimate measure of responsiveness into an incomplete account of value.

One day I watched a new employee called Emre examine a desk chair that had been placed beside the collection cage. Its upholstery was sound, and the problem appeared to concern a worn component that could be assessed and, if appropriate, replaced by a qualified technician. Emre asked why the chair had been condemned. I explained the authorization process. He asked whether we knew that a replacement would last longer than the existing chair after a repair. We did not know. Our comparison began at the date of the request and ended when the request was closed.

He had trained in a small furniture workshop before joining us. In that workshop, he said, a customer’s chair was not judged solely by its resale price. Its construction, condition, expected use, and the availability of safe replacement parts all mattered. Sometimes a new chair was clearly the better purchase. Sometimes the customer’s original chair could continue serving for years. The skilled work was deciding which circumstance applied.

I began wondering whether the organization had lost the ability to make that distinction. Not because our technicians had forgotten their training, but because the administrative environment made the exercise of their judgment increasingly expensive. Repair expertise became a cost visible in hours. The loss of that expertise was not recorded as a cost at all.

The disposal cage stood near the loading entrance. Its contents were collected through an approved waste service, and some materials could be recovered. I was pleased that the organization had considered that part of the process. Responsible disposal matters. Yet a material recovered after an unnecessary replacement does not automatically justify the replacement itself. A useful object has a value beyond the raw material from which it is made.

The cage began filling faster. We did not know whether the increase reflected genuine deterioration in our equipment or a change in the way we handled defects. The monthly report showed faster resolution of maintenance requests. A manager congratulated our team. I asked whether we could compare the number of items repaired, replaced, and disposed of before and after the change. The relevant records existed in different systems, and nobody had been assigned to bring them together.

The published reflection on accountability that dissolves across institutional divisions describes a problem familiar to our workshop. The maintenance team dealt with faults. Purchasing dealt with orders. The waste contractor dealt with collection. Each part of the arrangement had a clear responsibility. The question of whether the whole arrangement made good use of the organization’s equipment belonged nowhere in particular.

I asked our supervisor whether we might conduct a limited review. He agreed, provided we did not delay urgent work or attempt repairs beyond our authorization. We selected a small group of ordinary items already awaiting assessment. For each we documented its condition, the options available, the likely costs, and the uncertainty surrounding any estimate of remaining service. We did not assume that repair was always preferable. Several objects genuinely needed replacement.

The interesting cases were the ones in which the administrative path, rather than the condition of the object, appeared to decide the outcome. A suitable part might be available but difficult to order. A repair might be possible but require a longer approval process than a more expensive replacement. In those cases we asked whether the difference in procedure protected the organization from a meaningful risk or merely reflected the convenience of an existing purchasing agreement.

The finance manager raised an objection that deserved respect. An estimate of future usefulness is uncertain. A repair can reveal another fault, and employees need equipment that works reliably. A maintenance team cannot spend unlimited time investigating inexpensive objects. We agreed that decisions needed reasonable limits. The choice was not between examining every broken item indefinitely and replacing everything immediately. It was between a rule that discouraged judgment and one that made proportionate judgment possible.

We proposed a modest list of commonly used repair components, suitable approval limits, and a way to record why a particular object had been repaired or replaced. Technical staff would still follow appropriate safety requirements, and purchasing would retain accountability for expenditure. We also suggested reviewing repeated failures across equipment models before renewing supply contracts. A cheap item that often fails may be a more expensive choice over its useful life than its initial price implies.

The revised reporting system included the time required to restore service, the direct expenditure, and the type of decision made. Where credible information was available, it also considered recurring replacement and repair costs. We could not measure every environmental consequence of every object. We could stop presenting the speed of procurement as proof that nothing valuable had been lost.

I remembered the institutional authority of defaults. Replacement had become normal because it was an available and easily defended action. Nobody had formally declared that mending was unimportant. The administrative path had quietly made that declaration on behalf of the people who designed it. Changing the path helped technical judgment become a practical option again.

Not every colleague welcomed the change. Some remembered years of delays while inexpensive equipment was kept beyond its reasonable service life. Their experience mattered. Repair can become an unhelpful ritual when an organization refuses to recognize that an object is no longer suitable. I did not want our workshop to return to that habit. We needed to preserve what could responsibly be preserved and replace what genuinely needed replacement.

The kettle that began this letter had already been collected when our review was approved. I cannot tell you whether a safe repair would ultimately have been worthwhile. What troubled me was that our procedure had made determining the answer seem less reasonable than discarding the object. The question itself had become inefficient.

There is a lesson here beyond kettles and chairs. Institutions sometimes shorten their reporting periods until decisions with long consequences are evaluated only by their immediate effects. Preventive maintenance appears expensive until a failure occurs. Training takes time before it returns value. A building designed for easy modification may cost more at first and save resources much later. If the process recognizes only what happens before the next report, it has little reason to prefer arrangements capable of serving people well after the report is forgotten.

I am not asking you, dear system, to become slow for the sake of slowness. I am asking you to distinguish time spent understanding a situation from time wasted in unnecessary procedure. A careful decision may prevent years of repeated work. A rapid one may produce an object in a disposal cage before anybody has considered why it needed to go there.

Last week Emre returned a repaired chair to an office upstairs after the appropriate checks were completed. The employee who used it thanked him and went back to work. Nothing about the exchange deserved a ceremony. Yet the chair had been restored to service without the unnecessary purchase of another, and the decision had been recorded in terms the next reviewer could understand.

That is the kind of efficiency I would like us to recognize. It does not merely move a request toward its closing date. It considers what remains useful when the date has passed. It measures how well an institution serves its purposes while respecting the materials, knowledge, and time it has been entrusted with.

I will continue working at the bench, and some of the things brought to me will need to be discarded. I hope their departure will represent a defensible decision rather than the path of least administrative resistance. There is a world outside each reporting period. Let us leave something worth using in it.

With respect for useful things and the people who know how to care for them,

A technician who would still like to know why the kettle had to go

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to Top