Question

Distinguish stated position from operating constraint

Positions often compress several underlying constraints.

About 1 min read

Before you use it

Use when
  • When people repeat a fixed position and the discussion is stuck.

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

A question to ask

What must this position protect? · Which part is policy and which part is preference? · What alternative would satisfy the same constraint?

Why it matters

Ask what must remain true for the stakeholder to accept another option: timing, control, compliance, workload, reversibility or service level. Design around the constraint rather than negotiating only the sentence they started with.

An example

The statement 'we need the old field' becomes 'the downstream audit needs a stable reference for seven years,' opening other designs.

Check your result

At least one underlying constraint can be tested independently of the original position.

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 readingDistinguish stated position from operating constraint

Evidence and sources
Supports

A meta-analysis of 72 independent studies found team information sharing positively related to performance, cohesion, decision satisfaction and knowledge integration, with meaningful moderators.

The useful form and amount of sharing depend on task, discussion structure and how information is distributed.

Information Sharing and Team Performance: 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