I gave a talk recently about how I’ve been using data and analytics to guide my decisions in product management. I’ve edited the transcript a little and split it into bite-size parts for your entertainment. This final bit tells the secret behind meaningful product roadmaps. The previous bit was about the benefits of open and transparent data.
This content was originally published more than five years ago and is archived here for preservation.
More up-to-date content is available on this blog.
Your developers may be happiest when they’re hacking gnarly code, leaving you to get on with engaging with the market, but this doesn’t mean you can ignore their need for context – the ‘why’ of their project.
Over the years, I have spoken to many disgruntled developers over a beer after work. This isn’t entirely coincidental as they tend to dwell in the kind of pubs I enjoy: real ale, good selection of crisps, ability to hear oneself think, minimal bar fights, that kind of thing.
What tends to be a recurring theme of their disgruntlement is that they don’t see the point of their current project. They feel aggrieved that they’re not doing something more interesting instead. And you know what, if it’s your project, it’s your fault. Bad product manager.