Requirements Gathering Techniques

Brainstorming & Focus Groups

18 min Lesson 7 of 10

Brainstorming & Focus Groups

Every requirements-gathering toolkit includes at least one technique for generating ideas and another for converging on the right ones. Brainstorming and focus groups fill exactly those two roles. Used well, they surface requirements that no single interview or questionnaire would uncover — hidden frustrations, creative opportunities, and cross-functional conflicts that only emerge when the right people think together in the same room.

This lesson covers how each technique works, when to choose one over the other, and the practical facilitation skills that separate a productive session from a chaotic one.

Brainstorming: Generating Ideas Without Judgment

Brainstorming is a structured group creativity technique in which participants produce as many ideas as possible in a short, time-boxed window, deliberately suspending evaluation until the generation phase is over. The founding principle — defer judgment — is what makes brainstorming different from an ordinary meeting. When people know their idea will be criticised immediately, they self-censor. When they know every idea will be written on the board first and judged later, volume and variety both increase.

Classic format for a requirements session (60–90 minutes):

  1. Frame the problem (5 min): The analyst posts a clear problem statement — e.g., "What should our new clinic booking system allow patients and staff to do?" — visible to everyone throughout.
  2. Silent generation (10 min): Each participant writes ideas individually on sticky notes or a shared digital board. Silence prevents anchoring on the first idea shouted aloud.
  3. Round-robin sharing (15 min): Participants share one idea at a time in turns. Duplicates stay — they signal importance. The facilitator writes every idea exactly as stated, without paraphrasing.
  4. Clarification (10 min): Quick factual questions only — "What do you mean by 'real-time alerts'?" No evaluation yet.
  5. Affinity grouping (15 min): Participants silently move ideas into clusters by theme (e.g., Scheduling, Notifications, Payments, Accessibility).
  6. Dot voting (5 min): Each person places three sticky dots on their most valuable ideas. The result is a visible, democratic priority ranking.
  7. Wrap-up (10 min): Analyst summarises the top clusters and confirms next steps (which ideas proceed to formal requirement writing, which go to the backlog).
Tip — online brainstorming: Tools such as Miro, FigJam, or Microsoft Whiteboard replicate sticky-note brainstorming for distributed teams. Use a timed digital timer visible to all participants and keep the session under 75 minutes — attention fades faster online.
Brainstorming Session Flow Frame Problem 5 min Silent Generation 10 min Round-Robin Sharing 15 min Clarify (no eval) 10 min Affinity Grouping 15 min Vote & Rank 5 min Core Rule: NO evaluation during generation. Every idea goes on the board first — judgment comes only after all ideas are visible. Brainstorming Session — 60-Minute Flow Separate generation from evaluation to maximise idea volume and diversity
The six-step brainstorming flow: frame the problem, generate silently, share in rounds, clarify, cluster by affinity, then vote to prioritise.

Common Brainstorming Variations

The classic format adapts to different team sizes and risk profiles:

  • Brainwriting (6-3-5): Six participants each write three ideas on a sheet in five minutes, then pass it to the next person who adds three more. After six rounds you have up to 108 ideas in 30 minutes — with zero risk of vocal participants dominating.
  • Reverse brainstorming: Instead of asking "How can we improve the online store checkout?", ask "How could we make checkout as painful as possible?" The constraints that make checkout painful become, when inverted, positive requirements. This technique is powerful for uncovering non-obvious pain points.
  • SCAMPER: Prompts the group to Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, or Reverse features of an existing system. Useful mid-project when the team is stuck refining an existing process rather than starting fresh.

Focus Groups: Probing Depth with Targeted Participants

A focus group is a moderated discussion of 5–10 carefully selected participants who share a common role or experience. Unlike brainstorming — which maximises idea volume — a focus group's goal is depth of understanding: why do users feel the way they do, what trade-offs matter most to them, and where do different user segments disagree?

Consider a logistics firm planning a driver-facing mobile app. A focus group of eight long-haul drivers reveals that drivers overwhelmingly want offline capability because rural routes lose signal, yet the product team had assumed always-on connectivity. A single interview might surface this finding; a focus group, with participants building on each other's comments, makes it undeniable — and produces concrete details about which features must work offline.

Focus group structure (90 minutes):

  1. Welcome and ground rules (5 min): No right or wrong answers; everyone's experience is valuable; no names in the report.
  2. Warm-up (10 min): Low-stakes open question — "Describe the last time you booked a medical appointment. What was easy? What was frustrating?"
  3. Core discussion (60 min): 4–6 structured questions moving from general to specific. The facilitator uses probes ("Tell me more", "Does anyone else experience that?") not leading questions.
  4. Prioritisation card sort (10 min): Participants rank a set of proposed features printed on cards — produces tangible priority data.
  5. Wrap-up (5 min): Summary reflection — "We heard X and Y — does that sound right to you?"
Key distinction: A focus group is not a group interview. In a group interview, the facilitator asks each participant the same question individually. In a focus group, the conversation between participants is the data — the facilitator's job is to keep it flowing, not to conduct individual questioning in a group setting.
Brainstorming vs Focus Group Comparison Brainstorming Focus Group Goal: Maximise idea volume Generate as many requirements as possible Goal: Deepen understanding Probe the WHY behind needs and priorities Group Size: 6–12 participants Diverse stakeholders welcome Group Size: 5–10 participants Homogeneous segment (same role/context) Facilitator: Timekeeper + scribe Enforces no-judgment rule; records all ideas Facilitator: Discussion guide Uses probes; keeps conversation balanced Output: Prioritised idea list Feeds requirement backlog directly Output: Insight report + quotes Informs personas, user stories, priorities Best for: Early discovery, greenfield systems, innovation sprints Best for: Validating priorities, understanding user sentiment, trade-off analysis
Side-by-side comparison of brainstorming and focus groups across five dimensions: goal, group size, facilitator role, output, and best-fit scenarios.

Facilitation Skills That Make or Break Both Techniques

The quality of a brainstorming or focus group session is determined far more by facilitation skill than by the topic or the participants. Common facilitation failures — and how to prevent them:

  • HiPPO effect (Highest Paid Person's Opinion): Senior stakeholders can unintentionally shut down contributions from junior staff. Counter with anonymous dot voting, brainwriting (written ideas), or explicitly starting rounds from the most junior participant upward.
  • Anchoring: The first idea stated shapes all subsequent ideas. The silent generation phase directly combats this — participants form their ideas independently before hearing others.
  • Groupthink: Cohesive teams converge on comfortable consensus too fast. Introduce devil's advocate roles or use nominal group technique (individual ranking before group discussion) to surface genuine dissent.
  • Off-topic drift: In focus groups, heated side conversations about unrelated topics can consume the session. The facilitator must redirect — "That's an important point; let's park it on the issues board and return to our question."
Common pitfall: Recording the output of a brainstorming session as a raw list and presenting it to management as "the requirements" bypasses the critical convergence step. Raw brainstorm output is candidate requirements — each item still needs feasibility checking, conflict resolution, and formal specification before becoming a signed-off requirement.

A Worked Example: Online Store Checkout Redesign

An e-commerce company wants to reduce checkout abandonment (currently 68%). The analyst runs a two-hour session combining both techniques:

Phase 1 — Brainstorming (60 min, 10 participants: 3 developers, 2 UX designers, 2 marketers, 1 customer-support lead, 1 logistics manager, 1 product owner): The problem frame is "What would make our checkout experience delightfully fast and trustworthy?" After silent generation and round-robin, the board contains 84 ideas across six affinity clusters: Speed, Trust Signals, Payment Options, Error Recovery, Mobile Experience, and Post-Purchase Communication. Dot voting surfaces 12 high-priority ideas.

Phase 2 — Focus Group (60 min, 7 customers: mix of frequent and occasional buyers): The analyst runs a structured discussion on three of the 12 high-priority ideas, probing trade-offs. The group reveals that "guest checkout without account creation" is valued 3× more than "one-click saved payment" — a finding that would not have appeared in the brainstorm because no customers were present. The focus group also surfaces a strong emotional response to security badges near payment fields, adding a non-functional requirement about trust signals.

The combined output feeds directly into the next sprint's backlog — with evidence-backed priorities rather than the product owner's gut feeling.

Key Takeaways

  • Brainstorming separates generation from evaluation — the defer-judgment rule is not optional, it is the mechanism that produces volume and diversity.
  • Silent generation and dot voting reduce the HiPPO effect and anchoring bias that plague free-form group meetings.
  • Focus groups probe depth — the conversation between participants is the primary data source, not the facilitator's questions.
  • Run focus groups with homogeneous segments; mixing roles in a focus group suppresses honest responses from junior or less vocal participants.
  • Both techniques produce candidate requirements — outputs must pass through feasibility, conflict resolution, and formal specification before entering a requirements baseline.
  • Combine the two: brainstorming for breadth early in discovery, focus groups to validate and prioritise before committing to a solution direction.