There's a pending conversation in almost every team: the request nobody quite formulates, the complaint whispered in hallways but never said to someone's face, the broken promise nobody calls out to avoid "creating a bad vibe." The problem isn't having that conversation. The problem is how it's had —or how it keeps being avoided.
The cost of silence
What's not said still acts. A pending conversation doesn't disappear because you avoid it: it turns into accumulated resentment, into friction that keeps repeating without ever being named, into coordination of action that keeps failing for the same reason nobody ever says out loud. Avoiding the difficult conversation doesn't protect the relationship: it damages it more slowly, but it damages it all the same.
Separating the fact from the interpretation
Most difficult conversations break down at the same point: the observable fact ("you turned in the report three days late") gets mixed with the interpretation we make of that fact ("you don't care about the team"). The second one invites defense, not dialogue. Naming the fact first, and only then declaring how you're interpreting it —in first person, not as universal truth— completely changes how the other person receives it.
Avoiding the difficult conversation doesn't protect the relationship: it damages it more slowly, but it damages it all the same.
The structure behind the conversation: requests and promises
Much of the friction in teams doesn't come from bad intentions, it comes from poorly formed requests: no deadline, no clear conditions of satisfaction, no explicit yes or no from the other party. A well-run difficult conversation usually ends in a concrete request (what, by when, under what conditions) and an equally concrete promise in response —not in venting with nowhere to go.
Clear request = what's needed + by when + conditions of satisfaction. Without those three elements, it's not a request: it's an expectation the other person doesn't even know they're supposed to meet.
How this is worked in organizational coaching processes
In a operational friction diagnosis, much of the work consists of identifying which conversations are pending in a team and why they're being avoided —it's almost never a general lack of communication skills, but a specific conversational pattern that keeps repeating: ambiguous requests, promises that don't hold, feedback that arrives late or never arrives. Naming that specific pattern is what makes it possible to design a different way of having those conversations.
Frequently asked questions
Because we anticipate they'll damage the relationship or create conflict. But avoiding them doesn't remove the problem: the cost of silence keeps acting, and it usually turns into accumulated resentment or the same friction repeating without ever being named.
By separating the observable fact from the interpretation you made of it, and declaring your emotion in first person instead of accusing. A clear request, with concrete conditions of satisfaction, greatly reduces defensiveness compared to a vague complaint.
It's for anyone coordinating action with others, at any level of the org chart. The requests-and-promises structure isn't a management technique: it's the foundation of any effective coordination between people.
Comments