It's very often that we, the developers, make fun of how useless product managers (PM) are. They aren't contributing to the feature actually, they constantly only care about the deadline, and they can't be held responsible while actually pointing fingers at you.

Well, if your PMs are doing just bare minimum then yeah they will be pretty unhelpful. However, I've worked with a good PM and it's changed my view on how important product managers are and how do you keep a good relationship with them.

the main functions of the product managers are:

1.) managing expectations and request of high level stack holders.

This is often about having meetings with all levels of hierarchy, including you the developer, about what is the current plan, what are the potential ideas, and whether the projects are still on track or at risk of delay. This also means that PMs are constantly in communication with high level employees like directors, vice presidents, and even the CEOs about the latest status update; it's very unpleasant when the meeting isn't a simple "all is fine" and you definitely don't want to be the one delivering that news.

2.) filtering and prioritizing tasks.

This is a collaboration with the engineering managers and leads as well. The difference is that product managers have a wider cast of net and have to be aware of what other teams are doing, what general company direction is going towards and whether the development is matching that direction.

It also means that PMs sometimes have to deny requests from the high level employees; do you really want to be the one saying no to the CEO?

3.) hold business knowledge about the team, the bigger organization, and the company in general.

This is where the PMs really shine and it's why PMs are very valuable to the company too.

if you don't understand how important this is, please see my recent article about it

Now here is the fun part, how do you manage your relationship with the PMs and how do you best leverage their role in the company.

1.) communication is key.

If you haven't noticed yet, all the PMs do are basically communicating. If you are the one who isn't replying to slack messages or giving them regular updates, you will be a pain to work with for them.

this is hard especially in the world of hybrid/remote world that we are in today and I'll have an article about this too!

2.) Be reliable and the one they can go to.

PMs are super well aware that they can't actually give any solutions in a tech company. So if you want your PMs to like you, have a firm grasp on the features you are responsible for and more. If you are the one they can turn to when they have a question or when things go south, they'll definitely like you a lot better.

Now this means more responsibilities for you, and some people hold the philosophy that you shouldn't do more than what you are paid for. However remember that PMs are always communicating? I am willing to bet my life that they talk to your managers and all chains above more than you ever will. They won't be afraid to use your name as reason why they can't communicate properly and soon your head could be on the guillotine :)

Of course the opposite side is that if you are reliable, everyone will know you are a key player and your next promotion will be easier; also remember no matter how hard you advocate for yourself, it's always going to mean less than how others advocate on your behalf.

3.) keep an attitude that they are just trying to do what's the best for the team.

conflict is absolutely inevitable with your PM. It can be that they are asking you too many questions while deadline is looming. Maybe they asked you for some feature that straight up doesn't make sense. Whatever it may be, just keep in mind that their job is to make sure the company is going in the right direction and your team is too. They aren't trying to sabotage your job or anything and in fact if the team isn't being perceived as valuable it is a failure on their part (unless your feature keeps triggering production alerts of course ;D).

It'll be hard at times, but keeping in mind that they are trying to do the best by the team will help with your temper in checked. After all, you aren't the one having to answer to the CEO one hour later!!

4.) show an interest in the project and the discussion around it

everyone loves to be asked about their area expertise. For PMs, it is about the projects they manage and the talks leading up to it, including what was tried in the past and what business knowledge is around it. Showing more interest along will make the PM treat you more than just a jira bot, which will be great for your mental well-being too honestly.

This will also help you understand why you are doing this project to start with and whether there are suggestions you can offer that also fit the overall goal. This will be invaluable too when something unexpected happens, a lot, and alternatives are easier for you to do but just need to be signed off. In this way, you also start exhibiting behaviors beyond just a developer (senior and + levels).

If you like this article, please give a reaction or anything. Feel free to subscribe to me as I will be writing these higher level career articles for at least this week and more.

Also I was just laid off :) ... so if your team is hiring remote please refer me!!!