Principle 01
Subtext: What's Said Is Never What's Meant
The art of the eighth above the waterline
Dialogue · Iceberg
The Principle + The Master's Words
On the surface, a character says A; underneath, they want B — and all the power of good dialogue lives in that gap. Hemingway's "iceberg theory" says the same thing: only one-eighth should show above the water.
"If a writer of prose knows enough about what he is writing about he may omit things that he knows and the reader, if the writer is writing truly enough, will have a feeling of those things as strongly as though the writer had stated them."
— Ernest Hemingway, Death in the Afternoon (1932)
The dignity of an iceberg's movement, Hemingway adds, is due to only one-eighth of it being above water — the unstated does the work.
Why It Works
On-the-nose dialogue feels fake because real people almost never name the thing that matters. "I just wanted to double-check the timeline" in a meeting often means "I don't trust your estimate." Pull "what is said" away from "what is wanted," and the listener is invited to decode — and decoding is participation. McKee's warning to every screenwriter: if a scene is about what the scene is about, you're in deep trouble. The line is only the eighth above water; what holds it up is the seven-eighths below — everything the character won't say, yet points at with every word.
Spoken · Text · one-eighth
"What time did you get to bed last night?"
～～～ Waterline ～～～
Unspoken · Subtext · seven-eighths
"I can see you're burned out, and I've seen the bugs — I'm worried about you, but I won't call you out in front of everyone."
Hemingway's iceberg: the visible eighth rests on the seven-eighths beneath.
Before → After
Manager: "Your code quality has dropped lately, and I'm concerned." (Said = meant; no room to move, instant defensiveness.)
Manager: "What time did you get to bed on launch night?" (The line asks about sleep; the subtext is care plus a nudge — and now they volunteer the truth themselves.)
"I'm angry that you missed the deadline." (Emotion shouted outright — the scene dies.)
"Oh — you're done already? That was fast." (Sarcasm carries the anger; calm surface, churning depths.)
When to Use + Common Mistakes
- ✓ Writing dialogue scenes, quoting real conversation in a promo packet, negotiation, user stories in product work
- ✓ Reading others: hearing the real need beneath a colleague's line often matters more than the line itself
- ✗ All subtext, no text — the reader can't decode it; the eighth still has to show
- ✗ On-the-nose: writing the character's inner monologue straight into the line, with nothing left below the surface
This Week's Exercise + A Question
Write a two-person exchange in which one person wants to apologize but can't get the words out. The phrase "I'm sorry" is banned — let the remorse seep up from below the surface. Question: technical docs demand zero subtext (no ambiguity); human communication can't live without it — how do you switch between these opposite skills within a single day?
Principle 02
Scene Objective: Everyone Walks In Wanting Something
A scene without a want is small talk
Dialogue · Motive
The Principle + The Master's Words
For a scene to hold, the people in it must want something — even if it's only a glass of water. With no "want," dialogue becomes idle chatter and the reader drifts away.
"Make every character want something, even if it is only a glass of water."
— Kurt Vonnegut, preface to Bagombo Snuff Box (1999)
A want, however small, gives a scene its spine and its direction.
Why It Works
The objective gives dialogue direction. Once a character wants something, every line becomes an action — probing, pressing, conceding, deflecting. Stanislavski called it the "objective," and an actor asks before every entrance: what do I want in this scene? Meetings are the same: walk in without knowing "what I want to walk out with," and the meeting spreads into a puddle of information exchange. McKee adds a demand: a good scene must "turn" — between the open and the close, some value has to change (trust to doubt, no to yes). A scene with no turn can be cut and the reader loses nothing.
Before → After
A: How's progress? B: Fine, on track. A: Great. (Neither wants anything; flat; deletable.)
(A's objective: get B to volunteer for the thankless project) A: "Pull this off and it's the brightest line on the year." B: "Sounds like a trap." A: "That's why I didn't just hand it to anyone — I thought of you first." (Every line pushes toward the goal.)
"How's it going?" "Fine." "Great." (No one wants anything.)
(Objective: get the raise without naming it) "Three offers this quarter. I turned them down." "...Why are you telling me this?" "Because I'd rather you heard it from me."
When to Use + Common Mistakes
- ✓ Writing stories, setting an objective before a design review, 1:1s, negotiation, telling a child a story with stakes
- ✓ Auditing your own meetings: the stretch with no objective is the stretch to cut
- ✗ An objective too abstract ("to be appreciated") — it can't drive concrete lines; land it on an action
- ✗ Both sides want the same thing — no tension, no scene; let the two "wants" rub against each other
This Week's Exercise + A Question
Before your next important meeting, write one line: the specific action I want from the other side when we leave (not "reach alignment" but "approve X by Friday"). Afterward, check whether your lines all pushed toward it. Question: in real communication, "clear objective" and "looking like you have an angle" are a hair apart — what lets you walk that line?
Principle 03
Conflict & the Gap: Story Is Born in the Crack Between Expectation and Result
No conflict, no forward motion
Dialogue · Structure
The Principle + The Master's Words
A character acts, expecting the world to respond one way; the world responds another — the crack opens, and they're forced to act bigger. This repeated rupture between "expectation vs. result" is the engine of narrative.
"Nothing moves forward in a story except through conflict. ... Story is born in that gap between expectation and result."
— Robert McKee, Story (1997)
The wider the gap tears open, the bigger the character's next forced action — and the stronger the tension.
Why It Works
No one remembers a smooth story, and no one remembers a smooth report. What makes a reader sit up is always the crack: "we thought X, the result was Y." In a decision memo, name the real gap — the expectation that collapsed, the judgment that got overturned, the bottleneck that wasn't where you thought — and the reader is instantly pulled into "and then what?" This isn't manufacturing anxiety; it's honesty: real work is full of mismatches between expectation and result, and hiding them leaves the narrative as nothing but polished filler.
Expectationwhat the character
thought would happen
The Gapstory is born
in this crack
Resultwhat the world
actually returned
The wider the crack, the bigger the forced next move — and the stronger the pull.
Before → After
Retrospective: We executed to plan and hit our targets. (No gap, no memory, no one remembers.)
We thought the bottleneck was compute and spent three months scaling it; only at launch did we find the real chokepoint was the headcount for data labeling — that was the lesson this project taught us. (Expectation → collapse → reversal → takeaway.)
"The launch went well." (Smooth, no crack.)
"We expected a quiet launch. By noon the servers were on fire — in the best possible way." (Expectation and result diverge; tension appears.)
When to Use + Common Mistakes
- ✓ Retrospectives, case studies, the problem section of a pitch, personal-growth stories, the keystone project in a promo packet
- ✓ Any narrative you want read straight through — give it one real crack
- ✗ Manufacturing conflict for its own sake — false drama; readers smell the performance
- ✗ All conflict, no resolution — anxiety with no landing; the crack has to close again
This Week's Exercise + A Question
Take a recent "everything went smoothly" report and honestly find one real gap inside it (however small). Write it in two or three sentences: we expected... the result was... so we... Question: East Asian workplaces favor "reporting good news"; Western narrative prizes "show vulnerability first, then reverse" — reporting to a global team, how much of the crack do you reveal, and how do you close it?
Principle 04
Stage vs Screen: The Art of Language, or the Art of the Image
The medium shapes the words
Dialogue · Medium
The Principle + The Master's Words
The same story, written for the stage or the screen, is written utterly differently. The stage is far from the audience and the frame is fixed, so dialogue carries everything; the screen can hold a close-up, where one glance is worth ten lines. The medium isn't a container — it's the hand that shapes.
"Screenplays are structure. ... In a movie you can show; on a stage you must say."
— William Goldman, Adventures in the Screen Trade (1983)
What the stage must put into words, the screen can put into an image — choose the words to fit the channel.
Why It Works
Stage dialogue can be dense, ornate, full of monologue, because language is its only carrier; film prizes "show, don't tell," keeping lines few and exact and handing the work to image and editing. For a leader the transfer is nearly one-to-one: the same information, written as a memo (reader sets the pace, can re-read), delivered as a live talk (your presence, rhythm, pauses), or shot as a short video (one image and one hook) — each must be rewritten along the grain of its medium, not read aloud from the memo and called a video.
Stage / Memo
Carrier is language
Reader controls pace, can re-read
Holds detail, argument, density
Screen / Talk·Video
Carrier is image and presence
You set the pace; it's fleeting
Few and exact — one image beats ten lines
Before choosing a medium, ask: does this content's power come from "reading," or from "watching and listening"?
Before → After
Read an information-dense memo aloud, record it as a 5-minute video. (Audience can't keep up, no image, eyes glaze over.)
The video keeps one core number + one image + one hook; all detail folds into the memo linked at the end. Viewers remember one thing; the curious go read.
(Stage register, dropped onto the screen) "I have loved you since the day you walked into this office, though I never dared to say it."
(Screen version, let the image speak) He sees her across the room. He looks away. He'd kept her business card for three years.
When to Use + Common Mistakes
- ✓ Choosing a medium, recasting a memo as a talk, making a pitch video, splitting a long piece into video scripts
- ✓ Judging "is this worth a meeting" — if it can be read, don't say it; if it can be seen, don't write it
- ✗ Porting across media verbatim — reading text as video, sending slides as a document
- ✗ "Screen verbosity": piling on lines where an image should carry it — a film shot as a radio play
This Week's Exercise + A Question
Take an existing piece of your writing and produce two versions — one for "reading" (a one-page memo) and one for "watching and listening" (a 90-second video script). Compare what you cut and what you added. Question: AI makes text → image → video conversion nearly free; does that make the judgment of "which medium to write for" more important, or less?
Reflection
Going Deeper
Push the Edges
Subtext is a way of "not saying it directly" — does that conflict with the workplace ideal of transparency and candor?
No, because they govern different layers. Transparency governs information: facts, data, the basis for a decision — always laid bare. Subtext governs relationship and tact: how to say a sharp truth so the other person can catch it. "What time did you get to bed last night" hides no fact; it just offers a graceful step down. What to guard against is using "subtext" as a cover for avoidance — burying the fact you owe someone. That isn't craft; it's cowardice.
"Every character wants something" — but in real meetings, many people are just there to "sync information"?
That's precisely the sign the meeting shouldn't be held. If attendees have nothing they want to walk out with, the sync can happen asynchronously in a doc, more efficiently. Use the scene objective as a meeting filter: before the meeting, have each key participant write one line — "the result I want." Those who can't are those who needn't attend. This is the logic beneath the written cultures at Amazon and Stripe that replaced piles of meetings — delete a "scene" with no objective and no one understands less.
"Story is born in the crack" encourages exposing the gap, yet promo packets and external reports usually need to show success — contradiction?
The skilled move: use the crack as the hook and the resolution as the landing. "We thought the bottleneck was A, it was B, so we rebuilt the approach and ultimately delivered" — more credible than relentless good news, because it proves judgment and adaptability, not just luck. What the reader remembers isn't "you made no mistakes" but "you hit a real problem and solved it." The crack exists to make the success feel real, not to expose failure.
The same conflict written as dialogue (text), staged as a meeting (talk), or shot as a short film (video) — which is hardest to write?
Usually "talk," because it's live, unrepeatable, and dependent on your own presence. Text can be polished over and over; video can be rescued in the edit; only live speaking forces the subtext up through your pauses and your eyes in the moment, and sustains the conflict's tension by your rhythm alone. That's why speaking practice pays so well: it compresses the first three skills — subtext, objective, conflict — into a single channel with no undo button.
Can AI write good dialogue? If so, what's irreplaceable about the screenwriter and the communicator?
AI can write "passable" dialogue — natural phrasing, fluent rhythm, even the formulas of subtext. What it lacks is "these two specific people, here and now": the magic of real dialogue often anchors in an unrepeatable situation, a shared history, the stakes of the moment. The lesson for writers is consistent — the more formulaic the layer (pleasantries, transitions, information transfer), the faster it's replaced, so push your energy toward the line only you, who know this matter and these people, could write.