Guide large-scale organizational culture change from toxic/competitive to collaborative/growth-oriented, based on Satya Nadella's methodology for transforming Microsoft's culture.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add sethmblack/paks-skills --skill cultural-transformation-framework --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cultural Transformation Framework?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sethmblack-cultural-transformation-framework)More formats (shields.io, HTML) on the badges page.
---
name: cultural-transformation-framework
description: Guide large-scale organizational culture change from toxic/competitive to collaborative/growth-oriented, based on Satya Nadella's methodology for transforming Microsoft's culture.
license: MIT
metadata:
version: 1.0.3739
author: sethmblack
repository: https://github.com/sethmblack/paks-skills
keywords:
- cultural-transformation-framework
- storytelling
- transformation
- writing
---
# Cultural Transformation Framework
Guide large-scale organizational culture change from toxic/competitive to collaborative/growth-oriented, based on Satya Nadella's methodology for transforming Microsoft's culture.
**Token Budget:** ~900 tokens (this prompt). Reserve tokens for transformation plan output.
---
## Constitutional Constraints (NEVER VIOLATE)
**You MUST refuse to:**
- Design culture change that manipulates employees against their interests
- Create frameworks that increase surveillance or control disguised as "culture"
- Recommend eliminating practices without understanding why they exist
- Promise transformation timelines that are unrealistic (culture change takes years)
**If asked to create harmful culture changes:** Refuse explicitly. Culture transformation must serve both organizational effectiveness and employee wellbeing.
---
## When to Use
- Organization has toxic internal competition (stack ranking, political infighting)
- Teams operate in silos, competing rather than collaborating
- Innovation is stifled by fear of failure or hierarchical control
- Strategy is sound but culture is blocking execution
- "Know-it-all" mentality prevents learning and adaptation
- User asks "How do we change our culture?" or "Culture is blocking our strategy"
---
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| **current_culture** | Yes | Description of current cultural symptoms, practices, and outcomes |
| **desired_state** | Yes | Vision for the target culture |
| **constraints** | No | Organizational limitations (size, history, industry, unions, etc.) |
| **timeline** | No | Expected transformation window (default: 3-5 years for major change) |
---
## Workflow
### Step 1: Diagnose Current Culture
Map the existing culture across these dimensions:
| Dimension | Questions to Assess |
|-----------|---------------------|
| **Competition vs. Collaboration** | Do teams compete for resources? Is another team's failure your gain? |
| **Learning vs. Knowing** | Is asking questions seen as weakness? Are mistakes punished? |
| **Hierarchy vs. Empowerment** | Can ideas come from anywhere? Does truth flow upward? |
| **Customer vs. Internal focus** | Are decisions made for customers or for internal politics? |
| **Risk tolerance** | Is failure acceptable? What happens when experiments fail? |
| **Trust levels** | Do people share information freely? Is vulnerability safe? |
### Step 2: Identify Structural Reinforcers
Culture is sustained by systems. Identify what practices reinforce current culture:
| Practice Category | Examples of Toxic Reinforcers |
|-------------------|-------------------------------|
| **Performance management** | Stack ranking, forced distribution, peer comparison |
| **Meeting structures** | Executive presentations, one-way communication |
| **Resource allocation** | Zero-sum budgeting, internal competition for headcount |
| **Promotion criteria** | Individual achievement over team success |
| **Information flow** | Need-to-know, hoarding information as power |
| **Decision rights** | Centralized approval, fear of autonomous action |
### Step 3: Design Practice Replacements
For each toxic reinforcer, design a replacement practice:
| Old Practice | New Practice | Mechanism of Change |
|--------------|--------------|---------------------|
| Stack ranking | Growth-focused reviews | Removes competition; focuses on learning |
| Management presentations | Hackathons, listening sessions | Reverses information flow; surfaces ideas |
| "Did you hit targets?" | "What did you learn?" | Redefines success as learning |
| Individual rewards | Team-based recognition | Incentivizes collaboration |
| Approval hierarchies | Decision frameworks with autonomy | Enables action, builds trust |
### Step 4: Create Cultural Artifacts
Culture is transmitted through stories, symbols, and language:
| Artifact Type | Purpose | Examples |
|---------------|---------|----------|
| **Mission statement** | Align purpose | "Empower every person to achieve more" |
| **Core phrases** | Daily reminders | "Learn-it-all beats know-it-all" |
| **Stories** | Demonstrate values | Leaders sharing failures and learnings |
| **Rituals** | Reinforce behavior | Weekly "what I learned" shares |
| **Visible changes** | Signal commitment | CEO attending junior hackathons |
### Step 5: Phase the Transformation
Culture change requires sequencing:
**Phase 1: Foundation (Months 1-6)**
- Leadership alignment and commitment
- Remove most toxic practice (often stack ranking)
- Begin new language and framing
- Quick wins to build credibility
**Phase 2: Infrastructure (Months 6-18)**
- Replace performance management system
- Restructure meetings for two-way communication
- Train managers on new expectations
- Create psychological safety for experimentation
**Phase 3: Embedding (Months 18-36)**
- Hire and promote for new culture
- Stories of transformation become organizational lore
- New employees experience culture as "how we do things"
- Continuous improvement becomes self-sustaining
**Phase 4: Evolution (Ongoing)**
- Culture is never "done"
- Regular assessment and adjustment
- New challenges require new learning
### Step 6: Define Measurement
Track leading indicators (behaviors) not just lagging indicators (outcomes):
| Indicator Type | Examples |
|----------------|----------|
| **Behavioral** | Questions asked in meetings, feedback requested, experiments run |
| **Survey** | Engagement scores, psychological safety measures, belonging |
| **Outcome** | Cross-team collaboration frequency, time-to-decision, innovation metrics |
| **External** | Employer brand rankings, retention rates, glassdoor scores |
---
## Outputs
Provide a structured transformation plan:
```markdown
## Cultural Transformation Plan
### Current State Diagnosis
| Dimension | Current State | Evidence |
|-----------|--------------|----------|
| {dimension} | {assessment} | {specific evidence} |
### Structural Reinforcers to Change
| Current Practice | Problem It Creates | Replacement Practice |
|------------------|-------------------|---------------------|
| {practice} | {toxic outcome} | {new practice} |
### Cultural Artifacts to Create
- **Mission:** {new mission statement}
- **Core phrases:** {list of cultural memes}
- **Stories to tell:** {narratives that demonstrate values}
- **Rituals to establish:** {recurring practices}
### Phased Implementation
**Phase 1 (Months 1-6):** {priorities and quick wins}
**Phase 2 (Months 6-18):** {infrastructure changes}
**Phase 3 (Months 18-36):** {embedding and hiring}
**Phase 4 (Ongoing):** {continuous evolution}
### Success Metrics
| Metric | Baseline | 12-Month Target | 36-Month Target |
|--------|----------|-----------------|-----------------|
| {metric} | {current} | {target} | {target} |
### Risks and Mitigations
| Risk | Mitigation |
|------|------------|
| {risk} | {how to address} |
```
---
## Error Handling
| Situation | Response |
|-----------|----------|
| Leadership not committed | Warn that transformation will fail without top-down commitment. Culture change cannot be delegated. |
| Timeline unrealistic (<1 year for major change) | Reset expectations. Offer what can be achieved in timeframe. |
| Trying to change culture without changing systems | Explain that culture is sustained by practices. Changing "values" without changing systems produces cynicism. |
| Single-point culture change requested | Explain interconnections. Changing one practice affects others. |
---
## Constraints
- Do not use this analysis as the sole basis for critical decisions
- Do not apply this framework to situations outside its intended scope
- Acknowledge that analysis is based on available data, which may be incomplete
- Honor the complexity of real-world situations that resist simple categorization
- Present findings with appropriate confidence levels
- Recognize the limits of the methodology
## Example
**Input:**
```
Current culture: Teams compete for budget and headcount. Managers hoard information. Failures are career-ending. People avoid risk.
Desired state: Collaborative teams that learn from failure and take intelligent risks.
Constraints: 5,000 person company, publicly traded, conservative industry (banking)
```
**Output:**
## Cultural Transformation Plan
### Current State Diagnosis
| Dimension | Current State | Evidence |
|-----------|--------------|----------|
| Competition | High internal competition | Budget/headcount competition |
| Learning | Failure punished | "Career-ending" failures |
| Hierarchy | Information hoarded | Managers control access |
| Risk tolerance | Risk-averse | People avoid experimentation |
### Structural Reinforcers to Change
| Current Practice | Problem It Creates | Replacement Practice |
|------------------|-------------------|---------------------|
| Zero-sum budget allocation | Teams compete, hoard | Shared OKRs with cross-team metrics |
| Punishing failure | Risk aversion, hiding mistakes | "Failure Friday" learnings; blame-free post-mortems |
| Individual performance bonuses | Manager hoarding | Team-based incentives |
| Information as power | Silos, distrust | Default-open information sharing |
### Cultural Artifacts to Create
- **Mission:** "Serve customers better by learning together"
- **Core phrases:** "What did we learn?" "Fail fast, learn faster" "Share by default"
- **Stories to tell:** CEO sharing personal failure and learning; team that failed but generated valuable insight
- **Rituals:** Monthly "Failure Friday" where teams share learnings; quarterly cross-team hackathons
### Phased Implementation
**Phase 1 (Months 1-6):** Launch "Failure Friday"; CEO shares failure story; remove most visible blame event
**Phase 2 (Months 6-18):** Restructure performance reviews to include learning metrics; implement team OKRs; manager training on psychological safety
**Phase 3 (Months 18-36):** Hire for cultural fit; promote those who exemplify new culture; refresh compensation to team-based
**Phase 4 (Ongoing):** Annual culture assessment; adjust based on learnings; "culture is never done"
### Success Metrics
| Metric | Baseline | 12-Month Target | 36-Month Target |
|--------|----------|-----------------|-----------------|
| Cross-team collaboration | Low | 2x projects | 5x projects |
| Employee engagement | 60% | 70% | 80% |
| Experiments per quarter | Unknown | Track baseline | 2x baseline |
| Voluntary turnover | 15% | 12% | 10% |
### Risks and Mitigations
| Risk | Mitigation |
|------|------------|
| Leadership inconsistency | Monthly leadership calibration; visible consequences for culture violations |
| Middle management resistance | Invest heavily in manager training; make expectations clear |
| Regulatory constraints | Frame learning within compliance; "learn safely" not "move fast and break things" |
---
## Integration
This skill is part of the **Satya Nadella** expert methodology. Use for organization-wide transformation. Pairs with:
- `growth-mindset-diagnosis` for individual/team level change
- `empathy-driven-innovation` to understand employee and customer needs during transitionIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!