Michael Seibel: How do you decide what to build next?

Core Product Philosophy

• Product development cycles exist primarily to enable the simultaneous exploration of multiple concepts.
• Most proposed features will fail; the objective is to establish a process that identifies failures quickly to isolate working elements for iteration.
• Speed in building Minimum Viable Products (MVPs) is prioritized over individual visionary genius.
• The most effective teams combine technical talent capable of rapid, non-frustrating MVP creation with robust result-measurement systems.

Strategic Divergence

• Long-term vision (10-year outlook) requires imagination.
• Short-term tactical execution (3-month outlook) requires a rapid "build-measure-learn" process to validate moves that are difficult to predict in isolation.

Case Study: Justin TV

• The organization adopted a "swing for home runs only" strategy, attempting to build perfect products.
• Development cycles extended to three months per feature due to perfectionism.
• This approach resulted in a "spiral of death" caused by the inability to pivot quickly based on real-world feedback.

Forward-Looking Implication

• Companies should abandon perfectionism in favor of processes that allow for rapid elimination of ineffective features to sustain momentum.