Page 150 · Module 06, Build Your Team · this screen continues that page
All 108 frameworksMeeting Design - Meeting OS
Make every meeting earn its time or cancel it
The prompt
Copy & paste readyLabelsReplace theseSwap the role below
Pro tip, from the book
The most productive meeting reform any team can make is adding a mandatory read- out at the end of every meeting: 'What did we decide? Who owns each action? By when?' This 3-minute habit prevents the most common meeting failure, leaving with different understandings of what was agreed.
Who should run this prompt
Module role profileWho should advise on people and leadership decisions? Leadership decisions are the highest-leverage decisions in any organisation — and the hardest to get right because the stakes are human. The roles on this page bring the perspectives of people who have seen hundreds of teams succeed and fail. Use them before hiring, before giving difficult feedback, before restructuring, and before having the conversations you have been avoiding.
Choose any role to drop it into the prompt above. Only the highlighted opening clause changes — the rest of the prompt stays exactly as printed.
◆◆◆◆◆ → ◆ seniority, board level down to specialist◈ outside the organisation
How to make any role sharper
- Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
- Add what they care most about: "You care most about [X]" shapes every word of the output.
- Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
Use this when
The problem it solvesYour team spends too much time in meetings that end without clear decisions or actions. People leave unclear on what was agreed, who will do what, or why the meeting needed to happen at all.
How the framework works
From the printed pageDrawing from Patrick Lencioni's work on organisational health and broader meeting efficiency research, the Meeting OS is a set of design principles for every recurring and ad hoc meeting: define the meeting type (decision, discussion, update, or brainstorm), set the agenda 24 hours in advance, start with the most important item first, assign one facilitator, end with explicit decisions and owners recorded, and send a summary within an hour. AI can design a complete meeting operating system for any team structure.
The method, in four moves
Do these in orderDefine the type of every standing meeting most teams mix types and get the worst of each.
Put the hardest agenda item first energy and attention decline through a meeting, not increase.
End every meeting with the read-out: what was decided, who owns it, by when.
Audit all standing meetings quarterly, cancel any that have become status updates disguised as collaboration. Sending a summary within an hour doesn't mean the meeting worked. If the read-out says "we discussed X" instead of "we decided X, owner Y, by Z," the meeting still didn't earn its time. A Read-Out Isn't a Decision
Where the framework comes from
Patrick Lencioni, Death by Meeting, 2004 · Meeting efficiency research
Pairs well with
As printed with this frameworkModule 06 — Build Your Team
Build people who build the company leadership is the product.
12 frameworks, printed on pages 135–158.
When this page changes, your copy of the book does not have to.
The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.
If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.
Copying is free. An account keeps them.
Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.