Paddy Barrett in Ireland is preparing his Master’s thesis on Product Management and would like to interview (USA) state-side product managers for his primary research. It would be awesome if you could help him, and help us all.
Agile / Communication / Prioritization / Product Management / Product Strategy / Requirements gathering / Software development
Posted on:
Whole Product Game
How can Theodore Levitt’s classic Whole Product approach help with defining a product roadmap? I’ve been revisiting his concepts and their use recently, thinking about how to revise them for some exercises I’ve been doing with product teams.
Uncategorized
Posted on:
Why Write Requirements
There is a lot of advice out there for how to write requirements. There is not as much discussion about why to write requirements. Spend some time thinking about why you write requirements before you make decisions about how to write your requirements.
Uncategorized
Posted on:
Is Agile Really Cheaper?
There are several ways to answer the question “is agile cheaper than waterfall?” Here are two of my favorites: “It depends. Agile done well is cheaper, as long as you measure correctly.” “You’re asking the wrong question. The right question is: is agile better?”
Uncategorized
Posted on:
Cargo Cult Requirements
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 […]
Interface Design / Product Management / Uncategorized / UX
Posted on:
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 […]
Interaction design / Interface Design / Ishikawa Diagram / Kano Analysis / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / UX
Posted on:
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 […]
Agile / Ishikawa Diagram / Kano Analysis / Product Management / Requirements / Requirements Models / Software development / Uncategorized
Posted on:
Why Do Products Fail? – Incomplete Solutions
This article continues the series exploring the root causes of product failure. Even when you target the right users, and identify which of their problems are important to solve, you may still fail to solve the problems sufficiently.
Interaction design / Interviews / Prioritization / Product Management / Requirements / Requirements gathering / Uncategorized / UX
Posted on:
20/20 Vision – Innovation Game in Action
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 […]