IdeasMine
I
Global·57d ago
Startup Guides
Free

What Features to Cut from V1

What you'll learn The 12 features founders always add to V1 that they should always cut, and the 3 features that actually matter. Why it matters Feature bloat is the #1 reason V1s take 6 months instead of 4 weeks. Cutting ruthlessly is the founder skill. The playbook 1) Cut: Onboarding tour, dark mode, multi-language, admin panel, forgot-password flow (use Google OAuth), notifications, referral system, gamification, customisation settings, in-app analytics, chatbot help, mobile app (do web first). 2) Keep: The ONE core action, one way to pay (if paid), one way to sign up (Google OAuth). 3) Test: Can a user complete the core action in <3 taps/clicks from landing? If not, cut more. 4) Rule of thumb: If a feature would take >3 days to build and isn't the core action, defer to v2. 5) The 'Sunday test': Would a user come back on Sunday to use this? If not, you don't need most of what you're building. Common mistakes Building settings pages nobody uses. Adding social login providers you don't need (LinkedIn, Facebook, Twitter, GitHub — pick ONE). Perfecting empty states before you have any users. Next action List your V1 feature list. Draw a line at #3. Everything below the line is V2.
0

Discussion (0)

Sign in to join the discussion.
No comments yet — be the first.