Protocol
Separate person, intent and observable impact
Observable impact is easier to repair than inferred intent.
Before you use it
- Use when
- When feedback or conflict is sliding from a work problem into claims about character or motives.
Keep this limit in mind
- Psychological safety does not mean agreement, low standards or protection from consequences. Keep respectful challenge separate from unaccountable behavior.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Describe the behavior or decision, its effect, the requirement at risk and the next needed change. Ask about intent rather than asserting it.
Steps
- State the observable behavior.
- State the work impact.
- Name the requirement or boundary.
- Ask for context and agree the next change.
An example
Instead of 'you do not care about quality,' say 'the change entered test without the agreed reconciliation, so defects cannot be isolated.'
Check your result
The issue can be discussed without requiring agreement about someone's personality or motives.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingSeparate person, intent and observable impact
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaReward early problem surfacing with action
Evidence and sources
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
Edition and review
Version 0.1.0
No review details are supplied for this edition.