3 ms·
As a former PM, I kinda hate posts like this, because they imply that there's a single way to deal with engineers. It turns out, though, that engineers are huma
by awillen 5y ago
As a former PM, I kinda hate posts like this, because they imply that there's a single way to deal with engineers. It turns out, though, that engineers are human beings and thus are each very different! They have unique preferences and desires, and the best way to deal with them (which also happens to be the best way to deal with non-engineers) is to learn about those preferences and respect them.
You can see the problem in the fact that two back to back section headings are "Don’t isolate them from the outside world" and "Respect their time". Respecting engineers' time often means leaving them alone to work. This can also be construed as isolating them from the outside world, because it means you're not pulling them into meetings and spending lots of time giving them background.
Some engineers really want a lot of context on what they're doing. They'd love to join you in meetings with customers and other stakeholders so they can get a feel for the bigger picture. As a PM, I love this - engineers who get the big picture are incredibly valuable in providing feedback beyond the nitty-gritty.
On the other hand, many engineers loathe customer meetings! They want the PM to do the research and provide a clear spec on what needs to be built, so they can focus on the engineering side of things. If you put them into a bunch of meetings so they can get broader context, they will be unhappy because this is not what they want.
So yeah - deal with engineers like you'd deal with other people. Respect them, get to know them, and interact with them in a way that enables everyone to get their jobs done in the most efficient, pleasant way possible. I know that doesn't make for much of an article, but I think it's much better advice than what's presented here.
- rramadass 5y agoYou have hit the Nail right on the Head! >deal with engineers like you'd deal with other people. Respect them, get to know them, and interact with them in a way that enables everyone to get their jobs done in the most efficient, pleasant way possible That is all there is. I always say "People are NOT Resources". Each of them is unique and it is upto you to understand their wants and then craft a plan accordingly. I am coming to the conclusion that a PM's job needs; 1) Read up/Train on a little bit of Behavioural Psychology/Applied Behaviour Analysis/Organizational Politics/Communication Skills so you have an idea of how to read, manage and interact with people. 2) People, Time and Resources(inanimate things) are to be managed separately. The latter two always take second place to the first. 3) Every known process is just a template and thus needs to be customized to the situation at hand. Nothing is written in stone. 4) For every person on your Team create a "Spider Graph" identifying and ranking any measurable traits that you are interested in managing. 5) Delegate and give them their Autonomy for execution but within well understood and agreed upon parameters/deliverables. 6) Don't be a "paper-pusher" but understand the problem domain well so that you can have intelligent conversations with your Engineers. This is the only way to earn their respect and have them listen to you. 7) Practice "brinkmanship" when it comes to defending your Team members.