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

Interaction design / Interviews / Prioritization / Product Management / Requirements / Requirements gathering / Uncategorized / UX

20/20 Vision – Innovation Game in Action

Posted on:

Having an outside-in bias as a product manager is important – you need to understand how your customers (or your customer’s customers) would value capabilities you might build into your product. When running a workshop to collect that information, playing some “serious games” is a great way to get more […]

Agile / Business Analysis / Business Rules / Interaction design / Interface Design / Product Management / Requirements / Requirements gathering / Software development / Uncategorized / UX

A Prototype is Worth a Thousand Lines of Code

Posted on:

A picture is worth a thousand words. A prototype is worth a thousand lines of code. Two key elements of product management – and of agile development are elicitation and feedback. Low fidelity artifacts can significantly improve both. Polished, codified prototypes can create problems that prevent you from getting the […]

Business Analysis / Interaction design / Product Management / UX

Cadence Versus Risk

Posted on:

I’ve been thinking about the software development process. Big, upfront, design and requirements. User research and analysis. Market insights, gained on exploration or over time. Release cadence – how quickly you get, and incorporate, feedback from your customers about your product. How quickly you react to your competitors’ reactions to […]

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

Agile / Business Analysis / Interaction design / Interface Design / Product Management / Requirements / Requirements Models / Software development / Use Cases / User Stories / UX

Design-Free Requirements

Posted on:

Design-Free requirements are important for two reasons, and hard for two other reasons. Design-free requirements are hard because you “know what you want” when you should be documenting “why you want it.” Writing design-free requirements can be hard when you don’t trust your development team to “do the right thing” […]

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

Use Case Management is a Tough Balancing Act

Posted on:

Learning how to write use cases can be tough, but it is simple compared to the balancing act of determining which use cases to write and how to manage the expectations of all the stakeholders that are involved. It can be a difficult balancing act to prioritize use cases to […]