[chasd00]

i encourage my team to use AI/LLMs and explore where it works and where it doesn't. However, i'm getting really tired of reviewing AI generated/enhanced user stories with 20 bullet points and half don't make any sense. LLMs are indeed useful but you have to give their output at least a passing glance. I like the Mr Meeseeks analogy, helpful but they're not gods.

[patrickmay]

A "passing glance" is nowhere near good enough. Just as software developers must be held accountable for every line of code they check in, product managers must be held accountable for every word in their PRDs. LLMs can speed up some parts of the design and delivery process but humans still bear responsibility.

[chasd00]

i meant "passing glance" at the _very very least_ where anything > 0 is so much better than 0. I have people just blindly offloading pretty important analysis to LLM without any review whatsoever and it's super annoying and counter productive resulting in a lot of rework. I've covered refinement with developers trying to meet AC that make no sense. Many times i've just deleted parts of AC (which is a no-no where i live) and flat out told developers "this is bullshit and makes no sense, i'm deleting it."

Same goes for meeting recaps, i get a lot of LLM generated recaps from conference calls. If the meeting organizer just looks at it before sending it out then they'll instinctively edit/fix things a bit to make the recap more concise and accurate. I wish they'd just look at it before sending it.

[bryan_specgit]

Yes, have been sent many .MD files that clearly the prompter (too generous to call them authors) didn't read and expect you to read for them. And too many examples of asking a follow up question only for them to just paste my question to their LLM and send another .MD. Total PM malpractice with AI. No tooling will completely fix bad PMs.