You Asked 'What Do You Think?'. You Should Have Asked 'What's the Biggest Risk?'

You hit "Share." The doc is a thing of beauty. A tight problem statement, crisp user stories, a logical flow. You drop the link in Slack with a cheerful, “New PRD for Project Nightingale. Would love your feedback!”

You feel good. Collaborative. Open.

You come back an hour later. It’s a bloodbath.

Twenty-seven comments. The engineering lead is questioning the core premise. The designer left a dozen nitpicks about copy you considered placeholder. Someone from marketing is asking if this could be an AI feature. Two people are having a debate about a technical detail in a thread. Your clean, beautiful document now looks like a crime scene.

You just wanted feedback. You got a free-for-all.

The problem wasn't your doc. It was your question. "What do you think?" is one of the laziest, most dangerous questions a product manager can ask. It’s a blank check for unfocused opinions, bikeshedding, and scope creep. It invites everyone to poke holes without offering solutions. It turns your collaborators into critics instead of partners.

You don't need more opinions. You need specific, high-quality input that makes the plan better. To get that, you have to stop asking for feedback and start directing it.

From Open Mic to Guided Tour

When you share a doc, you are not a student turning in homework to be graded. You are a facilitator running a workshop. Your job is to give each person a clear role and a specific task. You need to channel their expertise toward the areas where you need it most.

Instead of a single, open-ended question, give your stakeholders a menu of targeted prompts.

For your Engineering Lead:

• Don't ask: "Does this look right to you?"