Master the art of technical influence as a Product Manager 👨‍🎓

It is expected that PMs won’t be doing coding in order to collaborate with fellow developers however they need to associate with developers & understand the engineering trade-offs for your product roadmap. It’s also imperative to get buy-in from developers for the items in your roadmap as well.

In order to achieve this seamlessly, it’s crucial to develop technical influence while working with the technology team.

Let’s understand the key steps which can help to build technical influence.

1. Enquire about technical operations, workflows & processes 🔁

Technical operations, workflows & processes vary from organization to organization so it is important to first understand the same for your product. You can also ask the developers about the product infrastructure, sister design, programming languages used, and technical architecture.

2. Be succinct & clear with your goals around the product 🎯

It’s crucial that while you are partnering with developers, you are able to articulate and present your product goals in a concise and clear manner. Engineering doesn’t appreciate the ambiguity and it’s your role as a PM to convert those ambiguities into a well-defined step that makes it easy for developers to chew upon. Always try to support your hypothesis with data points & predict the impact of the goals you are trying to achieve. It’s vital to involve them in your brainstorming sessions and eventually they will feel empowered and valued in this process.

3. Become a champion for developers in the organization 🏆

The role of PMs isn’t limited to just assigning P0 to developers. PMs need to first build a healthy & personal relationship with the developers so that they are able to grow abundant trust and comfort with you in terms of sharing the challenges they are facing. This can help to preempt any changes in the product which can help to achieve the overall goals successfully. This ensures that you are the developer’s advocate across the organization & always proactively champion their thoughts & ideas.

Building technical influence requires ample effort & time but it serves favorably in the long run.

Thanks for reading!
If you like 💚 my content, follow me on Twitter for more such resources & tools about Product Management.
Drop a 👋 on or connect with me on Linkedin →

Do check out exclusive Product Management resources 👇

Limited period ⏰ sale is going on right now.
Get all 3 resources at just $8 🤑.
Grab your copy now 🙌 →




Senior Product Manager @AngelOne, ex-@Flipkart, @Cleartrip. Interests: Product, Technology, Strategy, Startups, Fintech & E-commerce!

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Tips for Product Managers looking to ship features on time

Ultimate list of 100+ Product Management tools 🛠

Key App Metric with BigQuery Part 2: Power User Curve

Don’t start with the MVP

A red sign on the street that says “wrong way”

Mental Models, Product Success and You

When Language Makes a Difference: 7 Agile Coaches Key Differentiations

A Product Manager’s First Reference

How PMs can measure the success of their Product?

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Rohit Verma

Rohit Verma

Senior Product Manager @AngelOne, ex-@Flipkart, @Cleartrip. Interests: Product, Technology, Strategy, Startups, Fintech & E-commerce!

More from Medium

You have to ship X features, which requires 15 Engineers but you only have 8, what would you do?

Slack communities that every Product Manager must join

Distilling the role of a Product Manager

“Continuous Discovery Habits” Book Summary for Product Teams