A one-hour meeting with eight attendees is routinely booked and thought about as 'an hour' — the same unit of cost as a one-hour meeting between two people. It isn't. The actual cost, measured in person-hours, is eight times larger, and that multiplication almost never appears anywhere in the scheduling decision, because calendar software shows duration, not aggregate cost.
Why the multiplication matters more than it seems to
Making the person-hour cost explicit — even roughly, even just multiplying attendee count by duration — tends to change behavior in a way that simply asking 'is this meeting necessary' doesn't, because the abstract question is easy to answer yes to by default, while a concrete number (this meeting costs the organization roughly six person-hours) invites a genuine cost-benefit comparison against what those six hours could otherwise produce.
The effect is strongest for recurring meetings, where the per-instance cost is small enough to go unquestioned but the cumulative annual cost, once actually calculated, is often startling — a weekly one-hour meeting with ten people is roughly 500 person-hours a year, more than twelve full working weeks, for a meeting that may have been scheduled once, informally, and never revisited. For a practical software example related to wage percentage calculations, explore this overview.
Attendee count as a design lever, not a fixed input
Most meeting-cost thinking focuses on duration — shortening a meeting from an hour to thirty minutes — while a much larger lever usually goes unexamined: attendee count. Halving the number of attendees has the same effect on total cost as halving the duration, and it's frequently the easier change to make, since many meeting invitations default to including a broader group than the actual decision requires, out of politeness or habit rather than necessity.
- Calculate rough person-hours (attendees × duration) for any recurring meeting before deciding it's worth keeping as-is.
- Question attendee count as seriously as duration — a smaller meeting with a clear decision-maker set is often more valuable, not less, than a larger informational one.
- A meeting whose primary purpose is 'keeping everyone informed' is usually cheaper and more effective as a written update than a synchronous meeting for everyone.
- Recurring meetings deserve periodic review specifically because their cumulative cost compounds silently — an occasional audit catches meetings that outlived their original purpose.
What the cost framing doesn't capture
Person-hours is a useful first-pass lens, not a complete one — it treats every attendee's hour as equally valuable, which isn't true, and it doesn't capture the real coordination value some meetings provide that no written update can replace, particularly for decisions that genuinely benefit from real-time back-and-forth among several people. The framing is best used to flag meetings worth scrutinizing, not as a mechanical formula that automatically declares a given meeting good or bad value.
Making meeting cost visible is one of the simplest changes a team can make to its time-management culture, precisely because it doesn't require a new tool or process — just a habit of doing the multiplication before hitting send on a recurring invite. For additional background on this subject, consult the meeting overview.