Where Did Murphy's Law Come From, and What Did Murphy Actually Mean?

Picture a rail track laid across the dry lakebed at Muroc Army Air Field, California, in 1949. At one end sits a rocket-powered sled. Strapped to it, in most runs, is an Air Force doctor named John Paul Stapp, who volunteered to be slammed to a stop so the military could learn how much deceleration a human body survives. A reading comes back from the instruments on the harness. It says zero.

That zero is where Murphy’s Law begins. The short answer to what Murphy meant: if a part can be installed the wrong way, someone eventually will install it that way, so build things so the wrong way is impossible. The gloomy version most people quote today came later.

What lesson did the law start with?

Stapp, according to the account on Wikipedia, was once asked at a press conference how nobody on the project had been seriously hurt. He credited the team’s habit of considering Murphy’s law: think through everything that could go wrong before a test, then counter each item. That is a planning tool, closer to a checklist than a complaint.

The mood changed as the phrase spread. By 1952, Anne Roe’s book The Making of a Scientist was calling it “Murphy’s law or the fourth law of thermodynamics” with the wording “If anything can go wrong, it will.” Arthur Bloch’s 1977 collection Murphy’s Law, and Other Reasons Why Things Go Wrong carried it to a mass audience as a joke about doom. Underneath the joke, the original idea survived: failures that are possible are, over enough tries, expected.

What happened on the morning of the test?

The accounts disagree, so here is what holds up and what does not.

Project MX981 studied human tolerance to the forces of sudden stopping. Captain Edward A. Murphy Jr., an Air Force engineer from Wright Field, had proposed strain gauges on Stapp’s harness to measure the loads. When a run came back with a zero reading, the sensors turned out to have been wired backwards. Beyond that, the sources split:

• Sensor count: some accounts say four, others sixteen.
• Subject: the usual telling puts Stapp on the sled, but Wikipedia reports a chimpanzee in the trial that gave the zero reading, around June 1949.
• Who wired it: popular retellings blame an assistant or technician, and murphys-laws.com does not say who did the installation.
• The words: nobody wrote down Murphy’s remark at the time. Everything that follows is recollection.

Two recollections matter. George Nichols, a later quality-assurance manager at the Jet Propulsion Laboratory, told it this way: Murphy blamed the technician, saying in effect that if the man had any way of making a mistake, he would. The team boiled that down and attached Murphy’s name, Nichols said, partly in mockery of Murphy’s attitude. Murphy’s son Robert disputes this. He has said his father’s remark was about a job with more than one way to do it, where one way ends in disaster, and someone will pick that way.

Notice what the second version assumes. It treats the technician as an ordinary person facing a badly arranged job. The fix it points to is a different connector, not a better lecture. Murphy’s own account of the mistake also had an uncomfortable edge. Wikipedia says he turned down an offered chance to calibrate and test the gauges first. The man who gave the world its famous rule about errors skipped the check that would have caught his.

In 2003 Stapp, Murphy and Nichols shared an Ig Nobel Prize in engineering for (probably) giving birth to the name. The earliest printed use anyone has found of “Murphy’s law” is from 1951, and Wikipedia flags that source as shaky. So the 1949 sled is the best-supported origin, not a certified one.

Why does this matter for a personal goal?

Because most goals fail the way those gauges did: quietly, at a joint where two parts connect. You buy the running shoes (part one) and plan to run at 6:30 (part two), and the connection between them is a person who is asleep.

The broader research on plans agrees that people underestimate this. If you want the numbers, the planning fallacy is covered in why goals take longer than you expect, and a single weak link taking down an otherwise good plan is the subject of the morning failure blast radius. Mornings are where it shows up fastest, because the planner (you at 10 p.m.) and the executor (you at 6 a.m.) are in very different condition.

What are three ways to Murphy-proof a goal?

Which wrong action can you make impossible?

Murphy’s fix was physical. Look for the step where a person in a bad moment can do the wrong thing, then remove the option. Put the phone charger across the room so the alarm is not within arm’s reach. Set the gym bag by the door. Delete the app. Environment changes like these beat resolve because they do not require resolve at the moment it is scarcest.

If you cannot remove the wrong action, put a cost on it. DontSnooze, for example, makes you record a short video to prove you are up, and if you do not, a random photo from your camera roll goes to friends you chose. The point is the same as a keyed connector: the lazy path stops being free.

What are the three ways this has already failed?

Write the list from history, not imagination. Your last three missed attempts hold the real failure modes. A pre-mortem on your goal formalizes this: assume it failed, then list why. For each cause on the list, decide the response today. “If the first alarm fails, the second is on the other side of the bedroom” is a response. “I’ll be more disciplined” is a wish. Showing the list to someone who will poke at it, as in a small personal board of directors, catches the failures you are too close to see.

Have you tested the plan before the real run?

This is the step Murphy skipped. A run on the sled was expensive and rare. Your morning is cheap and repeatable, so rehearse. Set the alarm for a weekday-like evening, check the volume, check that Do Not Disturb is not muting it, confirm the backup actually fires. One chain of backup alarms is only as good as the last time someone checked it, and a test with no backup at all shows how quickly a single point fails.

If the dry run itself feels like too much, start with just ten minutes, the way the ten-minute rule suggests for hard starts. Five minutes of dry run catches the backwards wire. It will not catch everything, and nothing here guarantees a flawless morning. Some failures stay invisible until the real day. The goal is that fewer of them are the stupid kind.

So was Murphy a pessimist?

Judging by the best-supported version, he was a careful engineer who had just watched a preventable error cost the team a test. The attitude behind the law is not that things go wrong, but that you can know in advance where they will, because you have watched people, including yourself, take the wrong path when it was open. Close the path.