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 […]
Business Analysis / Ishikawa Diagram / Prioritization / Product Management / Requirements / Requirements gathering / Requirements Models
Posted on:
Why Do Products Fail? – Picking the Wrong User Goals
Continuing the series on root causes of product failure, this article looks at the impact of focusing on the wrong user goals. Even if you have picked the right users, you may have picked the wrong goals – creating a product your customers don’t really need, or solving problems that […]
Business Analysis / Ishikawa Diagram / Prioritization / Product Management / Requirements / Requirements Models
Posted on:
Why Do Products Fail? – Picking the Wrong Users
Exploring the reasons that a product might fail in the market is a useful way to triage and assess what you need to do to prevent the failure of your product. Instead of taking the “do these things” approach as a prescriptive recipe for product managers, I’m approaching the exact […]
Prioritization / Product Management / Requirements / Requirements gathering
Posted on:
Important Problems – Comparing Products Part 4
If you understand the important market problems, you can make a good product. If you understand how important each problem is, for each group of customers, you can make a great product. If you’re new to this series, go back and start at the first article, we’ll wait for you […]
Agile / Business Analysis / Prioritization / Process Improvement / Product Management / Project Management / Requirements / ROI / Software development / User Stories
Posted on:
Agile Estimation, Prediction, and Commitment
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 […]
Business Analysis / Kano Analysis / Prioritization / Product Management / Requirements / Requirements Models
Posted on:
Don’t Prioritize Features!
Estimating the “value” of features is a waste of time. I was in a JAD session once where people argued about if the annoying beeping (audible on the conference line) was a smoke alarm or a fire alarm. Yes, you can get to an answer, but so what?! The important […]
Agile / Business Analysis / Interaction design / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / Usability / Use Cases / UX
Posted on:
Use Cases for Iterative Development
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 / Ishikawa Diagram / Prioritization / Product Management / Requirements / Requirements Models / Software development / Software requirements specification / User Stories
Posted on:
Atomic Requirements
Each requirement you write represents a single market need, that you either satisfy or fail to satisfy. A well written requirement is independently deliverable and represents an incremental increase in the value of your software. That is the definition of an atomic requirement. Read on to see why atomic requirements […]
Administrivia / Agile / Business Analysis / Prioritization / Product Management / Project Management / Requirements / Requirements gathering / Requirements Models / ROI / Software development / Use Cases
Posted on:
Most Engaging Articles of 2009
Engagement – that’s what this whole product management blogging thing is about. Check out what Tyner Blain readers found to be the most engaging articles in 2009.