Who Saw the Connection? #07 — Nike × A Waffle Iron × Seeing Structure Differently
In 1971, Bill Bowerman was having breakfast with his wife when he looked at their waffle iron and stopped seeing breakfast.
He saw a running shoe.
Bowerman had been trying to solve a very specific problem for his runners at the University of Oregon. A new urethane track was hard and slick. Traditional spikes could dig in too aggressively, while ordinary flat soles didn’t give him the traction he wanted. He needed something lightweight that could grip different surfaces without relying on metal spikes.
Then, over breakfast, he noticed the waffle pattern.
The grid inside the iron created a repeating arrangement of raised and recessed squares. Bowerman wondered what would happen if that geometry were reversed. The cavities that shaped a waffle could become rubber projections on the bottom of a shoe.
So he did what any reasonable person would do after receiving an engineering insight over breakfast: he poured liquid urethane into his wife’s waffle iron.
He forgot an important detail.
Release agent.
The urethane bonded to the appliance and permanently sealed it shut.
One of Nike’s most famous ideas had begun by destroying a wedding gift.
There are probably smoother ways to introduce innovation into a marriage.
The Waffle Iron Wasn’t the Breakthrough
The popular version of the story makes the discovery sound almost magical.
Bowerman sees waffle iron. Bowerman invents Nike. Everybody gets rich.
The real story is much more useful.
Bowerman had already spent years cutting shoes apart, changing materials, modifying soles and testing different designs on his athletes. He was obsessed with reducing weight and improving traction. Shoes that arrived from manufacturers were not finished products to him. They were suggestions.
That background matters because millions of people had looked at waffle irons before him.
The appliance wasn’t hiding a running shoe from humanity.
Bowerman noticed something useful because he had spent years carrying a traction problem around in his head.
What he saw wasn't a kitchen appliance.
He saw geometry.
That distinction is the whole story.
The waffle iron had been designed to shape batter. Bowerman ignored its intended purpose and noticed what the pattern physically did: it created a repeating structure with lots of contact points while leaving space between them.
That could be useful somewhere completely different.
Breakfast Became Prototype Number One
After sacrificing the first waffle iron to research, Bowerman bought more second-hand irons and kept experimenting.
The process was not elegant.
He worked with urethane, rubber, local craftsmen and improvised molds. Some early versions failed quickly. Nike’s own historical account describes prototypes that could fall apart after very little running, while other experiments became considerably less friendly to the athletes testing them.
The famous waffle idea therefore wasn’t a single eureka moment followed by immediate commercial success. The observation gave Bowerman a direction. Then came the much less photogenic business of discovering whether that direction could survive contact with reality.
By 1971 and 1972, Oregon runners were testing early waffle-soled shoes. Around the 1972 U.S. Olympic Trials in Eugene, Bowerman and early Nike employees assembled shoes in small batches using imported uppers and locally produced soles.
Some of these early shoes were extremely crude compared with what Nike would later manufacture. But they answered the question that mattered at that stage.
Did the geometry work?
Runners liked the traction.
That was enough.
A prototype doesn’t always need to prove that you have a scalable business, a global brand and a twelve-quarter product roadmap. Sometimes it only needs to prove that your central assumption isn’t nonsense.
Bowerman’s early shoes were basically questions you could wear.
Does this grip?
Is it light enough?
What breaks?
Can we improve it?
Software teams could probably use more prototypes like that.
From a Kitchen Pattern to Nike’s First Big Shoe
Bowerman and Phil Knight had started Blue Ribbon Sports in 1964, initially importing Japanese running shoes. During the early 1970s, the business increasingly moved toward developing its own products under the Nike name.
The waffle sole became part of that transition.
Early versions helped produce what became known as the Moon Shoe, named partly because the sole pattern left footprints that reminded people of the tracks astronauts had left on the Moon. The Moon Shoe itself was produced in tiny numbers, but the waffle concept kept evolving.
Then came the Waffle Trainer.
By 1975, Nike says orders for the shoe had exceeded 100,000 pairs. The waffle outsole helped give the young company a distinctive product at exactly the moment it was trying to become more than a distributor of somebody else’s shoes.
That is a remarkable journey for a pattern first noticed at breakfast.
The original waffle iron itself disappeared for years. It was later rediscovered among old materials from the Bowerman property, still bearing the evidence of the experiment that had ruined it.
Nike eventually built enormous research facilities filled with biomechanics equipment, laboratories and sophisticated product-development technology.
One of the objects representing the beginning of that culture is still a household appliance somebody accidentally glued shut.
There is something reassuring about that.
Borrow the Mechanism, Not the Costume
This is the part of the story I think software engineers should steal.
Bowerman did not copy a waffle iron.
He extracted a mechanism.
That sounds obvious, but our industry gets this wrong constantly.
Netflix uses microservices, so a company decides it needs microservices.
Google runs Kubernetes, so apparently the eight-person accounting platform is now Google.
A large financial institution uses event sourcing, so somebody proposes an immutable event log for an application whose main responsibility is reminding people about dentist appointments.
We copy the visible solution and forget to ask what problem made that solution useful.
Bowerman could have made the same mistake. He might have concluded that waffle irons were excellent pieces of equipment and therefore shoes should inherit their hinges, heating elements and inconvenient relationship with pancake batter.
He didn’t.
He took one thing:
the geometry.
Everything else stayed in the kitchen.
That is the difference between borrowing an idea and performing architectural cosplay.
When another company uses a pattern successfully, the useful question is not, “How do we implement that too?”
It is, “What property of that pattern solved their problem, and do we actually have the same problem?”
Backpressure is useful because uncontrolled producers can overwhelm consumers. Event sourcing is useful when preserving the history of state changes matters enough to justify the complexity. Microservices can be useful when organizational and deployment boundaries genuinely benefit from being separated.
The names are less important than the forces underneath them.
Bowerman needed lightweight traction.
The waffle pattern happened to contain a useful answer.
Prove the Weird Part First
There is another reason I like the Bowerman story.
The early experiments were cheap enough to fail.
Not free. One waffle iron would probably disagree strongly with that characterization.
But compared with designing a factory, tooling an entire production line and launching a national shoe brand, the experiment was tiny.
Software development often reverses this order.
Someone has an idea for a product. Before proving that users care about the core behavior, we design authentication, organizations, permissions, subscription tiers, dashboards, notification preferences and an abstraction layer so elegant that future archaeologists may classify it as ceremonial architecture.
Or we propose a new technical approach and immediately discuss production infrastructure before establishing that the approach improves the thing it was supposed to improve.
Bowerman’s experiment answered a narrower question first.
Will this pattern create useful traction?
That suggests a question I’d like to hear more often in engineering discussions:
What is the cheapest version of this idea that could prove us wrong?
Not prove us right.
Wrong.
If the waffle geometry didn’t help runners, Bowerman needed to discover that before turning it into a shoe company strategy.
If your new search algorithm doesn’t improve results, find out before designing the cluster.
If users don’t care about the workflow, find out before building the admin portal.
If the architecture only works when the benchmark politely avoids realistic traffic, perhaps postpone the logo.
The earlier an assumption can fail, the cheaper the education usually is.
Expertise Changes What Ordinary Things Mean
There is a tempting conclusion to the waffle story: inspiration can come from anywhere.
True.
Also not particularly actionable.
You could spend tomorrow staring at household appliances and still fail to invent the next Nike. You may, however, develop a concerning relationship with your toaster.
The more useful lesson is that expertise changes what you notice.
Bowerman had been thinking about shoe weight, surfaces and traction for years. That problem was sufficiently developed in his head that a completely ordinary pattern suddenly carried another meaning.
This happens in software too.
An inexperienced engineer may look at a production trace and see noise. Someone who has spent years with distributed systems notices a retry pattern.
A customer complaint may sound anecdotal until someone realizes five apparently unrelated complaints describe the same failure mode.
A database execution plan can look harmless until somebody notices that one terrible estimate is quietly ruining everything downstream.
Experience is not only an accumulation of answers.
It gives ordinary observations more possible interpretations.
That is also why looking outside software matters.
Manufacturing has spent decades thinking about flow and bottlenecks. Aviation has spent decades thinking about checklists and human error. Logistics companies think constantly about routing, queues and constrained optimization. Hospitals deal with handoffs where incomplete information has consequences far more serious than a failed deployment.
Different industries use different words.
The underlying problems are often less original than we like to believe.
What Did Bowerman Actually See?
It would be easy to reduce this story to “think outside the box,” a phrase that has been used so often the box itself probably wants to leave the meeting.
Bowerman did something more precise.
He stopped looking only for products that resembled running shoes and recognized a useful structure somewhere that had nothing to do with footwear.
That is a surprisingly valuable engineering habit.
When you are stuck, don't only ask how people in your field solve the problem. Ask where else the same force, constraint or failure mode exists.
Then ignore the vocabulary and look for the mechanism.
A hospital can learn coordination from a Formula 1 pit crew. A watch engineer can learn shock isolation from a bouncing rubber ball. Bill Bowerman could learn traction from breakfast equipment.
None of them copied the original thing literally.
They recognized the same shape of problem.
That is what makes the waffle iron more than a nice Nike origin story.
Millions of people had seen that pattern.
Bowerman had spent enough time thinking about traction that he saw another use hiding inside it.
A few years later, that idea had travelled from his kitchen to the soles of one of Nike’s first major commercial successes.
Sometimes innovation really does require new technology.
Sometimes it requires years of research, enormous budgets and laboratories full of equipment most of us are not allowed to touch.
And sometimes the technology already exists.
The hard part is recognizing that somebody invented the shape of your answer for an entirely different reason.
Occasionally, they were just trying to make breakfast.
Just remember the release agent.
Sources & Further Reading
Nike’s Department of Archives provides the most detailed account of Bowerman’s waffle experiments, the original waffle iron, early prototypes, the Moon Shoe and the commercial development of the Waffle Trainer.
Nike’s historical material on Bill Bowerman provides broader context around his obsession with lightweight footwear, his experimentation with shoe construction and the early development of Nike products.
The Smithsonian’s National Museum of American History also preserves early Nike footwear and documents the role of Bowerman’s waffle-sole experimentation in the history of athletic shoes.
About the Person Who Is Now Suspicious of His Kitchen Appliances
I'm Amrishkhan Sheik Abdullah, a Technical Lead and software architect based in Dubai. I spend most of my working life around APIs, backend systems, microservices and distributed architectures, which increasingly involves discovering that somebody in another industry solved the shape of our problem decades ago and simply neglected to add us to the meeting invite.
I write about software architecture, distributed systems, engineering decisions, AI developer tooling and the surprisingly useful ideas hiding in places engineers don't normally search.
Who Saw the Connection? is my series about exactly that: true stories where somebody looked at an ordinary object, behaviour or industry and noticed something everybody else was looking straight through.
Read More of My Writing
I publish longer engineering articles, architecture deep-dives and stories that occasionally begin with ruined kitchen equipment and somehow end up questioning our microservice strategy.
Writing: amrishkhan.dev/blog
Elsewhere on the Internet
Portfolio: amrishkhan.dev
GitHub: github.com/amrishkhan05
DEV Community: dev.to/amrishkhan05
LinkedIn: linkedin.com/in/amrishkhan
Apparently my research methodology now includes staring suspiciously at breakfast appliances until one of them explains software architecture.
Top comments (0)