TThe Diary of a CEO
← All frameworks
Productivity

Draft-to-Discover Loop

Write rough versions early, share them, and rewrite without ceremony

Difficulty
Moderate
Time to result
~weeks to results
Steps
5
Confidence
96%

Rogen describes a writing process built around externalizing ideas quickly. Rather than spending too long discussing what a scene might be, he prefers to write it, inspect the result, try alternate versions, share rough material with a trusted group, and rewrite readily. He says he may produce a very large number of drafts and does not treat early wording as precious. The mechanism is discovery through artifacts: once an idea exists on the page, collaborators can react to something concrete, compare alternatives, and identify what is not working. The loop depends on psychologically separating a draft from the writer's identity and on choosing readers whose judgement is trusted. It is a creative iteration method, not permission to release unfinished work publicly.

Origin

Extracted from The Diary of a CEO

Core principles

  • 01A written attempt reveals more than prolonged abstract discussion
  • 02Early drafts are experiments rather than verdicts
  • 03Trusted feedback improves rough work before it hardens
  • 04Low preciousness supports many revisions

How to run it

  1. 1

    Externalize the idea

    Write the current best version before discussion becomes circular. Treat it as a test object rather than a commitment.

    Pro tip Set a short drafting window to lower the pressure on the first attempt.

  2. 2

    Read the artifact

    Evaluate what is actually on the page rather than what you intended. Mark where the result fails to create the desired effect.

    Watch out Do not defend the draft by explaining material that the reader cannot see.

  3. 3

    Generate alternatives

    Write different versions of weak sections instead of endlessly polishing one approach. Compare how each version changes the whole.

    Pro tip Change the underlying choice, not only the wording.

  4. 4

    Share rough work

    Send an early version to a small group whose taste and candour you trust. Ask what worked, what confused them, and where attention dropped.

    Pro tip Choose readers who understand the intended audience and form.

    Watch out Too many unfiltered opinions can blur the purpose of the work.

  5. 5

    Rewrite without ceremony

    Use relevant feedback to create the next version promptly. Repeat the loop until the work achieves its intended function.

    Pro tip Preserve old versions so deleting a weak choice feels reversible.

    Watch out Iteration can become avoidance if no success condition is defined.

In the wild

Testing a scene on the page

In a writing session, collaborators could spend an hour debating whether a scene should be tense or comic. Using Rogen's process, they instead draft both versions, read them, send the stronger attempt to trusted readers, and rewrite from the reactions. This is an illustrative application of the process he describes.

The decision is made against visible alternatives rather than abstract preferences.

Common mistakes

Protecting the first draft

Treating early wording as precious reduces the number of alternatives and makes useful feedback feel personal.

Talking instead of testing

Discussion cannot reveal every problem that becomes obvious once the idea is written and read.

Is it for you?

Best for

It is best for collaborative writing and other work where multiple versions can be produced and evaluated cheaply.

Not ideal for

It is not ideal for irreversible work where a rough attempt creates serious legal, safety, privacy, or reputational consequences.

From the transcript

just write it let's just write it let's just see how it looks

Seth Rogen · (1:11:00)

I share a lot of early versions of things with like a group of people that I trust

Seth Rogen · (1:11:30)

I'll rewrite it instantly I'll do a hundred drafts

Seth Rogen · (1:11:30)

From the episode

Seth Rogen Opens Up About His Self-Doubt & Struggles That Nobody Sees!