Skill

Review

Audit score 70

running-effective-meetings

refoundai/lenny-skills

Help users run more effective meetings using frameworks from 40 product leaders.

What is running-effective-meetings?

This skill helps you eliminate meeting waste and improve decision-making by applying proven frameworks from experienced product leaders. Use it when facing meeting overload, preparing important meetings, struggling to get decisions made, or wanting to improve your meeting culture.

Question whether meetings are necessary or could be handled asynchronously
Clarify meeting purpose (discovery, discussion, or decision) and design appropriate structure
Separate strategic from operational meetings to avoid mixing unstructured discussion with structured updates
Ensure decisions are captured with clear ownership and communication using standardized closing questions
Implement engagement techniques like state changes every 3-5 minutes to maintain focus in virtual settings
Use pre-reads and async updates to compress meeting time and improve preparation

How to install running-effective-meetings

npx skills add https://github.com/refoundai/lenny-skills --skill running-effective-meetings

Claude Code

Cursor

Windsurf

Cline

How to use running-effective-meetings

1.When a user asks about meetings, first question whether the meeting is necessary or could be resolved asynchronously
2.Determine the meeting's purpose: is it for discovery, discussion, or decision?
3.Design the structure with appropriate agenda and pre-work requirements
4.Identify the decision-maker and ensure all attendees know who that is
5.Plan how you'll capture decisions and next steps before the meeting ends
6.End the meeting by answering three questions: What did we decide? Who does what by when? Who else needs to know?

Use cases

Good for

Reducing meeting overload by identifying and eliminating non-essential recurring meetings
Preparing for high-stakes strategic decisions using time-boxed workshop approaches
Converting status update meetings to async with pre-reads and silent reading time
Improving decision quality by establishing shared context before jumping to conclusions
Increasing meeting engagement in virtual settings through structured state changes and interaction

Who it's for

Product managers and leaders managing team meetings
Executives preparing for strategic decision-making sessions
Team leads struggling with meeting culture or decision velocity
Anyone dealing with calendar overload from excessive meetings

running-effective-meetings FAQ

Should all three types of meetings (discovery, discussion, decision) happen synchronously?

No. According to Annie Duke's framework, only the discussion part should happen in meetings. Discovery and decision-making should happen asynchronously to preserve synchronous time for actual dialogue.

How do I reduce a 3-hour meeting to 45 minutes?

Require attendees to submit written updates and proposed solutions before the meeting, then dedicate the first part to silent reading. This shifts status updates to async and focuses synchronous time on discussion.

How often should I use state changes in virtual meetings?

Punctuate monologues with state changes (polls, chat prompts, speaker changes) every 3-5 minutes to maintain engagement and keep your audience attentive.

What's the difference between strategic and operational meetings?

Strategic meetings are open-ended with time for discussion, while operational meetings are highly structured for going through priority projects. Don't mix these two types.

What are the most common meeting mistakes?

Status update meetings using synchronous time, meetings without clear purpose, skipping context-setting before decisions, not documenting outcomes, and including too many attendees which reduces candor.

Full instructions (SKILL.md)

Source of truth, from refoundai/lenny-skills.

name: running-effective-meetings description: Help users run more effective meetings. Use when someone is dealing with meeting overload, wants to improve meeting culture, is preparing an important meeting, or struggles to get decisions made in meetings.

Running Effective Meetings

Help the user run more effective meetings using frameworks from 40 product leaders.

How to Help

When the user asks for help with meetings:

Question the meeting's necessity - Ask if this could be async or if a meeting is truly needed
Clarify the purpose - Determine if it's for discovery, discussion, or decision
Design the structure - Help them create an appropriate agenda and process
Ensure follow-through - Guide them on capturing decisions and next steps

Core Principles

Separate strategic from operational meetings

Naomi Gleit: "We have one weekly sort of strategic meeting. It's more open-ended, there is time for discussion... We also have one weekly operational meeting, which is highly structured where we go through all of the priority projects." Don't mix unstructured strategic discussion with structured operational updates.

Meetings are only for discussion

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." Discovery and decision-making should happen asynchronously. Reserve synchronous time for actual dialogue.

End with three questions

Alisa Cohn: "My three questions to end the meeting are, what did we decide here? Who needs to do what by when? And who else needs to know?" Ending meetings with standardized questions ensures alignment and prevents re-meetings.

Don't skip the priming phase

Evan LaPointe: "Meetings, generally speaking, are a combination of priming and decision making... A lot of meetings skip the priming step altogether." Most meeting dysfunction stems from skipping context-setting. Explicitly include a priming phase before diving into decisions.

Clear the calendar for important decisions

Jake Knapp + John Zeratsky: "The big idea with a design Sprint is to go from a zero to a prototype and a test of that prototype in just five days. And it's a recipe, it's a scripted set of activities." High-stakes strategic decisions benefit from time-boxed, calendar-cleared workshops.

Minimize meetings ruthlessly

Gibson Biddle: "Minimize meetings, okay? Minimize meetings. That sucks the life out of everybody, including you." Protect productivity by actively removing non-essential meetings. A full calendar is a badge of shame, not honor.

State changes maintain engagement

Wes Kao: "The state change method is that you should punctuate your monologues with state changes. So state changes are anything that shakes your audience awake." In virtual meetings, break up monologues every 3-5 minutes with polls, chat prompts, or speaker changes.

Pre-reads shift status updates to async

Matt Mochary: "If everyone pre-prepared their update... we could take a three hour meeting down to a 45 minute meeting." Require attendees to submit written updates and proposed solutions before the meeting. Dedicate the first part to silent reading.

Questions to Help Users

"Does this meeting need to happen, or could this be resolved async?"
"What's the purpose of this meeting: discovery, discussion, or decision?"
"What pre-work should attendees complete before the meeting?"
"Who is the decision-maker, and does everyone know that?"
"How will you capture and communicate decisions after the meeting?"
"What would need to be true for you to cancel this recurring meeting?"

Common Mistakes to Flag

Status update meetings - Using synchronous time for information that could be shared async
No clear purpose - Meetings without explicit objectives
Missing priming - Jumping to decisions without establishing shared context
No documented outcomes - Ending without capturing what was decided and who's doing what
Too many attendees - Every additional person reduces candor and increases cost