How many PMs to engineers does your team have?
- There is no magic in the work of PMs and neither is there much magic in 99% of the work of swe...
You can have self sufficient teams without any support and you can run an outsourced team of low paid engineers with a few months training that gets the job done.
Most high performing teams have strong members of different roles. That's the case in ALL top performing companies (and even the teams that traditionally didnt have PMs are transitioning to pm support after recognizing they are underperforming despite having some of the strongest e6+ engineers)
- Microsoft / ProductBrazukamoreMicrosoft's average is around 1:3-4. Too many PMs and little proactive devs/EMs because of it.
- This is Wayfair's problem - now imagine layering in a complete lack of technical leadership (CTO and architects who have never been engineers or haven't been writing code for >10 years) and Product leadership who have never been PMs before (management consulting, business development)
- Totally agree, Microsoft’s issue is PMs have to do too much project mgmt. sometimes devs saying can you open a bug? Pls open your own damn bugs if you find a mistake in your system. So PMs become shitty project mgrs. PMs should be doing more architecture and specs and not being told to schedule meetings.Jesus if you know you need a meeting schedule it yourself I’m not your secretary. If you really need a secretary; grow to A director role and get a business admin. . Now PMs barely do competitive analysis because of all this shit. Leads to shit product.
This comment was deleted by original commenter.