Protocol
Escalate process risk without attacking motives
Escalate the observable coordination failure and its impact.
When it fits
- When collaboration behavior itself threatens delivery but personal accusations would make repair harder.
When to avoid it
- Psychological safety does not mean agreement, low standards or protection from consequences. Keep respectful challenge separate from unaccountable behavior.
Why it matters
Document the repeated behavior, its effect on the work, prior repair attempts and the specific support or decision needed. Leave motive claims out unless independently evidenced.
Steps
- Record the observable pattern.
- Show delivery or control impact.
- List prior repair attempts.
- Ask for a specific intervention or decision.
An example
The escalation says approvals repeatedly arrive after the agreed window and block testing; it does not claim another team is sabotaging the project.
Check your result
The escalation can be acted on without requiring a judgment about character.
Keep this limit in mind
- Psychological safety does not mean agreement, low standards or protection from consequences. Keep respectful challenge separate from unaccountable behavior.
Connected ideas
Useful withDebrief the work, not the person
Evidence and sources
Limits
A meta-analysis found both relationship conflict and task conflict negatively related to team performance and satisfaction on average, with task and task-complexity moderators.
The result cautions against treating conflict itself as beneficial; constructive disagreement still requires process design and cannot be reduced to one correlation.
Task Versus Relationship Conflict, Team Performance, and Team Member Satisfaction: A Meta-Analysis · Abstract