The Maslow Pyramid of Product Development

Product development routinely involves prioritization of features. The line between the Minimum Viable Product (MVP or how should a product perform, look, cost etc.) and Time-To-Market (TTM or when can we put the 1st version on the market, then the 2nd  etc.) is always subjected to management decision.

Still,  my experience is that there are some guidelines that should be followed in order to give the customer the best experience possible, with every product version.

I demonstrate this to my clients with what I like to call the Maslow Pyramid of Product development. Ask any psychologist or ancient Egyptian: the pyramids help you remember the basics...

So, you start from essentials at the bottom and work your way up to the should-haves at the top, and like in the other pyramids, you move the the higher level only when the current one is stable:

Reliability mean that the product works when the customer needs it to work. you press the "ON" button and the machine turns on and works, and it doesn't break down just like that. Safety also is part of this level: you literarily don't want your customer to get hurt...

Functionality means that the product is actually doing what it is meant to do. if it is a 3D printer, it prints. You get parts out of it.

Performance Quality means that the product is delivering the advertised outcome. I.e: if it is a manufacturing machine, it delivers the advertised accuracy.

User Friendliness is allowing as little operator training as possible. Make the Product as seamless to operate as possible.

Data & Connectivity corresponds to the modern world. for machinery, Industry4.0 features like Condition Monitoring and Remote Access should be addressed, as well as Cybersecurity.

My recommendation to my clients is to widen the pyramids when moving to the next generations of then product, adding more and more features at the top while ensuring good foundations.