Most recurring meetings exist because someone, at some point, felt out of the loop. A status meeting is a patch for a trust problem. We didn't realize that until we ripped the patch off.
Sixty days ago we cancelled every recurring status meeting on the team calendar. Not standups — those stayed. Not planning sessions or retrospectives. Just the mid-week and end-of-week status rounds where each person reported what they'd done, what they planned to do, and what was in the way.
The calendar freed up three to five hours per person per week, depending on the role. That alone would have justified the experiment. But what happened next taught us more than the reclaimed time did.
We moved to written async check-ins. Every person posts a short update at end of day: done, doing next, blocked. No template longer than five lines. No thread required unless someone is actually blocked.
The rule: if you're blocked, say so in the check-in. If you see someone blocked and you can help, respond within two hours during working hours. Everything else is informational. Read it or don't.
We also added a single weekly digest — one person rotates the job — that summarizes progress against the quarter's goals. It takes about twenty minutes to write. Anyone on the team can read it in three.
Async check-ins sound clean on paper. In practice, the first two weeks surfaced a problem we hadn't named.
People stopped surfacing blockers.
In the old meetings, "anything in the way?" gave people social permission to admit they were stuck. The meeting was an accountability scaffold disguised as information sharing. Remove the scaffold and some people just… pushed through alone. Others quietly waited, hoping the blocker would resolve itself.
By day ten, two workstreams had stalled for reasons that would have come out in the first five minutes of a status round. That was the low point.
We made three changes after the first two weeks.
First, we separated "blocked" from "stuck." Blocked means you can't proceed without someone else's action. Stuck means you're uncertain about the right path forward. Both deserve a flag, but they need different responses. We added both words to the check-in prompt.
Second, we introduced a buddy system for blockers. Each person has a rotating partner who reads their check-ins and follows up directly if the update looks thin or absent. Not a manager — a peer. This replaced the social pressure of the meeting room with something lighter but still present.
Third, we made silence visible. If someone didn't post a check-in by end of day, their buddy pinged them. Not to scold — to ask if they were okay. Silence became the red flag, and we treated it as one.
After those three adjustments, the system started working.
Three things stood out.
Blocker resolution got faster. Average time from "I'm blocked" to "someone is helping" dropped from roughly a day and a half to about four hours. In meetings, blockers surfaced on a schedule — Wednesday or Friday. In async, they surface when they happen. The response window shrank because the signal traveled sooner.
Maker time increased measurably. Engineers and designers reported longer uninterrupted stretches. The calendar gaps left by cancelled meetings didn't fill with other meetings, which surprised us. People protected the time.
Written context accumulated. Sixty days of check-ins created a searchable history. When a new team member joined mid-experiment, they read two weeks of updates and understood the current state of every workstream without a single onboarding meeting. That was an accident, not a goal, but it turned out to be one of the biggest wins.
Not everything improved.
Relationship-building between teammates weakened slightly. Meetings, for all their cost, put people in the same room. Some informal bonding disappeared. We compensated with an optional weekly call — no agenda, just conversation. Attendance hovers around sixty percent, which feels about right.
The other trade-off: writing quality matters more now. A vague check-in wastes everyone's time the same way a vague status report did in a meeting. We spent real effort coaching people to write clearly and concisely. That cost was front-loaded but real.
The takeaway is that meetings often mask a missing system. If your status round is the only place blockers surface, the meeting isn't the problem — the absence of another path for blockers is.
We didn't just remove meetings. We replaced the function those meetings served: accountability, blocker detection, shared context. Then we fixed what broke in the first two weeks. The sixty-day mark is where we felt confident calling it a permanent change.
Your team's version will look different. The principle holds: figure out what the meeting is actually doing, build that function into your daily workflow, and then — only then — cancel the meeting.
Be the first to comment.
0 comments
Loading comments...