Interactive graph
Creative Output
Table of Contents
Notes are inventory - posts, sermons, code, and dinner experiments are the point.
Key Concept
- Output is the point - ship posts, sermons, code on a deadline, in distraction-free focus.
- The inventory only pays off the day it becomes something someone else can read, hear, or eat.
- Ship three sparks as one finished piece on Friday even if the cut is rough.
Level 1 - Recognize
Creative output is finished work that another person can read, hear, or use.
Level 2 - Explain
Notes are inventory until focused work shapes them into something delivered to an audience.
Level 3 - Use
Turn three saved sparks into one finished piece and ship it Friday even if the cut is rough.
Level 4 - Connect
Deep Work protects production time, while deadlines fight perfectionism; shipping too early still risks work that is unclear or unsafe.
Level 5 - Create
Create and publish a useful piece from the note pile, then use feedback to extend the next version.
Examples
- Friday film day means everyone shows one clip, rough or not - I do the same with my note pile, three sparks become one finished piece even if the cut is rough.
- We do not wait for perfect dinner photos - we ship the meal and fix the recipe next time.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Minimum Viable Product | Polished ship vs rough MVP when deadline forces cut scope |
| contradicts | The Collector's Fallacy | when ship pressure makes you skip capture needed for the draft |
| extends | Building a Second Brain | Offloaded notes exist to express ideas, not just store inventory |
| extends | Ship It | Finish-and-publish pressure this note defends |
| extends | Success is Stewardship | Inventory means nothing until it leaves your head |
