The Real Reasons Why Most Product Teams Struggle to Delight Users
Posted by ToddLankford@reddit | programming | View on Reddit | 8 comments
Posted by ToddLankford@reddit | programming | View on Reddit | 8 comments
javyQuin@reddit
Ask yourself “what about my product sucks the most”. Once you answer that in an honest way that should dictate your product roadmap. I’ve worked at places that will either not answer that question honestly or make excuses for why we couldn’t improve the sucky features. I’ve also worked at places that are really good about improving their product. The difference between the two in terms of business success is orders of magnitude
ToddLankford@reddit (OP)
Nice prompt to reflect on improving the product
vinciblechunk@reddit
We've been over this before, it's the design of our backend
Orbs@reddit
Is it because delight is a meaningless term that cannot be measured?
(This is a reasonable article about making sure you actually solve user problems but the word Delight instantly makes my brain turn off)
ModestJicama@reddit
At my old job I remember they switched to using "Minimum Delightful Product" instead of "Minimum Viable Product" and cycle time increased because product people went way overboard with the difference between MVP and MDP so they switched back 😂
sweating_teflon@reddit
In the food industry: Minimal Edible Product. In aerospace: Minimum Flyable Product. In television: Minimum Watchable Product.
Orbs@reddit
Ugh yeah I was at a company that tried "Minimum Lovable Product" with similar results
unua_nomo@reddit
This is basically just the original idea behind agile, just like... work on stuff your customer actually wants. Revolutionary.