The Concept
Instead of: "Let's have a meeting" (default)
New default: "Let's document this in writing"
Exception: "This truly requires real-time discussion"
Traditional vs. Reverse Default
Traditional Culture
- Meeting is automatic response
- Async must be justified ("Can't we just meet?")
- Calendar fills with meetings
- Deep work squeezed in between
Reverse Default Culture
- Written/async is automatic response
- Meetings must be justified
- Calendar mostly open
- Meetings are intentional
Meeting Justification Criteria
Valid reasons for sync meeting:
- Complex negotiation
- Sensitive conversation
- True brainstorming (building on ideas)
- Relationship building
- Decision with disagreement
Invalid reasons (use async):
- Status updates → written standup
- Information sharing → documentation
- Announcements → email/video
- Quick questions → Slack/message
- FYI updates → don't need meeting
Implementation
Policy Statement
"Before scheduling a meeting, consider: Can this be a document, email, or async discussion instead? If yes, use that. Meetings reserved for true collaboration."
Meeting Request Template
Require meeting organizers to answer:
- What's the goal?
- Why can't this be async?
- What decisions will we make?
- How will we know it's successful?
- What prep is required?
Approval Process
- Large meetings (5+ people) need approval
- Recurring meetings reviewed quarterly
- Meeting hours tracked and reported
Expected Outcomes
Meeting Reduction
- Typical: 25-50% fewer meetings
- More focus time
- Better meeting quality (only essential ones)
Async Improvement
- Better documentation
- Clearer writing
- Searchable decisions
- Inclusive (time zones, introverts)
Productivity Gains
- More deep work time
- Faster decisions (no scheduling delay)
- Better work-life balance
Change Management
Resistance Points
"Meeting is faster than writing"
- True for conveying, but not for quality decisions
- Writing forces clarity
- Time saved for 5+ people reading vs. meeting
"We need face time"
- Reserve for social connection (optional)
- Separate collaboration from coordination
Success Factors
- Leadership modeling
- Training on async tools
- Celebration of async wins
- Patience during transition
Tools to Support
- Loom (async video)
- Notion/Confluence (documentation)
- Slack threads (discussions)
- Decision documentation templates
Metrics
- Meeting hours per person/week
- Percentage of decisions made async
- Documentation completeness
- Employee satisfaction
- Time to decision