Collaboration / Source date:

Conference Calls: The Most Expensive Habit in Business

Dial-in culture normalized large passive audiences and made decision accountability hard to trace.

Illustrative reconstruction of an audio conference speakerphone, empty meeting chairs and an unfilled decision-owner-date ledger.

In March 2007 Cisco agreed to buy WebEx for roughly $3.2 billion, betting that online meetings were about to become core enterprise infrastructure. That October, eBay took an impairment charge of around $1.4 billion on Skype, having discovered that owning the world's most popular voice application is not the same as knowing how to sell it to businesses. Both transactions were about the same problem: the conference call had become the default unit of corporate work, and it was terrible. Nearly twenty years later, the technology has been rebuilt several times over. The underlying problem — conference call culture — has not been touched.

What a 2007 Conference Call Actually Was

A dial-in number. A participant code. A chairperson code held by whoever booked the bridge. Per-minute charges that finance queried once a quarter and nobody could allocate to a project. The ritual was universal. Five minutes of arrivals, announced by beeps. "Who just joined?" Someone's line with background noise nobody could isolate. A dial-in that failed for the one person whose input the meeting required. Ten minutes gone before the first substantive sentence. Then the call itself: no faces, no shared screen for most participants, no indication of who wanted to speak next, and a discussion dominated by whoever was most comfortable interrupting. Video conferencing existed — Cisco had launched immersive TelePresence rooms the previous year — but a three-screen suite cost as much as a small building fit-out and required a dedicated room at both ends. For everyone else, it was audio. The invitation list grew because inclusion was free and exclusion was political. Twelve people attended a call where three were required, and the other nine did email.

The Cost Nobody Put on a Line Item

The telecoms charge was the only cost anyone measured, and it was the smallest one. A weekly ninety-minute operations call with twelve attendees consumes eighteen person-hours a week — close to half a full-time equivalent, every week, before preparation. Priced at a blended senior rate, a single recurring call of that size costs a mid-sized business a meaningful six-figure sum annually. Most organizations have several, and none of them appear in any budget. The larger cost is decision accountability. Surveys of remote meeting behaviour have consistently found that most participants do other work during calls, and it is not a secret: everybody knows the audience is partially absent. That produces a specific and expensive failure:

  • A decision is discussed but not stated.
  • Nobody is named as owner, because naming an owner on a call with twelve people feels aggressive.
  • No deadline is set, because the call is ending and the next one is in four minutes.
  • Nobody writes it down, because minutes stopped being taken in most organizations around the time meetings moved to the phone.
  • The same item appears on next week's agenda, and the cycle repeats. The meeting felt collaborative and produced nothing enforceable. Multiply by the number of standing calls in the calendar and you have the real communication cost.

What Video and Chat Actually Fixed

It is worth being precise about the progress, because there has been some. Dial-in friction has largely gone: joining is a click. Screen sharing made discussion of actual artefacts possible rather than describing a spreadsheet aloud. Video restored some of the turn-taking cues that audio strips out. Recording and automatic transcription mean a decision can be retrieved rather than remembered. Chat gave people a way to contribute without interrupting. What none of it fixed: who is in the room, why the meeting exists, whether a decision was made, and who owns the outcome. Those are governance questions, and no platform has ever answered a governance question. In several respects the situation worsened. Zero-friction scheduling removed the last natural constraint on meeting volume — booking a bridge and a room used to require slight effort, and slight effort suppresses marginal meetings. Calendars are now the primary instrument of organizational drag, and the tooling makes it easier to add a meeting than to cancel one.

A Practical Standard for Meeting Effectiveness

The organizations that have fixed this did not buy anything. They applied rules and enforced them consistently.

  • No agenda, no meeting. The agenda must state the decision required, not the topic to be discussed. "Q3 pipeline" is a subject. "Approve or reject the two deals below threshold" is an agenda.
  • Name the decision-maker in the invitation. Consultation is legitimate; ambiguity about who decides is not.
  • Invite participants, not audiences. Anyone who does not need to speak gets the notes. Make declining a standing call normal behaviour rather than a signal of disengagement.
  • Default to shorter. Thirty minutes for a recurring operational call, and fifteen where the format allows. Work expands to fill the slot booked.
  • Write the decision in the meeting. One line: decision, owner, date. If it cannot be written, it was not a decision.
  • Kill recurring meetings on a schedule. Every standing call expires after a quarter and must be re-justified by its owner. Most are not re-justified, which tells you what you need to know.
  • Use asynchronous updates for status. Status reporting is the single largest category of meeting content and the one least suited to a synchronous format.
Turn a call into a decision recordThe meeting discipline proposed in the article. These steps do not imply measured savings.
  1. State the decision

    Write an agenda naming the decision required rather than only a topic.

  2. Name who decides

    Identify the decision-maker in the invitation.

  3. Invite contributors

    Give observers the notes rather than another standing call.

  4. Record the outcome

    Write the decision, owner and date during the meeting.

  5. Re-justify recurring calls

    Expire standing calls each quarter and use asynchronous updates for status.

Qualitative summary of this article's source text, not a measured outcome or performance estimate.

The Test

Open your calendar for last week. For each recurring meeting, write down the decision it produced and the person who owns the follow-up. If most entries are blank, the problem is not the conferencing platform, the connection quality, or whether cameras were on. It is that the organization is using meetings as a substitute for accountability — the same mistake it was making in 2007, on much better equipment.

Questions Operators Ask

How much do recurring meetings actually cost?

Multiply attendees by duration by a blended hourly cost, then by frequency across the year. A weekly ninety-minute call with a dozen senior participants routinely exceeds six figures annually, and almost never appears in any budget.

Why do conference calls produce so few decisions?

Because attendance is treated as participation, nobody is designated to decide, and outcomes are rarely written down during the call. Without those three elements, discussion substitutes for resolution.

Does video conferencing improve meeting effectiveness?

It improves turn-taking, engagement and the ability to share artefacts. It does not improve agenda quality, attendance discipline or decision ownership, which is where most of the waste sits.

What is the fastest way to reduce meeting load?

Expire every recurring meeting at the end of the quarter and require its owner to re-justify it with a stated purpose and decision rights. The ones that quietly disappear were never producing value.


Meeting Effectiveness Review — Outpace analyses your recurring meeting load, costs it in real terms, and replaces status-reporting calls with asynchronous reporting and decision records that hold people accountable between meetings.

Continue reading

Talk to OPS

Start with the operating problem.