dialectical-mapping-steelmanning_skill

Overview

This skill helps teams and individuals escape false binaries by steelmanning opposing positions, mapping underlying principles and tradeoffs, and synthesizing principled third-way solutions. It produces clear, actionable analyses that make costs and benefits explicit so decisions move beyond polarized arguing to practical resolution.

How this skill works

I first present each side in its strongest, most charitable form (steelman), identifying the core values and best arguments supporters would recognize. Next I map what each side optimizes for and what it sacrifices, producing a compact tradeoff view. Finally I propose a synthesis—a higher‑order principle or hybrid pattern—with explicit new tradeoffs and recommended guardrails for implementation.

When to use it

• When a debate is framed as a false dichotomy and better options likely exist
• When polarized stakeholders need their views fairly represented and respected
• When tradeoffs are hidden and must be made explicit for decision-making
• When you want a principled ‘third way’ (temporal, conditional, dimensional, or higher-order)
• During design, product, policy, or strategy discussions with competing priorities

Best practices

• Steelman each side so adherents would recognize the representation
• Identify underlying principles (why each side values what it values), not just preferences
• Prefer synthesis that transcends the binary rather than a 50/50 compromise
• Make new tradeoffs explicit: what you gain and what you sacrifice versus pure positions
• Validate synthesis by role‑playing critiques from both original positions

Example use cases

• Startup: prioritize growth vs profitability → produce ‘profitable growth’ with channel segmentation and staged scaling
• Product design: simple UX vs powerful features → propose progressive disclosure and power modes
• Org design: centralization vs decentralization → centralize strategy, decentralize execution with escalation rules
• Policy: privacy vs security → conditional rules, audits, and compensating controls
• Engineering: monolith vs microservices → hybrid boundary-first modularization and staged extraction