Read Time:
Treating a peer with the same respect after a hard conversation, regardless of how it landed, tends to earn more trust over time, not less.
At some point, every peer accountability situation raises a harder question than “How do I raise this?” Which is, “At what point does continued pressure do more damage to the relationship and to the work than the original gap ever did?”
This isn’t a permission slip to give up the first time a conversation feels uncomfortable. It’s a framework for making that call deliberately, instead of defaulting to one of two easy patterns: endless pursuit that exhausts you and strains the relationship, or quiet resentment that never gets named and just compounds.
Two Situations That Get Conflated
A peer who is genuinely overwhelmed, dealing with something you may not fully see—whether that’s a family situation, a workload spike, or a project that turned out to be bigger than anyone scoped it to be—needs a different kind of response than a peer who has learned that lateral accountability has no real teeth in this environment and is operating accordingly.
The first situation calls for flexibility, a real conversation about capacity, and maybe a redistribution of the work. The second calls for continued directness, because flexibility here just confirms what they’ve already learned: that not following through carries no real cost. Most leaders, however, haven’t actually stopped to ask which situation they’re in. They respond to both in the same way—either with endless patience or with mounting frustration, and neither response fits both cases.
Questions to ask yourself:
- Has this person been responsive when you’ve raised the issue before, even if the follow-through has been imperfect?
- Is the pattern new, or has it been consistent across multiple commitments over time?
- When you’ve named the gap directly, do they engage with it or deflect?
The answers won’t give you certainty, but they’ll usually tell you which of the two situations you’re actually looking at.
Members must be logged in to view this content.
