Sometimes I wonder whether someone's split-testing their article, because it seems like you're getting a completely different one.
Right before the 'significant impact' sentence is this one:
One of the first things I did was steer the company
in the right direction from a strategy perspective.
I constantly butted head with one of the founders
but my strategies were clearly impacting the revenue
numbers. For example one of the tactics doubled the
weekly revenue.
Seems pretty day-to-day to me. He's apparently in there as some sort of product manager / biz dev guy, but somehow you have the impression that he's a wet behind the ears engineer.
How should a PM/biz-dev guy handle this type of situation?
I'm curious how much do PMs really do push backs and shielding for the development teams and to what extent are they just taking marching orders from upper management.
It depends on the specific company and politics, but I'm guessing for me personally, if I was a PM, I put in the work to get into lowest rung of management. I make more than a engineer but not in a worker-bee role anymore so I'm pretty expendable. So I'm going to look out for my own self preservation first with upper management. Some engineers have combative attitudes and analytical view on creating business value without taking into consideration of expending political capital to get things down and massaging people's egos. Sounds like this guy is approaching a social game with still a programmer's mentality. PMs, please feel free to chime in how you pick your battles and push back with upper management correctly.
I'll offer my take on it, as a recovering software engineer who moved over to the product side. The first thing you have to learn is that nobody works for you--you can't tell anyone what to do. You have to persuade and convince. Both upward to your bosses and across to engineering, marketing, user experience, finance, QA, customer support, ops, everyone. You've got to get them to buy them into taking the product in the direction it needs to go. You have to be the buffer. You've got to shield your team from all the "churn" and "swirl" and indecision coming down from the execs, whilst shielding the execs from the day-to-day chaos, the bug firehose, and software design debates that are always part of major development projects.
And yea, you're seen as much more expendable than the engineers since you're not writing the actual code, so you have to play a little politics (the better the company, the less of that game you have to play). When a bad idea comes down from up top, you have to push back. You can't put all the CEO's product ideas on the fast track, as tempting as it is. Ever since that goddamned Steve Jobs book came out, every senior exec in the Valley thinks they're some kind of product visionary. You've got to have the judgment to marginalize and stall the bad ideas and go all-in on the good ideas--work with engineering to make them awesome.
But once in a while, something's gonna get rammed into the product over your objection, and it's going to suck. You just have to deal with it. Make sure when it's released it "sucks less". Make sure there are analytics all over it so in a few weeks/months you can point to hard numbers showing how much it sucks, and hopefully the product can pivot away from it.
I agree with you that PMs have to use charisma and influence to get things done, but I completely and utterly disagree that they are more "expendable." A good, certified, educated and experienced PM is worth a dozen engineers. You can find engineering talent almost anywhere - but good managers are a diamond in the rough.
I've been a PM for about a half decade now, and was previously a software engineer for some big name companies. I'm telling you, PMs, if they know what they are doing and are educated properly, are worth their weight in gold - because writing code can be outsourced, management can't.
Maybe it's different in Silicon Valley (which would explain a lot of the risk-taking, lax attitudes and failure rates of startups), but the rest of the country is the opposite of what you describe as the "expendable" PM.
Wow, it's so refreshing for me to read your post, thank you!
Unfortunately in my experience (on both ENG and QA sides), PMs only serve to try and fuck you over or overload your "plate" in one of dozens delicious ways. I'm desperately trying to avoid having my experience color the rest of my perceptions (and interactions) with PM, but it's a losing battle. It's becoming all the more easier to just say "fuck PMs" and be done with it :(
Right before the 'significant impact' sentence is this one:
Seems pretty day-to-day to me. He's apparently in there as some sort of product manager / biz dev guy, but somehow you have the impression that he's a wet behind the ears engineer.