The Architecture of Trust: Brandon Sanderson's Writing Lessons from The Way of Kings
Spoiler policy: This piece discusses character arcs and structural choices through roughly the first two-thirds of the novel. One plot development near the end is referenced in general terms only. Nothing is spoiled outright, but if you haven't started the book yet, you might want to read a hundred pages first.
Most writers who pick up The Way of Kings for the first time do so as readers. They come back to it as writers, because something about the machinery of it nags at them. It's a thousand pages long. It introduces three separate protagonists across wildly different social strata. It has an appendix on ecology. And yet the thing moves. That's not an accident, and it's not just Brandon Sanderson's work ethic. It's architecture.
What follows isn't a summary or a celebration. It's a breakdown of specific techniques you can study, test, and adapt for your own work.
The Magic System as a Promise to the Reader
Sanderson's First Law gets quoted everywhere: a writer's ability to solve conflict with magic is proportional to how well the reader understands that magic. Most people treat this as a rule about fairness, a prohibition against deus ex machina. That's true, but it undersells the craft point.
Stormlight, the magic in this novel, is governed by Stormlight itself (the luminescent energy harvested after highstorms), by the physical Shardblades and Shardplate, and eventually by the Radiant oaths Kaladin begins to approach. Sanderson introduces each element in stages, always tethered to cost and limitation. Kaladin can't simply will himself to safety; the Stormlight drains, the ability falters under stress, the body still breaks. Every constraint is dramatized before it matters to a plot turn.
For your own work: write down every power or advantage your protagonist has. Then write down its ceiling. If you can't articulate the ceiling clearly, neither can your reader, and you've built a promise you can't keep. The ceiling is where your best scenes live.
Worldbuilding That Earns Its Page Count
One of the more common failures in epic fantasy is what I'd call the museum-tour problem: the author has built a magnificent world and is determined to show you all of it, whether or not you need it now. The Way of Kings has an enormous world. Roshar's ecology alone (crustacean fauna, storm-adapted plant life, a sky that cycles between catastrophe and calm) could fill a field guide. Sanderson doesn't dump it.
Instead, almost every piece of worldbuilding is filtered through character need or dramatic function. Shallan's scholarly obsession with fabrials and natural history doesn't exist to teach us about fabrials; it exists to tell us who Shallan is and to pay off a specific revelation about her abilities. Kaladin's understanding of highstorms is survival knowledge, not atmosphere. The world detail arrives when a character requires it, and that requirement is almost always emotional before it's informational.
The practical lesson: when you're drafting a scene heavy with world-detail, ask what the POV character wants in this moment and whether the detail serves that want or interrupts it. If it interrupts, cut it or move it. Your reader is tracking the character, not the scenery.
Three POVs, One Structural Spine
Kaladin, Shallan, and Dalinar are not interchangeable. Their chapters have different rhythms, different sentence-level textures, different relationships to time. Kaladin's sections are often claustrophobic and immediate; Dalinar's are more expansive, weighted by memory and political pressure; Shallan's carry a kind of brittle wit that masks grief. Sanderson differentiates them at the prose level, not just the plot level.
But here's what holds the structure together: all three characters are, in different registers, asking the same thematic question. What does it mean to protect someone, or something, when the cost is yourself? Kaladin asks it in chains. Dalinar asks it in a throne room. Shallan asks it in a library, lying to everyone including herself. The question is the spine. The three storylines are three different pressure tests of it.
When you're managing multiple POVs, this is the principle worth stealing. Your POVs don't need the same plot; they need the same thematic pressure. If they're each exploring a completely different question, the novel fractures. If they're each breaking the same question open from a different angle, the reader feels the resonance even if they can't name it.
The Interlude Structure: A Technique Worth Borrowing
Between the main parts of the novel, Sanderson inserts short interlude chapters following minor characters across Roshar. These aren't filler. They do three things at once: they expand the sense of a living world beyond the main cast, they plant seeds for later volumes, and they give the reader a breathing rhythm between long sustained arcs.
For writers working on a single-POV novel, a version of this technique still applies. A scene from a secondary character's perspective, even a brief one, can reset pacing and signal scope. It tells the reader that the world doesn't pause when your protagonist isn't looking. That sense of ongoing life outside the main story is harder to achieve than it sounds, and interludes are one structural solution.
Working with a Story Coach While You Draft
If you're planning a novel with this kind of structural complexity, multiple POVs, an intricate magic system, a long arc that needs to earn its length, the hardest part is often keeping your own decisions visible to yourself. You make a choice in chapter three and forget it by chapter twenty.
This is where Writing Nexus's in-app coach, Nexa, is worth knowing about. Nexa works as a developmental-editor-style mentor inside your drafting workflow. You can bring her your outline, a scene you're stuck on, or a structural question ("Does my magic system's constraint actually show up before the climax?"), and she'll help you think it through, flag inconsistencies, and suggest next steps. She doesn't write the novel for you. She helps you see your own decisions more clearly, which is what a good developmental editor does.
For a project as architecturally demanding as epic fantasy, that kind of ongoing structural check matters more than most writers expect until they're deep in a second draft wondering why the middle isn't working.
What You Can Apply to Your Draft Right Now
Here are the specific things worth trying:
- Write your magic system's ceiling before you write its first scene. The limitation is the drama. Know it first.
- For each worldbuilding detail in your current chapter, identify which character need it serves. If you can't answer that quickly, the detail may be in the wrong place.
- State your novel's thematic question in one sentence. Then check each POV: is this character under pressure from that question, or are they in a different story entirely?
- Read your POV chapters aloud in sequence. If two characters sound like the same narrator, the differentiation is happening at the plot level only. Go deeper, into rhythm and diction.
Sanderson's BYU lecture series (freely available on YouTube) goes into the Laws of Magic in his own words, and the Writing Excuses podcast, which he co-hosts, has dozens of episodes on structure and worldbuilding that are worth your time alongside this novel.
If you want to stress-test your own structure before you're fifty thousand words in, start planning your novel at Writing Nexus and work through the architecture with Nexa before the draft gets away from you.
