Skip to main content
Hit enter to search or ESC to close
Close Search
Stephen Gay
Menu
  • UX
  • Why Always Wins
  • Books
  • Coaching
  • About Me

    How to Build a Minimum Viable Product

    By Stephen GayOctober 8, 2015January 27th, 2016Design, Engagement Design, Innovation
    No Comments

    Summarizing what MVP means:

    1. Build something useful & delightful at every stage (even with limited functionality)
    2. Don’t just implement all the features in a half-assed way, pick a subset of features and really do a great job on them

    Reference to the original post by Henrik Kniberg.

    Making sense of MVP (Minimum Viable Product) – and why I prefer Earliest Testable/Usable/Lovable

     

    mvp

     

    Recent Posts

    • Google Ads Launches Discovery Ads
    • Everything the Buddha Ever Taught in 2 Words
    • “What Skills do UX Hirers Look for in an Applicant” for Interaction Design Foundation
    • Conversational UI: How to walk the talk (SF Design Week 2017)
    • Focus on First Time Use – LinkedIn Group
    • Focus on First Use: Three Frameworks for Designing Onboarding Experiences
    • Classic Advice from Theodore Levitt
    • Chatbot – Penny – Track Your Money, Bills, Saving & Spending
    • The difference between User Experience and Design
    • Intuit’s CEO on Building a Design-Driven Company
    Share
    Share Share Share Pin

    © 2026 Stephen Gay.

    • twitter
    • linkedin
    • google-plus
    Close Menu
    • UX
    • Why Always Wins
    • Books
    • Coaching
    • About Me