The Status Call Trap

I've sat in on a lot of implementation calls to audit delivery teams. And nine times out of ten, I see the exact same failure mode.

The Implementation Manager opens the call by sharing their screen.

They pull up a Gantt chart or a spreadsheet.

And for the next 45 minutes, they literally read the rows of the spreadsheet out loud to the customer.

“Okay, so task 14 is complete. Task 15 is pending your data upload. Task 16 is blocked until task 15 is done.”

The customer nods. The Implementation Manager nods.

Everyone agrees to meet again next week to read the spreadsheet again.

This is the Weekly Status Call Trap.

You are using synchronous time to solve an asynchronous problem. And in the process, you are teaching the customer that your meetings are low-value administrative check-ins.

The Signal

The signal that your status calls are broken usually shows up in the attendee list.

Week 1: The Executive Sponsor, the Project Lead, and three power users attend.

Week 3: The Executive Sponsor declines the invite.

Week 5: The Project Lead sends a junior admin in their place.

When executives stop attending your implementation calls, they aren’t signaling that they trust you. They are signaling that the meeting is a waste of their time.

And the moment you lose the executive sponsor, you lose the ability to drive change management.

Other signals are harder to see in the moment but impossible to ignore in hindsight. The customer stops completing their homework between calls. The meeting consistently ends 20 minutes early because “there isn’t much to update.” Or worse, it goes 20 minutes over because the customer is using the time to ask basic support questions instead of focusing on the implementation.

The System

The root cause of the Status Call Trap is a lack of operational discipline.

We default to meetings because meetings feel like progress. If we are talking to the customer for an hour every week, we must be moving the project forward.

But a meeting is not progress. A meeting is an alignment mechanism.

The hidden dependency here is your project management tooling. If your customer doesn’t trust or understand your project management system — whether that’s ClickUp, Asana, or a shared portal — they will force you to read it to them on a call.

When you allow the status call to become the primary mechanism for information transfer, you train the customer to ignore your emails, ignore your portal, and wait for Tuesday at 10 AM to find out what they need to do.

You stop being a strategic partner. You become their administrative assistant.

The Tactic

To fix this, you have to flip the ratio. Stop spending 45 minutes on the past and 15 minutes on the future. Spend 5 minutes on the past, and 40 minutes driving the project forward.

1. The Asynchronous Update

Send the status update 24 hours before the call. Include what was completed, what is blocked, and exactly what the customer needs to do. If the customer hasn’t read it, do not read it to them on the call. Ask: “Are there any questions on the status report sent yesterday?” If no, move on.

2. The Working Session Pivot

Change the name of the meeting. Stop calling it a “Status Call.” Call it a “Working Session” or an “Alignment Briefing.” Use the synchronous time to do things that actually require two people to be on a call: making complex decisions, unblocking technical hurdles, or aligning on change management strategy.

3. The Escalation Trigger

If the customer misses two deadlines in a row, the working session stops. You do not move forward. You use the call to explicitly address the blocker. “We are currently paused because we do not have the data file. We cannot proceed until this is resolved. How do we unblock this today?”

The Engagement Loop

Think about the last status call you led or attended.

Did you actually move the project forward, or did you just read a spreadsheet out loud?

How do you keep executive sponsors engaged during a 90-day implementation? I’d genuinely like to know.