Why Being Technical as a Product Manager Matters
5 Reasons Why Being Technical Is Essential for a PM
Technology is a Language
Requirements Documentation Required
Technical writing need not necessarily require a lot of jargon and complicated language. The best technical writers create product specs, features, and detailed requirements that can be understood by any developer. The secret to quality specifications is supplying enough detail on what needs to be done, but not on how to do it. However, being technical allows the Product Manager to make decisions on what to write and how detailed the spec needs to be properly communicated. Product Managers with good technical writing skills find that they can speed up the product development process because there are fewer misunderstandings between them and the development team.
Earn the Respect of the Tech Team
For instance, we viewed a job description for a Product Manager that required background/domain knowledge in at least two of the following: identity management, security token services, distributed policy management, and data labeling. If you are unable to understand how important these capabilities are with respect to the overall product function, how can you make quality decisions? The PM serves as a central product information hub for people across the organization. That means the PM needs to be the corporate expert on the competition, market trends, and other factors that might affect products. The more technically savvy a PM is, the more comfortable the PM will be more prepared to properly react to these new technological opportunities and pitfalls.