Formula 1 in the operating theatre
At Great Ormond Street Hospital in London, children were coming out of cardiac surgery and being moved to intensive care. It is a short journey with a lot of risk. Monitors come off and go back on, drugs are handed over, information passes between two tired teams. Things were being missed.
Two of the doctors were watching a Formula 1 race and noticed a pit crew change four tyres and refuel in seconds — a high-speed handover, rehearsed, silent, with one person watching the whole thing rather than doing any of it.
They contacted Ferrari's team. The pit crew's technical director walked them through how it worked: a fixed sequence, defined roles, nobody speaking unless something is wrong, one person in charge of the process itself.
The hospital rebuilt its handover around that structure. Errors in information handover and technical mistakes both fell.
Nobody in medicine had solved this. Somebody in motorsport had, for entirely unrelated reasons.
Source: Catchpole et al., Paediatric Anaesthesia — Formula 1 pit-stop and aviation models for patient handover
A kitchen drawn on a tennis court
In 1948 Richard and Maurice McDonald closed a restaurant that was already making money. They cut the menu from twenty-five items to nine, got rid of the carhops, the plates and the cutlery.
Then they did something stranger. A little after eleven at night, they took red chalk to a tennis court behind a house nearby and drew their kitchen on it at full size. Staff stood in position and mimed the whole job — reaching for supplies, turning to the grill, passing food along — while the brothers watched for where people collided or waited. They rubbed out sections and redrew them. A draftsman stood by to turn the final layout into a working drawing.
They finished at two in the morning. After everyone went home it rained, and the whole thing washed away into puddles of red chalk water.
Nobody in catering designed kitchens this way. The logic came from the factory floor: one worker, one task, work moving past people rather than people moving around work.
Restaurants had been arguing about recipes. The McDonalds treated the kitchen as a production line, which was a question nobody in the industry was asking.
Sources: The McDonald's story — BBC News · Design thinking in the 1950s — SAP Community
The car factory that rebuilt software
Toyota spent decades working out how to build cars without letting work pile up. Keep it flowing. Move small batches rather than big ones. Let any worker stop the line the moment something looks wrong. Fix the problem where it appears instead of passing it along.
In 1990 a book renamed all of this Lean Production, and it began spreading into places that had nothing to do with cars — order processing, retail, aircraft maintenance, supply chains.
Then somebody did the translation properly. Researchers laid the two processes side by side and mapped them line for line. Unfinished parts sitting between manufacturing steps became unfinished information sitting between development steps. Moving small batches of parts became passing along preliminary information early instead of holding it back until it was complete. Frequent changeovers on the line became frequent releases.
Software teams had been treating half-finished work as progress. On a factory floor it is called inventory, and it is a cost.
One industry was building something physical, the other something invisible. Underneath, both were about work stuck in a queue where nobody could see it going wrong.
Sources: The history of lean software development — Mary and Tom Poppendieck · What is Agile/Lean? — Project Management Institute
The kingfisher and the bullet train
Japan's Shinkansen had a problem that engineering could not remove. Entering a tunnel at speed pushed a wall of air ahead of the train, which burst out of the far end with a bang loud enough to disturb people a quarter of a mile away.
Eiji Nakatsu, the engineer leading the redesign, was also a birdwatcher. He knew that a kingfisher dives from air into water — two very different densities — at high speed, and barely makes a splash. The beak was already solving the problem of entering a dense medium without a shockwave.
He reshaped the front of the train after the beak. The boom went away. The train also drew about fifteen percent less electricity and ran faster than before.
The answer existed. It had just never been filed under trains.
Source: The Shinkansen and the kingfisher — Biomimicry New Zealand
What stuck to the dog
In 1941 the Swiss engineer George de Mestral came back from walking in the mountains and found burrs stuck to his trousers and to his dog. Most people pull them off without thinking.
He put one under a microscope. The burr was covered in tiny hooks, catching on anything with a loop in it — fur, wool, thread. It was a fastening system, already finished, that had been evolving for a very long time.
It took him around ten years to reproduce it in fabric. He called it Velcro, from velours and crochet.
The burr was not an inconvenience that happened to be interesting. It was a working design that nobody had thought to read as one.
Source: Our story — Velcro
Eight clams guard the water
Warsaw's water supply is tested constantly by instruments. It is also watched by eight clams.
Each clam has a small magnet glued to its shell, with a sensor above it. Clams are filter feeders: they sit open in clean water and shut when something is wrong. If enough of them close at once, the system triggers an alarm and can shut off the supply.
They work faster than the chemical tests, because they are not testing for anything specific. A laboratory finds the contaminants it is looking for. A clam reacts to water it does not like, including substances nobody thought to test for.
The clams are returned to their river after about three months, before they adapt to the conditions, and replaced with a new group.
Every instrument in the building was built to answer a known question. The clams answer the unknown one.
Source: In Warsaw, clams decide if people get water — Maker Faire Rome
A weed becomes paper
Water hyacinth is an invasive plant that chokes lakes and rivers across southern India. It blocks sunlight, starves the water of oxygen, kills fish, and grows back faster than it can be cleared. The standard approach is removal and disposal.
Sushmita Krishnan, an ecologist working in Tiruchirappalli, treated it as raw material instead. Water hyacinth has long, strong fibres. She developed a process for turning it into paper without chemicals — including greaseproof paper suitable for food packaging — and has trained more than a hundred and fifty women to make it.
The plant is still a problem. It is now also a supply.
The same plant, unchanged. What changed was which industry was looking at it.
Source: Sushmita Krishnan and water hyacinth paper — The Better India
The machine that came from a wine press
Around 1440 in Mainz, Johannes Gutenberg was working on a problem of transfer. He had metal type and an ink that would stick to it. What he needed was a way to press that type onto paper with even pressure, cleanly, again and again.
The Rhineland was wine country. Winemakers had been using screw presses for centuries to bring a heavy plank down evenly onto grapes. The same mechanism was pressing olives, paper and linen elsewhere in Europe. None of it had anything to do with writing.
Gutenberg adapted it. A single press of that design could produce around 3,600 pages in a working day, against roughly forty by earlier printing methods and a handful by hand-copying.
Almost every part of what he made already existed — movable type, ink, paper, the press. Movable type had been invented in China four centuries earlier. What had not existed was someone putting them in the same room.
He did not invent the press. He recognised that the machine squeezing grapes in the next valley was doing exactly the thing he needed done.
Source: The printing press — History.com