negotiated-decision-framework
Multi-stakeholder coordination for decisions involving competing interests, different value systems, or organizational politics. Use when multiple parties must agree, when power dynamics affect decisions, or when consensus is required but perspectives diverge. Unlike DR (resolves conceptual tensions), NDF resolves stakeholder tensions.
What this skill does
# Negotiated Decision Framework (NDF) **Purpose**: Navigate multi-stakeholder decisions where different parties have legitimate but competing interests. NDF helps find decisions that stakeholders can live with, even if no one gets everything they want. ## When to Use NDF **Use NDF when:** - Multiple stakeholders must agree (or at least not block) - Different parties have different success criteria - Power dynamics or politics affect the decision - Past decisions created winners/losers who remember - "Best technical answer" won't get adopted due to stakeholder resistance - Need buy-in for implementation success **Don't use NDF when:** - Single decision-maker with clear authority (use ToT) - Stakeholders agree on criteria (use ToT with shared criteria) - Conceptual tension, not stakeholder tension (use DR) - Time pressure prevents negotiation (use RTR, negotiate later) **NDF vs Other Patterns:** - DR: Resolves conceptual/philosophical tensions (NDF: resolves people tensions) - ToT: Finds optimal given criteria (NDF: finds optimal given stakeholders) - BoT: Explores solution space (NDF: explores stakeholder space) --- ## Core Methodology: ALIGN Framework ### A - Analyze Stakeholder Landscape **Goal**: Map who matters and what they care about **Process:** 1. Identify all stakeholders (not just vocal ones) 2. Assess their power and interest 3. Understand their underlying interests (not just stated positions) 4. Map relationships and alliances **Stakeholder Mapping Template:** ```markdown ## Stakeholder Analysis ### Power-Interest Grid | | Low Interest | High Interest | |-----------|--------------|---------------| | **High Power** | Keep Satisfied | Key Players | | **Low Power** | Monitor | Keep Informed | ### Stakeholder Profiles #### [Stakeholder 1] - **Role**: [Title/Function] - **Power Level**: [High/Medium/Low] - **Interest Level**: [High/Medium/Low] - **Stated Position**: [What they say they want] - **Underlying Interest**: [Why they want it - the deeper need] - **Success Criteria**: [How they'll judge the decision] - **Potential Blockers**: [What would make them oppose] - **Potential Sweeteners**: [What would win their support] - **Relationships**: [Allies, conflicts with other stakeholders] #### [Stakeholder 2] ... ``` **Interest Archeology:** Don't just accept stated positions. Dig deeper: - "We need feature X" → Why? What problem does X solve? - "This must be done by Q2" → Why? What happens if Q3? - "We can't change the database" → Why? What's the actual constraint? --- ### L - Locate Zones of Agreement **Goal**: Find common ground before addressing differences **Process:** 1. Identify shared goals (even if approaches differ) 2. Find overlapping interests 3. Establish agreed constraints 4. Build on areas of alignment **Agreement Mapping:** ```markdown ## Zones of Agreement ### Shared Goals - [Goal that all stakeholders want] - [Another shared goal] ### Overlapping Interests | Interest | Stakeholders Who Share | |----------|------------------------| | [Interest 1] | A, B, C | | [Interest 2] | A, D | | [Interest 3] | B, C, D | ### Agreed Constraints - [Constraint everyone accepts] - [Another constraint] ### Foundation Statement "We all agree that [shared goal], within [constraints], and we all want [overlapping interest]." ``` **Use agreement zones to:** - Frame discussions positively - Remind stakeholders of shared purpose when tensions rise - Build solutions that honor common ground first --- ### I - Identify Irreducible Conflicts **Goal**: Understand where genuine conflicts exist (not all conflicts are real) **Conflict Classification:** | Type | Description | Resolution Approach | |------|-------------|---------------------| | **False Conflict** | Misunderstanding, same goal different words | Clarify, reframe | | **Resource Conflict** | Competing for same limited resource | Expand pie, prioritize, take turns | | **Value Conflict** | Different fundamental values | Acknowledge, find higher-order value | | **Interest Conflict** | Different parties want different outcomes | Trade, compromise, or escalate | | **Relational Conflict** | History/politics, not the actual issue | Address relationship separately | **Conflict Analysis Template:** ```markdown ## Conflict Analysis ### Conflict 1: [Name] - **Parties**: [Stakeholder A] vs [Stakeholder B] - **Type**: [False/Resource/Value/Interest/Relational] - **A's Position**: [What A wants] - **B's Position**: [What B wants] - **Underlying Interests**: - A really needs: [Deeper interest] - B really needs: [Deeper interest] - **Compatible?**: [Can both interests be met?] - **Resolution Path**: [How to address] ``` **Key Insight**: Many conflicts are about HOW, not WHAT. If underlying interests are compatible, the conflict is solvable. --- ### G - Generate Integrative Options **Goal**: Create solutions that satisfy multiple stakeholders' interests **Integrative Strategies:** 1. **Expand the Pie**: Find resources to satisfy everyone - "Can we get more budget/time/people?" - "Can we do both sequentially instead of choosing?" 2. **Trade Across Issues**: Give on low-priority, get on high-priority - "You care more about X, we care more about Y - swap?" - "We'll accept your timeline if you accept our approach" 3. **Add Issues**: Bring in new elements to enable trades - "What if we also addressed Z, which you care about?" - "Can we package this with the other decision?" 4. **Compensate**: Make up for losses elsewhere - "You lose on this, but gain on that" - "This time your priority, next time ours" 5. **Reframe**: Find higher-order framing everyone can support - "We all want customer success - here's how this achieves it" - "This isn't A vs B, it's achieving C" **Option Generation Template:** ```markdown ## Integrative Options ### Option 1: [Name] - **How it works**: [Description] - **Satisfies [Stakeholder A]**: [How it meets their interest] - **Satisfies [Stakeholder B]**: [How it meets their interest] - **Trade-offs**: [What each party gives up] - **Feasibility**: [Can we actually do this?] ### Option 2: [Name] ... ### Comparison Matrix | Option | Stakeholder A | Stakeholder B | Stakeholder C | Feasibility | |--------|---------------|---------------|---------------|-------------| | Opt 1 | [Score 1-5] | [Score 1-5] | [Score 1-5] | [High/Med/Low] | | Opt 2 | [Score 1-5] | [Score 1-5] | [Score 1-5] | [High/Med/Low] | ``` --- ### N - Negotiate Commitment **Goal**: Move from options to agreement with genuine buy-in **Negotiation Principles:** 1. **BATNA Awareness**: Know each party's Best Alternative To Negotiated Agreement - If their BATNA is better than your offer, they won't agree - Improve your offer or worsen their BATNA (ethically) 2. **Commitment Levels**: Not all agreement is equal - **Comply**: Will do it if required (weak) - **Accept**: Can live with it (moderate) - **Endorse**: Will support it (strong) - **Champion**: Will advocate for it (strongest) 3. **Legitimate Process**: Stakeholders accept outcomes better when process felt fair - Were they heard? Were their interests considered? - Is the decision-making process transparent? **Commitment Template:** ```markdown ## Negotiated Agreement ### Decision Summary [The agreed decision in clear terms] ### Stakeholder Commitments | Stakeholder | Commitment Level | What They Get | What They Give | |-------------|------------------|---------------|----------------| | A | [Comply/Accept/Endorse/Champion] | [Their gain] | [Their concession] | | B | [Comply/Accept/Endorse/Champion] | [Their gain] | [Their concession] | ### Conditions and Contingencies - [Condition 1]: If [X], then [Y] - [Review point]: Revisit at [date/milestone] ### Dispute Resolution If disagreement arises: [How to handle] ``` --- ## Power Dynamics Navigation **When Power is Unequal:** | Situation | Strategy | |-----------|----------| | You have low pow
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.