The Meeting That Stopped Serving the Work

An audit of standing meetings in a large IT organization showed how much of the week they consumed. The more important finding was what those meetings had been trying to compensate for.

03 RANK
The condition

The calendar was full, some departments spent around forty percent of their week in standing meetings, and agreed priorities still did not hold.

Two hours of status, and an inbox

The clearest evidence about a meeting is rarely in its agenda. At one client, we joined a call a few minutes early and overheard two product owners talking before the sprint review began. One told the other the review was painful and ineffective. It was two hours of listening to every person describe what they had done over the previous two weeks, as if to prove they were doing their jobs. None of it was relevant to him, so he answered email instead of listening.

He would not have said that in an interview or on a survey. The review had drifted from its purpose into a kind of employment justification, and the people it was meant to serve had quietly opted out while still attending. We added it to our observation plan, and sitting in on it surfaced specific changes to its agenda, attendee list, frequency, facilitation, and level of interaction.

Meetings get built over time. An agenda is adopted, the invite list settles, the cadence becomes habit. After a year or two nobody asks whether the meeting still produces what it was designed to produce. People keep showing up because it is on the calendar.

Counting the hours

At a large IT organization serving several business units, a member of the client's working team took meetings and decision points as his part of the diagnostic. The method was a simple spreadsheet. For each standing meeting he captured its name, its stated intent, the number of required and optional participants, its duration, how often it ran in a year, and a calculated total of annual hours. He filled it by combining calendar access from administrative assistants with sessions where people walked him through their meeting load.

The annual hours column is the one that lands hardest with leadership, which is why we always recommend it. The total across the IT organization surprised everyone in the room. Some departments were spending around forty percent of their working hours in standing meetings. A handful of mid-level managers were above fifty. One leader said he had known the number was high, but not that high, and that he did not believe most of those meetings were producing their intended outcomes.

Figure 1
A working week in the heaviest departments
  • About 40%Standing meetings
  • About 60%All other work
Some departments only; approximate
In some departments, standing meetings took around forty percent of working hours. This was the high end, not the organization-wide average, and a few managers were above fifty percent.
People seated around a meeting table, most of them focused on their own laptops.

Fit for purpose, unfocused, or just "sync"

He had also attended a sample of those meetings with their agendas in hand and asked whether each one achieved its stated purpose. The results fell into three groups. Some were fit for purpose. The leadership team's weekly portfolio review was well facilitated and reached the outcome on its agenda. Some were unfocused. Code reviews meant to catch defects before production kept drifting into writing and fixing code. Some had no clear purpose at all, such as a weekly call with twelve attendees whose agenda read, in full, "sync."

Sorting meetings this way shows which ones to fix, merge, or retire. It does not yet explain why so many of them exist. That explanation came from the meetings that were supposed to make decisions.

Figure 2
Three kinds of standing meeting
GroupExample observed
Fit for purposeWeekly leadership portfolio review
UnfocusedCode reviews drifting into fixing code
No clear purposeWeekly call, 12 people, agenda: sync
Observed against their own agendas, standing meetings sorted into three groups. Only the first was doing the job it was scheduled to do.

The council that did and did not exist

The most useful findings from a meeting audit are not about meetings. At the client where we had overheard the sprint review complaint, a product leader in a process-mapping workshop drew his prioritization council at the center of the flow and described it as the main mechanism for deciding what got built. A leader from the client-facing side studied the drawing and said it could not go there. It did not really happen, she said, or if it did, she was not invited. Days earlier she had complained that the product organization was unresponsive to her group's needs. The product leader acknowledged that the council met inconsistently and that he had not checked its invite list in a while.

The IT organization had its own version. A monthly meeting between IT leadership and business unit leaders was meant to resolve competing priorities across units. Across three observed sessions, the pattern held. Agreement was produced in the room. Over the following weeks, individual business unit leaders renegotiated those priorities directly with the IT teams. The meeting was happening. The alignment it produced did not survive contact with the rest of the organization.

Better facilitation would not have closed that gap. The people in the room did not have the structural authority to make their decisions stick. A member of the working team named it: they had been treating this as a meeting problem for two years, when it was a prioritization problem the meeting had been trying to compensate for.

What the calendar was carrying

The irregular meetings told the rest of the story. Recurring meetings show what an organization has institutionalized as the normal way to decide. Ad hoc meetings show where the system was never designed to carry the load. The team sorted them into three groups. Cross-team escalation meetings were happening at a high rate. Reactive stakeholder alignment calls were convened because the formal forums were not producing alignment that held. Crisis meetings ran weekly on issues that had been visible in the system for months and became urgent only when a deadline was about to be missed.

Read that way, the calendar was a map of missing structure. The escalations were a coordination failure across team boundaries, showing up as meetings. The reactive alignment calls were a prioritization failure showing up the same way. When the session ended, the sponsor said she would not have guessed meetings were the thing that mattered most. Looking at the hours chart earlier, her first question had been how much of it they could simply stop.

That question waited for the redesign. The discipline of the diagnostic was to name the gaps before proposing fixes, and the meeting load was clearly one of the larger ones, with real capacity to return to delivery teams once meetings that were not producing their intended outcomes were retired. But cutting the twelve-person sync would not make the monthly priority agreement hold. The audit's real value was showing which parts of the work system were being propped up by meetings that should never have had to carry that weight.

Figure 3
What each meeting was covering for
MeetingCompensating for
Monthly priority forumDecisions without authority to hold
Cross-team escalationsNo designed path across teams
Reactive alignment callsPriorities that did not stick
Weekly crisis callsIssues visible for months
The meetings themselves were symptoms. Each one was compensating for a decision or a connection the system had not been designed to provide.

When a meeting keeps failing, look for the decision it was never given the authority to make.

Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Not sure where to start?

Answer five questions about where work stalls. We send back a starting plan: where to begin and what to look at first.