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.
I remember once starting a product manager job where it took me two hours to establish where my desk was.
On the plus side, I gained a valuable insight into how NOT to manage a new starter. Here are three basic lessons I’ve learned, so that hopefully you won’t be the subject of a similar blog post some time down the line.
There are many questions that a product manager needs to ask to determine the best course of action or to analyse underlying motivations. Of them, I use the following three questions most often:
1. So what?
3. What’s stopping us?
If you want to succeed in global markets with a ‘one size fits all’ approach, you may want to reconsider that strategy. Pay as much attention, if not more, to getting the local details right.
Why write a blog? Up until recently if someone had suggested that I start writing a blog I would most likely have unfurled my ‘To Do’ list with a flourish, watched the unrolling end bounce off the floor and gestured vaguely into the distance. So what’s changed?