Writers room whiteboard

Behind the Scenes

Writers' Room

The messy process behind "Gil Is Awful." Post-its, arguments, coffee stains, and the conversations that shaped the story.

Charlie Head Writer
Emma Dialogue
Sarah Chen UX Lead
Marcus UI Design
Kai Motion

01 Initial Pitch Session

Session #1 | Monday, 09:14 AM | Conference Room B (the one with the broken AC)

Charlie: 09:14

Okay, hear me out. We open with Jan. Senior engineer. 15 years experience. He walks us through fixing a bug. Clean. Professional. The audience is nodding along, thinking "solid process, I wish my team did this."

Emma: 09:15

Standard tutorial format. Where's the hook?

Charlie: 09:16

The hook is at the end. Jan finishes. Says goodbye. The screen glitches. A different voice speaks.

Charlie: 09:16

"Here's the thing about Jan."

Charlie: 09:16

"Jan doesn't exist."

Emma: 09:17

...

Emma: 09:17

Oh. Oh that's good.

Sarah: 09:18

Black Mirror vibes. "Be Right Back" meets a tech conference.

Charlie: 09:19

Exactly. The horror isn't "AI is scary." The horror is: you couldn't tell the difference. You connected with something that doesn't exist. And it worked.

Marcus: 09:20

But we need the audience to trust Jan first. Otherwise the reveal doesn't land.

Charlie: 09:21

That's the whole game. We have to make Jan real. Likeable. Competent. The more human he feels, the harder the reveal hits.

The twist only works if they TRUST Jan first

- Charlie

Voice change = perspective change

1st person -> 3rd person

"The call is coming from inside the house"

- Sarah's analogy

02 Character Development: Humanizing Jan

Emma's notes on making Jan feel real | Tuesday morning

Emma: 10:32

If Jan is just "good engineer who fixes bugs," he's forgettable. He needs quirks. Real people have quirks.

Charlie: 10:33

What kind of quirks?

Emma: 10:34

Specific ones. Not "likes music" - that's generic. "Codes to Blade Runner on repeat. Vangelis understood focus." That's a person.

Emma: 10:35

I'm thinking: Seven mechanical keyboards. Bonsai trees on the windowsill. Instant coffee because "life's too short to optimize everything."

Marcus: 10:36

The coffee thing is good. It's contradictory. A perfectionist engineer who doesn't care about coffee? That's interesting.

Emma: 10:38

Right! He picks his battles. Saves his optimization energy for code. That's a real engineering mindset.

Charlie: 10:40

And after the reveal, the audience realizes: those "human" quirks were constructed. The bonsai trees don't exist. The keyboards don't exist. It was all designed to make them feel something for a character profile in a YAML file.

Emma: 10:41

That's what makes it unsettling. They connected with fiction, and it felt real.

Emma's Character Notes

Quirks (Humanizing Details)

  • + Seven mechanical keyboards (one from 1989)
  • + Bonsai trees - "Pruning is like refactoring"
  • + Instant coffee (picks his battles)
  • + Blade Runner soundtrack on repeat
  • - Has a cat named "Null" (too on-the-nose)
  • - Makes his own cold brew (contradicts instant coffee)

Voice Notes

  • Confident but not arrogant
  • Uses "we" sometimes - shows team player
  • Short sentences when focused
  • Longer explanations when teaching
  • Never apologizes for high standards
  • "That's how I like it." - signature phrase
"The bonsai/refactoring parallel is doing a lot of work. Keep it." - Charlie

03 The Twist: Structure & Timing

The reveal structure debate | Wednesday, heated discussion

Marcus: 14:22

I think we should hint at it earlier. Subtle glitches throughout. So the audience feels smart when they figure it out.

Sarah: 14:23

Hard disagree. If they expect something weird, the reveal loses impact.

Marcus: 14:24

But the title sequence is already unsettling. Black Mirror aesthetic. Glitch text. They're primed for something creepy.

Sarah: 14:25

That's the point. We WANT them primed, then we lull them into forgetting. The title says "something's off." Then Jan is so normal, so professional, they forget to be suspicious.

Kai: 14:27

Sarah's right. The contrast is what makes it work. Creepy title -> clean presentation -> BAM, the rug pull.

Charlie: 14:28

Think about "The Sixth Sense." You don't sprinkle hints that Bruce Willis is dead. You let the audience trust the reality, then recontextualize everything at once.

Marcus: 14:30

Fine, but I still think there should be ONE moment during Jan's section that feels slightly off. Not a glitch - something behavioral. So on rewatch, people go "oh, THAT was the tell."

Emma: 14:32

What about the line "I've seen this before"? He says it with complete certainty. But... when did a persona "see" anything? In hindsight, that confidence is unsettling.

Charlie: 14:33

That's perfect. It's not a glitch - it's a semantic tell. He has access to every Stack Overflow answer and browser compatibility table ever written. Of course he's "seen" it before. He knows everything.

Marcus: 14:35

Okay, I'm in. Subtle semantic tell, not visual. The audience won't notice on first watch but might on second.

Final Reveal Structure

Slide 78 "So that's how I work." JAN voice
Slide 79 "Pretty standard, right?" JAN voice
Slide 80 "Thanks for watching." JAN voice
CUT TO Back to Marcus - 11:45 PM timestamp SCENE CHANGE
Slide 81 "Module 29 of 87" MARCUS POV
Slide 82 "Just 58 more to go. I better get to bed." MARCUS voice + footsteps
FADE Fade to black - credits roll TRANSITION
Credits "SIMS IS AWFUL" + Cast Silent
POST-CREDIT The reveal begins... TWIST
Reveal 1 "Here's the thing about Jan." NARRATOR voice
Reveal 2 "..." 3 sec pause
Reveal 3 "Jan doesn't exist." NARRATOR voice
END CRT shutdown - screen collapses to line, then black CRT OFF

04 UX Review: Visual Contrast

Sarah Chen's notes on emotional pacing | Thursday design review

Sarah: 11:05

The reveal needs visual contrast. Not just words - the whole screen language has to shift.

Kai: 11:06

What are you thinking?

Sarah: 11:08

Three visual modes. Title sequence: cold, glitchy, unsettling - Black Mirror aesthetic. Jan's presentation: warm, clean, professional - standard tech presentation. Reveal: cold again, but different. More stark. More empty.

Marcus: 11:10

So the color temperature shifts? Jan is warm oranges and ambers. Reveal is cold blues and blacks?

Sarah: 11:12

Yes. But it's more than color. Jan's slides are busy - code blocks, terminal outputs, PR templates. After the reveal, it's mostly black. White text. Lots of empty space. Like the truth is being whispered in a dark room.

Kai: 11:14

The information density drops. Jan's sections are teaching. The reveal sections are... confronting.

Sarah: 11:15

Exactly. "Jan doesn't exist" shouldn't be surrounded by UI elements. Just black. White text. The audience needs to sit with it.

Jan's Sections (Act 2)

  • Warm colors: #ff6b35, #fbbf24
  • High information density
  • Code blocks, terminals, PRs
  • Standard presentation feel
  • Comfortable, familiar
  • First-person voice

Reveal Sections (Act 3)

  • Cold colors: pure black, white
  • Minimal information
  • Mostly empty space
  • Stark, confrontational
  • Uncomfortable, exposed
  • Third-person voice

"It's like that moment in a horror film when you realize the call is coming from inside the house."

- Sarah

05 Motion Design Notes

Kai's glitch effect decisions | Friday morning

Kai: 09:45

For the title sequence - full Black Mirror. Glitch text, chromatic aberration, static noise. Set the tone immediately.

Marcus: 09:46

How aggressive?

Kai: 09:47

Subtle enough that it's stylish, not annoying. The glitch should feel like the presentation itself is unstable - like something's wrong with reality, not with the projector.

Kai: 09:49

But Sarah's right - Jan's sections should be completely clean. Standard transitions. The audience forgets about the creepy intro. We're lulling them.

Charlie: 09:51

And the transition to the reveal?

Kai: 09:53

Screen tear. Brief static. Like an old VHS tracking error. Then the color temperature shifts colder. It's subtle but noticeable - the audience feels that something changed even before they hear the new voice.

Kai: 09:55

For the ending: Black screen. White text appears. Slight flicker - not full glitch, just... unstable. "Coming to your workplace." Beat. "2027." Hold for three seconds. Then credits.

Emma: 09:57

The flicker is key. The text itself isn't stable. The future is uncertain. Or maybe too certain.

Motion Specifications

Title Glitch

  • Duration: 0.5s loop
  • RGB split: 2-5px
  • Flicker: 4s cycle
  • Static: 3% opacity

Screen Tear

  • Duration: 0.3s
  • Clip-path slices: 4-5
  • X offset: +/- 5px
  • Hold after: 1.5s black

End Flicker

  • Timing: 92-97%
  • Opacity: 0.3-0.8
  • Random intervals
  • VHS aesthetic

06 Dialogue Samples: Before & After

Emma's refinements | Multiple sessions

Jan's Introduction

V1 (Too Generic)

"Hi, I'm Jan. I'm a software engineer with 15 years of experience. Today I'll show you my bug fixing process."

Final (Has Personality)

"Hi. I'm Jan. Senior Software Engineer. 15 years in the game. I've seen things. Fixed things. Broken things. Today I'm going to show you how I fix a bug. The right way. No shortcuts."

Emma: "Short sentences when he's stating facts. He's confident. Doesn't need to soften it."

The Coffee Line

V1 (Explanation)

"I drink instant coffee because I don't have time to make fancy coffee. I'd rather spend that time coding."

Final (Philosophy)

"I drink instant coffee. Life's too short to optimize everything. I save my energy for code."

Emma: "The v1 sounds defensive. The final is a life philosophy. It reveals character."

The Reveal Line

V1 (Too Wordy)

"But here's the thing you need to know about Jan. The truth is that Jan isn't a real person. He was never real."

Final (Stark)

"Here's the thing about Jan."
[pause]
"Jan doesn't exist."

Charlie: "The pause does more work than any words could. Let the silence land."

Section 4 - Investigation (Tracked Changes)

"Let me traceI trace the date formatting..."

"There it is. This is a classic browser quirk.Browser quirk. Classic."

"I think I've seen this issue before in another project.I've seen this before."

Emma: Removing hedging ("let me", "I think") makes Jan more confident. The terseness is his voice.

07 Cut Content: Ideas That Didn't Make It

The graveyard of good-but-not-right ideas

Jan's Coworker Subplot

Cut

Original idea: Jan mentions a coworker named "Alex" who made the original bug. After the reveal, audience realizes Alex doesn't exist either.

Charlie: "Too complicated. We want ONE twist, not a twist-within-a-twist. Dilutes the impact."

Interactive Element

Cut

Proposal: Let audience "ask Jan questions" via chat during presentation. He responds in real-time (actually AI).

Sarah: "Amazing idea but wrong format. This is a recorded presentation, not a live demo. Save for v2."

Mid-Presentation Glitches

Cut

Suggestion: Subtle visual glitches during Jan's presentation. Brief flickers. Things that seem like bugs but are actually hints.

Sarah: "Breaks the trust. If they're suspicious during Act 2, the reveal doesn't hit. They need to feel safe."

Photo of Jan

Cut

Idea: Show an AI-generated photo of "Jan" during his introduction. After reveal, show it was AI-generated.

Emma: "Too on-the-nose. The whole point is that Jan is built from traits and principles, not a face. Keeping him faceless makes him scarier - he could be anyone. Or everyone."

"Cat Named Null" Quirk

Cut

Early character note: Jan has a cat named "Null" or "NaN" - programmer humor.

Emma: "Too cute. Too 'developer Twitter.' Jan's quirks should feel like real human details, not tech in-jokes. The instant coffee works because it's universal. A cat named Null is pandering."

Darker Ending

Cut

Alternative ending: "You've been watching an AI. You've been learning from an AI. How do you know THIS isn't an AI talking to you right now?" Then silence.

Charlie: "Too nihilistic. We want unsettling-then-empowering, not existential-crisis-with-no-resolution. The current ending has hope: 'Now YOU can do this.'"

Key Takeaways

The twist works because we earned the audience's trust first.

Jan is real because his quirks are specific, not generic.

The visual contrast amplifies the emotional shift.

Less is more in the reveal - silence does the heavy lifting.

"The horror isn't that AI exists. The horror is that you couldn't tell."