Heuristic

Trace incentives before interpreting resistance

Resistance may be rational inside another person's constraints.

About 1 min read

Before you use it

Use when
  • When a stakeholder repeatedly resists a proposal and the team is tempted to label the person difficult.

Keep this limit in mind

  • Formal governance and accountability still apply. Stakeholder analysis should expose constraints and decision rights, not justify bypassing them.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Before attributing motives, inspect goals, penalties, workload, ownership boundaries and risk exposure. A proposal that creates local cost for global benefit needs a design response, not a personality diagnosis.

An example

A country team resists a global validation rule because it adds manual review without reducing its local audit exposure.

Check your result

The explanation of resistance includes at least one observable constraint or incentive before any claim about attitude.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingTrace incentives before interpreting resistance

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details