Sanderson's First Law
You may solve the climax with a special power only to the degree the audience already understands that power.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 94%
Sanderson's most quoted rule, as Ferriss reads it aloud, is that 'an author's ability to solve conflict with magic is directly proportional to how well the reader understands said magic.' Sanderson has since amended it to add 'in a satisfying way,' which is the part most people drop. The input is a design decision made before drafting: is this system hard, with rules the characters and readers can learn, or soft, deliberately unbounded? Lord of the Rings runs both — the One Ring has roughly three legible rules, and Gandalf is a mystery. The mechanism is promise, progress, payoff applied to capability: to let a power decide the ending, you must show the power, show a character failing at it, and show its limits, so that by the climax the audience is not being told the hero can do this, they already know. The output is an ending that lands as earned. Sanderson's counterexample is the ending where a character wins 'through the power of just caring really a lot,' and his Star Wars example is the positive case — Obi-Wan using the Force, Luke failing at it, targeting computers visibly missing, then Luke switching off the computer. Crucially, the law does not forbid soft magic. Gandalf's fall against the Balrog solves a problem unsatisfyingly on purpose: the fellowship is broken, the cost is enormous, and the scene functions as escalation rather than victory.
Origin
Sanderson derived the law from his own failure: his editor asked him to make the ending of Mistborn more spectacular, so he pulled forward an element he had planned for book two without ever setting it up. Readers liked the book but flagged that ending as a deus ex machina, and he wrote the rule so he would never repeat it.
Core principles
- 01An author's ability to solve problems in a satisfying way with magic is directly proportional to how well the reader understands that magic.
- 02The law is not about magic; any author can resolve a thriller or a romance by fiat, magic just makes the temptation obvious.
- 03Hard systems have rules the characters can learn and exploit; soft systems keep their limits unknown to the audience.
- 04Soft magic is not inferior — it is the correct tool for causing problems, creating dread and raising cost.
- 05A soft system used to solve the climax reads as deus ex machina; a hard system used to create mystery wastes its wonder.
- 06The word 'satisfying' is load-bearing: an unsatisfying resolution is sometimes exactly the emotion you want.
How to run it
- 1
Classify every system as hard or soft
For each source of extraordinary capability, decide whether the audience will be given learnable rules. Sanderson's test for hard is not plausibility but internal consistency — Superman drawing power from sunlight makes no external sense and is still a hard system.
Pro tip One story can and probably should run both kinds at once, as Tolkien does.
Watch out Undecided systems drift soft by default, then get used to solve things, which is where the complaints come from.
- 2
Name which system resolves the climax
Choose, in advance, the capability that will decide the final conflict. That choice determines how much explaining you owe the reader across the whole book.
Pro tip If two systems could resolve it, pick the harder one and let the soft one raise the stakes.
- 3
Front-load the rules of the resolving system
Spend the book letting characters study, test and argue about the system. Sanderson's ideal shape is a protagonist who realises by the ending that everyone has been using the system wrong, and that one tweak fixes what nobody else could fix.
Pro tip Turn exposition into puzzle-solving — his Mistborn fight scenes are combat and rules-lawyering at once.
Watch out Explaining via encyclopedia entries kills pace; deliver rules through characters using them.
- 4
Show failure before success
Let the audience watch the capability be attempted and missed. Sanderson points to the targeting computers in Star Wars failing before Luke succeeds without one — fallibility is what makes the eventual success mean something.
Pro tip Failure scenes double as free exposition nobody experiences as exposition.
Watch out A power that has never visibly failed cannot deliver tension when used.
- 5
Assign the soft system to cost, not rescue
Use unexplained capability to escalate, to frighten and to break things. Sanderson notes that when magic appears in Game of Thrones you get scared, because it means people are about to die.
Pro tip Gandalf versus the Balrog is the model: the problem is solved and the emotional result is devastation, not triumph.
Watch out The one thing soft magic must not do is win the final fight cleanly.
- 6
Audit the last chapter for unplanted rules
Before delivering, list every rule the ending relies on and confirm each was established earlier. Anything introduced inside the final act must be moved back or cut.
Pro tip You can revise foreshadowing in after the fact — Sanderson explicitly permits this.
Watch out An editor asking you to 'spice up' the ending is the exact moment this failure occurs.
In the wild
Sanderson reads Lord of the Rings as a manual for running both kinds of system side by side. The One Ring is hard: put it on, vanish from mortal eyes, be visible to Sauron, be corrupted over time. Because those three rules are known, Sam putting on the ring to rescue Frodo from the orcs is a cheer-worthy heroic beat. Gandalf is soft: he raises his staff and something happens, and nobody, including the other characters, can predict or control it.
→ Tolkien gets earned triumph from the hard system and devastating escalation from the soft one in the same book.
Sanderson's editor said the ending of the first Mistborn book was not as spectacular as they wanted. He had a capability planned for book two, so he simply let it happen in book one — with no setup. Readers enjoyed the novel but consistently pointed at that ending as feeling like a deus ex machina. His own verdict on the transcript: 'it is, I didn't set this up at all.'
→ The failure produced the law itself, which he now uses as a pre-delivery check on every book.
Common mistakes
Dropping the word 'satisfying'
People quote the law as if unexplained magic must never solve anything. Sanderson amended it precisely because soft magic solving a problem unsatisfyingly — Gandalf dying to save the fellowship — is a legitimate and powerful move.
Borrowing next book's payoff to patch this book's ending
Pulling a planned future element forward to satisfy an editor is exactly how Sanderson broke his own rule. The element arrives unplanted, and no amount of execution quality hides that from readers.
Assuming the law only applies to fantasy
Sanderson is explicit that any author can force a romance or a thriller to resolve by authorial fiat. Fantasy just makes the temptation visible; the same unearned-resolution failure happens in realist genres and in business narratives.
Is it for you?
Best for
Writers, game designers and franchise builders who need audiences to believe an invented capability can decide an outcome.
Not ideal for
Stories whose entire effect depends on the unknowable — cosmic horror and pure fable, where explaining the mechanism destroys the point.
From the transcript
“an author's ability to solve conflict with magic is directly proportional to how well the reader understands said magic”
“this person has been studying their entire time they've learned how the magic works”
“in the other one they get to the end they are unable to solve the problem but then through the power of just caring really…”
“that's what sanderson's first law is if you're going to use magic at the end of your story to solve the problem promise progress payoff”
From the episode
#794: Brandon Sanderson on Building a Fiction Empire, Creating $40M+ Kickstarter Campaigns, Unbreakable Habits, The Art of World-Building, and The Science of Magic Systems