Urgency is a contract you don't know you've signed
It's 7pm on a Friday. The team has just delivered the thing, that we need this by EOD today task, the one that required dropping everything, working through lunch, timing the send perfectly so leadership would have it in hand with enough of the day left to respond. They are still at their computers. Phones nearby, weekend plans on hold - dinner pushed back, a friend told Sorry, I still need to finish something here. They are waiting for the crucial response that will determine whether they can close their laptop and actually have a Friday evening.
Twelve hours later: nothing.
The Friday evening misattunement
The team has lived this exact scenario before. Multiple times. They know the drill. Urgent means drop everything, deliver fast, then wait. The response will come when it comes. Or it won't. When leadership is challenged about it, they respond with genuine concern. You're absolutely right, we need to do better. They mean it in the moment. Sometimes new processes get introduced. Nothing fundamentally changes.
This is what I call misattunement. In organizations, misattunement is the gap between what's said and what's sensed. In this case, the gap is between requested urgency and what was implicitly promised in return. Between the weight of the ask and the weight of what follows.
Both sides are reading the same situation in incompatible registers. Leadership operates in a register where urgent is relative: flexible, subject to shifting priorities, reorderable against tomorrow's demands. The team operates in a register where urgent means this matters right now. Urgent enough to disrupt the evening, urgent enough that the response will arrive while it still counts. Neither side is misreading the words. They're misreading what the words have promised.
But this is the move worth slowing down for: urgency is not just a deadline, it is an emotional contract. When a leader says drop everything, they're not setting a delivery date. They're asking for an emotional investment — focus, sacrifice, the suspension of someone's private plans — and that ask creates an obligation to match it. The deadline is the visible part of the contract. The matching response is the part that gets quietly left unpaid.
What usually happens on the other side
The most common reason the response never arrives is rarely the obvious one. It's not that the leader got too busy, or forgot, or deprioritized on purpose. It's that the urgency itself dissolved.
The opportunity that triggered the EOD request didn't materialize. The customer who escalated got handled differently. The investor question turned out to be rhetorical. The competitor announcement was less significant than it first appeared. Somewhere between the moment leadership generated the urgency and the moment the team delivered against it, the reason for the urgency went away.
From the leadership side, this is barely a memory. The situation changed. The mental file closed. Attention moved on to the next thing — and the next thing is always there, especially in a scaling company. By Monday morning, the Friday request is no longer a live item; it's been overwritten by Sunday's email thread, Monday's leadership meeting, the founder conversation at 9am. The leader is not avoiding the team. The leader has simply, and entirely understandably, moved on.
From the team's side, none of that closure is visible. They delivered the thing. They are still standing where they were left, waiting for feedback on work that no longer needs urgent feedback after all, on a problem that has now been solved by other means or never needed solving at all. They were never told the situation changed. They were never told they could stop waiting. They were never told the urgency had passed.
This is the specific shape of the misattunement: leadership experiences the dissolution of urgency as a quiet relief, and forgets that the contract is still open on the other side. The team experiences the silence as a verdict — on the work, on themselves, and on how much their time was actually worth in the first place.
What the team learns
After the third or fourth Friday like this, something shifts. The team still delivers. They still hit the deadlines. But they eventually stop believing the urgency means anything. They keep their weekend plans. They learn that urgent means urgent for them, but only optional for the person asking. And eventually: they stop raising it.
This is what misattunement does. It doesn't break anything dramatically. It reshapes what people believe about their work, and they stop telling you what they've come to believe.
The cost shows up as quiet recalibration rather than line items, which is why it stays invisible until people leave. Hope erodes in the spaces between decisions, not in the decisions themselves. A leader can make every individual call correctly — the request was reasonable, the situation genuinely changed, the follow-up was on the list — and still produce, through the accumulated experience of those moments, a team that has stopped believing the urgency means anything.
This is the part that's hardest to see from inside leadership. The decisions look fine in isolation. The pattern only exists in the texture between them. And that texture is what the team is actually responding to.
What attuned leaders begin to notice
The shift isn't to communicate urgency more carefully. It's to notice that urgency, once created, has been signed on both sides. If you ask someone to compress their Friday evening into your timeline, you've signed something. The signature is invisible to you and entirely visible to them. Until that asymmetry is named, no process change will reach what the team is actually responding to.
The Friday team didn't quit the next Monday. They recalibrated. They stayed.
But a part of them left.
Seeing this is where the work begins.
If this pattern lands — if you've recognized your organization in it, or yourself — I'd love to hear from you.
