3 ms·
Ah yes PMO! The concept that a technical PM can pick up any project in any problem domain is deeply flawed. The amount of time wasted trying to explain things
by DoingIsLearning 3y ago
Ah yes PMO!
The concept that a technical PM can pick up any project in any problem domain is deeply flawed.
The amount of time wasted trying to explain things in manageable chunks is absolutely non-negligible.
- OldGuyInTheClub 3y agoIn my industry, I've found that people with serious technical chops can figure things out and get things done in new areas, even as managers. The problem is with those who get onto the management track double-quick and replace any technical books they have with rah-rah management theories. They seek out management roles, get them, and then depend on others to do the hard thinking and tough trades. It is a point of pride to them to say, "I have people that do that for me" even if they have done Masters or Doctorate level technical work at some point.
- soco 3y agoOn the other hand, there's also the impact you can do higher up is much bigger. To answer on another comment, at this point the ideas don't have to be yours anymore, and it's good so. But your experience and your position will be able to filter them, merge or spread, thus impacting the entire multi-team environment in a positive way (of course, otherwise why are you there at all). And yes others will actually do it, but you should get and keep the good understanding on the what and why for every one of those pieces. Maybe that's more "architect" than "manager" though, so possibly I'm fighting the wrong debate here...