underneath, always
Subtext isn't a trick. It's the actual fight nobody is willing to name.
Two people order coffee and break up. Two people decide who pays for the meal and end an empire. The conversation on the surface is always less interesting than the conversation underneath, and the writers who master subtext are the ones whose dialogue you remember years later. We walk through the Maven subtext map, how to layer two conversations into one, and a sharp little prompt that uncovers what your characters are actually saying when they're talking about the dishwasher. The trick is that most subtext is generated by writing the surface conversation second, after you've named the buried one.
Surface conversation · subtextual conversation
| Surface | Subtext |
|---|---|
| The dishwasher is broken | I don't feel taken care of |
| The flight was delayed | I don't want to come home |
| Where are my keys | Why are we doing this anymore |
| More wine? | Stay |
| I'm just tired | I'm leaving you |
The subtext map (build it for your next scene)
- Write what they're actually arguing about. One sentence.
- Write what they say they're arguing about. One sentence.
- Draft the scene using only the surface conversation.
- Let the subtext leak through tiny details (a glance, a silence, a too-quick reply).
- Read the scene. Cut anything that names the subtext outright.
Subtext is the argument they're not having. Write it second. The surface conversation gets sharper when you know what's actually being said underneath.
— L.A. Walton, The Book Maven
From the Maven Catalog
- Master Course — Subtext Mastery
- eBook — Two Conversations, One Scene
- Toolkit — Subtext Workbook
- Planner — Scene-by-Scene Planner
Name the real fight. Write the polite one. Let the silences carry it. That's subtext. That's the entire craft. Use it carefully.