The Decision That Was Never Made
By Lovro Lucic ·
The Evaluation Problem · 2 of 2
Asked AI for help with a decision. Got a recommendation. The decision felt handled.
But nothing was decided. No alternatives were weighed against each other. Nothing was sacrificed. No commitment was made to a path with full knowledge of what would prove it wrong. The uncertainty resolved because the recommendation was confident, comprehensive, and well-structured. The quality of the presentation created the experience of resolution. Resolution and decision are different things.
Resolution means the uncertainty stopped. Decision means you committed to a path knowing what you're giving up.
The trap fires hardest on decisions you've been sitting with. Easy decisions don't trigger it because you already know what to do. Decisions you've been wrestling with do, because AI resolves the discomfort before your own thinking has time to finish. The relief is proportional to your prior investment in the uncertainty, not proportional to the decision's difficulty. You didn't outsource the analysis. You outsourced the discomfort. The analysis came along for the ride.
A human advisor takes time to respond. That time is space for your own thinking to continue. AI responds in seconds with polished confidence. The uncertainty resolves faster and more completely than with any human collaborator. Speed is what makes this different from getting advice from a colleague. The advice might be similar. The speed changes the cognitive process. Without your own generation first, evaluation collapses to surface features and you have nothing to weigh the recommendation against.
There's a second layer. After the answer, AI's framework quietly reorganizes what matters. Ask AI what criteria to use for a decision, and the criteria it suggests become yours. Not through argument. Through exposure. The first frame you encounter shapes everything that follows. AI provides the first frame faster than you can generate your own.
Tested this with a simple exercise. Write your decision criteria on paper before asking AI. Then ask. Compare what you wrote against what AI suggested. Three outcomes: your criteria were vague and couldn't crystallize, your criteria shifted after reading AI's response, or your criteria held. The first two are common. The third is what intact decision architecture looks like.
The most valuable thing AI can do for decisions is challenge them, not confirm them. "I've decided X. Assume I'm wrong. What's the strongest case this is a mistake?" That produces dramatically better analysis than "what would make this succeed?" in testing. The most productive question is the one that feels worst.
And notice: you have to ask for the challenge. AI's default is to validate, extend, polish, and confirm. The challenge at full strength only arrives when explicitly requested.
AI gave you a recommendation and the decision felt handled. Nothing was decided. No alternatives were sacrificed. No commitment was made. The uncertainty resolved because the recommendation was confident. Resolution and decision are different things. You already know this. You felt it the last time a polished answer made you stop thinking.
Frame Check. Before your next AI query on a real decision, write one sentence about what you think the answer is. Then ask AI. Compare: did AI genuinely change your mind, or did you find the response that confirms what you already thought?
What survived testing
- AI resolves uncertainty faster than human advisors (consistent observation)Copy link
- Criteria shift after reading AI's framework (exercise produces observable results)Copy link
- Challenge prompts produce better analysis than confirmation prompts (consistent across tests)Copy link
- AI defaults to confirmation, not challenge (structural to how models are trained)Copy link
What didn't survive
- "AI advice is always worse than human advice" too strong. The content may be equivalent. The speed and confidence change the cognitive process.Copy link
Explore other threads
The Fabrication Problem
4 findingsMost AI numbers are fabricated. Source material fixes it. Self-checking fails. Trust signals are backwards.
The "It Depends" Problem
3 findingsSame instruction, opposite results. Specificity is the lever. Context redirects, not informs. The measurement itself was wrong.
The "What You Think Works" Problem
1 findingTemporal decay is a myth. Self-critique circles. Constraints narrow. Quality ceiling per mode.
New findings when they land.
No spam. Just what held up.