What does it mean to be a good product manager in 2018?
For a while now it has no longer been solely about participating in the time-honoured rituals of whatever agile methodology your team happens to use. Nor is it only about creating products your users need.
Lovely Wife announced the other day that she is now an agile worker.
I’ll not lie: my eyebrow involuntarily rose an inch or two. I wasn’t aware such a product development methodology had reached the legal profession.
Early on in my blog, I wrote one of my most popular posts – 4 key ways to spot a successful product manager – about measuring the performance of product managers. The problem is that a lot – and I mean a huge amount – has changed in product management, and my own approach, since I wrote it.
I found myself describing to Martin Eriksson at his recent book launch some work I did at the UK’s Ministry of Justice on measuring product manager performance. So here’s an update to my original article from a real-life case study.
In addition to the ‘soft’ skills I discussed in the last post, a good product manager also needs ‘hard’ skills (product management techniques).
Read on for my list of the 16 most important technical skills a product manager needs.
(There is a point to these two listicles. It’s coming next post.)
I’m often asked what skills a product manager needs. In my view at least, a good product manager needs both ‘soft’ skills (emotional intelligence) and ‘hard’ skills (product management techniques).
Read on for my list of the 12 most important soft skills a product manager needs.
I bet you’ve found yourself in this situation. You’re trying to get your head around the main user problem your new product is going to solve. The thing is, for every question you try to answer, several more questions arise.
For a glitzy song contest, Eurovision has a lot to answer for.
There is a product management angle to this post. Eventually.
I enjoy being a product manager, although on some days I question whether my level of patience is suited to my chosen career. When working somewhere, I often spot opportunities for them to improve, gain a competitive advantage or reduce wasted effort, then become terribly frustrated when bureaucracy and organisational inertia prevent me from moving quickly enough to exploit them. If this feels familiar, read on.
During a class I was giving the other day over at Edtech, we were looking at possible risks that might affect the theoretical products we were discussing. One team of students was hotly debating the relative importance of one of the risks. They couldn’t agree how much of a problem it would be if they discovered that something similar already existed on the market. I call this The Coffee Shop Problem.
I’m writing about one hundred things I’ve learned as a product manager.
For a variety of reasons, in the last few months I’ve fallen out of the habit of writing regularly. And just as I fool myself that having a gym membership is the same as exercising regularly, so also I need to remind myself that blogs don’t write themselves.
Over the last few months I’ve been working with another set of great, challenging and occasionally misguided clients. They’ve been pleased with the results I’d helped them to achieve, and I’ve been able to learn a huge amount from working with them.
In turn, this has given me plenty to write about on the topics of product management, user research and changing the way organisations work and behave, so I’ll be sharing this with you bit by bit over the next few articles.
But as a writing warm-up – I don’t want my writing muscle to cramp – here are a few of my procrastination-beating tips for beating writer’s block.