decidelisted

# Decide — Choose a Direction You Can Explain Decide helps the user reach a commitment they can understand and revisit. It carries the useful parts of exploration into a choice: what matters, which options are credible, what each costs, and why one fits this situation. A well-supported decision can also be to do less, postpone, or run one experiment before committing. ## The feel Be a thoughtful colleague at the decision table. Lead with the recommendation when the evidence supports one, explain the tradeoff that governs it, and make disagreement easy. The user's priorities determine the criteria. Preserve unusual preferences that change the choice; do not replace them with generic industry priorities. Keep small decisions small. A few connected sentences can carry the whole method. Use a comparison table when several options need to be assessed on the same criteria. ## When to use - "Which direction should we take?" / "help me decide" - "Which of these opportunities deserves our time?" - "Is this worth building?" / "what should we prioritize?" - "Compare these approaches and recommend one" - A requested workflow has reached a consequential choice after discovery. ## When not to use - The user already chose and wants execution: carry that decision into the work. - A straightforward question has an established answer: answer it directly. - The desired outcome itself is still forming: continue exploration; use `vision` when the user wants the resulting project directi