The concept of “Product Management” in Software Product Company involves a high volume of interaction with the technical teams. When I say that, the first thing that comes to our minds is “Duh! That’s common sense!”, but quite often we don’t do the “interaction” part in the right way.
Product Managers are the CEOs of their own products, they are responsible for the technology, operations, sales, and accounts - basically the success of their products. Hence building the correct product and getting the development effort in the right direction is imperative, and by doing that, we ensure our contribution towards creating a strong and inspiring technical team in the long run. Some key attributes which makes your role as a “Product Manager” a big hit with the technical folks can be -
When interacting with the developers, think like them! - understand the problems in their perspective and contribute to alternative suggestions in solving the problems as well. If you’ve been interested in reading this article - get rid of the cliché thinking that Product Managers are not coders, they might not code on production environments but there’s no harm in getting your hands dirty to know what your company does better. Believe it or not, I’ve seen product managers with impressive profiles wasting precious development time on conducting unnecessary meetings, struggling to understand the impact of architectural changes because they are technically unaware. The more you know, the more confidence your technical teams have on you. Quoting Naval Ravikant (from one of his talks) - (Founder of several startups including Angelist, Venturehacks and one of the early investors in Twitter, Foursquare, StackOverflow to name a few) –
“Programming in the current generation is the skill of the elite - like reading and writing was in the past”
Sushant can be reached on Twitter @5uku5