PMs: How do you deal with vague requirements?
I’ve seen a lot of people lately saying requirements management is becoming “just throw a prompt into Claude Code” or that requirements are so vague engineers end up figuring things out as they build.
As a CS student who’s been trying to learn more about product management, I’m curious how this actually works in practice.
When requirements are vague or constantly changing, how do you usually manage them? Do you keep everything in Jira, Confluence, Notion, PRDs, or somewhere else? How much back-and-forth happens before engineering starts building?
I’m mainly interested in hearing how experienced PMs keep everyone aligned when requirements aren’t crystal clear.
u/Far-Reality-3659 — 10 days ago