running-meetings — скилл для Claude Code: как вести встречи

---
name: running-meetings
description: Help users master the art of facilitating productive, decision-oriented meetings that unblock teams, strengthen interpersonal bonds, and accelerate shipping velocity.
---

# Running Effective Meetings

Transform calendars from soul-crushing time-sinks into high-velocity alignment machines.

Help the user with running effective meetings using insights from 12 guests and posts across Lenny's Podcast and Newsletter.

## How to Help

1. **Audit current meetings** - Analyze the purpose and frequency of existing recurring sessions to ensure they solve specific problems that cannot be addressed asynchronously.
2. **Design the agenda** - Structure sessions with clear objectives, silent reading periods, and psychological safety rituals to maximize participation.
3. **Facilitate real-time alignment** - Use active listening and synthesis techniques to ensure stakeholders feel heard and blockers are surfaced.
4. **Streamline post-meeting debt** - Implement rituals to finalize action items and documentation during the meeting rather than after it.

## Core Principles

### Separate discovery from decision
Annie Duke: "People generally think the purpose of a meeting is for three things, discover, discuss, decide. The only thing that's ever supposed to happen in a meeting is the discussion part."

Complete the information gathering phase asynchronously before the meeting starts so synchronous time is reserved for high-value debate and final choices.

### Prioritize psychological safety
From "Ideal sprint length, designer vs. PM roles, running PM team meetings, running post-mortems, best product/executive coaches, and much more": "Our PM team has a section carved out for “what feels hard [harder than it should be]?” The purpose of this section is to discuss sticking points up and down the stack: troubleshooting comms with Team X; doing a teardown of a PRD that has raised unexpected questions and gotten “stuck”; trying on versions of a Vision/Strategy."

Create a dedicated space for vulnerability where team members feel safe to surface what is hard and seek help from their peers.

### Solve for administrative debt
From "Product manager is an unfair role. So work unfairly.": "Instead of adding action items from meetings to a to-do list, do the action items *live in the meeting*. With everyone watching. While screensharing."

Complete small tasks and alignment rituals during the meeting to prevent the accumulation of follow-up work and ensure immediate momentum.

### Validate before aligning
From "A PM’s guide to influence": "People often won’t listen to you until they feel that you’ve fully heard them. When people don’t think you deeply understand their POV, they often become obsessed with repeating their points more forcefully instead of hearing yours."

Use active listening and playback techniques to ensure stakeholders feel heard, which prevents defensive responses that block consensus.

### Audit for intentionality
From "Leading a PM team meeting - Issue 19": "Don’t do this meeting just to do it. Make certain that adding (or continuing this meeting) is consistently worth everyone’s time. What problem are you trying to solve?"

Only maintain recurring meetings that solve a specific problem that cannot be addressed more efficiently through other channels.

## Templates & Frameworks

- **PM Team Meeting Agenda Template** (Ideal sprint length, designer vs. PM roles, running PM team meetings, running post-mortems, best product/executive coaches, and much more) - A structured weekly PM team meeting agenda designed to increase transparency, psychological safety, and PM output
- **Dory and Pulse** (My favorite decision-making frameworks) - A two-part meta-framework for supercharging real-time decision-making in meetings by equalizing voices and removing groupthink, with 14 documented variations.
- **Note-and-Vote Decision-Making Technique** (Introducing the Foundation Sprint: From the creators of the Design Sprint) - A fast group decision-making method that prevents groupthink by requiring individual silent thinking before group discussion
- **Live-in-Meeting Action Item Checklist** (Product manager is an unfair role. So work unfairly.) - A list of action items PMs can complete live during meetings while screensharing, instead of adding them to a post-meeting to-do list.
- **WWW (Who/What/When) Action Clarity Test** (Introducing the GAIN framework for feedback: an evidence-based approach to giving feedback that people love, appreciate, and act on) - A simple three-word test to ensure action items from any meeting or conversation are actually actionable
- **Meeting Effectiveness Checklist for PMs** (Startup PM vs. big company PM) - A step-by-step checklist for running productive meetings as a product manager
- **PM Team Meeting Frequency Guide** (Leading a PM team meeting - Issue 19) - Guidelines for choosing the right cadence for PM team meetings based on team size
- **Exquisite Exec Team Meeting Format** (Matt Mochary) - A meeting structure designed to reduce a 3-hour meeting to 45 minutes by using asynchronous pre-reads.

See `references/artifacts.md` for the full list with details.

## Questions to Help Users

- "What is the specific problem this meeting is intended to solve?"
- "Could this information be communicated more effectively via a short video or asynchronous document?"
- "Who is the absolute minimum group of people needed to reach a decision?"
- "What artifacts or data must participants review before the meeting begins?"
- "How will you ensure that every participant feels safe enough to share their honest perspective?"
- "What ritual will you use to finalize action items before everyone leaves the room?"

## Common Mistakes to Flag

- **Status report syndrome** - Using synchronous time for one-way information sharing that could have been a dashboard or email.
- **Ambiguous ownership** - Ending a meeting without a clear owner and deadline for every discussed action item.
- **Ignoring the human element** - Focusing solely on the tactical agenda while neglecting team connection and psychological safety.
- **Passive facilitation** - Allowing the loudest voices to dominate the conversation rather than using structured rituals to surface all perspectives.

## Deep Dive

For all 19 sourced insights from 12 guests, see `references/guest-insights.md`

## Related Skills

- Product Reviews
- Executive Communication
- Managing Up
- Written Communication