role-switch_skill

Overview

This skill helps teams uncover blind spots, align stakeholders, and make better decisions by analyzing a situation from multiple roles. It turns a single perspective into a structured multi-stakeholder synthesis that highlights tensions, tradeoffs, and concrete paths to consensus. Use it to pressure-test proposals, build empathy, and design decisions that survive cross‑functional scrutiny.

How this skill works

You frame the decision, pick 3–6 relevant roles, then inhabit each role’s mindset: goals, fears, success metrics, and constraints. The skill surfaces where perspectives conflict, maps explicit tradeoffs, and proposes synthesis options (sequential, hybrid, mitigations). Final output recommends alignment steps, owners, and next experiments or escalations.

When to use it

• When stakeholders have conflicting priorities (e.g., engineering vs product vs legal).
• To pressure-test a proposal before presenting it to diverse audiences.
• When you suspect blind spots from a single perspective or missing assumptions.
• To build empathy and predict objections from other functions.
• When decisions have multi-dimensional impact (technical, business, regulatory).

Best practices

• Select 3–6 roles with different goals, incentives, or constraints for balance.
• Inhabit perspectives charitably—use the strongest plausible version of each role.
• Work at interest level (why they want something), not just positions (what they ask for).
• Surface explicit tradeoffs and propose sequential or hybrid paths to reduce friction.
• Flag assumptions and invite real stakeholders to validate perspective-taking.

Example use cases

• API version deprecation: surface eng, PM, CS, finance perspectives and propose phased deprecation with support tiers.
• Build vs buy decision: map engineering, finance, product, legal tensions and recommend pilot + fallback.
• Pricing strategy: balance finance, marketing, sales, product to design tiered or usage-based pricing.
• Return-to-office policy: synthesize leadership, employees, HR, finance to propose trial hybrid model.
• Technical migration: propose incremental migration plan addressing engineering, PM, users, DevOps concerns.