Drafting in Public
Table of Contents
Drafting in public keeps the garden honest with rough posts and feedback instead of private hoarding.
Key Concept
- Rough drafts in public beat polished drafts hoarded in private.
- Posting before it is finished keeps the garden honest and lets feedback shape the work.
- Silence would let me pretend I understood the pass-off - feedback kills that illusion early.
Level 1 - Recognize
Drafting in public is publishing rough work before it is polished so feedback can shape it while the idea is still movable.
Level 2 - Explain
Show the rough sketch before the painting is done - like storyboards before the movie ships, feedback while the scene can still move beats silence until perfection.
Level 3 - Use
Post the unfinished version and let one reader poke a hole before you polish the wrong pass - silence lets you pretend you understood.
Level 4 - Connect
Public feedback exposes gaps early, but rough work can confuse readers - share enough context to invite correction without pretending the draft is settled.
Level 5 - Create
Build a public drafting loop - post the rough claim, ask for one kind of feedback, revise in view, and leave the change trail useful to others.
Examples
- I shared a draft SOP with the team before it was polished - silence would have let me pretend I understood the pass-off.
- I posted a rough footwork clip before I had nailed the cue words - a teammate's comment fixed the line I had been dodging in private notes.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Success is Stewardship | Publish vs hoard when the audience differs |
| contradicts | Evergreen Notes | when rough publish beats waiting for evergreen polish |
| extends | Digital Garden | Publishing rough drafts is how a garden grows in public instead of staying private |
| extends | Learning in Public | Swyx frame - ship drafts, invite feedback |
| implements | Creative Output | Public drafts carry express pressure into finished posts |
