How many hours did you spend in status meetings last week?
For most consulting managers, it's somewhere between 5 and 10 hours. Weekly client status meetings. Internal project syncs. Team standups. Pipeline reviews. Each one following the same pattern: go around the room, share updates, surface blockers, agree on next steps.
Now ask yourself: how many of those meetings told you something you couldn't have learned asynchronously?
The Information Problem
Status meetings exist because information doesn't flow. The project manager doesn't know what the developer finished yesterday. The partner doesn't know which clients are at risk. The sales lead doesn't know what closed last week.
So we gather. We synchronize our mental models through the inefficient medium of spoken language. Everyone waits while one person talks. Then we go back to work, our information already starting to decay.
This made sense when information lived in people's heads. When the only way to know what someone knew was to ask them.
It makes less sense when information can live in systems. When what happened yesterday can be logged, aggregated, and surfaced without anyone having to remember to share it.
What Status Meetings Actually Provide
Pull apart a typical status meeting and you find three things:
1. Information sharing. "Here's what happened since we last met." This is the bulk of most status meetings, and it's the part that should be automated. If your systems track work, there's no reason humans need to verbally report on work.
2. Problem solving. "I'm stuck on X, does anyone have ideas?" This is valuable, but it doesn't need a scheduled meeting. It needs a way to surface blockers and route them to people who can help.
3. Alignment. "Are we all pointed in the same direction?" This is the hidden function of status meetings. The ritual of gathering creates a sense of shared purpose. But there are better ways to create alignment than weekly check-ins.
The Replacement
If information flows automatically, you don't need meetings to share information. You need:
Continuous status, not periodic updates. Project health visible in real-time, updated as work happens. Not reconstructed from memory every Monday.
Exception alerts, not round-robin reports. When something goes off track, the right people find out immediately. When everything's fine, no one's time is wasted confirming it's fine.
On-demand problem solving, not scheduled discussion. When you're stuck, you flag it and the right people see it. You don't wait until Thursday's standup to surface Tuesday's blocker.
Asynchronous alignment. Shared dashboards, documented decisions, clear ownership. The alignment that comes from everyone having access to the same information, not from sitting in the same room.
What's Left
When you remove the information sharing and automate the exception handling, what's left for meetings?
Relationship building. The human connection that comes from face time. This matters, especially with clients, but it doesn't need to be disguised as status reporting.
Complex problem solving. The kind that requires real-time back-and-forth, whiteboarding, building on each other's ideas. This is valuable, but it's different from status.
Decisions that require discussion. When there are genuinely multiple perspectives that need to be heard before deciding. Again, valuable, but not weekly.
Notice what these have in common: they're all things that actually require synchronous human interaction. They can't be replaced by better information flow.
The Transition
You probably can't kill all your status meetings tomorrow. But you can start shifting them.
Begin by tracking what percentage of each meeting is information sharing versus actual discussion. If it's 80% information sharing, that's a meeting that should be an automated dashboard.
Then start replacing. "Instead of everyone sharing their updates, let's look at the project dashboard together. We'll only discuss items that are yellow or red."
Over time, the meetings get shorter. Then less frequent. Then some disappear entirely, replaced by systems that do the information sharing better than humans ever could.
The time you get back is the time you should have been spending on clients in the first place.