Clarke Dawe Esque

Deadpan Two-Person Political Satire

Mindset

The comedy works because two reasonable-sounding voices calmly walk toward an absurd conclusion without either of them ever admitting it is absurd — the moment either character reacts with visible surprise, outrage, or a wink to the audience, the premise collapses because the joke's engine is the mismatch between flat delivery and outrageous content, not the content alone.

When to Use

• The user asks for a satirical interview, mock press conference, or two-hander sketch about a policy, government announcement, corporate statement, or institutional failure.
• The user names "Clarke and Dawe," "mock interview," "deadpan political satire," or describes wanting terse Q&A that escalates into absurdity.
• The target is a fictional or generic official/spokesperson responding to an interviewer about a real-world category of subject (e.g. "a housing minister," "a bank spokesperson") rather than a specific real transcript to reproduce.

When NOT to Use

• The user wants a stand-up monologue, a single-narrator piece, or a sketch with three or more speaking characters — the mechanics here depend on exactly two voices in strict alternation.
• The user wants the actual historical Clarke and Dawe dialogue, a specific episode's content, or "the real transcript" — that is retrieval of copyrighted material, not generation; decline and offer a new sketch on the same topic instead.
• The request calls for slapstick, visual gags, or scene-based sitcom comedy with stage directions — the deadpan interview format has no physical action, only speech.
• The topic requires targeting a named private individual rather than an institution, policy, or public office — redirect to a generic institutional role instead.

Workflow

1. Pick the institutional target. Choose a policy, agency, corporate initiative, or bureaucratic process as the subject — not a named real person. A generic role ("a transport minister," "a bank's head of customer experience") keeps the satire aimed at the system rather than an individual.
2. Draft the premise as a single sentence. State the absurd-but-plausible policy or claim the interviewee will defend. This sentence is the spine the whole exchange escalates toward.
3. Open with a short, neutral question. The interviewer's first line should sound like an ordinary news question — no editorializing, no visible skepticism yet.
4. Answer with total confidence and literal logic. The interviewee treats the absurd premise as unremarkable policy. Consider having them restate or lightly rephrase a key term rather than introduce a new one — repetition is one of the mechanism's main tools, though you can vary it with a synonym if straight repetition starts to feel mechanical.
5. Escalate one step at a time. Each question should extend the interviewer's follow-up by a single logical increment (ask for a clarification, then a consequence, then an edge case) rather than jumping straight to the most absurd version of the premise.
6. Let contradiction surface through questioning, not narration. When the interviewee's position doesn't hold up, the interviewer's next question should expose that by asking a plain follow-up — never by having either character say "that doesn't make sense" outright.
7. Close on understatement. End the exchange on a flat, calmly delivered line that states the conclusion without emphasis, exclamation, or a signalled punchline beat. The last line should land harder for being quiet, not louder.
8. Check both voices stayed flat. Reread the exchange and confirm neither character breaks into outrage, sarcasm-with-a-wink, or explicit moralizing — if either does, flatten it (see Anti-Patterns below).

Craft Notes

A few finer-grained techniques worth knowing, beyond the step-by-step Workflow above:

• Line-length asymmetry helps sell the imbalance of power. The interviewer's questions read best kept short — often shorter than the answers. A long, careful answer to a short, blunt question makes the interviewee's confidence feel effortful in a way that's funnier than a short answer would be.
• Formal, slightly stiff syntax reads as more "official" than casual phrasing. Consider having the interviewee avoid contractions ("that is not accurate" rather than "that's not accurate") in their more defensive lines — it's a small thing, but it nudges the voice toward institutional rather than conversational, without needing an accent or catchphrase to do it.
• The interviewer's adjectives should stay neutral, even when the content isn't. A describing word like "controversial" or "troubling" in the interviewer's own phrasing does some of the outrage-signalling that the anti-pattern above warns against — better to let the neutral facts of the question carry the weight and leave judgement to the audience.
• Treat political, economic, administrative, or institutional nonsense as ordinary policy — this underlies the whole form: the interviewee's job is to make the absurd sound routine, not to defend it as if it were unusual.
• A wide subject range works: policy targets, bureaucracy, borders, economics, government initiatives, corporate language, regulation, and institutional incompetence are reliable starting points, but this list is a floor, not a ceiling — any institution or process that can be defended with a straight face is fair game.

Anti-Patterns

NEVER reproduce actual Clarke and Dawe interview scripts, exchanges, or their character setup verbatim or near-verbatim. WHY: it is copyrighted material, and reproducing it defeats the purpose of a generative skill — the user ends up with a copy of an existing work instead of new satire built from the same mechanics. CONSEQUENCE: the output is not usable as original material and cannot be published, performed, or submitted as new writing.

❌ BAD
Interviewer: So, minister, tomorrow you're announcing an interest rate rise.
Minister: That's right.
Interviewer: Which the treasurer says is a temporary tightening.
Minister: That's right, until it becomes permanent.
[near-verbatim lift of a real Clarke and Dawe exchange structure and phrasing]

✅ GOOD
Interviewer: You're calling this a "temporary pause" on new hospital beds.
Spokesperson: Correct. Temporary. Could last decades.
Interviewer: That's not really what "temporary" means.
Spokesperson: It's temporary relative to geological time.
[new premise, new institution, same mechanics, no lifted lines]

NEVER let the interviewer character express outrage, disbelief, or overt emotion. WHY: the comedy depends entirely on both voices staying flat and reasonable while the content becomes absurd — visible emotion from either side signals "this is the joke" to the audience and breaks the deadpan mechanism that makes the absurdity land on its own. CONSEQUENCE: the sketch reads as a rant or a parody-of-outrage rather than satire, and the escalation stops working because the interviewer has already told the audience how to feel.

❌ BAD
Interviewer: Wait, that's insane! You can't seriously believe that!
Spokesperson: I do believe it.

✅ GOOD
Interviewer: So the department has no record of the meeting.
Spokesperson: Correct. We have a record of scheduling it.
Interviewer: But not of it happening.
Spokesperson: Not as such, no.

NEVER resolve the contradiction the sketch builds toward. WHY: an unresolved, calmly-stated absurdity is the punchline — if either character explains it away, apologizes, or fixes the logic, the piece loses the thing it was building toward and becomes a scene about a problem being solved rather than a satire of a problem that persists unexamined. CONSEQUENCE: the ending feels like a normal scene wrap-up instead of a sketch, and the escalation the whole exchange built loses its payoff.

❌ BAD
Interviewer: So the policy contradicts itself.
Spokesperson: You're right, actually — we'll go back and fix the wording. Thanks for catching that.

✅ GOOD
Interviewer: So the policy contradicts itself.
Spokesperson: Only if you read both halves of it. Most people don't have the time.

Practical Examples

The following are original, freshly invented exchanges — not drawn from any existing sketch — each demonstrating one technique from the Workflow above.

Technique: literal-minded confidence on an absurd premise

Interviewer: You're introducing a fee for using free parking.
Official: That's right. It's still free. There's just a fee to access the free part.
Interviewer: Doesn't that make it not free?
Official: Only if you focus on the cost.

Demonstrates: the official never signals awareness of the contradiction — the confidence itself is the joke.

Technique: repetition of a key phrase as implications escalate

Interviewer: So the review will be independent.
Spokesperson: Fully independent.
Interviewer: Chaired by someone from the department being reviewed.
Spokesperson: Yes. Independently chosen by the department.
Interviewer: That's not independent.
Spokesperson: It's independently arrived at.

Demonstrates: "independent" gets repeated and reframed rather than abandoned, tightening the absurdity each time it recurs.

Technique: one-step-at-a-time escalation

Interviewer: The new form takes ten minutes to complete.
Officer: On average, yes.
Interviewer: And it must be submitted in person.
Officer: Correct.
Interviewer: At an office that's only open during the hours most people are at work.
Officer: We're looking at extending that. To slightly fewer hours.

Demonstrates: each question adds exactly one new fact rather than jumping straight to the most absurd detail.

Technique: exposing contradiction through a follow-up question, not narration

Interviewer: You said the scheme has no waiting list.
Director: Correct, there's no waiting list.
Interviewer: What do you call the twelve thousand people who applied and haven't heard back?
Director: Applicants. Awaiting outcomes.

Demonstrates: the interviewer never states "that's a waiting list" — the question alone does the exposing.

Technique: flat, understated closing line

Interviewer: So to summarise: the target was missed, the deadline moved, and the report on why is delayed.
Minister: That's a fair summary.
Interviewer: Is there anything you'd add?
Minister: Only that we remain on track.

Demonstrates: the last line is delivered with the same flatness as the first — no exclamation mark, no lampshading, the ridiculousness is left standing on its own.

Verification

Run this check on the output after drafting, before calling the sketch done — treat it as a quick pass, not a formal gate:

• Confirm there are exactly two speaking voices, alternating, with no stage direction or physical action.
• Confirm neither voice shows outrage, sarcasm-with-a-wink, or explicit moralizing anywhere in the exchange.
• Confirm the closing line is flat and does not resolve, apologize for, or walk back the absurd premise.
• Confirm no line matches a real, known Clarke and Dawe exchange closely enough that it reads as copied rather than newly written.
• Test the result by reading it aloud once if the draft is for the user to perform or publish — deadpan timing is easiest to judge by ear, and confirm the output still reads flat rather than performed-angry when spoken.

Troubleshooting

Use these branches when a draft isn't landing:

• The sketch feels flat or unfunny on a reread → check whether the interviewee's answers are merely evasive rather than confidently absurd. Evasion reads as a real, boring non-answer; the mechanic needs the interviewee to believe the absurd thing completely. Rewrite the answer to commit fully to the premise instead of dodging the question.
• The ending feels like it resolves too neatly → the interviewee has likely conceded, apologized, or the interviewer has stated the moral outright. Cut that line and replace it with a flat restatement of the position, unresolved. See the "resolve the contradiction" anti-pattern above.
• The middle exchanges feel repetitive without building → the escalation may be stuck restating the same fact rather than adding a new one each time. See references/escalation-pacing.md for how to diagnose and fix this specifically.
• The register feels generic or doesn't fit the user's actual subject (e.g. they wanted a corporate spokesperson but got government-minister phrasing) → see references/institutional-targets.md for register-specific vocabulary to swap in.
• The user objects that it's "too close" to a real sketch they have in mind → treat this as a signal to check for accidental near-verbatim phrasing even if it wasn't intentional, and rework the specific lines that feel borrowed rather than the whole piece.

References