Running Effective Meetings

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

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

The Guide

5 key steps synthesized from 2 experts.

1

Define the objective and right-size the group

Clearly document the specific problem the meeting solves and limit the invite list to essential contributors. Ensure the meeting cadence matches the team size and project urgency to prevent burnout and redundancy.

Featured guest perspectives
"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?"
— Lenny Rachitsky
"I’d suggest one to two times a month. The bigger the team, the less frequent. A weekly PM team meeting becomes redundant with your 1:1’s."
— Lenny Rachitsky
"Include the goal of the meeting in your invite, ideally along with an agenda. If you attend a meeting that doesn’t feel productive, call it out. Invite as few people as possible. Leave with clear action items."
— Lenny Rachitsky
2

Prepare asynchronously for discovery

Distribute a structured pre-read or short video clip at least 24 hours in advance to handle information discovery. This allows the synchronous session to be reserved exclusively for discussing differences and making decisions.

Featured guest perspectives
"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."
— Annie Duke
"Use a Loom (or a Slack video clip) when the reason for a meeting is to communicate a nuanced, high-bandwidth concept. Treat your audience like, well, an audience; be intentional about converting them to view and click."
— Lenny Rachitsky
3

Facilitate with structured rituals

Start meetings with a silent reading period and use rituals like Pulse or Dory to collect feedback simultaneously. This levels the playing field and ensures that groupthink does not drown out valuable dissenting opinions.

4

Drive alignment through synthesis

Actively listen and play back stakeholder concerns in your own words to ensure they feel heard before moving toward a decision. Synthesize the discussion at regular intervals to maintain alignment on roadmaps and blockers.

Featured guest perspectives
"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."
— Lenny Rachitsky
"Pay attention to people around you that are good at shipping — how do they run meetings, how do they address issues as they arise, what systems do they use to keep their team aligned?"
— Lenny Rachitsky
5

Close the loop live

Finalize action items and draft meeting summaries in a shared document while the meeting is still in progress. Ask structured questions about accountability at the end to ensure ideas are converted into actual progress.

Featured guest perspectives
"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."
— Lenny Rachitsky
"Include the goal of the meeting in your invite, ideally along with an agenda. If you attend a meeting that doesn’t feel productive, call it out. Invite as few people as possible. Leave with clear action items."
— Lenny Rachitsky

Get this guide as an AI skill for Claude Code

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

Quick Install (Recommended)

Install this skill directly using npx:

npx skills add RefoundAI/lenny-skills --skill running-meetings

Or install all 76 skills:

npx skills add RefoundAI/lenny-skills
View on GitHub →
Manual Installation
1

Download the skill

Download Skill (.zip)
2

Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/running-meetings/SKILL.md
3

Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with running effective meetings

Guest Perspectives

Deep dive into what 1 podcast guests shared about running effective meetings.

Annie Duke 1 quote
Listen to episode →
"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."
Tactical:
  • Complete the 'discovery' phase of information gathering asynchronously before the meeting.
  • Use the actual meeting time strictly for discussing different perspectives and data.
  • Separate information sharing from the final decision to prevent social pressure and the loudest voices from dominating.
View all skills from Annie Duke →