Blog

Most writers don't fail because they chose planning or pantsing, they fail because they chose the wrong one for the kind of story they're trying to tell. Here's how to read the signals before you burn three months on a draft that won't close.

The plotter-versus-pantser debate tends to flatten a more useful question: not how much you plan, but what kind of planning your specific story is asking for. Some novels need a map before word one; others need you to write your way into the map.

Most writers treat planning and pantsing as a personality test, but the real question is more practical: how much do you need to know before chapter one to avoid rewriting the whole thing later? The answer depends less on your style and more on where your story is most likely to break.

Scott Lynch rarely writes a scene where dialogue is only conversation. In *The Lies of Locke Lamora*, every exchange between characters carries character voice, world-building, and plot pressure simultaneously, and studying how he pulls that off will change how you draft your own scenes.

Most on-the-nose dialogue isn't a line problem, it's a trust problem: the writer doesn't yet believe the reader will catch what's really happening. Here's how to stop over-explaining and start writing conversations that crackle with implied meaning.

When characters just come out and say exactly what they feel, the scene loses its charge. Learning to write dialogue through deflection, misdirection, and competing agendas is what separates flat exchanges from scenes readers can't put down.

Neil Gaiman's secondary cast in American Gods does something most novels fail at: each minor god doubles as a structural argument about the novel's central idea. Here's how to build a supporting cast that works the same way in your own draft.

David Mitchell gives each of Cloud Atlas's six narrators a completely distinct prose style, and that stylistic commitment does the work that plot continuity normally handles. Here's what that means for writers building multi-voice fiction.

Ernest Cline front-loads Ready Player One with walls of world-building that should, by every craft rule, kill momentum, yet readers keep turning pages. Understanding why that works, and where it quietly fails, is one of the more instructive exercises a novelist can do.

Cloud Atlas interrupts itself six times and asks readers to follow anyway. What Mitchell does at the sentence level to keep that trust intact is something every novelist can study and use.

Most worldbuilding advice tells you to add more: more history, more factions, more maps. But the worlds that grip readers are usually built on what characters cannot do, not on what the author invented.

The best-built fictional worlds don't explain themselves, they demonstrate their rules through what characters can't do, can't have, or can't escape. Here's how to make your world's constraints do the narrative work you've been trying to do with lore.