The Keyboard That Outlived the Problem It Was Designed to Solve

Oct 12, 2026 | 0 comments

Some of the most expensive recurring problems survive not because nobody can solve them, but because the organisation has built so much around them that changing them feels harder than continuing to pay.

Look down at your keyboard.

The arrangement beginning Q-W-E-R-T-Y is so familiar that most of us never question it. We learn it, technology manufacturers reproduce it, software assumes it and organisations train people to use it.

Yet QWERTY emerged in the age of mechanical typewriters.

The machines disappeared.

The standard survived.

For CEOs frustrated by recurring problems that consume money, capacity and management attention year after year, there is an important lesson hiding beneath your fingertips.

A Solution Built for a Different World

Early typewriters were mechanical machines.

Pressing a key activated physical mechanisms that moved typebars towards the paper. The design of keyboards evolved alongside those mechanical constraints, with QWERTY becoming established through the development and commercialisation of early typewriters.

Whatever combination of mechanical, practical and commercial factors drove its adoption, the important point is this:

QWERTY became embedded in a particular technological environment.

Then the environment changed dramatically.

Mechanical typewriters gave way to electric typewriters.

Electric typewriters gave way to computers.

Physical typebars disappeared entirely.

Yet QWERTY remained.

Why?

Because by then, the keyboard was no longer merely a technical design.

It had become a system.

The Standard Became Bigger Than the Original Decision

Millions of people had learned to type using QWERTY.

Manufacturers produced equipment around it.

Typing courses taught it.

Schools adopted it.

Employers expected it.

Software assumed it.

Muscle memory reinforced it.

Every additional person who learned QWERTY increased the value of continuing to use QWERTY.

That changes the economics of fixing something.

Even if someone could demonstrate a superior keyboard layout, adopting it would require people to relearn deeply established behaviour while manufacturers, organisations and technology providers coordinated around the change.

The question therefore stops being:

"Is there a better design?"

It becomes:

"Is the improvement worth disrupting everything that now depends upon the existing design?"

That is a very different question.

And CEOs encounter versions of it constantly.

Your Organisation Has Its Own QWERTY

Consider the recurring problems that everyone in your organisation knows about.

The monthly spreadsheet reconciliation.

The customer issue requiring intervention from a senior manager.

The duplicated approval process.

The system that cannot communicate with another system.

The meeting created years ago to compensate for poor information flows.

The reporting process nobody particularly values but nobody feels authorised to stop.

Many probably began for sensible reasons.

Someone encountered a constraint.

A workaround solved it.

People learned the workaround.

Processes incorporated it.

Technology supported it.

Controls were added around it.

Roles developed responsibility for it.

Eventually the workaround stopped looking like a workaround.

It became "how we do things here."

Yesterday's Constraint Can Survive Inside Today's Standard

This is where recurring problems become expensive.

Imagine a process created because information once took three days to obtain.

The organisation develops approvals, meetings and controls to manage that delay.

Years later, technology makes the information available instantly.

But the approvals remain.

The meetings remain.

The controls remain.

The roles remain.

The original condition disappeared.

Its organisational consequences did not.

Now imagine that happening hundreds of times across a large organisation.

That is how complexity accumulates.

Not necessarily through incompetence, but through layers of previously rational decisions surviving changes in the conditions that made them rational.

This Is Karamawari Hiding in Plain Sight

空回り, karamawari, describes effort that fails to translate into meaningful forward movement.

Organisations experiencing it are rarely inactive.

Quite the opposite.

People reconcile.

Escalate.

Approve.

Coordinate.

Report.

Review.

Correct.

Work around.

And because capable people become exceptionally good at keeping imperfect systems functioning, the organisation can continue operating successfully.

That can make the underlying problem harder to see.

A workaround that repeatedly prevents failure can eventually become evidence that the workaround is necessary.

The organisation stops asking why the work exists and starts measuring how efficiently people perform it.

That is when recurring cost becomes institutionalised.

The Real Cost Is Everything Built Around It

CEOs often look at a persistent problem and ask what it would cost to fix.

That calculation can miss something important.

The organisation is already paying.

It is paying through duplicated effort, management attention, additional controls, delayed decisions, frustrated customers, technology integrations, specialist roles and opportunity cost.

And every year the problem remains, more dependencies can accumulate around it.

Eventually removing the original problem means disturbing an ecosystem created to accommodate it.

The apparent cost of change rises while the recurring cost of staying the same becomes normalised.

QWERTY offers a wonderfully ordinary reminder of how this happens.

The world changes.

The original constraint disappears.

But the solution designed around that constraint can become so deeply embedded that it survives almost invisibly.

Perhaps that is where CEOs should look when a recurring problem refuses to disappear.

Not only at what is going wrong today, but at what the organisation once had good reason to do.

What expensive "standard" inside your organisation is actually yesterday's workaround, still solving a constraint that disappeared years ago?

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

seers cmp badge