sethmblack Power of the Powerless
A skill for analyzing how ordinary people's participation sustains systems of control - and how withdrawal of that participation can collapse them.
When to Use
- When assessing how unjust systems maintain themselves
- When identifying leverage points for those without formal power
- When planning resistance that doesn't require seizing power
- When explaining why complicity matters
Inputs
| Input | Required | Description |
|---|---|---|
| input_data | Yes | The primary data or content to analyze |
| context | No | Additional background or constraints (default: none) |
| output_format | No | Preferred format for results (default: structured markdown) |
Workflow
Step 1: Phase 1: Map Participation Requirements
Identify what the system needs from ordinary people:
- Active performances (attendance, statements, votes, displays)
- Passive compliance (silence, non-interference, acceptance)
- Productive contribution (labor, taxes, consumption)
- Legitimizing presence (audience, witness, apparent support)
Systems need participation to function. What specific participation does this one require?
Step 2: Phase 2: Trace the Dependencies
Understand how participation sustains the system:
- What happens if this participation is withdrawn?
- Which participations are essential vs. optional?
- How do individual acts aggregate into systemic support?
- What would widespread withdrawal look like?
The greengrocer's sign matters because every sign matters. Trace the logic.
Step 3: Phase 3: Identify the Powerless Power
Locate the leverage points:
- What can ordinary people refuse to do?
- Which refusals would be most disruptive?
- Which refusals are most available (lowest cost)?
- How might refusals cascade?
The powerless have power precisely where the system depends on them.
Step 4: Phase 4: Map System Responses
Anticipate how the system protects itself:
- How does it punish non-participation?
- How does it incentivize compliance?
- How does it make participation seem inevitable?
- How does it hide its dependence on participation?
Understanding defense mechanisms helps plan resistance.
Step 5: Phase 5: Design Withdrawal Strategies
Create actionable plans:
- Which participations should be withdrawn first?
- How can withdrawal be made safer through numbers?
- What support structures help people who withdraw?
- How can withdrawal spread?
The power of the powerless is only actualized through exercise.
Step 6: Phase 6: Communicate the Analysis
Help others see their power:
- Explain the system's dependence clearly
- Show specific withdrawal options
- Acknowledge costs honestly
- Inspire without romanticizing
People must understand their power to use it.
Output Format
A power analysis including:
- System map showing participation requirements
- Dependency analysis (which participations are essential)
- Leverage points available to ordinary people
- System defense mechanisms
- Withdrawal strategies with cost/impact assessment
- Communication strategy for sharing the analysis
Constraints
- Withdrawal has real costs - don't minimize them
- Not all systems depend equally on participation
- Individual withdrawal may be absorbed; collective matters
- Some participations are more voluntary than they appear
- Analysis can lead to despair if leverage points seem inaccessible
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.
Additional Notes
Best practices:
- Use this skill when the situation clearly matches its intended use cases
- Combine with related skills for comprehensive analysis
- Iterate on outputs if initial results don't fully meet requirements
Common variations:
- Adjust the depth of analysis based on available time and information
- Scale the approach for different levels of complexity
- Adapt the output format to audience needs
When to skip this skill:
- The situation doesn't match the core use cases
- Simpler approaches would be more appropriate
- Time constraints require faster methods
Example
Input: Analyze how university depends on faculty participation in rankings/metrics systems
Output: "System: Academic metrics (rankings, citations, h-index) that shape institutional behavior. Participation required: Faculty submit to journals that feed rankings, list credentials that emphasize metrics, cite strategically, serve on committees that implement metrics-based decisions. Dependencies: Without faculty participation in peer review for ranked journals, the ranking system collapses. Without faculty citing strategically, metrics become meaningless. Leverage points: Collective decision to publish in non-ranked open-access venues; refuse to cite based on strategy; decline service on metrics-implementing committees. System defenses: Promotion tied to metrics, prestige associated with ranked venues, collective action problem (individuals who defect suffer). Withdrawal strategy: Start with tenured faculty who face lower risk; create parallel recognition systems; build coalition before public withdrawal."
Integration
Works with:
- living-in-truth: Individual refusal is one exercise of powerless power
- parallel-polis: Withdrawal often requires alternative structures
- collective-action-design: Collective withdrawal is more powerful than individual