Classifying Market Problems

Theodore Levitt may have developed the¬†whole product model to help companies compete more effectively with their products. ¬†We wrote about the¬†whole product game based on Mr. Levitt’s work. ¬†Recently, I’ve been using a variant of this model as a way to view a product and upcoming roadmap items. ¬†It is a powerful way to share a perspective on your product with the rest of the team, and frame conversations about where best to invest.

Read the rest of the article …

Agile Cadabra

Agile is not magical. Changing from a waterfall process to an agile process changes how your team works, and helps eliminate inefficiencies. Adopting an agile process does not let you magically have a more successful product. What makes agile powerful is also makes it dangerous.

Read the rest of the article …

How is SaaS Changing Product Management – A Research Thesis

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.

Read the rest of the article …

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.

Read the rest of the article …

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.

Read the rest of the article …