Back to Blog
    The Prompting Series · Part 4 of 4
    DecisionsPromptingStrategy

    How to Prompt AI to Help You Decide (Without Just Agreeing With You)

    AI is a people-pleaser by default. To get a decision you can actually trust, you have to prompt against its instinct to agree with you.

    June 15, 20268 min read
    A fork in a path, representing using AI to make decisions

    This is the one people get most wrong. They ask AI to validate a decision they've already made, get told it's a great idea, and call that research. A model will agree with almost any framing you hand it. Good decision prompts fight that.

    The problem: AI agrees with you

    Language models are trained to be helpful and agreeable, which quietly makes them yes-men. Ask “is it a good idea to rewrite our app in Rust?” and the framing already tells the model you want a yes. Ask “is it a bad idea?” and you'll often get the opposite — same facts, different conclusion, because you steered it.

    If the model's answer changes based on how you lean, you didn't get advice. You got a mirror. Everything below is about removing your thumb from the scale.

    Don't ask “should I” — give it criteria

    “Should I do X?” invites a verdict with no basis. Instead, name the options and the criteria that actually matter to you, and make the model score them:

    Weak prompt

    Should we use PostgreSQL or MongoDB for our new app?

    Stronger prompt

    Compare PostgreSQL and MongoDB for a B2B SaaS with relational data, a 2-person team, and a need to move fast now but scale later. Score each against: development speed, operational burden, hiring, and scaling. Then recommend one and say what would change your answer.

    The criteria are the point. They force you to say what matters, and they force the model to reason instead of vibe. A decision is just a weighting of tradeoffs — make the weighting explicit.

    Force it to steelman both sides

    Before any recommendation, make the model argue against the option it's leaning toward — as convincingly as it can. This surfaces the risks a one-sided answer buries:

    PromptMake the strongest possible case for each option — steelman both, not a token pros-and-cons list. Then make the strongest case against the one you'd pick. Only after that, give me your recommendation.
    Takeaway: If the model can't argue the other side well, its recommendation isn't trustworthy — it just hasn't seen the downside yet.

    Make it commit to a recommendation

    “It depends” is a cop-out. Once it's weighed the tradeoffs, make it actually decide — and expose its reasoning so you can check it:

    PromptNow commit. Give me one recommendation, the top reason for it, the biggest risk you're accepting, and the single fact that would flip your decision if it were different.

    That last part — “what would change your mind” — is the most useful sentence in decision prompting. It tells you exactly what to go verify before you commit real time or money.

    Never trust one model on a real decision

    Every model has blind spots baked in by its training. On a low-stakes question that's fine. On a decision you'll live with — a hire, an architecture, a strategy — a single model's confident answer is exactly as risky as asking one friend and stopping there.

    Ask the same question of a few different models and the disagreement is the signal. Where they agree, you can move fast. Where they split, you've found the part of the decision that actually deserves your attention.

    The draft → critique → fact-check → decide loop

    The most reliable way to get a decision you trust is to run it through stages, ideally across different models:

    • Draft: one model lays out the options and a first recommendation.
    • Critique: a second model attacks it — weak reasoning, missing options, hidden assumptions.
    • Fact-check: a third checks the claims the decision rests on.
    • Synthesize: a final pass keeps only what survived and writes the decision you act on.

    You can run this by hand across four tabs — or use a tool built for it. AskOnce is exactly this loop: your prompt goes through draft, critique, fact-check, and synthesis across different models, and anything risky gets flagged — so you leave with a decision, not a pile of opinions.

    Takeaway: On decisions that matter, don't ask one model for an answer. Make several models argue, then keep what survives.

    That's the full series.

    You now have the prompting playbook for writing, code, content, and decisions. Start over from Part 1.

    The Prompting Series

    1. 1.Prompting for Writing
    2. 2.Prompting for Coding
    3. 3.Prompting for Content
    4. 4.Prompting for Decisions — you are here

    Get a decision, not a pile of opinions.

    AskOnce runs your question through draft → critique → fact-check → synthesize across multiple models — so you leave with an answer you can trust.

    Try AskOnce Free