This is a great testimony. I think that stretching their capacity is a forcing function to stay high level and vision oriented, and avoid having PMs go too deep and start building up useless processes, or over-define features.
Ah, so that's what a product manager is supposed to do. When product managers were introduced at a company I worked at, they did very little of any of that. They certainly weren't speaking to customers. They weren't technical, so they weren't managing our Jira tickets. And "managing leadership" fell mostly on our managers' plates. I think the PMs mostly had meetings, talked to leadership, talked to engineers, wrote documents, and presided over the (now very long) sprint planning meetings.
I can imagine product managers that did your list of things being a lot more valuable.
For example, look at the scope and definition of a "program manager" from Microsoft or the US DoD in the 1980s, 1990s+, as well as literature describing the role of a program manager and the discipline from that time.
Most companies with product managers have fewer customers and less complex products than 1990s Microsoft.
In my experience, as soon as you decide your projects will be formal and managed, you are already doomed to that negative value.
You can’t build a £20m facility with a series of sprints.
You need a formal design. This doesn't mean you need a formal project. Some amount of planning ahead very obviously helps, but how much is debatable, and when you have people whose sole specialization is "planning ahead", you are certainly past the point where it's too much.
Anyway, the most valuable people are the ones "planning behind", looking for what was left broken and could be done better from now on. Project management defines those people out of existence.
It is a high level abstraction that allows all parties to understand what they need to do and when they need to do it. For large projects it is simply essential - you need your external vendors to plan their availability, months or sometimes years in ahead, so that they can commit to the timeline.
If you're lucky enough to work on large software projects where there are no managers or other stakeholders asking "and how long will this take, exactly?" then maybe the design is enough.
But pretending planning ahead on large projects that is something that will just happen by osmosis or people "just doing it" simply won't work. Good project managers who do what they're supposed to are worth their weight in gold (just like good product managers).
How well can your project managers answer how long will this take? Because on my experience, 10000% delays are all but routine (ok, on construction it's usually bounded to something around 1000%). And how much value do people that can give you an estimate between 1% and 10000% of the target?
> But pretending planning ahead on large projects that is something that will just happen by osmosis
I'm telling you that planning ahead has a small value, following up with the plan has a high negative value, and the thing with a high positive value that is reexamining the plan is fought against by the practitioners.
If things start to slip, they find out where and why and apply what pressure they can to get them on track. If they cannot get them on track, they then liaise with everyone downstream to make them aware of the slippage, adjust the entire schedule, and get everyone reorganised.
It's not just putting things in the calendar and forgetting about them - it's a constant, ongoing herding of cats to get them all going the same way.
It sounds like you just might not have been lucky enough to work with really great project managers!
What is a product but a large project anyways?
A project manager is in charge of planing, execution and governance of a project. They don’t define any of the goals or vision.
Saying product is a large project is a big over simplification. If we go that route anything could be called a “large project”.
Yes. That's precisely the point. What's the difference between "X manager" and a "project manager" when the X itself is obviously a project?
This sounds like if you were trying to hire a race-car driver instead hired two people, and put one of them in charge of steering to the left and the other in charge of steering to the right.
A project has a defined start and end. You know when it’s done, and you should know that before it even starts.
A product is ongoing. It reacts to business changes.
BIT meeting on my calendar. Is it behavioral intervention team or something about the bachelor of information technology or Business Information technology or bachelor of industrial technology or are we talking about income taxes or what?
The split between project manager and product owner seems clearest.
A project manager is running the team. Who does what and when? How do we plan the work?
A product owner is kind of like the representative stakeholder. What should this do? How important is launching now Vs fixing these bugs?
How Vs what.
Good people in these roles are incredible. I've been fortunate to work with some.
Project Manager: They ensure that all the tasks for a project get done on time. They make the gantt charts, work with teams to break it down into sections, keep track of budgets, manage risks, report on progress to stakeholders, etc.
I've never worked with a Product Owner since I understand it is mostly a software related position and that is not my area. From what I understand, they are an intermediary that sits between PdM and PjM.
The wiki for “programmer” has “software developer, a software engineer, a programmer or a coder” as interchangeable terms in the first sentence.
Do you have a good UX team, but the engineering team is just a bit too big to be comfortable? Then the PM should work with the team to streamline communications and processes.
The hard part about this is that on the one hand, you need a PM that is experienced enough that they can set up processes and be disciplined enough to make sure they are followed. On the other hand, you need a PM that is able to embrace the chaos on aspects of the teams organization where it is beneficial for the team. Oh, and also they should be a domain expert, if possible. Know SQL. Know how to talk to management. Etc.
I think if you have a good one, it is a strong force multiplier for the team. If you have a bad one, it is a force subtractor.
And it is extremely difficult to tell beforehand (or even while they are actually working in that team!) which kind of PM you have. It’s one of those roles that, if it’s done perfectly, people won’t be sure whether you have done anything at all.
But I agree with the premise that there are probably too many bad ones in circulation right now.
So it follows there will be more anecdotes about bad managers than good ones.
With respect, if you've never had a good, or great, manager then I understand it'll be hard to envision a good one.
I say this not to invalidate your anecdote but yo say that managers, like programmers, are not created equal and they cannot just be swapped like burgers at macdonalds.
I'm currently trying desperately to get two different PM's to talk to each other so we can be consistent with permissions sets across two different projects. Both projects use the same set of API's.
One of the PM's is basically incognito, the other has actively been trying to avoid doing any of the work.
But the technical teams will get blamed for this, I know because I've watched these same PM's blame the technical teams for their own failings on other projects.
I'm with the article, fuck Product Managers, grab a senior developer and let him or her spend part of their time interfacing with business while also teaching the younger developers the skills necessary to do it.
The problem isn't that their responsibilities aren't useful, it's that there shouldn't be a role dedicated to their responsibilities, it immediately draws moats around everything and suddenly the need for communication and collaboration jumps through the roof because the people in that role don't understand the technology the way a senior developer would.
There's a segment of the developer population that wants to put their head in the sand, do their job, and clock out. These developers are low value and will never be able to take on the role described above.
There's a large number of companies where the company is the one wedging the PMs there.
My view is that a PMs job should include (but not be limited to) diplomacy, negotiation and facilitation. But if your heart isn't in that (and it can be easy to become disheartened), then it easily becomes "politics", and the worst parts of politics, at that.
I don't know if the same role makes as much sense at a B2C company, so maybe people are B2Bs see their value and people at B2C companies don't as much?
So tech people (even IC non-leads) end up on weekly calls with various internal stakeholders that the PM can't make (literally this is your job dude) and take the brunt of all the feedback/relationship management/etc with the trickier ones.
The worst was when he said he would take the weekly calls with Asia users but wanted to pre-meet with me first and ask I ride along with the weekly user call for a while. So we would pre-meet and then he would ghost on the user call so I end up having two calls instead of one.
Just cargo cult CTOs reading too many books and not actually looking at the evidence in front of their eyes.
In B2C the customer is way clearer and the relationship is everything and it’s quite hard a bad professional hide for long.
TA’s will devour the BA’s because tech folks can learn business easier than the other way around.
Still, BA’s can learn the details and get more fluent in working with them.
A decade+ of low-interest-rate fueled growth in the tech sector has meant a lot of us have succeeded just by showing up.
What’s not great is customers arguing with engineers about which features to implement first or whether their bug report ought to have been backlogged. This is where a strong product role is essential.
For any product of reasonable complexity, taking to users is something a PM should be spending ~1.5 days/wk on. Plus overseeing quantitative user research.
If your engineers are all spending that kind of time on users, that's slowing down the amount of time writing software by a huge amount.
I operate as principle on a project, and I have opinions, but I cannot set the roadmap alone
We have loads of project managers where I work and I thank my stars we have every one of them. The coordination and planning required is ferocious for the work we need to deliver. It is not trivial and it would quickly fall apart without them.
But you're right that my comment focused only on the latter thing and ignored the former one.
But setting that aside, there is certainly a personality thing at play here. If I worked where you work, I would probably be more skeptical of the value of all the time being put into project management, and if you worked at my favorite companies that I've worked at, you would probably feel like it's a poorly managed mess (I've had lots of coworkers who felt that way!).
To some extent different folks just like different strokes, and that's one of the things that makes it really hard to do things that require lots of people to pull in the same direction.
Program management is a level above project management as you say, coordinating multiple projects. But there is definitely a space for complex single projects (not programs) that still require detailed planning and coordination.
It's not really about personal preference though, unless this issue is a show stopper for you in terms of where you work. I've worked in both informal and formal settings. I personally dislike heavyweight project management processes but they are sometimes required!
(I get it, sometimes the need for a lot of planning is imposed from the top, like if you sign a contract with an immovable delivery date, but I think most organizations should do whatever they can to avoid doing that, in order to enable them to structure projects flexibly and have small mostly-autonomous teams.)
I think the personality thing is important both in terms of contentment with your work (and thus which organizations and projects you choose) and in terms of how you analyze the relative value of things when evaluating trade-offs between the different things an organization can invest its time and resources on.
I agree that it's good if it's possible to avoid all that and still deliver what you need to!
Also agree that many people simply can't stand working in really heavyweight environments. While I dont love it, I can live with it.
One thing I think is that a lot (though not all!) of the requirements imposed in heavily-regulated industries are actively counter-productive, because they more effectively introduce friction on positive changes than risky ones. But it's basically impossible to strike the exact right balance between mitigating tail risks, which is critical, vs. introducing counter-productive friction. So I have sympathy, I just also find it very frustrating to work in such environments.
Friction certainly makes it harder to introduce positive change. I don't think it makes it easier to make riskier ones though, but you often can't do everything you'd like to get done.
They may jump in occasionally to tell us another team needs X or the business wants to see more Y so we should re-think what we work on next, but I struggle to see why that couldn’t be handled by our technical team lead.
Those PMs in the PMO knew their shit, they were realistic, they understood different strategies, they handled managing up and down, and ensuring everyone knew what they had to do.
I wrote a linkedin review for my favorite PM and it's as follows:
When I first met Rajitha, she was in the process of managing a company wide Windows 7 to 10 upgrade. As it turns out I was one of the last holdouts and was badly overdue. She was incessant! I hated it!. Finally, I gave into her demands and as these things go, I was pleasantly surprised how smoothly it went.
Fast forward a few months and Rajitha was tasked to work along side myself and others on several complex tech merger/acquisition projects. Moving parts, moving people, the whole thing was a whirlwind held down by a few important people on the team, including her. My initial resentment was replaced with a new deeply held respect for her capabilities and skillset. She was amazingly diligent and focused, friendly and compassionate.
If you're get a chance to work with Rajitha, count yourself among the lucky few!
Sorry Rajitha, this recommendation is many years overdue. I was cleaning out my filing cabinet and found a stack of old Church & Dwight papers. A print out of "How I learned to stop worrying and love Direct To Consumer". A "Magneto", not "Magento" project cover, and a handwritten note -- left on my desk -- from you to make sure I followed up a task that was in my queue".
Development was so much smoother. I didn't have to spend time explaining why we couldn't do this or that. He'd nix bad ideas at higher levels before it even hit us. We were given ample warning on how we approach things ("Custom B will want this, and if box what you're doing now it'll be harder blah blah blah").
When this role is dumped into engineering, engineering management or general management, it weakens the engineering practice. If I need engineers, I need to select for that ability and frankly shield them from people on the outside. If the org requires that my teams handle interaction, now I'm hiring people with mixed skillsets in one org, which inevitably waters down the engineering side.
They are different disciplines, and like any profession there's likely more people who are not good at it than people that are.
But I've worked with great visionary product people and excellent project and program managers (and strive to be one every day myself). Neither could do the other's job well or effectively. They need to be laser focused on different things, and their EQ tends to be tuned to different wavelengths.
We can define and name the roles all sorts of things (project manager, product owner, product manager, product marketing manager), but what it boils to is for any complex product there is a need for the management of the product at a holistic level and a need for management of a product at a granular level.
What I’ve witnessed over a 20 year career is that weak product people devolve to mediocre project managers. It’s easier to be a shitty project manager.
Good project managers are gold. I worked with one who stood out a decade ago - his leadership at execution was such that a $350M, 20 month implementation, with collaboration with construction, tech, and external suppliers completed 45 minutes ahead of the original schedule. He’s since retired and passed away, but an inspirational leader I was privileged to get to know. Ponder that - how many project managers are acknowledged as leaders?
This made me smile. I'm assuming you mean 45 days or something. Not that any number 'ahead of schedule' is inherently a bad thing (within reason), but my mind went to "Are there really companies out there tracking 2 year projects and counting the minutes?" (and sadly, there probably are).
That said, some major elements were tracked to the minute. I wish I could share more, it's a great story!
I'd argue that the position taken above weakens the engineering practice. Understanding requirements (e.g. constraints) is a core element of engineering, engineering management, and general management. Part of the problem plaguing the tech industry is the "dumping" of this responsibility, and others such as "project management" into some other role. What some like to call a "specialization" may also be called an abdication of responsibilities and ultimately accountability.
In my opinion, the essence of engineering is the methodical art and practice of solving problems. A fundamental part of engineering is understanding the problem(s) to be solved, the constraints, as well as the trade space and trade offs of solutions for those problems.
Not all aspects of (engineering) problems are "technical" in nature, and a failure to understand this and cultivate this understanding weakens the engineering practice.
Determination, evaluation, and articulation of requirements is the sweet spot of the product manager role. Understanding those requirements is certainly necessary for an engineer to build to the requirements.
Once upon a time, this too was a formalized practice in engineering that people called "Systems Engineering":
https://en.wikipedia.org/wiki/Systems_engineering
https://www.nasa.gov/reference/2-0-fundamentals-of-systems-e...
Writing good code is a very separate skill set from that kind of problem-space work, and software engineers are mostly hired for the former.
Imagine developing an AAA game with no one in charge of the overall product. Or creating a movie without a producer or a director, expecting the talent to somehow organise itself.
PM isn't an engineering job, it's a vision job - one that needs enough technical knowledge to create a vision that's grounded in reality, while also appealing to customers, while also being able to sell it up and down the org.
That skillset is incredibly rare.
The article was all about the consequences of the skill set being incredibly rare.
Imagine if a director was a bureaucrat. One who followed checklists and made policy documents, and did not have the slightest clue about the actual craft of setting lights, working the camera, and acting.
What's our profession's equivalent of a film director? One with deep knowledge about data structures, who cared about getting it right, together with professionals?
Scrum master.
Good product managers identify the problems to be solved, and prioritize which ones should be solved first.
Why on earth would being able to handle interactions “water down” engineering? They’re two perpendicular skillsets. We’re not in Hollywood, engineers don’t have to be autistic
Those are the marketing people. On most places they are stupidly completely focused on sales, but that's not ideal.
Product management is also a task for those people, but singlemindly focusing them on PM is about as bad as doing that for sales.
> manage leadership, play politics for resource allocation
And those are management tasks. It makes no sense at all to give both sets of tasks to the same set of people.
Over and over, the staff were pounded with "we are an engineering first company." Well, that means the engineering teams were allowed to do whatever the hell they wanted and chase the shiny newest techs. There's 3.5 main products (really 4.5) each made from a different tech stack. There's another eight or so legacy products we have to support due to legacy demands. There's no inter-operability of standardization between products. Basically, there's no knowledge transfer, so the cost of development is through the roof.
Twice this year, I had to explain to 20 year-tenure engineers that don't understand why it's a bad thing that one API is TLS 1.3 only, another is 1.x, and another doesn't even require TLS.
Customers hate us. For my product, they literally wrote the marketing materials first, and let the engineers figure it out. One stage of my product takes Oracle data and puts it into parquet. The guys who did it did it in three different languages, two other DBs inbetween (MySQL AND PG), and was going to introduce Redis before I stopped the insanity. Everything is fragile and sucks.
Thankfully, PE took over two years ago and we now have an ultimatum to make money or else. We are a twenty year old company that has never made money (we've been a cost center). Even if we don't meet it, I feel like the Universe will be better off without the travesties against software design that we created.
APIs using different TLS versions falls into the same category. Unless the TLS version is part of the product (which is the case for e.g. API Gateways, webservers and proxies) PMs will likely not care. They should however care about the difference between no TLS at all and a "somewhat modern TLS", because "no security" is definitely an important gap in the product.
The point is though, product never challenged on approaches, and you’re right. They never came from technical backgrounds. Product managers were promoted from the BA ranks. They never raised technical questions like that - “Is it a bad thing if the customer has to connect this way for this API and another way for another API?” If the idea is that engineering asks those questions, I’d counter with that’s venturing squarely into product’s realm.
- Someone to understand the customer's desires and shut down unnecessary work.
- Drive the team to deliver features that the customers/business actually needs.
- drive tech decisions to prevent future inoperability with other products
- roadshow and maintain a team's reputation across the org
- etc
I can think of a bunch of different ways of solving this that would take a few days to build out.
The problems you describe are legit but unless you have extremely technical product managers, hiring more PMs will only make the problem worse.
Does the vast majority of PMs need to tell the difference between TLS 1.3 and 1.x?
I mean, is that a relevant aspect of the vast majority of products?
If not, why should a PM bother about irrelevant details?
One of the cardinal sins of proponents of this "engineers should rule everything" mentality is failing to tell apart the critical factors from the irrelevant details, and conflate not caring about obscure implementation details with incompetence. Except the cheekiest little fallacy in software development circles is that the purpose of all software projects is not correctness or code coverage or uptime or resilience. The purpose of each and every single software project is to serve their users' interests. That's the critical part of a project, and the thing that PMs focus on for the right reasons. Naturally, PMs prioritize work with the biggest impact. Does TLS trivia fit this requirement? No.
Non-technical PMs tend to gloss over things like that as an engineering-driven feature. Clients don't ask for TLS 1.3 (at least until it's often too late) because they generally aren't considering TLS trivia until it comes time for their next audit.
You see, I don't think that's true at all. If it was, certainly you'd have clients complain loudly enough for the PMs to notice.
But that doesn't seem to even register a concern, both from the client and from the PM point of view.
Convenience is a nice-to-have, and fixing problems that don't exist registers even lower in the priority queue.
> Non-technical PMs tend to gloss over things like that (...)
See, this is where I think we disagree at a very basic level.
There is no such thing as a technical and non-technical Product Manager, because a product isn't technical. A product is something that meets the needs and expectations of its customers. A Product Manager's responsibility is to know their product and manage it to meet its clients' needs, and in the process help guide the development effort to maximize its returns on investment. Whether it's to paint a button red instead of blue, or to tell if they need to upgrade TLS, a PM's job is to read the room and deliver what meets the needs.
Because engineering failed to consider these details. Now I'm the one that has to point out how amateur we look when in some areas we don't require TLS and others we're so strict, we only have 1.3. Engineers (management or rank and file) who can't understand why this is a problem is exactly the reason you need technical PMs.
I don't think you got the point. The point is that no one cares, or think it's important enough and much less critical to justify wasting time with it. Product Managers are there to create value, and spending time on things no one notices is not how you create value.
It seems to me, especially in the wild and woolly mom-n-pop end of the market, that there might be ample room for a company to sustainably put food on a certain number of employees’ family tables without much left over to characterize as profit.
well just remember that engineers do this to have portfolio pieces on their resume. they need validation from other people that they worked on a software stack, and to be able to do live interview assignments about that software stack.
this actually just another symptom of a really bad interviewing process where nobody can tell that you're a competent engineer unless you pigeon-hole yourself to one stack that might not always have jobs for it, or for very long. there is also pressure to work on the coolest software stacks, because maybe you will be a scarce resource for a few years and get a major premium in compensation on the fastest growing companies. the other symptom is that companies aren't doing training, they're allergic to it, so they only want engineers that have years of potentially verifiable experience working on the exact stack they have, so that engineer could "hit the ground running" despite needing to keep the job opening up for 6 months to find that person.
I read this and thought you worked at my previous employer (household name in IT).
Engineering first company. Oof. This meant that as a PM, I got introduced to two of the products I'd be managing when Engineering and Architects had come up with a grand idea to build a component/subsystem to replace a previous one which had been over-engineered and never gained traction. They hadn't talked to any customers who used it, or that had liked the idea, but not the execution. They were just given a wide latitude to experiment (don't get me wrong, some experimentation and exploration is useful), got a greenlight for some time to prototype it, and did so.
And then, and only then, was I called in as a PM, and told, here's our prototype, here's some vague documentation of what we wanted to solve with this - "Now, Mr PM, can you shoehorn a Product Requirements Document around what we've already built and where we see it going, and can you do the Market Requirements Document to answer the questions we probably should have asked before getting this far?"
And then I would get catch-22s. Express doubt over the needed research and potential for the product and I was told by management that "PMs need to be passionate and fearless advocates for their products"... and then when I do try to eke something out, but lo and behold, our internal 'market', let alone customers are ambivalent about why we are working on a "v2" of this feature, when the market is either accepting the weaknesses of "v1" or have long built out their own solutions and moved on, and as a result we have a stakeholders meeting where we decide to end the experiment, and I'm chastised for "poor product management judgment" for not killing the project far earlier... the project I have no authority to kill, because it's an Engineering first company, and the project whose existence I learned of when it was tossed into my lap as a 90% complete prototype/proof of concept.
And then you have a few hundred (yep) Product Managers in our BU all trying to do their own thing, some empire-building, some truly product-focused... and it's a shit show.
I love being a product manager. I took a similar path as you... although most of my engineering background is SysAdmin/Devops/SRE/infrastructure and then management thereof. I love being a product manager, and thought that this role, at this company, would have untold potential and I could settle in, learn, grow, build from there. But it was everything from a Dilbert cartoon.
I’ve never met a PM that did any of that either ;)
That’s what CX is for.
> interview users to identify potential features
That’s what designers are for.
> manage leadership, play politics for resource allocation
That’s what your lead/people manager is for.
You don’t need a PM. You need an org chart.
Also, what engineer doesn’t understand the product deeply from both a technical and business perspective? Maybe a contract dev, or a new hire.
Reforge provides good training for product managers. This article provides a good overview of a role of a PM: https://www.reforge.com/previews/product/what-does-a-product...
Now we have Product Manager orgs with Associate PMs, junior PMs, senior PMs, group PMs etc…
A junior PM almost by definition can’t be a product owner. They don’t have the seniority to make decisions, so what you end up with is a situation where senior PMs are handing down solutions to junior PMs who are coming up with even more detailed solutions to engineers. I’ve seen it time and again.
I mean product owner as in the person responsible for the product.
Designers interview people, and potential features may come out of that. They don't put those potential features into a roadmap and allocate resources to them. I'm a designer: if it were up to me, I'd spend 99% of my time improving the UX of the product we have, because that's what I care about most. Somebody has to own the vision for the product with respect to the company's business goals, and individual designers and engineers are not the right people for that. Maybe I ought to have phrased that better originally.
That kind of depends. The product-minded ones (who are naturally interested in the "producty" kind of work) are excellent people for that. So you may find that in some companies the people doing product work are either engineers or designers. I've often done that from the engineering side, and I've seen it done really excellently by UX designers too. In other companies you may have dedicated people.
In my experience, whether it works well or not is less a function of how the roles are divided and more a function of whether the individuals doing product work are good at product work (which is difficult to find, even when they are dedicated product specialists). I think I would probably argue that due to the nature of the job being a lot about connecting different functions of the business and synthesising into a coherent whole, product people tend (on average) to better at their job when they do also have experience with at least some of the other roles they are interacting with (although this isn't necessary to do the job well).
A PM will say things like: "I spent 120 hours talking with our users last quarter. They want a macro language added to the product to make their work easier. Our major competitor already has this feature. We have a budget from the executives and 6 months to get it done. We can get the CX person to do some focus groups to figure out how the users expect it to work, the designer to create some interface options for everyone to choose between and then do the UI wireframes, then the leads can work together to plan the coding schedule based on the implementation phases I will give them."
Now program managers, it remains to be seen where their value comes from and I hope it does
Second, bad PMs just create unnecessary work for everyone around them. Everyone believes they just have to do what the PM says, and then suddenly you have a whole eng team contributing nothing.
It sounds so ridiculous, and yet ... it happened.
in my experience, they manage project managers for systems with a high degree of complexity, e.g. an aircraft, and the product managers work through them, instead of through project managers directly. Or they are themselves the product manager, just with different terminology depending on the industry
This sounds like a combination of charisma, leadership, and drive, which makes sense as a pretty rare set of qualities for one person to have.
... And reading that, I think I left out that they were super nice, and everybody liked them.
there aren't enough good software developers to go around. My belief is the number of people cut out to be a good software developer scales linearly with the size of the population. You need certain personality traits and other qualities that can't be taught. You can mint mediocre SWDevs in school, but you can't make good ones that way, let alone great ones.
That's not what a PM does. You're missing leaders.
Customer relations is generally under sales. Resource allocations, politics, that's engineering leadership stuff.
Customer interviews is part of what a PM (or UXer) does. It's never been a critical pain point in any business I've been though. It's part of defining the product, oftentimes companies have a X years backlog of features users asked for and not enough time to build.
Fast-forward to my current company, the PMs here are absolutely shocking. The people they report to have no clue. It seems like every PM at my company has fallen upwards, as a result of newly hired PMs quitting shortly after they join. Engineers here are technically competent, but lack direction. Projects spin up before requirements have been defined, leading to massive losses of time. I’ve considered reaching out to my former company’s PMs to offer a referral, but it’d be a disservice to them.
The path to becoming a great PM is longer and arguably harder than becoming a great engineer. Like you say a lot of what makes a great PM comes from years of experience in a variety of roles and companies.
Because the more you do, the more you are responsible for, but what you get doesn't increase. It's a question of profit distribution.
My current company is full of smart people, and (for a variety of reasons) we don't have product managers. It sucks. What happens is that the things a PM does do not get done. Very few engineers want to maintain relationships with customers, interview users to identify potential features, manage leadership, play politics for resource allocation, and so on. So it doesn't get done. That's what happens there.
At my last company, where I worked for about a year, I had three product managers. Two of them were fired because they were incompetent. One was really, really good (tremendous, in the parlance of this article). Our team still got more done in a year with a fraction of a good PM than my current company has gotten done in over two years without any PMs.
I agree with one thing: there aren't enough good PMs to go around. My belief is the number of people cut out to be a good product manager scales linearly with the size of the population. You need certain personality traits and other qualities that can't be taught. You can mint mediocre PMs in school, but you can't make good ones that way, let alone great ones. The problem we are dealing with is that the software industry did not scale linearly, it exploded exponentially, and it needed 100x the number of people wearing the PM hat than there were actual, bonafide PMs in the world.