What Claude Does Well in Decision-Making
Claude is genuinely useful for decisions because it is not emotionally invested in the outcome. No sunk cost feelings, no confirmation bias, no fear of looking wrong. It will tell you the strongest case against your preferred option without social awkwardness.
Claude is less useful as a decision-maker and more useful as a decision-stress-tester. The best use is not "what should I do?" but "here is what I am leaning toward -- argue against it as forcefully as you can."
The most underused capability: asking Claude what you might be missing. "What important factors have I not mentioned that might change this decision?" often produces the most valuable output of any decision-related prompt.
The Decision-Support Prompt Framework
Step 1 -- Full context dump: Tell Claude everything relevant. The options you are considering, what you know about each, what you are optimizing for, constraints, what you have already ruled out and why.
Step 2 -- Ask for blind spots first: "Based on what I have described, what important factors or considerations have I not mentioned?" This surfaces what you are missing before asking for analysis.
Step 3 -- Ask for the opposing argument: "What is the strongest case against the option I am leaning toward? Argue against it as forcefully as you can." Claude produces this without the social friction a human advisor would feel.
Step 4 -- Ask for decision criteria: "What are the three to five most important criteria for evaluating this decision, and how does each option perform on those criteria?"