Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI Product Management

deeplearning.ai

Post reply on HN
Print view View original

31–40 of 45 posts

Re: AI Product Management

#31

Post by ben_w »

zarathustreal wrote: post #23
SilverBirch wrote: post #12

I'm not sure some of this is a good idea. It reads a bit like "These LLMs are great! We can get rid of those pesky engineers!". It reminds me of the xkcd[1] about how some problems are trivial and some are almost impossible and as a layman you don't know which is which. That's more true than ever will LLMs, everything is new and so very few people actually know what is easy and what is hard. When you say "You can go…

Well I think it’s as simple as P vs NP. This is the primary difficulty with AI and always will be. Solutions are easy to get AI to construct. The difficulty is in verifying those solutions. This can be seen in industry even now, evals are the hardest part of non-trivial AI systems

I agree, but I think this also forms part of the solution: try to always ask the AI to create things which are easy to verify.

Re: AI Product Management

#33

Post by eichi »

ivanmontillam wrote: post #28
dartos wrote: post #24

Earlier quoted context omitted.

Advocating for waterfall? Not every product can be totally designed and spec’d out from the outset. Especially when time to market is important. Maybe this works at the individual feature scale, but at any reasonably large product, designing _everything_ from the outset would result in brittle design.

> Not every product can be totally designed and spec’d out from the outset I'd argue that no product can be spec'd 100% from the outset. Not even something like the regular Notepad.exe. You'll always find some hidden complexity overlooked that results in the revision of the spec at the middle of development. Embrace the change.

There is common misconception among engineers about agile.

Agile is for reducing bunch of implementation docs. Your heavily crafted implementation docs will be gabage since implementation can be changed easily. However, we still need to define requirements and specs so that we won't create things no one want.

Re: AI Product Management

#34

Post by esel2k »

The only thing that article says is: With AI you can iterate more rapidly/make prototypes faster.

Nothing new - we heard the same message with Figma, containerisation… you name it.

Having a good sense what problem solve, building rapport and trust with early customer and being a fantastic leader and communicatore has always been the most important skills. Thanks, nothing to see here…

Re: AI Product Management

#35

Post by n4r9 »

esel2k wrote: post #34

The only thing that article says is: With AI you can iterate more rapidly/make prototypes faster. Nothing new - we heard the same message with Figma, containerisation… you name it. Having a good sense what problem solve, building rapport and trust with early customer and being a fantastic leader and communicatore has always been the most important skills. Thanks, nothing to see here…

You came away with a completely different understanding to the article than I did! I took it to be

"here's some guidelines for being a PM of an AI dev team"

Rather than

"Here's how to use AI to be a better PM"

Re: AI Product Management

#36

Post by n4r9 »

eichi wrote: post #33
ivanmontillam wrote: post #28

Earlier quoted context omitted.

> Not every product can be totally designed and spec’d out from the outset I'd argue that no product can be spec'd 100% from the outset. Not even something like the regular Notepad.exe. You'll always find some hidden complexity overlooked that results in the revision of the spec at the middle of development. Embrace the change.

There is common misconception among engineers about agile. Agile is for reducing bunch of implementation docs. Your heavily crafted implementation docs will be gabage since implementation can be changed easily. However, we still need to define requirements and specs so that we won't create things no one want.

> Your heavily crafted implementation docs will be gabage since implementation can be changed easily.

I've heard this before but I'm not convinced. I'm sure lots of product teams use Agile and still manage to have thorough, up to date docs. You just need to factor doc updates into your issues.

Re: AI Product Management

#37

Post by mlnj »

shard wrote: post #30
mlnj wrote: post #16

Earlier quoted context omitted.

100% A couple of cron jobs can easily automate this for my team. Most of the PMs I've seen in the wild only do this. Very few PMs are actually valuable to a team from the product perspective.

Is it me or does this sound like a Project Manager and not a Product Manager? Where is the discussion and negotiation with customers and engineering teams on specs/targets/requirements? Where is the roadmap alignment with strategy and marketing teams? Where is the discussion with research teams on future features? Product managers don't babysit engineering teams on their deliverables. Calling someone doing the work l…

>Calling someone doing the work listed on the grandparents post a product manager does not make them one.

Despite this, so many individuals stick around and try to make scrum their entire personality. It's insufferable at times to be around folks who do not even want to talk about customers or the product specifics.

Re: AI Product Management

#38

Post by noworriesnate »

lifeisstillgood wrote: post #8

I often bang on about Software as a new form of literacy - and that just as organisations that were staffed by literate people (Catholic churches, nation states, banks) were qualitatively different to organisations without literacy (stonemasons?) then software literate companies (I call them programmable companies in my upcoming book) will be different from the ones we know today. And this is an example I feel of the…

Yeah but product management work has to happen prior to implementing the product. It sounds like you're saying you should implement the software first, then do product management on it.

Re: AI Product Management

#39

Post by gigatexal »

senko wrote: post #27
gigatexal wrote: post #13

Cron: bug devs about tickets that are late Cron: bug devs every day at a given time for updates aka a standup Given an epic with keywords organize tasks into that epic and estimate the time and then track if it’s on track or not. Yeah not a lot to PM work. Ooh also a 50/50 coin flipper to saying no to adhoc things There that’s an AI PM

That's project management, not product management.

I’ll admit a good PM does interface well with stakeholders and gets them to finally agree to what they really need and to flesh out the requirements.

Otherwise it’s a role not too many teams need but when you need one you know it and you really need one.

Post reply on HN