Running Meetings
Help users master the art of facilitating productive, decision-oriented meetings that...
Install
npx skills add RefoundAI/lenny-skills --skill running-meetings -g -a claude-code -y- Repository
- RefoundAI/lenny-skills1.5k
- Category
- Engineering
- Updated
- 4mo ago
- License
- MIT
- Context cost
- Mediumabout 1,570 tokens
- Runs scripts
- No, instructions only
What it does
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
- Audit current meetings - Analyze the purpose and frequency of existing recurring sessions to ensure they solve specific problems that cannot be addressed asynchronously.
- Design the agenda - Structure sessions with clear objectives, silent reading periods, and psychological safety rituals to maximize participation.
- Facilitate real-time alignment - Use active listening and synthesis techniques to ensure stakeholders feel heard and blockers are surfaced.
- 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.
