Explore *Then* Expand *Then* Extract

When should you optimize database performance: before scaling or after bottlenecks appear?

Pre-emptive performance tuning during product exploration wastes resources and slows experimentation. Kent Beck argues for a three-phase approach—explore for product-market fit, expand by fixing bottlenecks as they emerge, then extract maximum profit—where optimization happens only when real usage patterns demand it, not speculative architecture.

Read full essay on Substack ↗

Questions this essay answers

  • Should you build scalable infrastructure before you know if your product will succeed?
  • How do you balance moving fast in exploration with preparing for growth in expansion?
  • When is the right time to pause feature development and fix performance bottlenecks?
← All essays