News for hackers. Stuff that matters.
Re:The product manager role is a mistake by karaterobot on Sunday October 29, 2023 @12:05PM (#38059857)
> You hire everyday great people. Each one needs to be great at something, obsessed by their craft, and driven by quality. You then put them together in a team, without individual responsibilities, ensuring that there’s minimal overlap in areas of greatness.

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.

Re:The product manager role is a mistake by charles_f on Sunday October 29, 2023 @12:39PM (#38060253)
> 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

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.

Re:The product manager role is a mistake by justinpombrio on Sunday October 29, 2023 @12:29PM (#38060140)
> 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

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.

Re:The product manager role is a mistake by jpatt on Sunday October 29, 2023 @12:37PM (#38060224)
Sounds a lot more like a project or program manager than a product manager.
Re:The product manager role is a mistake by moandcompany on Sunday October 29, 2023 @12:56PM (#38060415)
And ironically it seem like the things you'd positively attribute here to a product manager used to be/are actually part of the scope of what was traditionally a "project manager" or "program manager."

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.

Re:The product manager role is a mistake by lukevp on Sunday October 29, 2023 @01:46PM (#38060906)
Why’s that ironic? There didn’t used to be frontend / backend / full stack devs either. As software engineering has matured and grown in scale, more subdivision of responsibilities is a natural outcome of that. We’re not all just directly writing code on mainframes and our customers aren’t just < 1k of users who directly call us on the phone if something goes wrong anymore, it’s millions of people using services 24x7 now. MS wasn’t making real-time collaboration systems and cloud sync in the 80s and 90s. They were making a stand-alone offline machine that barely could install device drivers and didn’t know what the internet was. Completely different products, and much simpler.
Re:The product manager role is a mistake by pseudalopex on Sunday October 29, 2023 @04:55PM (#38062691)
What subdivision of responsibilities? Clients and servers were divided for as long as clients and servers existed. Full stack is aggregation of responsibilities. DevOps too. Dedicated QA is rare now.

Most companies with product managers have fewer customers and less complex products than 1990s Microsoft.

Re:The product manager role is a mistake by ajkjk on Sunday October 29, 2023 @12:56PM (#38060424)
Nevertheless it is the role called "product manager" at many companies.
Re:The product manager role is a mistake by sanderjd on Sunday October 29, 2023 @01:03PM (#38060501)
Yep, a common pitfall is to not understand how product managers are supposed to do, and thus they just do project management, which often has neutral or negative value.
Re:The product manager role is a mistake by marcosdumay on Sunday October 29, 2023 @01:39PM (#38060846)
I've seen competent project managers work very hard to achieve that neutral-value proposition. I haven't yet seen any one succeed.

In my experience, as soon as you decide your projects will be formal and managed, you are already doomed to that negative value.

Re:The product manager role is a mistake by midasuni on Sunday October 29, 2023 @02:08PM (#38061080)
Sometimes you need a formal project. We’re kitting out a new office over the next couple of years, it’s a major programme of multiple projects, all which interact. At the end of it though we have a building fit for purposes following the plans currently set. I’m sure those plans will adjust a little, but the end date is January 2025, or July, or something - I’m sure the date will slip.

You can’t build a £20m facility with a series of sprints.

Re:The product manager role is a mistake by marcosdumay on Sunday October 29, 2023 @02:54PM (#38061467)
Well, the Empire State Building was famously built as 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.

Re:The product manager role is a mistake by trog on Sunday October 29, 2023 @04:31PM (#38062452)
Think of the "formal project" is the API by which executing the design can be understood by all stakeholders.

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).

Re:The product manager role is a mistake by marcosdumay on Sunday October 29, 2023 @07:15PM (#38063821)
> 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.

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.

Re:The product manager role is a mistake by trog on Monday October 30, 2023 @12:43AM (#38065764)
If they are good project managers, they plan for non-routine delays and account for them in the project schedule. Before people are allowed to commit to schedule, the project managers make sure that these people have properly scoped and estimated their part of the work, by asking pointed questions, using their domain expertise and general experience to figure out if they're being bullshitted or not.

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!

Re:The product manager role is a mistake by glimshe on Sunday October 29, 2023 @01:11PM (#38060581)
It sounds like you had a project manager, not a product manager. A good product manager is very valuable.
Re:The product manager role is a mistake by elicksaur on Sunday October 29, 2023 @01:38PM (#38060832)
It seems like whoever named these titles did a poor job. They’re so close, can you blame people for not seeing a difference?

What is a product but a large project anyways?

Re:The product manager role is a mistake by alonsonic on Sunday October 29, 2023 @01:48PM (#38060920)
A product manager is expected to view things from a business point of view. To identify features for the product and help it succeed in the market.

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”.

Re:The product manager role is a mistake by TeMPOraL on Sunday October 29, 2023 @04:17PM (#38062298)
> 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?

Re:The product manager role is a mistake by kaibee on Sunday October 29, 2023 @04:53PM (#38062673)
> in charge of planing, execution and governance of a project. They don’t define any of the goals or vision.

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.

Re:The product manager role is a mistake by lazystar on Sunday October 29, 2023 @05:57PM (#38063245)
this is exactly why back-to-office initiatives have value - it's easier to coordinate when the steerers are next to each other
Re:The product manager role is a mistake by IanCal on Sunday October 29, 2023 @09:00PM (#38064508)
Navigating and driving the car are two very obviously distinct tasks that regular people and rally drivers split up.
Re:The product manager role is a mistake by stcroixx on Sunday October 29, 2023 @09:16PM (#38064609)
The product manager decides which direction the car should be turned and the project manager turns the wheel.
Re:The product manager role is a mistake by tcmb on Sunday October 29, 2023 @01:52PM (#38060962)
A project has a planned end date, a product typically doesn't.
Re:The product manager role is a mistake by almostnormal on Sunday October 29, 2023 @02:40PM (#38061352)
[delayed]
Re:The product manager role is a mistake by JCharante on Sunday October 29, 2023 @04:03PM (#38062152)
Development phase is the project. Maintenance phase before sunsetting is I guess another project.
Re:The product manager role is a mistake by TeMPOraL on Sunday October 29, 2023 @04:18PM (#38062309)
Isn't it the other way around? Projects tend to never end. Products eventually get released.
Re:The product manager role is a mistake by gardenhedge on Sunday October 29, 2023 @04:54PM (#38062678)
A released product is not the end of the product. See: Google, Facebook, WhatsApp, X, Gmail, Dropbox, Firefox, etc.
Re:The product manager role is a mistake by johannes1234321 on Sunday October 29, 2023 @06:21PM (#38063434)
A release ist ksut the begining of a product. After that you have to collect customer feedbackand figure out what to prioritize for the next release.
Re:The product manager role is a mistake by midasuni on Sunday October 29, 2023 @01:58PM (#38061003)
My company had project managers and product owners to avoid that verbal confusion.

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.

Re:The product manager role is a mistake by esafak on Sunday October 29, 2023 @02:46PM (#38061401)
Project managers co-ordinate the teams and stakeholders associated with a project. It only applies to bigger companies. In smaller projects senior engineers and engineering managers do the same job.
Re:The product manager role is a mistake by isbvhodnvemrwvn on Sunday October 29, 2023 @05:20PM (#38062934)
There's sometimes also program managers who organize relevant projects across the company (for example with GDPR compliance a program manager might coordinate between legal and various products, identify risks and report progress to C-level, and each product will have a project kick off to get it into compliance (depending on the effort, the person overlooking this project and working with program might be a dedicated project manager, engineering manager, some engineer etc).
Re:The product manager role is a mistake by starky on Sunday October 29, 2023 @01:32PM (#38060773)
Last time I saw one of these types of articles on here it quickly became apparent that a lot of companies don't know the difference and call their project managers by the wrong name.
Re:The product manager role is a mistake by koonsolo on Sunday October 29, 2023 @02:07PM (#38061068)
People using "PM" is adding to the confusion.
Re:The product manager role is a mistake by wombatpm on Sunday October 29, 2023 @02:57PM (#38061503)
That’s why I use PMP for Product Management Professional. Much clearer
Re:The product manager role is a mistake by starky on Sunday October 29, 2023 @03:09PM (#38061614)
This adds to the confusion since Project Management Professional is a certification for a Project Manager that specifically uses that acronym and not all project managers have the certification.
Re:The product manager role is a mistake by namdnay on Sunday October 29, 2023 @03:25PM (#38061743)
I think it was a joke
Re:The product manager role is a mistake by Terr_ on Sunday October 29, 2023 @06:11PM (#38063364)
Alas, the joke is "Too Real" and on all of us.
Re:The product manager role is a mistake by Loughla on Sunday October 29, 2023 @05:18PM (#38062916)
For what it's worth, I enjoyed that joke. I work in education and the number of redundant acronyms and initialisms (if that's a word) is astounding.

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?

Re:The product manager role is a mistake by starky on Sunday October 29, 2023 @03:04PM (#38061564)
Agreed, PjM and PdM are what I use when referring to them.
Re:The product manager role is a mistake by naravara on Sunday October 29, 2023 @03:00PM (#38061529)
A lot of teams with poor business operations seem to treat project, product, and program management as a generic blob of “help us be organized please” duties instead of specific jobs with specific operational missions.
Re:The product manager role is a mistake by TeMPOraL on Sunday October 29, 2023 @04:15PM (#38062284)
What is the difference then, between a project manager, product manager, a project owner and a product owner? Always thought they're approximately the same thing. Isn't any product you're working on a project too?
Re:The product manager role is a mistake by zappb on Sunday October 29, 2023 @04:59PM (#38062731)
The main difference is between a product and a project. The gist is that projects are short term specific plans while products are a bit more open-ended ideas with continual feedback. Here’s a decent overview: https://martinfowler.com/articles/products-over-projects.htm...
Re:The product manager role is a mistake by IanCal on Sunday October 29, 2023 @08:57PM (#38064487)
Imo projects are company details, products are what your users see.

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.

Re:The product manager role is a mistake by starky on Sunday October 29, 2023 @10:03PM (#38064909)
Product Manager: They are essentially the voice of the customer and upper management. They work on the product roadmap and determine the requirements for the product based on the needs that are determined by conversations with the stakeholders as well as other market research. In addition to this they also work on things like product pricing, release strategy, etc.

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.

Re:The product manager role is a mistake by ragestorm on Sunday October 29, 2023 @01:12PM (#38060595)
Agree. Similar to a developer vs. SWE.
Re:The product manager role is a mistake by willsmith72 on Sunday October 29, 2023 @01:20PM (#38060674)
Disagree. Project manager is extremely different to product. Dev vs SWE is completely arbitrary
Re:The product manager role is a mistake by elicksaur on Sunday October 29, 2023 @01:37PM (#38060814)
What do you see as the difference between a developer and a SWE?
Re:The product manager role is a mistake by ipaddr on Sunday October 29, 2023 @02:03PM (#38061046)
One is DevOps and one is a programmer
Re:The product manager role is a mistake by _rutinerad on Sunday October 29, 2023 @04:21PM (#38062337)
They’re both programmers and you can’t “be devops”.
Re:The product manager role is a mistake by 59nadir on Monday October 30, 2023 @04:12AM (#38066815)
The vast majority of my colleagues would say "that person is a devops" instead of "that person does devops", which I don't get at all. I've assumed it's some deeply rooted misunderstanding of language (my colleagues are eastern european) that has taken hold across the entire local industry.
Re:The product manager role is a mistake by elicksaur on Sunday October 29, 2023 @10:26PM (#38065041)
That didn’t really clarify for me, which is which? What is DevOps to you? (Seems to be different for everyone)

The wiki for “programmer” has “software developer, a software engineer, a programmer or a coder” as interchangeable terms in the first sentence.

[1] https://en.m.wikipedia.org/wiki/Programmer

Re:The product manager role is a mistake by boredtofears on Sunday October 29, 2023 @01:19PM (#38060654)
there is no difference between a developer and an SWE except a fancy title
Re:The product manager role is a mistake by jefftk on Sunday October 29, 2023 @01:52PM (#38060956)
Which one is fancier?
Re:The product manager role is a mistake by JCharante on Sunday October 29, 2023 @04:04PM (#38062162)
Software Development Engineer is the one title to rule them all
Re:The product manager role is a mistake by fnordpiglet on Sunday October 29, 2023 @02:10PM (#38061100)
Most companies don’t understand what a product manager does, and they are busy eliminating project management roles in favor of an “agile” workflow, so they just repurpose the project managers to be product managers because it’s only two letters different. With predictable results.
Re:The product manager role is a mistake by esafak on Sunday October 29, 2023 @03:43PM (#38061940)
Project management was the role Larry Page once axed in 2001: https://medium.com/illumination/google-once-fired-all-manage...
Re:The product manager role is a mistake by gardenhedge on Sunday October 29, 2023 @04:50PM (#38062651)
Sounds like he fired a type of project manager - one who controlled the team. A project manager can manager the team by supporting them and unblocking them while doing non-implementation type work such as managing and reporting the project's budget, managing and reporting progress and delivery aims.
Re:The product manager role is a mistake by singron on Sunday October 29, 2023 @08:34PM (#38064337)
Google currently has program managers (and technical program managers). I could not tell you the difference between them and product or project managers.
Re:The product manager role is a mistake by jack_h on Sunday October 29, 2023 @02:54PM (#38061471)
It changes between companies. At my company the Product Owner is the one who maintains the relationship with customers. Product Managers are there for prioritizing the feature requests. We also have Project Managers for inter-project dependency tracking and Engineering Managers for resource allocation and work output.
Re:The product manager role is a mistake by haizhung on Sunday October 29, 2023 @03:36PM (#38061861)
I think that’s the challenging part. A product manager is supposed to stuff holes in your team that no one else currently does. Do you have a strong TL with a good product sense? Then the PM should probably spend their time talking to customers, and not interfere with the engineering team so much.

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.

Re:The product manager role is a mistake by bruce511 on Sunday October 29, 2023 @03:54PM (#38062062)
There are certainly more bad managers than good ones. (Just like programmers.)

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.

Re:The product manager role is a mistake by PH95VuimJjqBqy on Sunday October 29, 2023 @04:03PM (#38062155)
My experience with product managers is that they wedge themselves between the business and the technical teams and then wield political power while doing very little.

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.

Re:The product manager role is a mistake by FireBeyond on Sunday October 29, 2023 @06:07PM (#38063324)
> My experience with product managers is that they wedge themselves between the business and the technical teams and then wield political power while doing very little.

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.

Re:The product manager role is a mistake by foota on Sunday October 29, 2023 @06:10PM (#38063351)
I wonder if part of the gap here is about whether a company is B2B or B2C. In my experience at a largely B2B company, the product managers are people that aren't necessarily technical, but have experience in the relevant domain and meet with customers to find out what they need and coordinate launches etc., with them.

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?

Re:The product manager role is a mistake by steveBK123 on Sunday October 29, 2023 @06:39PM (#38063566)
I've seen shops hire product managers for INTERNAL customer facing apps, and then have the PMs basically not talk to those customers. They did instead talk extensively to product & tech management as well as the c-suite.

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.

Re:The product manager role is a mistake by braza on Sunday October 29, 2023 @06:59PM (#38063709)
Same experience, but I have one hypothesis: in B2C the “client” after some point become some abstract entity where people ship code/product to. A great PM can talk with those masses and extract exactly what needs to be done. This is a very hard skill.

In B2C the customer is way clearer and the relationship is everything and it’s quite hard a bad professional hide for long.

Re:The product manager role is a mistake by j45 on Sunday October 29, 2023 @11:07PM (#38065250)
The issue too often is business analysts wanting to be product managers when technical analysts may enable to learn the role better.

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.

Re:The product manager role is a mistake by plorkyeran on Sunday October 29, 2023 @11:33PM (#38065391)
My experience with B2B PMs is that exactly one that I've worked with was amazing and the rest were just an awful intermediary that added a day of latency to any communication with our contact at customers and often managed to mangle things too.
Re:The product manager role is a mistake by alexchantavy on Sunday October 29, 2023 @06:16PM (#38063395)
I feel like that list of responsibilities describes a staff engineer too
Re:The product manager role is a mistake by breckenedge on Sunday October 29, 2023 @12:37PM (#38060222)
Are they really that smart if they’re ignoring those things? Talking to users has always been on my list of things required for engineers.

A decade+ of low-interest-rate fueled growth in the tech sector has meant a lot of us have succeeded just by showing up.

Re:The product manager role is a mistake by twoodfin on Sunday October 29, 2023 @12:54PM (#38060392)
In my experience, close technical customer-developer collaboration is incredibly valuable.

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.

Re:The product manager role is a mistake by breckenedge on Tuesday October 31, 2023 @11:46AM (#38086667)
I agree. Have the product team facilitate communications between customers and engineers and guide efforts towards development that has the biggest returns. Sadly I don’t really ever see it functioning that way anymore.
Re:The product manager role is a mistake by crazygringo on Sunday October 29, 2023 @01:44PM (#38060885)
> Talking to users has always been on my list of things required for engineers.

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.

Re:The product manager role is a mistake by esafak on Sunday October 29, 2023 @03:05PM (#38061565)
In big companies there is not even a way for engineers to reach out to users. They come to you through feedback.
Re:The product manager role is a mistake by calvinmorrison on Sunday October 29, 2023 @12:38PM (#38060232)
Someone's gotta own the roadmap and prioritize the work queue, be it at a project level or updating the Microsoft project plan or the sprint. There's always a multitude of stakeholders. Devs, sales, marketing, ops, all have needs and idea. Someone must be the arbiter.

I operate as principle on a project, and I have opinions, but I cannot set the roadmap alone

Re:The product manager role is a mistake by sanderjd on Sunday October 29, 2023 @01:06PM (#38060533)
If all you want is someone to do team-level project management toil, a line manager can do that (or hire them a part time assistant if they don't want to and you don't want to invest in better automation). This is not a whole career-level job.
Re:The product manager role is a mistake by MattPalmer1086 on Sunday October 29, 2023 @03:03PM (#38061550)
I get the feeling you don't work on massively complex projects.

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.

Re:The product manager role is a mistake by sanderjd on Sunday October 29, 2023 @07:09PM (#38063778)
Some of what you described in the comment I replied to fits the description of complicated company-spanning project management - a valuable role I have typically seen referred to as "program management" - but some of it, the team level dealing-with-task-backlogs type stuff, are things that managers and team members can just do in the course of their work.

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.

Re:The product manager role is a mistake by MattPalmer1086 on Monday October 30, 2023 @04:19AM (#38066850)
There is certainly a distinction between teams just dealing with their task backlog and project management. I wouldn't waste a project manager on that.

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!

Re:The product manager role is a mistake by sanderjd on Monday October 30, 2023 @01:57PM (#38073114)
Yeah I was thinking last night that my comments here were a lot more strident about this than I am in real life. I agree with your whole comment, except I think the middle ground between team-level management and program management is more often better served by tooling, architecture, requirements, or team structure changes rather than project management.

(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.

Re:The product manager role is a mistake by MattPalmer1086 on Tuesday October 31, 2023 @04:55AM (#38081910)
In our case we are a heavily regulated industry and the level of coordination, governance and compliance that is required to make change is shocking!

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.

Re:The product manager role is a mistake by sanderjd on Tuesday October 31, 2023 @11:30AM (#38086372)
Yep! I think, somewhat humorously for how this thread started - which was entirely mea culpa! - our perspectives on this are pretty closely aligned.

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.

Re:The product manager role is a mistake by MattPalmer1086 on Tuesday October 31, 2023 @04:34PM (#38090984)
Yeah, we aren't too far apart! It's why I like HN, you can actually have a civilised conversation :)

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.

Re:The product manager role is a mistake by sanderjd on Thursday November 02, 2023 @01:35AM (#38109376)
Just to clarify, I didn't mean regulatory friction makes it easier to do things that are risky. I think regulation is pretty much entirely successful at making that harder. What I meant is that, in my view, regulations that reduce the chance of tail risks by let's say X% often seem to increase the friction on making improvements by more like say 2X%. Of course this isn't scientific or anything, but it's my intuition, that the trade-off doesn't seem to be 1:1 when you take on some friction to reduce the likelihood of some tail risk.
Re:The product manager role is a mistake by tennis_80 on Sunday October 29, 2023 @01:48PM (#38060918)
Eh, in my current role (engineer) we have a PM but they’re not all that useful. In theory, they do what you describe, but because they don’t have a technical background they struggle to identify blockers & engineers drive most prioritisation sessions.

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.

Re:The product manager role is a mistake by lazyasciiart on Sunday October 29, 2023 @12:23PM (#38060062)
In my experience: working with a good or great PM is fun and productive. Working without a PM is ok. Working with a bad PM is somewhere between irritating and infuriating.
Re:The product manager role is a mistake by semiquaver on Sunday October 29, 2023 @12:34PM (#38060193)
Yep. A great PM is an amazing force multiplier. A bad PM drags the whole org down.
Re:The product manager role is a mistake by esafak on Sunday October 29, 2023 @03:06PM (#38061580)
So you're saying PMs are powerful.
Re:The product manager role is a mistake by calvinmorrison on Sunday October 29, 2023 @12:45PM (#38060314)
One of my most enjoyable experiences in regards to project management was working at a fortune 500 with an entire PM Org. The PMO grew out of IT where it was really formalized and then got its tentacles into all of the different orgs, sales, marketing, finance, etc. What an amazing force multiplier is right. Before IT would be sitting around waiting for Finance, now Finance was part of a global PM situation.

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".

Re:The product manager role is a mistake by BHSPitMonkey on Sunday October 29, 2023 @01:10PM (#38060573)
This applies to colleagues in all roles, especially the ones with more authority.
Re:The product manager role is a mistake by Belopolye on Sunday October 29, 2023 @01:10PM (#38060579)
Been having this lately with one of our clients, and my impression is that more than one of these PMs have their role as a placeholder while something else is found for them to do.
Re:The product manager role is a mistake by snapetom on Sunday October 29, 2023 @01:43PM (#38060878)
I had several companies where the PM were horrible, lost, and egotistical. I then ran into a company where the PM spent ten years as a developer for some popular game companies. That guy was worth his weight in gold.

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").

Re:The product manager role is a mistake by Spooky23 on Sunday October 29, 2023 @01:19PM (#38060656)
Product Management is a hard job. You need to be technical enough to understand whats happening and have a bullshit detector, but high EQ enough to speak human. The dumb ones become sort-of project managers, tracking another set of books for tasks. The smart ones tend to deeply understand the business and move up or out. It's also a tough role to govern in that sometimes they get alot of credit for the work of others, or get no credit for anything and languish from a career pov.

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.

Re:The product manager role is a mistake by shostack on Sunday October 29, 2023 @01:31PM (#38060759)
I really hope you're not implying that project managers are or need to be less smart than product managers.

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.

Re:The product manager role is a mistake by alienlid on Sunday October 29, 2023 @02:06PM (#38061059)
Project managers usually don't need to know as much as product managers, or be as thoughtful as them to be a great value add. Project managers have a larger range of "acceptable" performance to be able to add value, so their job certainly is easier.
Re:The product manager role is a mistake by kcplate on Sunday October 29, 2023 @02:36PM (#38061306)
Perhaps it was inelegantly put by the original commenter, but I think the gist is that the product managers who lack some of the important product management skills around vision, ability to be customer facing, and effective and articulate communications tend to work more like project managers—effective acting as tactical managers within a product as opposed to strategic ones for the product.

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.

Re:The product manager role is a mistake by Spooky23 on Sunday October 29, 2023 @03:53PM (#38062041)
I wasn’t writing a treatise on every occupation and was being a little jocular.

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?

Re:The product manager role is a mistake by trog on Sunday October 29, 2023 @04:33PM (#38062477)
Couldn't agree more. I didn't really get project management until I'd worked with a few good ones.
Re:The product manager role is a mistake by FireBeyond on Sunday October 29, 2023 @06:23PM (#38063455)
> 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

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).

Re:The product manager role is a mistake by Spooky23 on Sunday October 29, 2023 @10:59PM (#38065224)
It's a little tongue in cheek. There were completion incentives around certain tasks, especially on the construction and physical side, being completed on a date. Date was defined as 4PM on the date, and there was a financial benefit to be early in many cases. The last physical task required to be completed and submitted was done at 3:15, thus "45 minutes early".

That said, some major elements were tracked to the minute. I wish I could share more, it's a great story!

Re:The product manager role is a mistake by moandcompany on Sunday October 29, 2023 @02:23PM (#38061213)
> 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.

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.

Re:The product manager role is a mistake by kcplate on Sunday October 29, 2023 @02:48PM (#38061421)
> 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.

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.

Re:The product manager role is a mistake by moandcompany on Sunday October 29, 2023 @02:52PM (#38061450)
An engineer's understanding of requirements entails determination, evaluation, and articulation of those requirements. Calling oneself an engineer doesn't preclude their ability to do these things, and force them to call themselves a "product manager" for doing so. And quite often, especially at more senior levels, an engineer must do these things.

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...

Re:The product manager role is a mistake by ketzo on Sunday October 29, 2023 @02:58PM (#38061517)
Doesn’t preclude the ability, no, but there are only so many hours in the day.

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.

Re:The product manager role is a mistake by sarchertech on Sunday October 29, 2023 @05:10PM (#38062835)
Once you get to staff+ level, engineers are no longer hired mostly for writing good code.
Re:The product manager role is a mistake by ketzo on Monday October 30, 2023 @02:08AM (#38066211)
That’s fair, but that is… what, 1% of all software engineer hires?
Re:The product manager role is a mistake by sarchertech on Monday October 30, 2023 @08:05AM (#38068351)
I don’t know about as a percent of total hires, because staff+ engineers tend to stick around a bit longer. But in my current bigco it’s a bit north of 10% and I’ve seen it go as high as 20%.
Re:The product manager role is a mistake by TheOtherHobbes on Sunday October 29, 2023 @02:55PM (#38061481)
It does, but it's still not something engineers do well.

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.

Re:The product manager role is a mistake by pseudalopex on Sunday October 29, 2023 @03:44PM (#38061948)
Separating product from engineering, engineering management, and general management does not mean 1 person is in charge. Integrating them does not mean no one is.

The article was all about the consequences of the skill set being incredibly rare.

Re:The product manager role is a mistake by xorcist on Sunday October 29, 2023 @03:59PM (#38062105)
That was well put. Imagine that. Still we train our product managers to follow checklists, write endless documents about personas, have discussions about methodology and such things only loosely connected to the work that goes into making the actual product.

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?

Re:The product manager role is a mistake by saulpw on Sunday October 29, 2023 @04:25PM (#38062383)
> What's our profession's equivalent of a film director?

Scrum master.

Re:The product manager role is a mistake by yCombLinks on Sunday October 29, 2023 @07:19PM (#38063842)
Hardly. Scrum master is more like a production assistant. Make sure everyone knows when and where they are supposed to be. Communicate any issues with the plan
Re:The product manager role is a mistake by ketzo on Sunday October 29, 2023 @02:57PM (#38061493)
Good engineers work to deeply understand the problem given to them. They understand the different possible solutions, and implement the best one they can, given their constraints.

Good product managers identify the problems to be solved, and prioritize which ones should be solved first.

Re:The product manager role is a mistake by namdnay on Sunday October 29, 2023 @03:29PM (#38061778)
> 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.

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

Re:The product manager role is a mistake by marcosdumay on Sunday October 29, 2023 @01:36PM (#38060813)
> maintain relationships with customers, interview users to identify potential features

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.

Re:The product manager role is a mistake by huytersd on Sunday October 29, 2023 @01:57PM (#38060994)
PMs at most companies DO NOT play politics for resource management, the stakeholders are frequently just other departments within the company so there isn’t a lot of maintaining client relationships. TPMs with sales people are generally the ones that maintain relationships with clients. PMs do very little besides put out a high level requirement document that then truly gets fleshed out by the engineering team and the EMs.
Re:The product manager role is a mistake by snapetom on Sunday October 29, 2023 @02:05PM (#38061054)
Every thing you just said rings true. I went from 20 years engineering into engineering management, and took my first PM role last year. I took the role at a twenty year-old software company that's never had good product management, and the place is horrible.

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.

Re:The product manager role is a mistake by Matthias247 on Sunday October 29, 2023 @02:27PM (#38061238)
This certainly sounds like your company is having a gap. But the gap sounds to me more like the lack of technical leadership (a strong lead, principal engineer, etc) than a PM. 10 out of 10 PMs I worked with (and it had been more) wouldn't commend on software architecture and internals and wouldn't prevent the needless complexity and unmaintainability aspects. They can at most point out that feature development and bugfixes are too slow, and then its up to the engineering team to improve on this. But also for 10 out of 10 PMs feature development will always be too slow, since customers are asking for things being done yesterday, so this alone isn't a great indicator that engineering is broken.

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.

Re:The product manager role is a mistake by snapetom on Sunday October 29, 2023 @02:53PM (#38061455)
A lack of engineering leadership is certainly true. As is often told, the VP of engineering enjoyed creating PRs more than actually leading. There has never been an architect.

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.

Re:The product manager role is a mistake by sokoloff on Sunday October 29, 2023 @03:16PM (#38061653)
I don't claim greatness at modern product design/theory, but I'd expect "what version(s) of TLS are supported?" to be primarily an engineering responsibility (say 80-90%) versus a product concern (say 10-20%).
Re:The product manager role is a mistake by d0gsg0w00f on Sunday October 29, 2023 @03:58PM (#38062095)
I think that most "good" engineering managers share the same traits as good Product Managers.

- 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

Re:The product manager role is a mistake by 360walk on Sunday October 29, 2023 @07:12PM (#38063793)
If TLS version support was materially affecting your client’s ability to integrate with your products’ APIs then the Product Manager should have picked this up and worked with the development team on a way to remove this friction.

I can think of a bunch of different ways of solving this that would take a few days to build out.

Re:The product manager role is a mistake by jahewson on Sunday October 29, 2023 @07:14PM (#38063816)
I agree. Founders who are bad engineers surround themselves with non-technical people who don’t question them.
Re:The product manager role is a mistake by aeternum on Sunday October 29, 2023 @02:14PM (#38061130)
In my experience, the vast majority of PMs could not describe the difference between TLS 1.3 and 1.x.

The problems you describe are legit but unless you have extremely technical product managers, hiring more PMs will only make the problem worse.

Re:The product manager role is a mistake by snapetom on Sunday October 29, 2023 @02:55PM (#38061480)
I do believe that the traditional PM role/background should be considered obsolete, especially in software companies. Well-rounded engineers should be in these roles these days.
Re:The product manager role is a mistake by kranke155 on Sunday October 29, 2023 @02:58PM (#38061516)
Are there enough of them?
Re:The product manager role is a mistake by aurareturn on Monday October 30, 2023 @03:57AM (#38066735)
The vast majority of engineers I encountered do not have what it takes to be a good PM. I'm an engineer myself.
Re:The product manager role is a mistake by rewmie on Sunday October 29, 2023 @03:20PM (#38061689)
> In my experience, the vast majority of PMs could not describe the difference between TLS 1.3 and 1.x.

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.

Re:The product manager role is a mistake by aeternum on Sunday October 29, 2023 @04:01PM (#38062135)
Generally it is quite important especially for SaaS. Old TLS will cause SOC2 cert, PCI cert failures and similar. It is the kind of thing that can derail a major deal as often the 'whale' clients are the ones that really care about security certs while smaller companies and startups don't.

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.

Re:The product manager role is a mistake by rewmie on Sunday October 29, 2023 @04:57PM (#38062713)
> Generally it is quite important especially for SaaS.

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.

Re:The product manager role is a mistake by snapetom on Sunday October 29, 2023 @07:50PM (#38064043)
> If not, why should a PM bother about irrelevant details?

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.

Re:The product manager role is a mistake by rewmie on Monday October 30, 2023 @04:54PM (#38075648)
> Because engineering failed to consider these details.

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.

Re:The product manager role is a mistake by BlackJack on Sunday October 29, 2023 @04:14PM (#38062272)
A good PM doesn't have to know the differences, but should understand that mixing encryption protocols is going to break things. Ideally an eng lead would be flagging these issues.
Re:The product manager role is a mistake by simmerup on Sunday October 29, 2023 @03:23PM (#38061716)
How does a company not make any money for 20 years that sounds insane
Re:The product manager role is a mistake by alwa on Sunday October 29, 2023 @03:35PM (#38061847)
I don’t know if it applies to the situation the GP described, but profit != revenue.

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.

Re:The product manager role is a mistake by stcroixx on Sunday October 29, 2023 @09:30PM (#38064708)
I work at a 20 year old company about like this. We’re all comfortable, it’s really nice.
Re:The product manager role is a mistake by snapetom on Sunday October 29, 2023 @07:51PM (#38064053)
cost center
Re:The product manager role is a mistake by swells34 on Sunday October 29, 2023 @03:40PM (#38061909)
Most the problems described here are just bad software engineering. Never seen a PM with any oversight on which DB is used, how shiny the tech is, how the API works, any of that. It definitely seems like there's a lack of coherence and customer focus, which would be in the PM's wheelhouse to deal with, but that's it. Need a better lead engineer with the time and authority to implement good practices.
Re:The product manager role is a mistake by yieldcrv on Sunday October 29, 2023 @04:33PM (#38062474)
the grift is strong with this one.

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.

Re:The product manager role is a mistake by FireBeyond on Sunday October 29, 2023 @06:21PM (#38063433)
> I took the role at a twenty year-old software company that's never had good product management, and the place is horrible. > 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.

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.

Re:The product manager role is a mistake by intelVISA on Monday October 30, 2023 @12:31AM (#38065701)
You can stil be engineering focused (whatever that means) and have strong leadership. The issue is that a person who lacks significant stake in the company (i.e. most) is not going to want to be a strong leader - you're just risking yourself as personally accountable for any failures vs. limited rewards.
Re:The product manager role is a mistake by liquidpele on Sunday October 29, 2023 @02:29PM (#38061259)
> 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.

I’ve never met a PM that did any of that either ;)

Re:The product manager role is a mistake by ryanSrich on Sunday October 29, 2023 @02:35PM (#38061303)
> Very few engineers want to maintain relationships with customers

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.

Re:The product manager role is a mistake by rrrrrrrrrrrryan on Sunday October 29, 2023 @03:06PM (#38061570)
This might make sense for a company with one product, but for a larger company with many products, there's a lot of benefit in having one person per product who understands their product deeply, and can put on any of these hats when required to make the product better.
Re:The product manager role is a mistake by ryanSrich on Sunday October 29, 2023 @03:34PM (#38061837)
Seems like you’d have a lot of overlap if what the PM is doing are the activities I listed, and you also employ the people I listed.

Also, what engineer doesn’t understand the product deeply from both a technical and business perspective? Maybe a contract dev, or a new hire.

Re:The product manager role is a mistake by ako on Sunday October 29, 2023 @04:11PM (#38062239)
It’s about responsibility, the PM is responsible for the success of a product. To achieve this he collaborates with all the parties you mention, but in the end the PM has the responsibility. Key in this is bringing together knowledge of the market, the competitors, the customer problems, the value of a solution to these customers, determining a roadmap that will lead towards a successful product, coordinate launch, service, support, and continuous monitoring of the state of the product (does it have the right features, what is the competition doing, what does sales need to effectively sell the product, etc).

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...

Re:The product manager role is a mistake by sarchertech on Sunday October 29, 2023 @05:27PM (#38062997)
Having one product owner is fine. The problem is that it should be a role someone moves into from one of the disciplines involved. Design, engineering, domain expert etc…

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.

Re:The product manager role is a mistake by ako on Monday October 30, 2023 @04:31AM (#38066913)
Product Owner and Product Manager is not the same, especially in a larger organizations. Product Managers usually dont manage sprint backlogs, as its too fine grained. I often see sprint backlog that contain 20+ stories that add up to 1 customer facing capability/feature.
Re:The product manager role is a mistake by sarchertech on Monday October 30, 2023 @08:12AM (#38068405)
I’m not talking about “product owner” as it’s practiced in shitty scrum orgs.

I mean product owner as in the person responsible for the product.

Re:The product manager role is a mistake by karaterobot on Sunday October 29, 2023 @03:32PM (#38061812)
> That’s what designers are for.

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.

Re:The product manager role is a mistake by nicoburns on Monday October 30, 2023 @08:57AM (#38068904)
> individual designers and engineers are not the right people for that

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).

Re:The product manager role is a mistake by chiph on Sunday October 29, 2023 @03:35PM (#38061848)
A product manager works at a higher level than those roles. They aren't implementers - they collect information, identify needs, create plans, and get approvals. And then direct the roles you mentioned to do the work needed.

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."

Re:The product manager role is a mistake by shuckles on Monday October 30, 2023 @03:31PM (#38074508)
A project manager will do most of that without the unearned self-importance, minus the talking to customers part which should either be done by product marketing or design, depending on the specific business insight you seek.
Re:The product manager role is a mistake by xkcd-sucks on Sunday October 29, 2023 @02:56PM (#38061491)
yeah +1, I used to wear the product manager hat in an engineering role, while working with bad product managers, and so I thought the role was a grift at best. Also dealing with a herd of b2b clients sucked while trying to focus on doing the things we argued about / committed to doing. Then a good PM got hired, he actually understands what's going on / makes the effort to learn, and the life of "Engineering" roles got so much better. It may be significant in this case that product works with engineering in a kind of liason role and doesn't "dictate" much.

Now program managers, it remains to be seen where their value comes from and I hope it does

Re:The product manager role is a mistake by lostdog on Sunday October 29, 2023 @03:51PM (#38062024)
Yeah, the problem is that accountability for PMs is usually missing. No one checks whether the PM is adding or removing effectiveness, so the good PMs go unrecognized and the bad ones keep siphoning energy from the project.

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.

Re:The product manager role is a mistake by PH95VuimJjqBqy on Monday October 30, 2023 @08:41PM (#38078247)
I've legit seen PM's just move their own deadlines. Their decision, no attempt at justification, and I've seen it put everyone behind because they're waiting on the PM. I've legit seen a PM deliver a set of requirements 3 days before a deadline and blame the technical team for non-delivery (multiple times!).

It sounds so ridiculous, and yet ... it happened.

Re:The product manager role is a mistake by ImPostingOnHN on Sunday October 29, 2023 @04:09PM (#38062222)
> Now program managers, it remains to be seen where their value comes from and I hope it does

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

Re:The product manager role is a mistake by iamwil on Sunday October 29, 2023 @02:58PM (#38061519)
What made that one PM great? What did they do or what was their philosophy? The outcome was that they got the team to be more productive, but what was the input that differed from the other PMs?
Re:The product manager role is a mistake by karaterobot on Sunday October 29, 2023 @03:27PM (#38061759)
I can't really say. I'll describe some of the things I observed: they had incredibly good people skills with both customers and coworkers, they had the ability to ask incisive questions, and make good decisions with imperfect information, they context switched smoothly, they were well organized, and they made people excited about what they were working on. They also worked longer hours than anyone I know of at the company.

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.

Re:The product manager role is a mistake by homarp on Sunday October 29, 2023 @04:40PM (#38062550)
>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.

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.

Re:The product manager role is a mistake by nintendo1889 on Sunday October 29, 2023 @04:43PM (#38062578)
So you're saying that the dude fired in 'Office Space' for bringing the specs from customers to engineers was necessary?
Re:The product manager role is a mistake by jokethrowaway on Sunday October 29, 2023 @05:21PM (#38062941)
> 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 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.

Re:The product manager role is a mistake by fooster on Monday October 30, 2023 @12:36AM (#38065731)
Customer relations under sales? Who does that??
Re:The product manager role is a mistake by flockonus on Sunday October 29, 2023 @06:28PM (#38063487)
Want to corroborate, been through several companies and several PMs. The excellent ones are rare, and have disproportionate impact in the team's performance.
Re:The product manager role is a mistake by mitemte on Monday October 30, 2023 @12:28AM (#38065687)
I can relate to this. At my previous company, the first PM our team had was absolutely amazing. She had an engineering background but transitioned to management ten or so years ago. At some point, she was promoted and the replacement PM, while good, was not as good.

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.

Re:The product manager role is a mistake by bazmattaz on Monday October 30, 2023 @03:38AM (#38066639)
As a PM I think this is spot on.

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.

Re:The product manager role is a mistake by xialvjun on Monday October 30, 2023 @03:41AM (#38066650)
> 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.

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.