The New Normal
Most of us who use technology suffer an uneasy sense of “What will break now?”
It’s a feeling that creeps in when a phone updates overnight. When a laptop restarts after installing “improvements.” When a familiar app changes its interface, removes a feature, or suddenly behaves in ways it didn’t yesterday. We’ve learned to brace ourselves. Not for delight, but for disappointment.
This wasn’t always the case.
There was a time when buying a new device or installing a new version of software carried an expectation of improvement. New features meant added capability. Updates meant refinement. If something broke, it was an exception, not the norm.
Today, that expectation has quietly inverted.
Shipping Problems Alongside Features
Many people now assume that new versions will ship new problems along with new features. We open the box knowing something inside may already be cracked. We download the update expecting a tradeoff. And because we’ve learned to live with this pattern, we’ve stopped demanding better.
That shift matters.
When expectations fall, craftsmanship erodes. Products stop being carefully finished objects and start becoming provisional releases. Instead of being shaped, tested, and refined until they are ready, they are pushed out the door because the market tolerates it.
Products Without Brakes
The brakes were not worn down over time. In many modern systems, they were never installed in the first place.
Unlike cars, which are regulated machines with mandatory safety standards, software exists in a kind of Wild West. Oversight is optional. Guardrails are self-imposed. The only standards that apply are the ones manufacturers choose to honor, and speed often wins that internal argument.
When systems built without brakes inevitably crash, the response is rarely careful repair.
When Things Go Wrong, They Vanish
When features disappear in updates, it is rarely thoughtful simplification. More often, it is retreat.
Something went wrong badly enough that the safest move was to remove the entire capability rather than understand it, refine it, or rebuild it properly. The goal shifts from making something better to making it less dangerous.
This is not craftsmanship. It is damage control.
And over time, users learn a second lesson: not only should they expect things to break, they should expect them to quietly vanish.
Trust Is Earned, Not Bestowed
Trust is not granted automatically. It is earned slowly, through consistency and care. Brands that build well over time create a reserve of trust, like money in the bank. When something goes wrong, that reserve absorbs the shock. Users forgive a flaw because history tells them it’s an exception.
But when a brand has not banked that trust, even one serious failure can push their trust account into the red. And unlike software bugs, trust deficits are hard to patch.
What We’ve Taught Ourselves to Accept
In software, we have normalized the opposite of reliability.
We accept constant updates. We accept regressions. We accept outages, rewrites, and reversals as the cost of progress. And because we keep downloading, keep upgrading, keep clicking “agree,” manufacturers receive a clear signal: this is acceptable.
The danger is not that systems fail. Failure has always been part of innovation.
The danger is that we are training ourselves to expect failure — and training makers that this expectation is enough.
When people stop believing that tools will work reliably, they begin to rely on them differently. Carefully. Cynically. With diminished trust. And when trust erodes at scale, it doesn’t just change products. It changes institutions. It changes how people relate to the systems that increasingly govern their lives.
This path does not collapse things overnight. It slowly changes what they are for.
And once expectations are lowered far enough, rebuilding trust becomes far harder than maintaining it ever was.
A Quiet Reckoning
None of this happened all at once.
It happened because speed was rewarded, and care was optional. Because unfinished things shipped anyway. Because we learned to work around flaws instead of demanding they be fixed. Because every individual failure felt small, until the pattern no longer was.
We did not wake up one day expecting things to break. We learned it.
And what we learn, we can also unlearn — but only if we are willing to remember that reliability is not nostalgia, and craftsmanship is not a luxury. They are choices. Repeated ones.
If we no longer expect things to work, it is worth asking when we decided that was acceptable.
Speed is often blamed for the loss of quality, but the relationship isn’t that simple. Skilled craftsmen don’t work slowly. They work smoothly. Experience turns caution into instinct, and quality checks into habit. Teams that build with care can move fast precisely because they don’t relearn the same lessons every time. Quality isn’t about waiting longer. It’s about knowing when something isn’t ready — and being willing to say so.
