The Square Peg That Saved a Mission
Apollo 13 did not invent new equipment. It used constrained resources and systems thinking to keep three people alive.
They did not invent a new canister. They reread the stack: air, power, time, inventory already on board, and a crew treated as a subsystem rather than as passengers.
Apollo 13 is remembered as a square peg in a round hole. That image is a costume. The interesting object was a ground team that could only work with what had already flown, a crew that could execute, and a function — scrub carbon dioxide — that had to survive a mismatched interface.
The adapter was not a clever gadget in isolation. It was a reading of the whole stack: available materials, procedures, power, time, and the chemistry of the air.
HACKERS studies function-over-part. Heroic narrative can hide the institutional work: training, checklists, degraded-mode design, and the decision to treat the crew as part of the system.
When the specified part is gone, the problem is no longer the part. It is the function, the inventory, and the time.
This is not a gadget story. It is a function-over-part story.
A damaged spacecraft, rising carbon dioxide, mismatched lithium-hydroxide canisters between the command and lunar modules, and a ground team that could only work with what was already on board.
The catalogue is the world. The part is a suggestion.
Engineering culture is trained to reach for the specified component. When that component is on another planet of a spacecraft, the reflex is still to mourn the part.
Function-over-part asks: what transformation must continue, with which objects that actually exist, in how many minutes, under whose hands?
Improvisation myths are dangerous. The work that made the adapter possible was rehearsal, inventory discipline, and a ground-crew loop. You cannot hack a spacecraft in 1970 without a method that was practised when the air was still cheap.
Name the false object, then drop it.
C1
We need the right part
The round hole defined the brief.
We need the function: move air through lithium hydroxide.
C2
Invention is a gadget
The adapter as a product photo.
The invention was a reread of inventory plus procedure.
C3
Heroics on the fly
A Hollywood of genius under pressure.
Rehearsed constraint. Checklists. A crew already trained as operators.
C4
Ground knows, crew obeys
Passengers in a tin can.
The crew is a subsystem with hands, limits, and knowledge of the vehicle.
C5
Time is background
The clock treated as weather.
Time is a material. It constrains which functions are even eligible.
What actually sat on the table.
Engineering solutions require the right part. If the square canister does not fit the round hole, the system fails.
The lithium-hydroxide canisters did not match because two modules were designed as if they would not have to share a lung. The interface debt was already in the vehicle. The emergency collected it.
Ground teams prototyped with analogue inventory. Crew executed under instruction. The makeshift loop held. The transferable lesson is institutional, not folkloric.
Do not study the outfit.
The photograph of cardboard, plastic, and tape is a costume. It is true and insufficient. Without the ground loop, the chemistry, and the crew as operators, it is a craft project.
If the case study stops at ‘they made it fit’, you have a meme. The studio begins when you can run the same method on a system that is not famous.
The famous adapter was not a clever gadget in isolation. It was a reading of the whole stack: available materials, crew procedures, power, time, and the chemistry of the air.
Right part available
Use it. Do not mythologise.
Clever gadget, no procedure
Looks like Apollo. Fails in gloves.
Function reread, illegal materials
A render. It did not fly.
Function + catalogue + clock
The only cell that holds.
S0 Specified part
myth 90 / live 90
S1 Part gone
myth 10 / live 10
S2 Gadget hunt
myth 60 / live 20
S3 Function reread
myth 40 / live 70
S4 Inventory + procedure
myth 55 / live 85
S5 Rehearsed degraded mode
myth 50 / live 95
The only cell you can schedule before the emergency.
F1
Function first
Name the transformation, not the SKU.
F2
Inventory is the catalogue
Only objects that exist are legal materials.
F3
Time is a material
A perfect adapter in six hours is a failure if CO₂ peaks in two.
F4
Hands are a subsystem
Procedure must fit gloves, fatigue, and the vehicle as it is.
F5
Rehearse degraded modes
The emergency should not be the first time you reread the stack.
P1 Function
What must continue?
Mourning the missing SKU.
P2 Inventory
What actually exists?
Designs that need a shop.
P3 Procedure
Who does what, in what order, with what feedback?
A gadget without a crew loop.
P4 Clock
When does the function fail if nothing ships?
Open-ended tinkering into a closed atmosphere.
| ID | Failure | What broke | Control |
|---|---|---|---|
| F1 | SKU lock | The brief stayed with the canister shape. | Rewrite as a function with units and a deadline. |
| F2 | Shop thinking | Parts that did not fly. | Legal materials: onboard only. |
| F3 | Genius myth | A lone adapter as folklore. | Credit rehearsal, checklists, and the crew as operators. |
| F4 | Passenger model | Crew as cargo. | Design procedures for the people who are there. |
| F5 | Clock denial | The chemistry was treated as patient. | Time-box by the failing function, not by elegance. |
| F6 | No degraded mode | The first reread was during the emergency. | Catalogue and practise before you need it. |
Incident response
You cannot SSH to a box you do not have.
Runbooks plus inventory of what is actually in prod.
Field medicine
The kit on the truck, not the hospital SKU.
Function (airway, bleed, time) over catalogue fantasy.
Climate retrofit
The building that exists, not the one in the render.
Legal materials are the current fabric and the occupants.
Agent tools
The model wants an API you did not grant.
Function over part: do the job with tools that exist, or halt.
Reframing ‘we need the correct filter’ into ‘we need to move air through lithium hydroxide using only what flew’.
Ground teams prototyped with onboard inventory. Crew executed under instruction. The makeshift loop held. The wider lesson is rehearsed constraint, not improvisational myth.
01 Rewrite the brief
Function, units, deadline. Ban the SKU in the first sentence.
02 Catalogue
Only what exists. Photograph the room.
03 Time-box by failure
When does the function die if nothing ships?
04 Write the hands
Procedure for the operators who are there, as they are.
05 Prototype in analogue
Ground loops with the same inventory class.
06 Rehearse before
Degraded modes are a curriculum, not a miracle.
- The brief is the missing part.
- Materials include the shop.
- Crew waits for a solution.
- Time is a background variable.
- Success is a clever object.
- The brief is a function with units.
- Materials are the onboard catalogue.
- Crew is a subsystem with a procedure.
- Time is a material.
- Success is a loop that holds.
R0 Part
The specified interface is gone.
R1 Function
Air, power, or data still has to move.
R2 Crew
Hands, fatigue, procedures.
R3 Ground loop
Who can prototype with analogue inventory?
R4 Clock
The chemistry or the orbit does not wait.
R5 Myth
If you tell it as genius, the next crew will not get a rehearsal.
| Topic | Typical brief | HACKERS studio |
|---|---|---|
| Engineering | Component specification. | Function, inventory, clock, hands. |
| Design | Ideation without a catalogue. | Illegal materials are not creative. They are fiction. |
| Leadership | Stay calm. | Treat operators as a subsystem. Give them a procedure, not a speech. |
| Safety | Redundancy of parts. | Redundancy of functions, including degraded ones. |
| History | Hero narrative. | Institutions, rehearsal, checklists. |
Elite programmes still stop at the object.
Aerospace courses teach the accident. MBA courses teach leadership under pressure. Neither requires a student to catalogue a room and rewrite a brief as a function with a clock.
HACKERS does. SCAN the inventory. FLIP the SKU. BUILD a procedure that fits the hands. BREAK it against the clock. PROVE a degraded mode you could teach next week, not a legend.
Heroic narrative can hide the institutional work: training, checklists, and the decision to treat the crew as part of the system rather than passengers.
Do not admire the turning point. Redesign the join.
Take a critical process you own. List only the objects already in the room. Could the function survive if the official tool vanished?
Take a critical process you own. Write the specified tool. Now ban it.
List only objects already in the room. That list is now the catalogue.
Rewrite the brief as a function with units and a deadline.
Write a procedure a tired operator could run. No heroics.
Schedule a degraded-mode rehearsal while the air is still cheap.
Are you still mourning a part?
If the sentence starts with the missing object, rewrite it.
0–8h
Ban
Pick a process. Ban the official tool. List the room.
8–20h
Function
Units, deadline, failure clock.
20–36h
Procedure
Tired-operator steps. Analogue prototype.
36–48h
Rehearse
Run it once. Present the loop, not the gadget photo.
- Tell it as a genius gadget.
- Design with parts that did not fly.
- Treat operators as passengers.
- Ignore the chemistry of the clock.
- Skip rehearsal and call it culture.
When the specified part is gone, the problem is no longer the part. It is the function, the inventory, and the time.
Design for degraded modes. Catalogue what is already in the box. Practise the reframe before the emergency writes it for you.
- Was the adapter the hack?
- It was the visible costume. The hack was function-over-part plus inventory discipline plus a crew treated as operators.
- Can we improvise without NASA?
- You can practise degraded modes. You cannot summon a ground loop you never staffed.
- Is this anti-specification?
- No. Specifications are how the part exists in the first place. Function-over-part is what you do when the specification has left the vehicle.
- How does this transfer to software?
- When the API you wanted is down, the function still has a clock. Catalogue the tools you actually have. Halt if the grant is missing.
- Why warn against hero myths?
- Because they steal rehearsal from the next crew.
Cited for classification and method. Not as a manual. Atlas cases are educational and defensive.