The Status Meeting We Want You To Cancel
How many recurring meetings does your team sit in weekly? How many people are in on it? How many of the updates are manual vs automated? How much of the data is your team trusting and using to inform their work?
Nine times out of 10, teams sit in multiple recurring meetings, drone on about manual updates because they don’t trust the data to automate it, and it becomes a human progress report that should’ve been an email.
It's Not a Communication Problem
A lot of times, when issues surface, we point to the people and assume there’s a communication problem, a capacity issue, or a skill gap. That may be true, but a lot of times the issue goes a little deeper. When you respond to the assumption of communication, capacity, and skill, you typically solve that problem by adding a tool, a process, or a person. All of this adds additional context to coordinate around and typically exacerbates the issue.
Every coordinated handoff between a person, a system, or a phase is a re-entry point. Re-entry is unbilled labor that directly impacts your margins.
Last week, we walked you through the importance of capturing current state processes. So thinking about your current state processes, what happens if someone goes on maternity leave or quits unexpectedly? What would slow down, stop completely, or become a vulnerability for your organization?
The Four Common Handoff Challenges
Sales to Delivery
What is sales promising to prospects? Can delivery actually deliver on the promise? Or, during kickoff, is the delivery team asking repetitive questions that they should already know (sales should’ve passed on that context)?
Individual Handoffs
Two SMEs have a meeting, the meeting is the handoff. Nothing is documented. The person who took the baton during the meeting waits two days to start work, forgets the context from the meeting, and re-does discovery. That’s unbilled rework.
System Handoffs
Your tools work together to produce outputs, but only if a human forces it. Instead of your tools being integrated and talking to each other, your team has to export from one tool and paste into another on a recurring basis.
Completed Work to Visibility
There’s no source of truth for project progress or engagement health. So if leadership wants a status update, they can only get it by asking a human for it, which makes for some complicated conversations with clients.
Do the Math For Your Company
You probably recognized yourself in a few of those examples. But what is that actually costing your bottom line? We can’t tell you that, but we can give you the info to run the numbers yourself.
Count coordination hours per person, per week (status meetings, chasing updates, re-entering data between tools, re-explaining scope)
Multiply by the number of people involved in each one
Multiply by a blended hourly rate. We use $56/hour as a working benchmark for a mixed delivery team — unloaded, so no benefits or overhead. Adjust it up if your team skews senior.
Multiply by 48 working weeks.
Here's what that looks like for a 25-person firm with an 8-person delivery team:
Weekly delivery status meeting (1 hr × 8 people) = 8 hours per week
Monday leadership check-in (45 min × 4 people) = 3 hours pe rweek
PM compiling status from four tools = 3 hours per week
Rework from undocumented handoffs = 2 hours per week
Total = 16 hours per week
16 hours × $56 = $896 per week.
$896 × 48 weeks = $43,008 per year.
That's $43,000 of unbilled labor inside of billed engagements. You can find this on the delivery margin that maybe skewed lower than expected, especially on projects that “went well”.
Now, you're not going to recover all of it. Some coordination is real work, and a team that never talks to each other has a different and worse problem. But if half of that 16 hours exists only because the handoff wasn't built, you're looking at roughly $21,500 a year.
What does “good” look like?
“Good” is pretty simple (which is one of our values at The 128 Collective).
Work moves through a defined path, not a person's memory
Status is a byproduct of doing the work, not a separate reporting activity
Handoffs produce an artifact, not a conversation
Moving Work Isn't the Same as Owning It
Connecting your processes is about motion. Capture told you what the work is and where it lives; Connect asks whether that work can move without a person carrying it. When the path is built, the handoffs produce artifacts instead of meetings, and status stops being something you have to go ask for.
But work that moves cleanly through an unclear structure just moves the confusion faster. A defined path doesn't help much if two people think they own the same step, or if nobody's sure what "done" means. That's Clarify, and we’ll dive into it next week on the blog.
In the meantime, go back to the question we opened with: if the person who just knows how this works took two weeks off, what would stop? Write down the three things. That list is your Connect gap, and you already have it.
If you need help sorting through this, drop us a line. It’s kinda our thing.
