Jock Busuttil’s (@jockbu) series “100 Things I’ve Learned” is what he’s learned about product management over the years – usually the hard way.
If you were to inherit a portfolio of ninety legacy products, some of which hadn’t been updated in years, what would you decide to do with them? And how would you prioritise which ones to work on? This article explains how.
If you find yourself attempting to win over the rest of your organisation to a more user-centric, evidence-led way of working, remember how jarring change can be and actively work to soften the impact for them.
I’ve never enjoyed job interviews. The inane questions annoy me most.
What do you need to learn if you want to qualify for a job as a product manager?
If one were to heft a half-brick down Old Street in London, there would be high probability of hitting someone currently engaged in building a minimum viable product (MVP) of some sort or another. There’s also almost as high a probability that they’re doing it wrong. Allow me to explain.
For those of us who are artistically challenged (read: crap at drawing), it can be daunting to contemplate the use of pictures over text to make a point. I’m a perfect case in point.
A post in which Jock starts to think he’s Gwyneth Paltrow.
You can learn all the theory you like, but at some point you just have to stop thinking about what the answer might be and dive in to find out. Product managers learn by doing.
This is the story of why I’m going to be disappointed with 99% of all airlines for the foreseeable future. A guide to the Kano model.
Curating the product roadmap is one of the most typical responsibilities of a product manager. But have you ever thought about why you bother with them in the first place and how you could make them more effective?
