Too Long; Didn't Read
If you had to use 1 word to sum up what PMs do, most PMs I know would likely pick “Product Roadmap”. (Okay that’s technically 2, but you get the drift.) Product Roadmap is so important, not because it’s the holy grail of what we do as PMs, but rather it embodies all the blood, sweat, and tears of what makes a product, the finished product. In my post today, I won’t attempt to show you exactly how to make the <em>perfect </em>Product Roadmap (mainly because I don’t believe such a thing exists), but rather the thought framework that I typically use when I’m creating a Product Roadmap. To give some color to the framework below, I’m going to pretend that we got the mandate to go build ‘HR software for candidate tracking and better communication between candidates and the firm as the candidate goes from the initial sourcing stage to when the candidate finally accepts the offer”.