Comments on: Eliminate Features to Differentiate your Product https://www.romanpichler.com/blog/eliminate-features/ Expert Training & Consulting in Agile Product Management Tue, 21 Dec 2021 22:37:18 +0000 hourly 1 https://wordpress.org/?v=6.7.1 By: Roman Pichler https://www.romanpichler.com/blog/eliminate-features/#comment-2604 Mon, 27 Apr 2015 09:54:54 +0000 http://www.romanpichler.com/?p=9146#comment-2604 In reply to Roger L. Cauvin.

Thanks for your comment, Roger. I fully agree that selecting and prioritising the problems a product should address or the benefits it should provide is crucial. I find it helpful to distinguish between the primary problem and secondary ones, as suggested by Clayton Christensen in his jobs-to-be-done theory.

]]> By: Roger L. Cauvin https://www.romanpichler.com/blog/eliminate-features/#comment-2603 Mon, 27 Apr 2015 09:50:38 +0000 http://www.romanpichler.com/?p=9146#comment-2603 I take things a step further and apply the grid to the problems the product should solve. Solving a non-cohesive set of problems is almost as bad as including too many features.

All decisions to include features or solve problems should be viewed through the lens of a single, overarching value proposition.

]]>