Product development: Perfection vs. minimalism

The perfection pitfall

Minimum viable product

Key questions to ask

  1. What is the problem we’re trying to solve? What is the most basic nature of the problem we’re sorting out for the user?
  2. Who are the people using the application?
  1. Is this item/function solving the core user’s problem?
  2. How can we simplify it and still solve the core problem?
  3. Isn’t there any backlog item more important, without which the app does not solve the core problem and is therefore meaningless?

Mailing example

On the right way to good quality product

--

--

--

Tech blog from developers, designers, and other experts working on mobile apps at Cleverlance. https://www.mobileit.cz/

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Building strategic partnership with engineering tech leads

How to manage product experiments in Confluence Cloud

Top Strategies to Prioritize Features for Innovation Teams

Top 5 Habits which can make you Kickass Product Manager !!

Mario Di Nucci — The 5 What

Managing ideas at scale

A an artistic message that reads ‘turn ideas into reality’

Why this brainy product task requires a HEART?

Heart with a brain depicting the importance of a heart framework for Product managers and UX designers to mseasure success

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
mobile.IT

mobile.IT

Tech blog from developers, designers, and other experts working on mobile apps at Cleverlance. https://www.mobileit.cz/

More from Medium

Why did BDD came back to the scenario again with Agile?

Scrum smells, pt. 8: Scrum has too many meetings

Why Do We Love and Hate Agile at the same time?

How to get more from Scrum (and why testers make perfect Scrum Masters)