E2: MVP-First Iterative Delivery
Large feature releases delay feedback, increase risk of building unwanted functionality, and make course correction expensive. Teams spend months building features customers don't actually need.
MVP releases validate assumptions early. Telemetry provides objective usage data. Customer feedback guides subsequent iterations. Small bets with fast feedback loops outperform big bets with delayed validation.
Principle
- Feature proposals SHOULD start with Minimum Viable Product (MVP) scope, proactively instrument telemetry, gather customer feedback, and iterate multiple times rather than attempting comprehensive features in a single release.
MVP focuses on core value proposition to validate primary hypothesis, critical path only for fastest time to learning, basic error handling that is usable but not polished, and telemetry hooks to measure what matters. Edge cases, performance optimization, advanced features, and perfect UI/UX should be deferred until the direction is confirmed through feedback.