stakeholders-org-design

# Stakeholders & Organizational Design

## Table of Contents
1. [Purpose](#purpose)
2. [When to Use](#when-to-use)
3. [What Is It](#what-is-it)
4. [Workflow](#workflow)
5. [Stakeholder Mapping](#stakeholder-mapping)
6. [Team Interface Contracts](#team-interface-contracts)
7. [Capability Maturity](#capability-maturity)
8. [Common Patterns](#common-patterns)
9. [Guardrails](#guardrails)
10. [Quick Reference](#quick-reference)

## Purpose

Stakeholders & Organizational Design provides frameworks for mapping influence networks, designing effective team structures aligned with system architecture (Conway's Law), defining clear team interfaces and responsibilities, and assessing organizational capability maturity to guide improvement.

## When to Use

**Invoke this skill when you need to:**
- Design or restructure organizational teams (functional → product, monolith → microservices teams, platform teams)
- Map stakeholders for change initiatives (power-interest matrix, influence networks, champions/blockers)
- Define team interfaces and contracts (APIs, SLAs, handoff protocols, decision rights)
- Assess capability maturity (DevOps/DORA, security/CMMC, agile, data, design maturity models)
- Apply Conway's Law (align team structure with desired system architecture)
- Establish governance frameworks (RACI, decision rights, escalation paths)
- Plan cross-functional collaboration models (product triads, embedded vs centralized)
- Design team topologies (stream-aligned, platform, enabling, complicated-subsystem)

**User phrases that trigger this skill:**
- "How should we structure our teams?"
- "Map stakeholders for [initiative]"
- "Define team interfaces"
- "Assess our [capability] maturity"
- "Conway's Law"
- "Team Topologies"
- "RACI matrix"

## What Is It

A framework combining:
1. **Stakeholder Mapping**: Power-interest matrix, influence networks, RACI for decision rights
2. **Organizational Design**: Team structures aligned with architecture and strategy
3. **Team Interfa