As you may be aware, I’ve written a book called The Practitioner’s Guide To Product Management. It’s really a collection of stories from my own experience and others’ about how NOT to manage products. So if you just follow my Golden Rule (to ignore or do the opposite of everything I suggest), then you’ll be fine. Probably.

Last time I published an article explaining why I thought roadmaps were a little like DVD box sets. DonorDrive product manager Kasey Marcum (@kaseymarcum) asked in the comments:

“Always enjoy your posts, Jock! I really love the high level idea of this. What does this actually look like in the wild?”

Imagine your roadmap and sprints being as engaging as a hit movie – just think how much easier they’d be to “sell” to your stakeholders and customers! Let’s see how you can do this.

This week, we’ve been looking at two different lifecycles: the product lifecycle and the development lifecycle – cycles within cycles!

One of the challenges of being a product manager is that it’s sometimes difficult to read between the lines of what your (potential) customers want in order to determine what they actually need. This article explains how to identify and differentiate between needs, features and benefits.