About two months ago I started writing Product Guy series, reflecting what I have learned over the years about making products and/or software.
I may or may not return to this topic (hence the Vol 1 in the title), but now it is time to summarize.
I didn’t have much of a master plan on the topic of the posts. I just wrote whatever was topical on my mind, either through my own reflection or through the commentary I received via multiple channels, public and private.
Now that I look back, the posts, however, do give an idea of the broad spectrum of issues Product Guy needs to deal with.
Product Guy needs to know the teachings of the wise Greek men, find his inner hipster and hone the skills of the method acting to the the Jesse Eisenberg level of markzuckerberg-ness.
And that’s just the planning part of the job. Then the actual work starts. Being able to focus on the right things, requires having an air traffic controller -grade real-time scoreboard and a clear understanding how to move mountains. And all this must be done iteratively, which requires the wisdom to separate the signal from the noise, diligent review practices, continuous, honest assessment of own and competitor products, and unavoidably some – or a lot – of fire-fighting.
So a lot of stuff. I used a lot of Hollywood metaphors, not only because I love movies, but because I thought the analogies would capture how captivating the journey can be.
Sometimes the project is a drama. Sometimes it’s a tragedy that may border becoming a comedy. But if you put your heart into it, there’s one guarantee you can make to your team members: “It will not be boring.”
I hope you enjoyed reading.
p.s. Now Real Box Score blog will go on extended Easter break. Hence, next posts – at least any longer than 140 characters – are not to be expected before mid-April or so.