After my first couple of months in the realm of QA, I noticed something rather interesting. Some of my colleagues, who did the same work I did for the same pay, started describing themselves with different verbiage. Specifically, they changed their titles on email signatures and LinkedIn. Before I knew it, we were all calling ourselves Quality Assurance Engineers, Test Engineers, Test Strategy Coordinators, and so on.
Didn’t change the fact that we were QA. Certainly didn’t change how we were viewed by PMO or development.
That’s what I think of when I read articles like this very well written piece by Startup Blender on the difference between a Minimum Viable Product versus Minimum Delightful Product. Regardless of whatever differences you see, if the first iteration of a product does not delight stakeholders or the customer, then it’s not viable in the least.
I wholeheartedly understand and support the sentiment the writer aspires to. Viable is boring and utilitarian, which is not what a designer or big thinker wants to put in front of users. He wants to wow them from day one, and if that isn’t achieved you must start over.
Just be careful that you don’t walk down a rabbit’s hole of making sure the title of your idea is perfect. You might make your next pitch session a little peppier than normal, but those you really want to impress won’t be fooled.
You delight your users by finding what is described as the “product gestalt”. This description of the perfect union of design, UX, and ideas was the best part of this post. As that famous person said that time, “form and function are one.”
If you need to change one word of MVP to achieve that, go for it. Go on with your bad self delighting users. Just don’t try and convince me that’s not what viable is supposed to mean. We all know better.Read more "Blog Post: Does ‘Delight’ Change The Meaning of MVP?"