Classifying Market Problems

amphicar

Theodore Levitt may have developed the whole product model to help companies compete more effectively with their products.  We wrote about the whole product game based on Mr. Levitt’s work.  Recently, I’ve been using a variant of this model as a way to view a product and upcoming roadmap items.  It is a powerful way to share a perspective on your product with the rest of the team, and frame conversations about where best to invest.

Continue reading

Cargo Cult Requirements

Photo of Melanesians with bamboo plane

Is your team focusing on the mechanics of creating good software, without understanding the connections from your efforts to your goals? Are you primarily focused on the structure of use cases, the syntax of user stories, and the cardinality of your domain diagrams? All of these things are important to effective communication – but if this is your primary focus, you may be in a cargo-cult environment.

Continue reading

Why Do Products Fail? – Ignoring Context

Wrapping up the your product failed because you didn’t enable your users to realize value branch of the root causes of product failure, is this article on the context in which your user is using your product.  If you ignore your user’s context, they won’t be able to realize the value you provide – or won’t be interested in solving those particular problems at that particular time.

Continue reading

Why Do Products Fail? – Forgetting that Users Learn

Next up in the series on the root causes of product failure – products that fail because you have ignored the user’s level of experience.  The first time someone uses your product, they don’t know anything about it.  Did you design your interfaces for new users?  After they’ve used it for a while, they get pretty good at using it.  How much do you think they like being forced to take baby steps through a guided wizard now?

Continue reading