A Spoiler Policy First
Minor structural observations and early-chapter mechanics are fair game throughout. One section near the end flags a significant late-book revelation. Skip that paragraph if you haven't finished.
Most writers are told to open fast. Cut the prologue. Drop the reader into action. The Way of Kings does almost none of that, and it works anyway. Understanding why is worth your time, because the lessons aren't about epic fantasy specifically; they're about how to make a reader trust you across a long, slow build.
The Structural Contract Sanderson Makes on Page One
The novel opens with a prologue set years before the main story, featuring a character (Szeth) who then vanishes from the narrative for hundreds of pages. That's a bold choice, and it would collapse in most hands. It works here because Sanderson is doing something specific: he's making a promise about competence. Szeth's scene is tight, kinetic, and governed by a magic system with visible internal logic. You don't know the rules yet, but you can see there are rules. That's the contract. The reader thinks: this author knows what he's doing. I can follow.
As a writer, ask yourself what promise your first ten pages make. Not about plot, but about craft. Does your prose demonstrate that you're in control? A reader can survive a slow start if they believe the guide knows the terrain.
Three POV Characters, Three Pacing Registers
Sanderson runs Kaladin, Dalinar, and Shallan as the primary viewpoints, and each has a distinct rhythm. Kaladin's chapters are the most relentlessly pressured; he's in a survival situation for most of the book, so scene endings tend to close on loss or narrowly avoided catastrophe. Dalinar's chapters breathe more, weighted with political negotiation and the slow creep of his visions. Shallan's move fastest in terms of plot mechanics, her scenes often hinging on a single social gambit with a clear success-or-failure shape.
The lesson here is that POV isn't just a camera position. Each viewpoint character should carry its own pacing contract with the reader. If all three of your POV characters feel like they're moving at the same speed, you lose one of the most powerful tools for managing a long book's rhythm. Vary the pressure. Let one strand simmer while another boils.
How He Handles Backstory Without Stopping
Kaladin's past is delivered in interlude chapters labeled "Flashback" (Sanderson calls them "interludes" in a loose sense, though the Kaladin-specific past sections are clearly marked). They're not embedded as memory dumps inside present-action chapters. They run as self-contained scenes with their own narrative tension. His relationship with his brother, his early medical training, his reasons for joining the military: all of it arrives in discrete units that could almost stand alone.
This is a technique worth stealing. If you have a character whose history is essential to understanding their present choices, resist the urge to drop that history as exposition inside a tense scene. Pull it out. Give it room to breathe as its own scene, with its own small arc. The reader processes it more cleanly, and you don't have to slow your present-tense momentum.
The Payoff Architecture (Minor Spoiler Zone)
For most of the book, Kaladin's arc feels like a study in grinding him down. He fails. He's punished. He fails again. Some readers bounce off this, and that's worth acknowledging: the technique demands reader trust that you will pay the suffering off. Sanderson earns it because the setbacks are never arbitrary; each one is caused by a character choice or a systemic injustice that the novel is explicitly examining. The suffering has thematic purpose, which keeps it from feeling like authorial cruelty.
(Significant spoiler follows.) The moment Kaladin's powers fully manifest while protecting his men on the plateau is structured to land as release after sustained compression. The book has been storing potential energy for several hundred pages. When it releases, the scene hits harder than it would if he'd simply been competent throughout. That's payoff architecture. You design for it at the outline stage, not the revision stage.
What to Watch Out For
Sanderson's weaknesses are as instructive as his strengths. His dialogue, particularly in Shallan's early chapters, sometimes functions as a delivery system for exposition rather than character. Characters explain things to each other that both parties arguably already know, because the reader needs the information. Watch your own drafts for this. If two characters are having a conversation that exists mainly to tell the reader something, consider whether a scene or a brief summary might carry that information more honestly.
Also: his prose style is deliberately plain. That's a deliberate trade-off, not an oversight. Clarity at scale serves a thousand-page novel differently than literary texture serves a two-hundred-page one. Know which trade-off you're making.
How Nexa Fits Into This Kind of Planning
If you're writing something with multiple POV threads and a long payoff arc, the hardest part isn't the prose; it's tracking whether your structural promises are actually landing. Writing Nexus's in-app coach, Nexa, works like a developmental editor you can consult mid-draft. You describe your plot architecture, your character arcs, your pacing concerns, and Nexa gives you specific, project-focused feedback: where your threads are misaligned, whether your act breaks are earning their weight, what your next scene needs to accomplish. She doesn't write your novel. She helps you see the structural problems before they compound across two hundred pages. For a book with Sanderson-style ambition, that kind of early diagnostic is worth building into your workflow.
Takeaways for Your Draft
Here's what's actually transferable from The Way of Kings:
- Your opening pages make a contract about craft competence, not just story. Honor it.
- Give each POV character a distinct pacing register. Pressure isn't one-size-fits-all.
- Backstory works better as discrete scenes than as embedded memory. Pull it out; give it shape.
- Payoff architecture is an outline-stage decision. If you're writing toward a big release, the compression has to start early and stay consistent.
- Identify your prose trade-offs consciously. Clarity, texture, and velocity don't all peak at once.
If you're planning a multi-POV novel and want to map your arc structure before you're three hundred pages in and tangled, start with Writing Nexus and work through it with Nexa as your coach. The structural thinking you do now is the revision work you won't have to redo later.
