Interactive graph
Ship It
Table of Contents
Ship the good-enough version live instead of polishing until the deadline owns the work.
Key Concept
- Publish the good-enough version live instead of polishing until the deadline owns the work.
- Level 1: Put the good-enough version out there instead of polishing forever - like sending the draft before the deadline runs you over.
- Level 2: Put the good-enough version out there instead of polishing forever until the deadline runs you over.
- Level 3: Publish the workable draft - polish has diminishing returns once feedback could arrive.
- Level 4: Because perfect-in-private never meets reality, shipping tests the idea against users and clocks.
- Level 5: Publish the good-enough version live instead of polishing until the deadline owns the work - done beats hypothetical.
- Freelance parallel: Selling Static Sites - ship the first client site before the three-tier pricing PDF exists.
- Feedback on a live, flawed version teaches more in a week than another month of internal debate.
Examples
- The menu went live with one typo fixed after service - customers ate tonight.
- We ran the new play ugly in scrimmage instead of drilling it another month.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Attention to Detail | when the opposite frame fits better |
| contradicts | Change Window | when milestone pride ships Friday at 5:01 |
| contradicts | Rollback Principle | when milestone pride blocks calling rollback Friday night |
| contradicts | Staged Rollout | when blasting to everyone beats waiting for the small-slice signal |
| extends | Creative Output | Output beats polish when feedback is the fuel |
| extends | Minimum Viable Product | Smallest shippable slice beats endless polish |
| extends | Selling Static Sites | First paid client site before polishing the service brochure |
