Skip to article
Bridge

Meetings for product managers: from customer evidence to decisions

A product manager's meetings feed two things: evidence about what customers need, and decisions about what to build. Run discovery interviews around real stories, treat secondhand requests as leads, score options in the open and record what you decided and why. Then the evidence is still findable when someone asks about it months later.

What product managers need from meetings

Marty Cagan of SVPG names four product risks: value, usability, feasibility and business viability. He makes the product manager responsible for value and viability, and accountable for outcomes.

So most PM meetings serve one of two jobs. Some gather evidence that customers will use and buy something. Others decide what the team builds next, and why.

MeetingWhat it should leave behind
Customer discovery interviewSpecific stories, needs and pain points, in the customer's own words
Sales or support reviewLeads to explore in later interviews, not ready-made requirements
Prioritization sessionScores, the reasoning behind them and the chosen next items
Roadmap or stakeholder reviewA decision, what was not chosen and who owns the next step

Discovery interviews: collect stories, not opinions

Teresa Torres of Product Talk teaches story-based interviewing. You ask about specific past behavior, starting with a prompt like "Tell me about the last time you…". Needs and pain points emerge from those stories.

Keep the raw interview, not just your summary. When a teammate questions a finding, you can return to what the customer said.

  • Write one outcome at the top of your interview notes, such as raising first-week activation.
  • Ask about the last real time, not what they usually do or would want.
  • Note each need with the moment it came up, so synthesis has evidence to point to.

Treat sales and support requests as leads

Feature requests also arrive through sales calls and support tickets. Torres notes that these usually lack context, which risks solving the wrong problem. She uses them as inspiration for what to explore in upcoming interviews.

A simple rule works: log the request with the customer's words, then confirm the underlying need in a discovery interview before it reaches the roadmap.

Prioritization meetings: score in the open

A shared scoring method keeps the meeting on evidence rather than volume. Intercom's RICE scores each idea on reach, impact, confidence and effort.

Confidence is the useful one in a meeting. Intercom uses it to curb enthusiasm for exciting ideas that lack data. Ask what evidence supports each estimate, and link the interviews or metrics behind it.

Record the scores and the reasoning. A ranked list without reasons gets reopened every quarter.

Roadmap reviews: record the decision and the trade-off

Stakeholder reviews often end with a nod and no record. Close each one by saying the decision aloud, what was not chosen and who owns the next step.

Write down the trade-off, such as delaying an integration to fix onboarding. When a sales leader later asks why their request slipped, you can show the decision and the evidence behind it.

Example: a request that changed shape

This example is illustrative. Sales reports that three prospects want a bulk-edit feature. The PM logs it as a lead and asks about it in the next four discovery interviews.

The stories show customers bulk-edit mainly to fix records after a messy import. The team scores two options with RICE: bulk edit and a clearer import preview. The import preview wins on reach, and the roadmap review records why.

Keep product evidence findable in Bridge

Bridge records the interviews and reviews you host on Bridge, and captures Zoom, Google Meet and Microsoft Teams calls. Each meeting gets structured notes (summary, decisions and follow-ups) and a speaker-labeled transcript.

Both work on the free Starter plan, where meetings hosted on Bridge are capped at 5 participants and 60 minutes. Starter keeps a limited meeting history. Professional and Business keep it unlimited and add:

  • Spaces: file one product area's meetings and files together. The Space's Assistant answers from that Space's meetings and files.
  • The workspace Assistant: ask across all your notes, with source links back to the meetings each answer drew from.
  • Linear and Asana connections: Bridge can create Linear issues or Asana tasks from a meeting's action items.

Sources & further reading