JobCannon
Tutte le competenze

Meeting Facilitation

Running productive meetings that drive decisions and action

⬢ LIVELLO 2Competenze trasversali
+$10k-
Impatto sullo stipendio
4 mesi
Tempo di apprendimento
Facile
Difficoltà
3
Carriere
In sintesi

Meeting facilitation is the meta-skill of running 30-minute reviews instead of 90-minute rambles. Essential for PMs (sprint planning), EMs (team ceremonies), scrum masters (cadence), and leaders in async-first cultures where synchronous time is expensive. Core sub-skills: agenda design, decision capture (RACI), time-boxing, and managing dominant voices. Correlates strongly with promotion (managers who run tight meetings ship 40% faster). Improves decision-velocity and reduces meeting load by 50% when done right. Salary bump: +$10-20k for IC; +$15-30k for managers who scale via better meetings.

Cos'è Meeting Facilitation

Meeting facilitation is the skill of designing and running meetings that achieve their purpose efficiently. In an era of meeting overload, professionals who run focused, well-structured meetings that end with clear decisions and action items are invaluable. The average professional spends 31 hours per month in unproductive meetings. A skilled facilitator can cut meeting time by 50% while improving outcomes through proper preparation, structured agendas, and disciplined follow-through.

🔧 STRUMENTI ED ECOSISTEMA
MiroMuralFigJamLucidsparkZoomGoogle MeetOtter.aiFellowHugoHypercontextRange

🎓 Certificazioni

IAF Certified Professional Facilitator
Liberating Structures
Lean Coffee
Agile Coaching ICF

🎯 Carriere che usano Meeting Facilitation

Community Organizer
Design Ops Manager
Product Operations Manager

❓ Domande frequenti

Should you have this meeting at all?
Default to 'no'. Before scheduling, ask: What decision must we make? Could email/Slack make it? If you need real-time debate (not just alignment), schedule it. If it's status updates, async doc. If it's brainstorm, time-box to 30min. Litmus test: 'In 3 months, will this meeting be what caused us to ship faster?' If no, kill it.
What is a decision matrix and RACI?
RACI = Responsible (does the work), Accountable (approves), Consulted (gives input), Informed (gets notified). Document before the meeting. FigJam RACI template: draw roles across columns, map decisions to rows, color-code. Decision matrix: rows = options, columns = criteria (speed, cost, risk). Score each. Outcome: less 'but what about' in the meeting, more 'we picked #2 for these reasons.'
When should meetings go async?
Async wins when: (1) no real-time debate needed, just alignment on written proposal; (2) participants span >3 timezones; (3) decision deadline is >48hrs away; (4) meeting was pure update/information. Turn it into a doc, Slack thread, or async Figma review. Loom video for nuance instead of live call.
How do you time-box without cutting people off?
Announce the cap upfront: 'We have 20 min, goal is X decision. If we can't decide, we table and async.' Use a visible timer (FigJam timer, Miro stopwatch). When 5min left, say 'Final thoughts, then we decide.' Respect the box, people hate watching meetings that should've been 30min stretch to 60min. If the topic needs more time, that signals the framing is wrong; fix the agenda, not the clock.
How do you manage one person dominating the discussion?
Prep matters. Limit speakers upfront: 'Each person 2 minutes, then we go around table.' Use written input first (Figma/FigJam 10 min of quiet brainstorm), then discuss. In real-time, use the parking lot: 'That's a great point, let's note it and come back if we have time.' Name the pattern once (not publicly): offline message: 'I notice you have a lot of energy on this, could we hear from others?' Have a quiet-voice rule: introverts share first, then open floor.
How do you capture decisions so they don't get lost?
Send summary within 1 hour. Format: (1) Decision made, (2) Why (trade-offs), (3) Owner + deadline, (4) 'What changes because of this.' Use Fellow or Hypercontext to auto-capture and assign action items in meeting. 80% of meeting value comes from the written record. No summary = meeting happened, no decision actually landed.
How do you handle distributed teams across timezones?
Never default to live sync. Instead: (1) async proposal in a doc, (2) Slack/email feedback window (24h), (3) live sync only for nuance/debate. Record every sync for async viewers. Rotate meeting times if recurring. Consider: APAC 8am = EMEA noon = Americas midnight. Accept that someone's time is bad; pick <2x/week. Use async tools first: Figma, FigJam, Google Docs with comments, live meetings are for decisions that actually need debate.

Non sei sicuro che questa competenza faccia per te?

Fai il Career Match — ti suggeriremo i percorsi giusti.

Trova le competenze adatte a te →

Trova il tuo percorso di carriera ideale

Abbinamento basato sulle competenze per 2521 carriere. Gratis, ~3 minuti.

Fai il Career Match — gratis →