Kim had told her head of product, in passing, at the end of a Tuesday call, that she wanted the team to “move faster on customer feedback.”
She didn’t mean it as a decision. She meant it as a mood. A nudge. The kind of thing a CEO says between two other things, already half-thinking about the next call.
Three weeks later, the head of product had restructured the intake process, cut the customer success team out of the triage loop, and told them the change came “from Kim.”
It hadn’t. Not really. What Kim had said was one sentence, unscoped, unwritten, said once. What the head of product had heard was a mandate. And what customer success experienced was a decision made about their work, by someone who’d never spoken to them, that nobody could quite trace back to a moment where it was actually decided.
Kim found out about all of it in a Friday retro, three people deep into a conversation about whose call it had even been.
Nobody had lied. Nobody had overstepped, exactly. The head of product had filled a gap the only way anyone can: with their best guess at what the CEO probably meant, extended a little further than the sentence itself ever went.
This is the part that’s easy to miss. Structural silence doesn’t look like conflict. It doesn’t look like anyone hiding something or refusing to communicate. It looks like an ordinary Tuesday, a passing comment, and three weeks of a team quietly organizing around a decision that was never actually made — because nobody had been forced to write it down, scope it, or say out loud who it belonged to.
The tell isn’t in what was said. It’s in what happened next, and how many people had a different version of it by the time it surfaced.
A few places this shows up, if you’re looking for it in your own organization:
Two people, in two different meetings this week, each confidently describing the same decision — differently. Not disagreeing. Just each holding a version they’d quietly assembled themselves, because no shared version was ever put in front of them both.
A change that “came from” you, that you don’t remember deciding. Not because your memory is bad. Because it was never a decision in the first place. It was a comment, and someone downstream had to turn it into one.
A question that keeps getting asked in slightly different words, by slightly different people, months apart. Not because the answer is hard. Because it was never actually answered — just implied, once, to someone who’s since moved teams or moved on.
None of these are dramatic. That’s what makes them structural rather than personal. Nobody is the problem. The problem is what a system does with the space nobody has filled — it fills it anyway, with whatever each person’s best guess happens to be, and it does this quietly, continuously, whether or not anyone intended it to.
Kim’s team wasn’t wrong to act. They were doing what any team does when the top of the organization leaves something unscoped: they scoped it themselves, and hoped it matched.
Sometimes it does. That Friday, it hadn’t.