Running Meetings

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.