Perspective Rotation Pattern

Problem

Solution

Implementation steps

1. Define 3–5 relevant domain perspectives for the question type (e.g., for product decision: engineering, user experience, business model, security, regulatory)
2. For each perspective, generate an isolated analysis: "Analyze this from the perspective of a [role] who cares most about [primary_concern]"
3. After all perspectives complete, run synthesis pass: identify conflicts between perspectives, identify blind spots in original framing, surface non-obvious considerations
4. Final output must include: per-perspective summary, cross-perspective conflicts, and synthesis recommendation that explicitly weights perspectives
5. Document which perspectives were applied so future agents can identify missing viewpoints

Examples

• –Architecture decisions evaluated by security engineer, performance engineer, and product manager
• –Business strategy evaluated from customer, competitor, and regulator viewpoints
• –Research findings reviewed from methodology, statistics, and domain expert angles

Anti-patterns

• –Fake rotation where all perspectives reach same conclusion — indicates generic prompting rather than genuine perspective shift
• –Too many perspectives (>7) causes cognitive overload and diluted synthesis
• –Skipping synthesis step — the value is in the intersection, not the individual perspectives