Skip to article
Bridge

Run requirements-gathering meetings that end in a reviewed spec

Requirements gathering turns what stakeholders say in meetings into a document they have reviewed and agreed, then into work the team can track. The hard part isn't the meeting. It is capturing each requirement with who asked for it and how you'll know it's met, and getting stakeholders to confirm the draft before anyone builds.

What this workflow produces

IIBA's BABOK Guide describes business analysis as defining needs and recommending solutions that deliver value to stakeholders. Requirements meetings are where those needs get stated, by the people who request, approve, operate or support the change.

This page is about those stakeholders. Research with end users and proposals for a client are different jobs, with their own pages.

  • A requirements document that each stakeholder has reviewed.
  • An open-questions list with an owner for each answer.
  • Work items in your tracker, each linked back to the requirement it delivers.

Before: decide whose requirements you need

A missed stakeholder is an expensive gap, because their requirement can surface after the build starts. List the roles first, then decide what each one can tell you.

Send the problem statement and the questions ahead, in the calendar invite, so people come with examples instead of opinions.

StakeholderWhat to ask them for
Sponsor or budget ownerThe goal, how success will be measured and what is out of scope
People who do the work todayThe current process step by step, including the workarounds
Security, legal or complianceRules the solution must follow, and who signs off
Support or operationsWhat breaks today and what they will need to run the new thing
Engineering leadConstraints, existing systems and rough cost of the options

During: ask for the goal, the rule and the exception

A requirement without a reason is hard to test and easy to gold-plate. For each one, get three things on the record before you move on.

  • The goal: why the stakeholder needs it. The GOV.UK Service Manual calls the goal the most important part of a user story.
  • The rule: what the system must do, in the stakeholder's words.
  • The exception: ask "what happens when…" for the unusual cases, such as a missing approver or a refund over the limit.
  • The test: restate it as acceptance criteria. GOV.UK suggests writing them as a list that starts "it's done when…".
  • The status: say aloud whether it is confirmed, an assumption, or in conflict with another stakeholder.

An illustrative requirements document outline

This outline is a starting point, not a standard. Adapt the sections to how your team reviews and builds.

SectionWhat goes in it
Problem and goalOne paragraph on the problem, and the measure the sponsor will judge success by
StakeholdersWho was consulted, their role, and who approves the document
ScopeWhat is in, and what is explicitly out
RequirementsOne row each: ID, requirement, reason, source stakeholder and meeting, acceptance criteria, priority
ConstraintsRules, systems and deadlines the solution must respect
AssumptionsWhat you believe but haven't confirmed, and who can confirm it
Open questions and conflictsEach with an owner, a due date and who decides
Review recordWho reviewed which version, and when they approved it

After: draft from the transcript, then review it

Write the first draft from the transcript, not from memory. Memory keeps the requirements you agreed with and drops the exceptions.

Then send the draft to each stakeholder with their own requirements highlighted. Ask them to confirm, correct or reject each one by a date. Conflicts go to the person named as the decider, not to a vote.

Example: one requirement, from meeting to work item

This example is illustrative. Northwind's finance team wants an expense approval tool. Here is how one requirement moves through the workflow.

StageText
Said by the finance controller"Anything over the limit has to go to me, obviously."
Exception found by asking"What if you're on leave?" "Then my deputy approves."
Requirement R-07Expenses above the team limit route to the finance controller, or to a named deputy when the controller is marked as away.
Acceptance criteriaIt's done when an over-limit expense reaches the deputy while the controller is marked away.
Status after reviewConfirmed by the controller; the limit amount is an open question owned by the sponsor.
Work itemRoute over-limit expenses to controller or deputy (R-07)

Doing this in Bridge

With a calendar connected, Bridge builds a Brief for each upcoming meeting from the event, the attendees, earlier conversations and connected tools. A Brief can include the agenda, previous action items and participant context. Agenda, history and participant context need a paid plan; Starter gets limited preparation.

During the meeting, the Conversation panel shows the live transcript. Afterwards you get structured notes, the full speaker-labeled transcript and an Assistant scoped to that meeting.

  • Write your questions in the Brief's private Notepad. Keeping the Notepad open during the live call, and the live Artifacts panel, need a paid plan.
  • Ask the meeting's Assistant to list every requirement stated, who stated it and the exceptions raised. Check each one against the transcript before it goes in the draft.
  • On a paid plan, save that request as a custom prompt in Preferences so every session uses the same wording.
  • With Notion or Google Docs connected, the Assistant can create a page or document from the meeting notes as your first draft.
  • After review, choose Plan and execute next steps. Agent steps can create Linear issues, ClickUp tasks or Notion pages, and you approve, revise or skip each one.
  • Asana tasks can be created from meeting content, and the GitHub connector can create issues from Bridge.
  • Plans: full Brief context, the live Notepad and Artifacts, custom prompts, GitHub, productivity and project connectors, and workflow plans are not on the free Starter plan.

Sources & further reading