The 1916 Design Pattern That Still Works

In 1916, Cadillac released the Type 53. It only existed for a year, yet it might be the most influential car ever built.

It was the first car that worked the way cars work today. The Model T is famous, but you would not know how to start it without someone teaching you the sequence and the quirks. The Type 53 changed that. The basic experience is the same as a modern Escalade. Same pedals. Same steering. Same logic.

The difference is everything underneath. A new car is a rolling data centre. Thousands of micro-decisions every second. And somehow the experience is still familiar, because familiarity is the point.

The urge to reinvent

Most product teams feel a pressure to disrupt. It is more exciting to pitch a bold new interaction model than to fix the loading state that fails 2% of the time. But disruption is expensive. Every time you change how a tool works, you ask users to pay a cognitive tax.

That bet rarely pays off. Most users don't want novelty. They want the thing they already know to work better.

A framework for when to change (and when not to)

Two frameworks clarify this: Jobs to be Done and the Kano Model.

Jobs to be Done asks: what job is your product actually hired to do? If the fundamental job hasn't changed, changing the interface is almost always a mistake.

Nest didn't reinvent the thermostat interface, because the job never changed. You still set a temperature. But underneath, it learned patterns, optimised energy usage, and removed the tedious programming. The dial stayed familiar, but the bill went down.

The Kano Model asks: within that job, where should you invest?

Basic expectations must work reliably or users become frustrated. The pedal communicates its function through shape, position, and resistance. These must be predictable and consistent.

Performance attributes are where more is better. You keep the pedal in the same place, but you add antilock brakes. You keep the interface stable while making the performance exponentially better.

Delighters are unexpected bonuses that don't disrupt the core experience.

Most product teams get this backwards. They chase delighters while basic expectations remain unreliable.

The long way works

The real work isn't reinventing how people interact with your product. It's making the familiar interaction capable of doing more.

Progress isn't always exciting. Often, it looks like fixing the thing that breaks the flow, making error messages clear, or ensuring a button behaves consistently. It is about making the familiar experience work so well that people forget it was ever difficult.

That patience is what turned the Type 53 into a hundred-year standard. Once the interface works, the job is making it work better, not making it different.

I write more about this stuff at holenventures.substack.com if you're interested.