meeting facilitation

Meeting Facilitation Skill

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "meeting facilitation" with this command: npx skills add danhvb/my-ba-skills/danhvb-my-ba-skills-meeting-facilitation

Meeting Facilitation Skill

Purpose

Run productive, focused meetings that achieve their objectives. A critical soft skill for BAs who spend 30-50% of time in workshops and interviews.

Types of BA Meetings

  • Discovery/Elicitation: "Tell me what you need."

  • Workshop: "Let's solve this problem together."

  • Review/Walkthrough: "Is this correct?"

  • Prioritization: "What comes first?"

  • Sign-off: "Do you agree?"

The 3 Ps of Facilitation

  1. Preparation (Before)
  • Purpose: Why are we meeting? (If no purpose, cancel).

  • Product: What is the output? (e.g., A list of requirements, a process map).

  • People: Who must be there? (Decision makers, SMEs).

  • Process: Agenda. How will we work?

Agenda Template:

  • Introduction (5m): Goal, Rules.

  • Context (10m): Where we are now.

  • Activity/Discussion (40m): Brainstorming, Mapping, etc.

  • Review (10m): Validate findings.

  • Next Steps (5m): Action items.

  1. Performance (During)
  • Start on time.

  • Set Ground Rules: "No phones", "One conversation at a time", "No bad ideas".

  • Manage Time: Use a timer (Timeboxing).

  • Manage Personalities:

  • The Dominator: "Thanks John, I want to hear what Sarah thinks."

  • The Silent One: "Mike, how does this affect your team?"

  • The Tangent: "Great point, let's park that in the Parking Lot to stay on track."

  • Visuals: Use whiteboards, screen sharing. Don't just talk.

  1. Processing (After)
  • Send Minutes: Within 24 hours.

  • Action Items (3Ws): Who does What by When.

  • Parking Lot: Follow up on parked items.

Facilitation Techniques

Brainstorming

  • Rules: Quantity over quality initially. No judgment.

  • Method: Sticky notes (Miro/FigJam). 1 idea per note. Group affinity mapping.

Root Cause Analysis (5 Whys)

  • Keep asking "Why" to dig deep into a problem statement.

Fist of Five (Voting)

  • Quick consensus check.

  • 5 fingers: Love it.

  • 3 fingers: Okay with it.

  • 1 finger: Block/Disagree.

  • Result: If anyone shows < 3, stop and discuss constraints.

Dot Voting

  • Give everyone 3 dots.

  • Place dots on ideas they like best.

  • Visual heat map of priorities.

Handling Difficult Situations

  • Deadlock: "Let's list the pros/cons of both options." or "Can we try Option A for 2 weeks?"

  • Disengagement: Call a break. Ask a provocative question. Change the format.

  • Conflict: Acknowledge valid points on both sides. Focus on the problem, not the person.

Tools

  • Lark Meetings: Auto-notes/recording.

  • Miro/Mural: Virtual whiteboarding.

  • Voting Tools: Polls inside Zoom/Lark.

Checklist for Success

  • Is the goal clear?

  • Are the right people invited?

  • Is the agenda sent in advance?

  • Did we capture Action Items?

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

process mapping

No summary provided by upstream source.

Repository SourceNeeds Review
General

double diamond design

No summary provided by upstream source.

Repository SourceNeeds Review
General

data modeling

No summary provided by upstream source.

Repository SourceNeeds Review
General

user story writing

No summary provided by upstream source.

Repository SourceNeeds Review