The Empty Chair

How much do your teams know about each other's work?

There's a space between every two teams who hand work back and forth, period after period. Most of the time nobody can see it. It doesn't show up in a process map. It doesn't get flagged in a status report. It just sits there, quiet, until something depends on it and the dependency doesn't hold.

Every period, month, quarter, year, Finance closes the books and reports results. By the deadline, everything's reconciled, accrued, journal entered, evidenced. Pull the results and reports and the support's there, clean and complete. On paper, nothing's missing. The close looked perfect. But was it, really?

What the results and reports never show is the cost of getting there. The overtime nobody tracked. The nights and weekends spent hunting down data or information that should've been handed over on schedule and instead showed up late, forcing whoever was responsible to redo the calculations and stay until it closed.

So the timeline absorbed the slack the only way a broken timeline knows how. People started earlier. People stayed later. Weekends got swallowed, not by the close itself but by the chase it triggered: following up on data and information that showed up late or changed after the new schedule had already gambled that it wouldn't. One missing handoff cost an email. A pattern of them cost hours, every period, eaten by whoever had to stay until it was done.

Someone starts a project to fix that. Shorten the timeline. Give people their evenings back.

Each finance team got interviewed. Activities got identified. Dependencies got mapped. A new close timeline came out of it, built around the one constraint nobody could touch: the period closes on the same date, every single time, no negotiation.

Yet, there was a tell sitting right in the interviews, if anyone had been listening for it. The first team described their own process with total confidence. Every step accounted for, every answer certain. Then they got to the team they handed off to, and the certainty cracked. The answer still came, but it came hedged. "I think." "I believe." There were empty chairs at that table.

Then the next team got interviewed. Same pattern. Sharp on their own work, soft on the handoff. The team after that, same thing again. Every interview produced one crisp map of a single workstream and one blurry edge where it touched another team.

Nobody ever laid those maps side by side. If they had, the mismatches would have surfaced immediately. Team A believed the report landed by end of day. Team B, the one sending it, said sometime that night, a gap neither side knew existed until someone asked both questions in the same room. Team B, in turn, assumed Team A ran a specific calculation on what they received. Team A didn't, hadn't in over a year, but nobody on the sending side had ever confirmed that, so the assumption just kept getting passed forward, unchecked, period after period. Two teams, two confident guesses about each other's work, both wrong, never reconciled, never even introduced to each other. The project had every piece it needed to end the confusion. It just never put the pieces in the same room.

None of this is a knock on the project team's rigor. Nobody cut a corner. The empty chair never shows up in an audit finding, because audits check whether the work got done accurately, not what it took out of the people who did it. The real cost lands in hours nobody planned for, burnout, and attrition, quietly carried by people absorbing a structural gap that was never supposed to be theirs to carry.

I keep coming back to those maps. Each one was honest. Each one was sharp about what that team owned and shaky about what happened on the other side. Put together, side by side, they might've told the whole story. Rarely are they put together.

That's the part I find most interesting about this work. The gap never hid. It surfaced in nearly the same words, interview after interview, team after team, practically begging someone to notice the pattern. The information existed the entire time. What never existed was the view across it. Getting everyone in a room at once costs time nobody wants to spend. What it saves downstream, period after period, is far more.

All this is rarely a failure of effort. The people running those interviews did exactly what they were asked to do, one team at a time, the way these projects almost always get scoped. What it tells me is that some gaps only reveal themselves when teams answer the same question, in the same room, and one of them finally says, "No, that's not what happens," or, "That's only partially true." A single-team interview will never produce that moment. It wasn't built to.

This doesn't reach a steering committee. Part of the reason is that the project had nothing built to measure it. The close happened. The deadline held, period after period. And yet, the hours absorbing the gap mostly belonged to salaried people, the ones whose time never lands on a timesheet, never gets coded as overtime, never shows up anywhere a sponsor would think to look. The cost is real. It just doesn't have a line item.

So on the next project, ask yourself this question: Do we have empty chairs?

Part of an ongoing series on operational design, process transformation, and what it takes to make change endure.