Asimov’s Three Laws
A policy that lists values with no stated priority order produces inconsistent decisions the moment two of those values collide.
What Is It?
Isaac Asimov’s fictional Three Laws of Robotics, a robot may not injure a human or allow harm through inaction; must obey humans except where that violates the first law; must protect its own existence except where that violates the first two, aren’t primarily a story device. They’re an explicit priority ordering meant to resolve conflicts between values before those conflicts happen in real time. The genius of the structure is that it treats conflicts between good principles as inevitable rather than exceptional, most value statements pretend those conflicts don’t exist; Asimov starts by assuming they will. The structure worth borrowing isn’t the specific content of the laws, it’s the pattern: a stated ranking, decided in advance, for what wins when values collide. Values tell people what matters. A priority order tells them what to do when two important things can’t both be maximized.
Why Does It Matter?
Most organizational values statements list several good things, safety, speed, customer commitment, cost discipline, quality, with no indication of which one wins when two of them genuinely conflict. Every consequential decision eventually forces two legitimate values into conflict, and without a stated order, different people improvise different resolutions on the spot, which is why two well-intentioned teams can make opposite calls while citing the same values document. A policy that states “safety over speed, customer commitments over internal convenience” resolves the collision before anyone has to negotiate it live, under pressure, without one. It also lets decisions scale: explicit priorities allow people to decide consistently at the point of conflict without escalating every collision to someone higher up. Every organization has a priority order already, the only question is whether it was designed deliberately or discovered accidentally through conflict.
What Changes Once You See It?
You start reading a values list as an unfinished document until it also says what wins when two of the values point in different directions.
You also start noticing that most conflict between well-meaning teams isn’t disagreement about values, it’s disagreement about a priority order that was never actually decided, and you get suspicious of value statements that read like aspirations rather than operating instructions.
Common Misunderstandings
- It isn’t a claim that a fixed priority order anticipates every situation. Asimov’s own stories are built around edge cases the laws didn’t foresee; a good priority order needs periodic revisiting, not permanence.
- It isn’t the same as having only one value. The point is ranking multiple real values, not reducing to a single metric, which risks the failure modes covered by Goodhart’s Law and Surrogation instead.
- It doesn’t mean every possible conflict needs its own explicit rule. A general priority order for the handful of values that most often collide covers most real cases without needing to be exhaustive.
- It isn’t about eliminating judgment. A priority order exists so that judgment begins after the priorities are known, not before.
Diagnostic Question
If these two values collided right now, does everyone in the room already know which one wins, or would we be improvising?
Explore Further
Field Notes
None yet.
Related Field Guide
Origin
Isaac Asimov introduced the Three Laws in his 1942 short story “Runaround,” later collected in I, Robot; borrowed here as a structural pattern for explicit value-priority ordering, not as a literal robotics framework.