Rapid Shipping Framework

A framework for driving rapid execution in software development, centered around aggressive shipping timelines and social pressure.

Core Philosophy of Rapid Execution

• Focus on immediate shipping over perfect execution
• Use social pressure to enforce rapid deployment
• Avoid sideways movement that feels like progress but isn't
• Prioritize customer-facing deployments over local development

The "Tonight-Only" Shipping Method

• Default answer to any timeline question must be "tonight"
• Success metrics:
  • 30% of projects ship nothing
  • 70% ship a rough version
  • 10-20% ship completed version
• Creates cultural expectation of immediate execution
• Forces rapid decision making and deployment

"Local Host Shaming" Technique

• If developer spends >1 day on localhost:
  • Stop using their name
  • Refer to them only as "localhost"
  • Continue until they ship to production
• Purpose:
  • Enforce values through social pressure
  • Create urgency around shipping
  • Prevent extended local development

Why This Works

• Addresses hard, embarrassing tasks first
• Prevents analysis paralysis
• Forces focus on customer-facing results
• Creates clear accountability
• Uses social dynamics to drive behavior

Implementation Guidelines

• Must be brutal about enforcement
• Focus only on two key questions:
  • Do people want this?
  • Can we get customers repeatedly?
• Actively avoid all other activities
• Maintain consistent pressure to ship