Interaction design / Interface Design / Ishikawa Diagram / Kano Analysis / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / UX

Why Do Products Fail? – Forgetting that Users Learn

Posted on:

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 […]

Agile / Business Analysis / Prioritization / Process Improvement / Product Management / Project Management / Requirements / ROI / Software development / User Stories

Agile Estimation, Prediction, and Commitment

Posted on:

Your boss wants a commitment. You want to offer a prediction. Agile, you say, only allows you to estimate and predict – not to commit. “Horse-hockey!” your boss exclaims, “I want one throat to choke, and it will be yours if you don’t make a commitment and meet it.” There’s […]

Agile / Business Analysis / Interaction design / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / Usability / Use Cases / UX

Use Cases for Iterative Development

Posted on:

Almost everything I’ve read about use cases focuses on describing what needs to be added to your product. Agile development says “get it working first, make it better second.” That means changing the way the software enables a user to do something they can already do. How do you manage […]