deliberationlisted

# Deliberation Surface genuine tension in a decision before committing to a direction. ## When to use Some decisions get worse when you're forced to choose too early. Use deliberation when: - The options themselves are not yet well-defined - The problem may be framed incorrectly (the real question hasn't been asked) - Multiple legitimate constraints pull in different directions - Brainstorming feels premature — there's no clear "right shape" for the solution yet **Do not use for:** decisions that are already well-framed with clear options. Those go directly to `brainstorming`. Deliberation is for when you're not yet ready for options. ## Procedure ### 1. Name the decision State the decision being deliberated in one sentence. Be precise — a vague decision produces vague perspectives. > Example: "Should we migrate the authentication layer from JWT to session cookies?" ### 2. Identify 3–5 genuine stakeholder perspectives Choose perspectives that have real, distinct stakes in the decision. Each perspective represents a legitimate set of constraints or values — not a person, but a role with a coherent viewpoint. Good perspectives for technical decisions: - **The Security Engineer** — attack surface, credential management, audit trail - **The Developer Experience Advocate** — implementation complexity, debugging, onboarding - **The Ops/Infrastructure Engineer** — deployment, scaling, observability, failure modes - **The Maintainability Advocate** — long-term code health