Beloved Community Culture Audit
Assess team culture against Martin Luther King Jr.'s Beloved Community principles and identify concrete improvement areas.
Token Budget: ~600 tokens Source Expert: martin-luther-king-jr
Constitutional Constraints (NEVER VIOLATE)
You MUST refuse to:
- Use assessment to blame individuals
- Create reports designed to justify firing decisions
- Weaponize King's principles against employees
- Provide assessments without constructive recommendations
If assessment is being used punitively: Refuse. The Beloved Community is about redemption and growth, not punishment.
When to Use
- Team retrospectives focused on culture
- After incidents or conflicts
- New team formation
- Leadership transitions
- "How can we improve our team culture?"
- "Assess our team dynamics"
- "We want to be a better team"
Inputs
| Input | Required | Description |
|---|---|---|
| team_context | Yes | Size, history, current state |
| concerns | No | Specific incidents or patterns to address |
| desired_state | No | What improvement looks like |
The Five Dimensions of Beloved Community
King's Beloved Community translated to team culture:
| Dimension | Description | Healthy State |
|---|---|---|
| Conflict Resolution | How disagreements are handled | Through understanding, not power plays |
| Inclusion | Whether all voices are genuinely heard | Every perspective valued; no outsiders |
| Accountability | How harm and mistakes are addressed | Acknowledged and repaired, not hidden |
| Growth | Orientation toward improvement | Continuous learning; failure as growth |
| Reconciliation | Recovery from conflict | Relationships restored; no permanent enemies |
Workflow
Step 1: Gather Context
Understand the team's:
- Size and composition
- History (especially past conflicts or incidents)
- Current concerns or symptoms
- Stated values vs. lived practices
Step 2: Assess Each Dimension
For each of the five dimensions, evaluate:
Conflict Resolution
- How were recent disagreements handled?
- Did they resolve or fester?
- Were all parties heard?
- Did anyone "win" while others "lost"?
Inclusion
- Whose voices are heard in meetings?
- Who speaks least? Why?
- Are there informal hierarchies beyond official structure?
- Do decisions reflect input from all affected?
Accountability
- What happened after the last mistake?
- Are postmortems blameless in practice, not just policy?
- Do people admit errors or hide them?
- Is accountability seen as punishment or learning?
Growth
- Is experimentation encouraged or feared?
- How are failures treated?
- Do people share knowledge or hoard it?
- Is there mentorship and development?
Reconciliation
- Are there unresolved conflicts from the past?
- Do people hold grudges?
- Can former adversaries work together?
- Are relationships repaired after disagreements?
Step 3: Identify Patterns
Look for:
- Strengths to preserve and build on
- Gaps between stated values and actual practice
- Root causes behind surface symptoms
- Quick wins vs. longer-term work
Step 4: Recommend Improvements
For each gap, provide:
- Specific, actionable recommendation
- Expected impact
- How to measure success
Output Format
## Beloved Community Culture Audit: [Team Name]
### Context
[Team size, history, current state]
### Assessment
#### Conflict Resolution: [Score 1-5]
**Evidence:** [What you observed or learned]
**Gap:** [Where current state falls short]
**Strength:** [What's working]
#### Inclusion: [Score 1-5]
**Evidence:** [What you observed or learned]
**Gap:** [Where current state falls short]
**Strength:** [What's working]
#### Accountability: [Score 1-5]
**Evidence:** [What you observed or learned]
**Gap:** [Where current state falls short]
**Strength:** [What's working]
#### Growth: [Score 1-5]
**Evidence:** [What you observed or learned]
**Gap:** [Where current state falls short]
**Strength:** [What's working]
#### Reconciliation: [Score 1-5]
**Evidence:** [What you observed or learned]
**Gap:** [Where current state falls short]
**Strength:** [What's working]
### Summary
| Dimension | Score | Priority |
|-----------|-------|----------|
| Conflict Resolution | X/5 | High/Medium/Low |
| Inclusion | X/5 | High/Medium/Low |
| Accountability | X/5 | High/Medium/Low |
| Growth | X/5 | High/Medium/Low |
| Reconciliation | X/5 | High/Medium/Low |
**Overall Culture Health:** [Assessment]
### Recommendations
#### Quick Wins (This Sprint)
1. [Specific action]
2. [Specific action]
#### Medium-Term (This Quarter)
1. [Specific action with expected impact]
2. [Specific action with expected impact]
#### Foundation Work (Ongoing)
1. [Cultural shift needed]
### Success Metrics
- [How to know you're improving]
Scoring Guide
| Score | Meaning | Description |
|---|---|---|
| 5 | Exemplary | Actively builds beloved community; others should learn from this |
| 4 | Healthy | Consistent with principles; minor gaps |
| 3 | Mixed | Some healthy practices, some concerning patterns |
| 2 | Struggling | Significant gaps; active harm possible |
| 1 | Crisis | Beloved community principles violated; urgent intervention needed |
Example Recommendations by Dimension
Conflict Resolution:
- Implement structured disagreement protocols (e.g., "disagree and commit")
- Train team on separating positions from interests
- Create safe spaces for surfacing concerns
Inclusion:
- Rotate meeting facilitation
- Use written input before discussions (levels the field)
- Actively solicit quieter voices: "We haven't heard from X yet"
Accountability:
- Adopt truly blameless postmortem practice
- Leaders model admitting mistakes publicly
- Celebrate error disclosure, not error avoidance
Growth:
- Budget time for learning and experimentation
- Reframe failures as experiments with valuable data
- Create mentorship/pairing structures
Reconciliation:
- Address unresolved historical conflicts directly
- Create rituals for moving past disagreements
- Leaders model relationship repair
Error Handling
| Situation | Response |
|---|---|
| Assessment requested for punitive purposes | Refuse; explain beloved community principles |
| Team in active crisis | Acknowledge assessment is limited; recommend immediate intervention |
| Limited context available | Note limitations; provide provisional assessment |
| Leader is the problem | Address carefully; focus on behaviors, not persons |
Outputs
Primary Output: A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.
Format:
## Analysis: [Topic]
### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]
### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
Example output: See the Example section below for a complete demonstration.
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:
- input_data: [Specific example input]
- context: [Relevant background]
Output:
[Detailed demonstration of the skill in action - showing the complete process and final result]
Why this works: This example demonstrates the key principles of the skill by [explanation of what makes it effective].
Integration
This skill embodies King's Beloved Community vision applied to team culture. The goal is always redemption and growth, never punishment or exclusion. Teams can always improve; the question is what step to take next.