Reducing unnecessary meetings

{{whyLabel}}: You cannot optimize what you haven't measured; understanding your current 'meeting debt' is the first step to systemic change.

{{howLabel}}:

• Export or review your calendar from the past 4 weeks.
• List every recurring meeting and its total monthly duration.
• Note the number of participants for each session to calculate 'man-hour' costs.

{{doneWhenLabel}}: [A spreadsheet or list exists showing all meetings, their frequency, and total time consumed.]

{{whyLabel}}: Different meeting types require different async replacements; a one-size-fits-all approach will fail.

{{howLabel}}:

• Label every meeting as 'Information Sync' (status updates), 'Decision Making' (complex choices), or 'Social/Relational' (1:1s, team building).
• Identify 'Information Syncs' as the primary targets for immediate elimination.
• Mark 'Decision Making' meetings as candidates for the 'Silent Meeting' format.

{{doneWhenLabel}}: [All current meetings are tagged with one of the three categories.]

{{whyLabel}}: Quantifying the cost of meetings provides the necessary leverage to convince stakeholders and yourself to change.

{{howLabel}}:

• Use the formula: (Number of meetings x 20) + (Total meeting minutes) / 4 weeks.
• A score over 1200 indicates 'Bad Meeting Health' requiring urgent intervention.
• Estimate the financial cost: (Attendees x Average Hourly Rate x Duration).

{{doneWhenLabel}}: [A final 'Meeting Health Score' and estimated monthly cost are documented.]

{{whyLabel}}: Systemic change requires clear, shared expectations to prevent 'notification anxiety' and ensure accountability.

{{howLabel}}:

• Define expected response times (e.g., 4 hours for internal chat, 24 hours for email/docs).
• Establish the 'Meeting Tax': No meeting can be booked without a written agenda and a pre-read document provided 24 hours in advance.
• Set 'Core Collaboration Hours' (e.g., 10 AM - 2 PM) to protect deep work time.

{{doneWhenLabel}}: [A one-page document outlining communication rules is ready for sharing.]

{{whyLabel}}: Async communication fails if information is scattered; you need a 'Single Source of Truth'.

{{howLabel}}:

• Choose a tool that supports nested pages and inline comments (e.g., a modern Wiki or Knowledge Base).
• Create folders for 'Decisions', 'Project Updates', and 'SOPs' (Standard Operating Procedures).
• Ensure all team members have edit access to foster collaborative writing.

{{doneWhenLabel}}: [The hub structure is live and accessible to the relevant team.]

{{whyLabel}}: Based on Paul Graham's 'Maker's Schedule', creators need 3-4 hour uninterrupted blocks to be productive.

{{howLabel}}:

• Block out 'Deep Work' sessions (e.g., 8 AM - 12 PM) as 'Busy' in your calendar.
• Enable 'Speedy Meetings' settings to automatically end 30-minute meetings at 25 minutes.
• Set your status to 'Focus Mode' during these blocks to mute notifications.

{{doneWhenLabel}}: [Calendar shows recurring daily blocks for deep work.]

{{whyLabel}}: Status updates are the lowest value meetings; they are better consumed at the reader's own pace.

{{howLabel}}:

• Create a recurring automated prompt in your chat tool (e.g., every Monday at 9 AM).
• Ask three questions: What did you do? What are you doing? Any blockers?
• Mandate that all updates happen in a single thread to keep the channel clean.

{{doneWhenLabel}}: [The first automated async status update is successfully completed.]

{{whyLabel}}: Amazon's '6-page memo' method ensures everyone has the same context before speaking, leading to faster, better decisions.

{{howLabel}}:

• For complex topics, require a written narrative (1-6 pages) instead of a slide deck.
• Start the meeting with 15-20 minutes of silent reading and commenting in the document.
• Use the remaining time only for discussing unresolved comments and making the final decision.

{{doneWhenLabel}}: [One decision-making meeting has been conducted using the silent reading format.]

{{whyLabel}}: Video captures tone and visual context that text lacks, without requiring a live audience.

{{howLabel}}:

• Record a 3-5 minute screen share for project demos or feedback instead of booking a call.
• Share the link in the relevant project thread.
• Encourage viewers to use time-stamped comments for feedback.

{{doneWhenLabel}}: [A video walkthrough has been shared and commented on asynchronously.]

{{whyLabel}}: A defined test phase reduces resistance and allows for 'safe' failure and learning.

{{howLabel}}:

• Announce to the team: 'For the next 2 weeks, we will default to async for all internal syncs.'
• Cancel at least 50% of recurring meetings during this window.
• Keep a 'Friction Log' to note whenever async communication feels slower or confusing.

{{doneWhenLabel}}: [The 14-day pilot period is completed.]

{{whyLabel}}: You need honest data on whether the team feels more productive or more isolated.

{{howLabel}}:

• Ask: 'Do you feel you have more focus time?' and 'Are you missing critical information?'
• Use a 1-5 scale for 'Meeting Satisfaction' vs. 'Async Satisfaction'.
• Collect specific examples of where async failed during the pilot.

{{doneWhenLabel}}: [Survey results are collected and summarized.]

{{whyLabel}}: No system is perfect on day one; iteration ensures long-term sustainability.

{{howLabel}}:

• Adjust response time expectations based on pilot feedback.
• Re-introduce 'Social 1:1s' if the team feels isolated.
• Formalize the 'Meeting Tax' checklist (Agenda + Pre-read + Clear Goal) as a mandatory requirement for all future invites.

{{doneWhenLabel}}: [The final version of the Async-First Manifesto is published and enforced.]