Product management roles offer a viable career path for business analysts. This path is especially relevant for business analysts who currently work on custom software development projects in their current role. Here are the stories of four people who shifted from business analysis to product management.
Sometimes the outcome you're asked to deliver is a reduction in staff. This post explores how to deal with mandated outcomes such as reducing staff.
I often suggest that you focus on outcomes over output, but never explained why. Here's a look at the benefits and pitfalls of a focus on outcomes.
A collection of techniques you can use to make sure you're solving the real problem: pop the why stack, socratic questioning, and setting outcomes.
Design thinking is an approach to solving problems that is human centered, cross functional, iterative, creative, and practical; and you may already do it.
When you develop products, you have to interact with customers, users, and stakeholders. To be effective, you need to understand the different perspectives.
There are differences between a minimum viable product (MVP) and minimum marketable feature (MMF), but in order to understand the difference, you need to understand the concepts, not just know their names. In this excerpt from Beyond Requirements, I describe both concepts, how they differ, and where they can be useful for product people.
4 considerations when conducting interviews about an internal product. Inspired by Alan Klement's book about Jobs to be Done, When Coffee and Kale Compete.
The Five Whys Technique (also known as “Popping the Why Stack”) has long been suggested as a way to get to the ultimate reason for a project. But when you ask why repeatedly, you run the risk of looking quite pedantic and annoying stakeholders. With that in mind, I thought I’d provide a list of …