Status Meetings Are a Symptom, Not a Solution

Field Note #02: Status Meetings Are a Symptom Something's Wrong

The meeting that should have been unnecessary

Every week, the same ritual. Everyone gathers in a room or on a call, and one by one, each person recites what they're working on. "I'm waiting on approval from finance." "I sent that over last week, haven't heard back." "I think Sarah was handling that, but I'm not sure." Thirty minutes later, the only thing anyone has accomplished is confirming that nobody really knows where things stand.

I've sat through thousands of these meetings. And at some point I realized something: we weren't meeting to coordinate. We were meeting because we had no other way to find out what was happening.

Status meetings aren't a sign of a disciplined team. They're a sign that your work has no visibility and management can't see into it. And when you have multiple teams scaling a mountain, stopping them every hundred feet to ask them if they're on track, isn't discipline. It's a symptom of not having a clear trail, not knowing what's next, and not having a system to measure progress.

What status meetings actually reveal

On the surface, they feel productive. People are talking. Updates are shared. Action items get scribbled down. But if you look closer, status meetings expose deep structural problems that no amount of calendar coordination can fix.

1. Work is invisible until someone asks about it

If the only way to learn what's happening within your company is to ask everyone handling it, your processes have no built-in visibility. Every task, every handoff, every approval lives in someone's inbox or their head. Nothing is surfaced until a meeting forces it out.

That means you're always three steps behind. You don't know about a blocker until the next meeting. You don't know about a delay until the next meeting. You don't know about a miscommunication until the next meeting. The work is happening, but it's invisible until you stop to ask.

2. Handoffs happen through conversation, not structure

In a healthy workflow, when one person finishes their part, the next person is automatically notified. In an undocumented process, that handoff is a Slack message, an email, or a verbal mention in a meeting. And if that message gets missed? The work sits. Sometimes for days.

Status meetings become the safety net for broken handoffs. They're where people discover that a task was supposed to be passed to them last Tuesday and nobody told them. That's not coordination. That's damage control.

3. Accountability is fuzzy

When a process isn't structured, ownership gets vague. "I think that's with IT." "Marketing was supposed to review it." "Someone from ops said they'd handle it." These phrases show up constantly in status meetings, and they all mean the same thing: nobody is clearly assigned, and nobody is tracking it.

I've seen the same task discussed in three consecutive meetings because no one could confirm who owned it. Each time, someone would say "I'll follow up." And each time, the follow-up fell through because there was no system holding anyone accountable. Just a meeting.

4. The meeting itself becomes the bottleneck

Here's the irony: when status meetings are the only way to surface information, works stalls between them. A question that could be answered in seconds waits until Monday. A blocker that could be resolved immediately sits untouched because the next sync isn't until Wednesday. The meeting that was supposed to speed things up becomes the thing that slows them down.

You wouldn't stop mid-climb to hold a meeting about where you are on the mountain. You'd look at the trail markers and keep moving forward. But when there are no markers, you have no choice but to stop and ask.

5. They scale terribly

A status meeting with four people takes fifteen minutes and mostly works. A status meeting with twelve people takes an hour and mostly doesn't. As teams grow, the round-robin update becomes unbearable. Half the room zones out because the updates aren't relevant to them. The meeting bloats. Side conversations spin off. And afterward, people still message each other asking for the real status.

Why we default to meetings

I don't blame anyone for scheduling them. When you don't have visibility into the work, what else can you do? The instinct is right: you need to know what's happening. The method is just wrong.

Teams default to meetings because the alternative, maintaining a wiki, updating a spreadsheet, sending summary emails, is tedious and unreliable. People stop doing it. The shared doc falls out of date. The spreadsheet becomes a graveyard. And so the meeting survives, because at least when you put people in a room, you get something.

The problem isn't that teams communicate too little. It's that the work doesn't communicate for itself.

What replaces the meeting

The answer isn't "more async updates" or "better meeting agendas." It's building visibility into the work so that status is always available without anyone having to report it.

When every request follows a defined service, when every task has a clear owner, when every handoff is tracked, you don't need a meeting to find out where things stand. You just look. The trail tells you what's next.

That's what Everstep does. Each ticket moves through a defined workflow. Tasks are assigned to teams. Progress is visible to everyone involved right at ticket creation. When something stalls, you see it immediately, not three days later in a standup.

• Tickets show real-time status so you never have to ask "where is this?"
• Task assignments create clear ownership so there's no ambiguity about who's responsible
• Workflow steps surface blockers automatically instead of waiting for someone to mention them in a meeting

This doesn't mean you'll never have a meeting again. But it means you'll stop having meetings just to figure out what's going on. Your meetings can be about decisions, strategy, and problem-solving instead of status recitation.

A simple test

Next time you're in a status meeting, count how many updates are just people reporting the state of a task. "It's in progress." "Waiting on approval." "Done, sent it over." If most of the meeting is this, it's not a meeting. It's a workaround for missing visibility.

You don't need a better meeting. You need a system where the work speaks for itself.

Stop stopping on the trail to ask where you are. Mark the trail, and keep climbing.