conflict-resolution-diagram
Skill3 starsChanged 6 months agoMITView on GitHub
Use conflict resolution diagrams to resolve opposing demands by uncovering underlying needs and a shared goal. Use when a personal, team, product, or organizational conflict appears mutually exclusive.
In this repository23 other files it gives its agents.
- abstraction-ladderingSkill
- balancing-feedback-loopSkill
- concept-mapSkill
- confidence-determines-speed-vs-qualitySkill
- connection-circlesSkill
- cynefin-frameworkSkill
- decision-matrixSkill
- eisenhower-matrixSkill
- first-principlesSkill
- hard-choice-modelSkill
- iceberg-modelSkill
- impact-effort-matrixSkill
- inversionSkill
- ishikawa-diagramSkill
- issue-treesSkill
- ladder-of-inferenceSkill
- minto-pyramidSkill
- ooda-loopSkill
- productive-thinking-modelSkill
- reinforcing-feedback-loopSkill
- second-order-thinkingSkill
- situation-behavior-impactSkill
- six-thinking-hatsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
When facing a seemingly impossible conflict
- Distinctive: line 51
Shared Goal: Run a profitable business
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Conflict Resolution Diagram
Overview
Category: Problem Solving
A tool designed to help resolve conflicts by finding win-win solutions while ensuring the needs of both sides are met. Developed as part of the Theory of Constraints by Eliyahu Goldratt.
How to Use
When to Use
- When facing a seemingly impossible conflict
- Professional or personal conflicts
- Internal or external disagreements
Steps
- Identify demands/proposals of opposing sides
- Define underlying needs behind each position
- Find the shared goal
Diagram Structure
- Demands/proposals (mutually exclusive)
- Underlying needs/requirements
- Shared goal/objective
Process
- Work backwards (right to left)
- Ask key questions:
- What does each side want?
- What needs are satisfied by each proposal?
- What higher-level objective unites both sides?
Example Scenario
Context: Debating website redesign with a colleague
Initial Positions:
- Colleague: Wants to redesign website
- You: Against the project
Needs Discovered:
- Colleague: Improve conversion rate
- You: Minimize resource waste
Shared Goal: Run a profitable business
Resolution: Conduct small, targeted website experiments to improve conversion without extensive resources
Additional Resources
- Template Worksheet Available
- Sources:
- "The Logical Thinking Process" by H. William Dettmer
- Forte Labs Blog article on Logical Thinking Process
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.