Ross Rondeau

Why I Built This: The Operating System for Enterprise Collaboration

Bad meetings are the largest unmanaged expense on any enterprise balance sheet. When ten people attend an hour-long status sync, the company burns ten hours of payroll on a conversation that rarely produces a decision. In my companion articles, On Meetings and On Time Blocks, I treat meetings as distributed systems workflows: they either run with engineering discipline or collapse into calendar sprawl.

This calculator acts as an objective calendar gatekeeper. It evaluates invites against empirical research, calculates direct salary burn and multitasking risk, and gives a clear verdict: Accept, Clarify, or Decline in favor of async documentation.

How It Works: The Five Empirical Triage Gates

The triage engine evaluates any incoming meeting request across five distinct research-backed operational gates:

1. The Separation of Meeting Types: Meetings serve exactly one of three fundamental purposes: Information Sharing, Decision Making, or Socialization. Tactical problem solving functions as targeted, isolated troubleshooting. When organizers blend information sharing with decision making into generic "workshop" sessions, you get the cost of both with the quality of neither. The information is not absorbed before the decision is debated, and the senior person implicitly decides anyway, creating a demoralizing illusion of control.

2. Meeting Duration (15 Minutes to 7 Hours+): In On Time Blocks, decision meetings should be short: under 30 minutes. For meetings scheduled under 30 minutes, lightweight outcomes (a binary decision, status update, or socialization) are acceptable. Sessions scheduled for longer than 30 minutes (spanning 45 minutes up to full-day 7-hour sessions) must have a durable artifact with assigned tickets, or an updated technical specification written before the call adjourns.

3. The Role and Autonomy Gate: Published by Stanford, Microsoft, and Amazon research demonstrates that participants who lack an active, named contribution mute their microphones, turn off their cameras, and multitask. If your role in a gathering is that of a passive spectator, attending live squanders expensive focus time. The engine automatically flags passive roles for conversion into asynchronous status reviews.

4. The Remote Equity Gate: Research published in Business Horizons by Standaert, Muylle, and Basu analyzed fifteen collaborative meeting objectives, showing that unmitigated hybrid meetings (mixing in-person conference room clusters with dial-in remote attendees) underperform across every single objective due to asymmetric communication channels and fractured social presence. Furthermore, longitudinal research by Jaime Teevan, Jenna Butler, and colleagues at Microsoft Research demonstrates that split hybrid rooms create severe proximity bias and "second-class citizen" dynamics for remote workers. However, in companies with remote employees, enforcing all in-person attendance is exclusionary and physically impossible. When remote employees participate, the mandate is meeting equity: either enforcing "One Remote, All Remote" (where all attendees, even those on-site, join from individual webcams) or assigning an in-room Remote Advocate with remote-first turn taking and digital-first whiteboarding.

5. The 24-Hour Pre-Read Gate: Decision-making requires pre-work. Verbal slide deck presentations waste collective cognitive bandwidth reading information that attendees could absorb faster in writing. High-performance teams enforce a 24-hour advance memo accompanied by a 5-to-10 minute silent-read block at the start of the meeting. If a decision meeting lacks pre-distributed material, the engine recommends requesting the pre-read memo before accepting.

Practical Benchmarks & Assumptions

All tool metrics rest on peer-reviewed studies and company data:

1. Fully Loaded Compensation & Annual Touchpoints: Base salary represents direct payroll without company benefits, using 2,000 work hours per year. The tool separates base pay from employer burden with an overhead slider (defaulting to 1.30x from SBA data). Annual touchpoints scale by cadence: 250 for daily, 52 for weekly, 12 for monthly, or 1 for single calls. The formulas calculate:

   • Base Salary Burn = Duration (Hours) * Attendees * (Average Base Salary / 2,000) * Annual Touchpoints
   • Employer Load Burden = Base Salary Burn * (Employer Overhead Load Factor - 1)
   • Direct Loaded Salary Burn = Base Salary Burn + Employer Load Burden
   • Total Organizational Overhead = Direct Loaded Salary Burn + Context Recovery Drag

2. Multitasking Probability Model: Data from Cao and colleagues (ACM CHI 2021) and On Meetings. The model sets baseline multitasking risk by call length. It adds penalties for group friction:

   • Meeting duration: 18% for under 30 minutes, 32% for standard 30-minute calls, and 68% for calls over 30 minutes or all-day sessions.
   • Group size: +0% for up to 5 attendees, +10% for 6 to 10 attendees, and +20% for groups over 10 due to social loafing.
   • Cadence: +25% for daily calls, +15% for weekly calls, and +8% for monthly recurring schedules.
   • Session setup: +25% for passive observers, +10% for split hybrid rooms, and +15% when cameras stay off.
   • Preparation credit: 15% discount when organizers share a disciplined 24-hour pre-read memo.

3. Meeting Recovery Drag: Low-engagement meetings leave staff drained for 30 to 45 minutes after the call ends. In On Time Blocks, scattering calls across the day destroys focus. The engine models this context-switch cost as a 50% payroll penalty on calls over 30 minutes without a committed deliverable. Grouping calls into one window recovers up to 75% of this lost time.

4. Time Window & Focus Block Alignment: Multitasking peaks during morning hours as staff clear inboxes. In On Time Blocks, morning meetings break the 2-hour blocks needed for deep focus (Kahneman). The engine adds a 10% risk penalty to morning meetings and flags invites that split deep focus blocks. All-day sessions (7 hours or longer) consume both morning and afternoon focus blocks, automatically incurring the 10% morning risk penalty and context recovery drag.

Tactful Pushback Scripts & Meeting Charter

When the triage engine recommends declining or clarifying an invite, push back with professional, non-defensive copy-paste scripts:

• Decline for Passive Observers: "Thank you for the invite. Reviewing the agenda, I cannot connect the meetings purpose from my contribution to it. Feel free to send along any summary notes or recording, I'd be happy to provide feedback! Please tag me directly in Jira or Slack if a specific question requires my input."

• Clarify for Missing Deliverables (>30 Minutes): "I see this meeting is booked for general discussion. I try to ensure that meetings over 30 minutes to be anchored to a deliverable, is there a Jira Task for this or OKR this aligns with? Before we meet, can we define what specific document we will commit before the room adjourns, or compress the conversation to 20-minutes?"

• Clarify to Enforce Remote Equity Rules: "Since we have remote team members, can we agree to adopt 'One Remote, All Remote' with everyone on their individual laptops, or designate an in-room remote advocate so remote contributors have an equal voice?"

• Clarify to Protect Focus Blocks (Reschedule to Collaborative Window): "Thank you for the invite. This is currently scheduled during my morning heads-down focus block. Could we move this conversation into our team's designated collaborative meeting window (1:00 PM to 3:00 PM)? If that window does not work, please feel free to send the agenda items and I will review them before the end of the day."

• Clarify for Missing 24-Hour Pre-Read: "I see this decision meeting is scheduled on our calendar, but the pre-read memo has not been circulated yet. Could you share the memo today, or should we reschedule so the team has time to review?"

Download the complete companion Excel workbook above (Meeting_Invite_Triage_Worksheet.xlsx) to access the offline triage calculator, the full 15-objective Standaert decision matrix, and the standardized 1-page Meeting Charter template.

Sources & Empirical Literature

• Rondeau, R. (2026). On Time Blocks: Why knowledge workers require 2-hour focus blocks and how to recover up to 75% of productive capacity. LinkedIn Pulse. LinkedIn.
• Rondeau, R. (2024). On Meetings: What meetings are actually for, what they silently cost when misused, and the patterns industry leaders use to fix them. LinkedIn Pulse. LinkedIn.
• U.S. Small Business Administration (2019). How Much Does an Employee Cost You? U.S. Small Business Administration. SBA.
• Cao, H., Lee, C. J., Iqbal, S., Czerwinski, M., Wong, P., Shang, R., Zhou, J., Bernstein, M., & Yang, L. (2021). Large Scale Analysis of Multitasking Behavior During Remote Meetings. Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems (ACM CHI). arXiv:2101.11865.
• Standaert, W., Muylle, S., & Basu, A. (2021). Business meetings in a postpandemic world: When and how to meet virtually. Business Horizons, 65(3), 267-275. PMC9418882.
• Teevan, J., Baym, N., Butler, J., et al. (2021). The New Future of Work: Research from Microsoft into the Pandemic's Impact on Work Practices. Microsoft Research. Microsoft Research.
• Ringelmann, M. (1913). Recherches sur les moteurs animes: Travail de l'homme. Annales de l'Institut National Agronomique. Foundational literature on group coordination friction and process loss in expanding teams. Ringelmann Effect.
• Wiese, C. W., & Burke, C. S. (2019). Advancing research on teams and team effectiveness in implementation science. Team-level structure, coordination overhead, and optimal team size. PMC7327318.
• Pink, D. H. (2009). Drive: The Surprising Truth About What Motivates Us. Riverhead Books.
• Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
• Rogelberg, S. G. (2019). The Surprising Science of Meetings: How You Can Lead Your Team to Peak Performance. Oxford University Press.