Bit Anatomy
Every bit is built from the same skeleton. Knowing each part tells you exactly where a joke is broken — and which tool fixes it.
The territory. The observation, frustration, or confusion the bit is built on. Not funny yet — just real. Good premises come from things that genuinely bother, confuse, or fascinate you.
Right start: "This actually happened / bothered me / didn't make sense"
The specific observation within the premise that makes it a bit instead of just a topic. Most flat jokes have a strong premise and a vague angle. Keep pushing until you can state it in one crisp sentence.
Weak angle: They're obsessed with it
Strong angle: Coffee drinkers built a personality around tolerance to a substance that no longer does anything for them — junkies chasing a high they'll never get back, in fleece vests
Builds a false expectation in the audience's mind. Its job is misdirection — get the audience to commit to one interpretation of the connector so the punchline can shatter it. A good setup is factually true, clear, specific, visual, and one idea only. It is NOT funny on its own.
Shatters the setup's expectation by revealing an unexpected interpretation of the connector. The reveal word triggers the laugh — it must land at the very end of the sentence. Buried in the middle, it dies.
The word, phrase, image, or idea with two interpretations: the expected one (the setup builds it) and the unexpected one (the punchline reveals it). Every joke has one. Find it and you can write punchlines systematically.
Core Philosophy
The lenses to write through. If a joke doesn't connect to at least one of these, it may not belong in the set.
Put the realization at the farthest depth most people can follow. Not so obscure it's missed, not so shallow it lands without satisfaction. The sweet spot: a penny dropping the audience almost dropped themselves.
The surreal needs a logical spine — a reality that could exist if the normal rules were extended to their absurd conclusion. The setup makes the audience nod; the punchline reveals they were nodding at something insane.
Two disparate things compared well = easy laugh. The more unexpected the pairing and the more precisely it fits, the bigger the payoff. There are usually 3–4 jokes inside one good analogy.
Unique premises, counterintuitive angles, never the first word that comes to mind. Originality is a competitive advantage at the open mic level, where everyone tells similar jokes.
Comedy is a pressure release valve. The best bits point at something uncomfortable the audience has felt but never said out loud — and make it safe to laugh at.
You write memorable jokes because you have to remember them without notes. A joke that's hard to memorize is usually too long, too complex, or lacks a clear punchline architecture.
Your Voice
The comedic point of view every generated bit should serve.
Open mic / early stage — still finding a persona, building material from real observations.
Favors plausible surrealism and clever analogies over shock or pure absurdism.
Values specificity over generality — the more exact the detail, the funnier.
Wants the realization moment pushed as far as most people can follow — not obscure, not surface-level.
Believes uncomfortable truths are relieved by laughter — comedy as emotional pressure valve.
Writes memorable jokes, because you have to remember them on stage (the Paul McCartney principle).
Wants jokes that don't fit in — original, unexpected, distinct.
Don't write generic jokes. Don't write "clean open mic" safe material unless asked. Write toward the edge of where this comic actually lives, intellectually and observationally.
The 5 Modes
Click a mode to see its trigger, goal, and step-by-step protocol.
Brainstorm
New bit from scratch — from raw idea to a usable setup + punchline, with 2–3 angles to choose from.
Punch-Up
Sharpen existing material — 3–5 variations, each a different technique, with a clear top pick.
Tag Generation
Additional punchlines after the main one — 5–10 tags, fast, labeled by type.
Callback Construction
Identify plants and harvest moments; connect bits across a set with recontextualized payoffs.
Set Structure Review
Map the energy arc of a full set, flag problems, and give specific reordering recommendations.
Brainstorm — Protocol
- Lock the PremiseRestate the idea as one clean sentence, no jokes yet. Is it something genuinely noticed or felt? Is the territory specific enough?
- Find 3 AnglesRun the premise through the 11 Funny Filters and the personal technique palette. Label each: Angle A/B/C — [Filter] — [one-sentence description].
- Write Draft Setups + PunchlinesSetup: factual, clear, specific, visual, not funny yet. Punchline: reveal word last. Check against SUCCES.
- Generate Tags2–3 quick tags after the first punchline, labeled by technique.
- Score and FlagRun the bit through the Bit Scoring System. Note what's checked, flag what's missing.
Punch-Up — Protocol
- Diagnose FirstWhere's the connector? Does the reveal word land last? Is the setup too long? Is the angle vague? Is the gap wide enough? State the diagnosis in 1–2 sentences.
- Generate 3–5 VariationsEach tackles a different repair: Compression, Specificity, Inversion, Filter Swap, Word Surgery.
- Name the Top PickState which variation wins and why, in one sentence.
- Flag Callback PotentialIf the line has a strong image, phrase, or character, note its potential for later in the set.
Adapt to feedback: "Faster" → strip labels, just list variations. "Explain the best one" → go deep on technique. "Give me more" → add variations on a different axis.
Tag Generation — Protocol
- Identify What's EstablishedWhat character, situation, or rule does the punchline create? What's the new "normal" after it lands?
- Generate Tags by TypeAt least one of each applicable type. Use: "because…" completion / "what does [character] do next?" / worst-case extension / what assumption can now be shattered.
- Stack TestOrder weakest to strongest — they should escalate. If tag 2 is weaker than tag 1, cut it. Three tags max before the premise is exhausted.
Callback Construction — Protocol
- Audit for Callback CandidatesUnusual phrases that landed, characters who could return, a premise rule that could be broken, the most memorable opener image, anything physically distinctive.
- Design the PlantMust land its own laugh independently, be distinct enough to be remembered, and not telegraph itself as a setup.
- Design the HarvestSame element in a new context that recontextualizes or extends it. Should work as a joke in the current bit AND as a callback. The second laugh is bigger.
- Placement LogicPlant early, at least 3–5 bits of distraction, harvest near or at the close.
Set Structure Review — Protocol
- Build the Energy MapPer bit: energy level (High/Med/Low), laugh density, callback status, character function.
- Flag ProblemsBack-to-back high energy, cold opener, energy valley with no recovery, orphaned plants, weak closer, character inconsistency, premise orphans.
- Give Specific RecommendationsNot "consider moving Bit 3" — instead the exact move and the reasoning behind it.
- Identify Missing ElementsA closer worthy of the set? Missing callback opportunities? A character-establishing moment early enough? Is the runtime right (3–7 min, err tighter)?
11 Funny Filters
Run a premise through each filter and see which one sparks something. You don't need all 11 — you need the one that fits this material.
How to use these while brainstorming
Take the premise, apply each filter, write one sentence. Which one made you laugh? Start there. Which three produced interesting angles? Those are the variations.
Greg Dean's Joke Map & Mine
A systematic excavation method for when you're stuck on a premise with no angle. It generates quantity — curation is on you.
Joke Map — Writing Setups
- TopicStart with a subject (e.g. "coffee")
- Association DetailsList 10–20 specific things tied to the topic (baristas, foam, ordering, addiction, price...)
- Punch-PremiseFor each detail, write a negative opinion. "Baristas are incompetent at remembering names"
- Setup-PremiseFlip to a positive opinion — this is the misdirection. "Baristas are excellent at personalizing the customer experience"
- SetupWrite a factual, non-funny statement from the setup-premise that leads to a false expectation.
Joke Mine — Writing Punchlines
- Identify the ConnectorThe word/phrase in the setup with two possible interpretations
- Lock the Target AssumptionThe interpretation the audience will naturally assume
- Generate Reinterpretations5–10 interpretations that contradict the target assumption
- Write the PunchlineReveal word lands at the end
- Select and CompressPick the most surprising + credible reinterpretation; cut to minimum words
The setup-premise is not the setup itself — it's the concept multiple setups get written from.
SUCCES + LIONS
From Chip & Dan Heath's Made to Stick, applied to comedy. Run any joke through this before calling it done.
Highlight only the most important point. One joke = one idea. If the setup needs two jokes' worth of information, split or cut it.
Open a gap in the audience's knowledge, then fill it. The punchline closes a gap they didn't know was open.
Sensory information. The Velcro Theory: new info sticks better when it relates to familiar concrete images. "My neighbor's seventeen-year-old beagle who only barks at wind" beats "the dog."
The audience should be able to test the idea against their own experience — not just take your authority for it.
Frame the message to elicit the right specific emotion — not just "fear," but the exact fear underneath the premise.
A specific date, place, and person — Dale Carnegie style. Not "one time at a party" but "last Thursday at my cousin's birthday at the Applebee's on Route 9."
LIONS — Language Framework
A secondary clarity/memorability pass, applied after a joke is structurally solid.
L — Language Easily Understood: No jargon, no inside references the majority won't catch, no setup requiring pre-existing knowledge the audience may lack.
I — Illustrations: Give the audience a picture. Abstract ideas become jokes when they become images.
Bit Scoring
After writing or reviewing a bit, score it against these. More boxes checked is better — click to test a bit as you go.
Set-Level (per bit)
Joke-Level (per setup + punchline unit)
Punch-Up Toolkit
Run these diagnostics on any flat joke before rewriting it.
Diagnostic Questions
- Does the punchline word go last?If not, restructure the sentence so it does.
- Is the setup longer than it needs to be?Cut to the last possible moment before the connector.
- Is the angle vague?Push it to specificity.
- Is there a better word?Harder consonants (K, P, T) beat soft ones. Concrete nouns beat abstract ones. Brand names beat categories.
- Does the punchline reinterpret something from the setup?No connector being flipped may mean there's no joke structure — just a statement.
- Is the surprise big enough?The gap between predicted and delivered = the size of the laugh. Bigger gap, bigger laugh — up to the credibility limit.
Word-Level Surgery
Cut filler first: "I was like," "you know," "basically," "kind of" — comedy killers.
Make the noun specific: "A dog" → "my neighbor's dog" → "my neighbor's seventeen-year-old beagle" → "my neighbor's seventeen-year-old arthritic beagle named Lieutenant."
Make the verb active: "He went" → "He power-walked" / "He shuffled" / "He lumbered."
Syllable count matters: Funny words tend to run 2–3 syllables. "Pickle" beats "cucumber" — not always, but often.
Hard consonants (K, G, T, P, B) tend to land harder than soft ones (F, S, W, H).
Move the reveal to the end. Read the punchline aloud — is the last word doing the heavy lifting?
Structural Repair
| Problem | Fix |
|---|---|
| Setup too long | Cut everything before the connector. Start as late as possible. |
| Punchline doesn't surprise | Find the connector. What expectation was set? What's the opposite or unexpected read of it? |
| Joke explains itself | Cut the explanation. If the audience needs it, rewrite the punchline clearer, not longer. |
| Premise too broad | Apply a specific filter: who exactly? Where exactly? When precisely? |
| Punchline buried mid-sentence | Restructure: verb + subject + context → reveal word at the end. |
| True but not funny | Apply a filter from the 11 Funny Filters — whichever is most natural for the premise. |
The 5-Angle Method
When a joke isn't landing, generate 5 completely different punchlines for the same setup:
1. Analogy "This is like…"
2. Hyperbole Push to the most extreme possible version
3. Inversion What's the exact opposite of where this is going?
4. Misplaced Focus What's the wrong thing to focus on here?
5. Character What does the character in the setup say or do unexpectedly?
Tag Writing
A tag is an additional punchline after the main one — a second turn from the same premise. Tags enhance a joke that already works. They do not save a broken one.
Stacking
Each tag should get a bigger laugh than the last. If tag 2 underperforms tag 1, cut it and use tag 1 as the out. Three tags max before the premise is exhausted — though Jim Gaffigan regularly runs 5–7 (study the Hot Pockets bit for stacking architecture).
Finding Tags — The Method
1. After the punchline, write "because…" and finish the sentence — often a tag.
2. Ask: "What does [character in the setup] say next?" — a POV shift tag.
3. Ask: "What's the worst-case extension of this?" — a logical extension tag.
4. Ask: "What did the audience assume wouldn't happen that technically now could?" — an assumption shatter tag.
Callback Construction
A callback references an earlier joke, generating a second, larger laugh through recognition + surprise in a new context. Often the best closer available.
Early in the set. Must get its own small laugh, be distinct enough to recall, and not telegraph itself as a setup. The longer the gap before harvest, the more distinct the plant needs to be.
Middle of the set. Get the audience fully invested elsewhere — 3–5 jokes minimum between plant and harvest, so the element feels forgotten before it returns.
Later, often at the close. The element returns in a new context that recontextualizes or extends it. Works both within the current bit AND as a connection back. The second laugh should be bigger.
What Can Be Called Back
Phrase A specific phrase or unusual word combination — John Mulaney's "dogs without horses"
Mannerism A character's voice or gesture — Tim Allen's grunt
Physical bit A prop or physical moment
Premise rule Establish a rule early, break it with the callback
Persona trait A comedic character trait revisited
At Open Mic Level (3–7 min sets)
Callbacks work best when the set runs 5+ minutes, with one strong plant in the first 90 seconds and one harvest near the close. The callback should recontextualize, not just repeat — the audience should think "oh — that's what that meant."
Set Energy Architecture
A set is not a playlist. It's a designed arc.
Standard Open Mic Arc (3–7 min)
Strong + quick opener → biggest / most reliable first bit → new material or second bit → callback or biggest punchline as closer.
Opener Goals (first 30–60 seconds)
Quick laugh to break the ice (self-deprecation or a strong one-liner).
Establish character — who are you on stage?
Lower audience anxiety — "this person knows what they're doing."
Plant a callback element if the set runs 5+ minutes.
Energy Management
Never run three high-energy bits in a row — the third underperforms not because it's worse, but because the contrast is gone.
Alternate: big premise → smaller observational → crowd moment → big premise.
The second bit should be slightly less strong than the first, to create a valley before the closer.
Closer Principles
The strongest punchline should be the last word the audience hears.
Callbacks in the closer reward attention and create the "full circle" feeling.
End on a laugh, not an explanation.
Energy Map Format
General Writing Principles
The rules that apply across every mode, every bit, every rewrite.
Every extra word is a vote against the punchline. The setup's only job is to build the right expectation. Cut everything else.
The funniest word in the sentence belongs at the end. If it's not there, rewrite until it is.
A joke that needs to be explained after delivery is a joke that needs to be rewritten before delivery.
"A large coffee" isn't as funny as "a 32-ounce Pike Place from the Starbucks inside a Target inside a Walmart." Specificity signals truth. Truth makes jokes credible. Credible jokes land harder.
The premise is just the zip code. The angle is the specific street corner. Most flat jokes have a great premise and a vague angle — push the angle until it's unambiguous.
Aim for the highest laugh-per-minute density the material allows. A tight 3–5 minute set with one strong bit and two supporting bits beats a rambling 7-minute story. Leave them wanting more.