Bad decisions have a format. They're usually made in a meeting that ran 20 minutes over, with six people who wanted different things, zero written criteria, and someone saying "let's just go with our gut" right before lunch. Then someone else sends a recap email that invents consensus. You know the one.

AI decision-making prompts won't fix the politics. But they can do something genuinely useful: force the mess into a structure before it becomes a regret. If you know what you're deciding, what matters, what you're risking, and what you don't know yet, you're already ahead of most decision processes. AI can help you get there faster. It can't make the call for you, and it shouldn't.

Here's how to use it without handing over your judgment.

Why AI decision-making prompts work (and where they fail)

AI is fast and confident. Those two qualities together are a trap if you're not careful.

Throw a vague question at ChatGPT or Claude and it will hand you back a beautiful, structured, completely authoritative-sounding recommendation. The problem: it's optimizing for plausible, not correct. It doesn't know your company's real constraints. It doesn't know which executive will kill a project if it touches their budget. It doesn't know what your customers actually said last quarter versus what the last meeting slide claimed they said.

Rule #5 in Don't Replace Me is blunt about this: it's not smart, it's fast. Fluency is not wisdom. AI will write you a confident decision memo whether or not the underlying logic holds up. Your job is to bring the constraints, the stakes, the context, and the final call.

Used right, AI is a decision analyst with infinite patience and no ego. It will compare options, surface counterarguments, draft memos, and run structured thinking exercises without getting defensive about its preferred option. That's actually rare and useful. The catch is: garbage in, garbage fog out. Vague prompts get vague output dressed up as insight.

The prompts below are built around that reality. They help you structure your thinking, not outsource it.

Before you start: a quick word on what not to paste in

Seriously, don't skip this part.

Do not paste the following into any AI tool that hasn't been approved by your company's IT or legal team: confidential company strategy, unreleased product plans, acquisition details, customer names or private data, employee information, financial figures that aren't public, legal matters, security details, or system credentials. Ever.

Anonymize everything. Replace "our Q3 acquisition of [Company Name]" with "a potential strategic acquisition in our sector." Replace customer names with "Client A." Replace specific revenue figures with ballpark ranges or just describe the scale. You can get 90% of the structured thinking value without giving AI anything it shouldn't have.

Also: once you've got output, a human verifies it. All of it. Facts, numbers, timelines, risks, ethical implications, legal exposure, and stakeholder impact need human eyes before anything gets committed to paper or presented to anyone who matters.

The reusable AI decision-making prompt formula

Before you get to the 10 templates, here's the underlying structure they're all built on. You can use this as a starting point for any decision prompt you write:

Context: [What's the situation? What's already decided or fixed?]

The decision: [State it as a clear, specific question with a deadline or trigger if relevant.]

Constraints: [What are the real limits? Budget, time, people, legal, political.]

Options on the table: [List them, even the ones that seem unlikely.]

What I need from you: [Comparison table? Risk list? Draft memo? Devil's advocate?]

Audience: [Who will see or act on the output?]

The clearer you are with those six inputs, the more useful the output. Skip any of them and you're back to getting plausible-sounding mush.

The reason most people get bad AI output on decisions isn't that the tool is limited. It's that they paste in "should we do X or Y?" with no context and expect the response to be useful. It won't be. AI has no idea what X and Y actually cost you, who championed them internally, or what the fallback looks like if both go wrong. This formula forces you to think that through before you type anything.

This came from a book.

Don't Replace Me

200+ pages. 24 chapters. The honest version of what AI means for your career, written by someone who actually builds this stuff.

Get the Book →

10 copy-paste AI decision-making prompts

These are ready to use. Edit the brackets for your situation. Keep the structure.


1. Turn a messy situation into a clear decision statement

I need help clarifying a decision before we analyze it further.

Here's the situation: [Describe what's happening and why a decision is needed.]

Help me write a clear, one-sentence decision statement in this format: "We need to decide [WHAT] by [WHEN] in order to [WHY IT MATTERS]."

Then list any sub-decisions that depend on the main one.

2. Compare options against real constraints

I'm comparing [NUMBER] options for [DECISION TOPIC].

Options: [List them.]
Key constraints: [Budget range, timeline, team size, any hard limits.]
What matters most: [List 3-5 criteria in rough priority order.]

Create a comparison table scoring each option against each criterion. Use a simple scale (Low/Medium/High or 1-3). Note where you're uncertain rather than guessing.

3. Identify hidden assumptions

Here is the decision we're considering: [State the decision.]
Here is our preferred option: [Describe it.]

List the assumptions we're making that this option depends on. For each assumption, tell me how likely it is to be wrong and what would happen to the decision if it is.

4. Build a risk register

We're moving forward with [DECISION OR INITIATIVE].

Generate a risk register with these columns: Risk, Likelihood (Low/Medium/High), Impact (Low/Medium/High), Early warning signs, Possible response.

Include at least one risk in each of these categories: operational, financial, people/stakeholder, and external/market. Flag anything you're uncertain about rather than filling in confident-sounding guesses.

5. Run a pre-mortem

It's [DATE 12 MONTHS FROM NOW] and the decision we made to [DECISION] has failed badly.

Write a short post-mortem report as if this already happened. What went wrong? What did we miss? What assumptions were wrong? What warning signs did we ignore?

Be specific. Don't give me generic risks. Make it feel real.

This is one of the most useful prompts on the list. It bypasses the optimism bias in most planning discussions. Nobody wants to be the pessimist in a meeting, but a fictional failure report gives everyone cover to say the uncomfortable thing.


6. Pressure-test a preferred option

Our team is leaning toward [OPTION] for [DECISION].

Play the role of a skeptical senior stakeholder who has seen this kind of decision go wrong before. Ask me the five hardest questions you'd ask before approving this. Don't be gentle.

Pair this one with the pre-mortem. Between the two, you'll surface more real problems in 15 minutes than most teams find in a two-hour review.


7. Write a one-page decision memo

Help me write a one-page decision memo for [AUDIENCE, e.g., "a senior leadership team"].

Decision: [State it clearly.]
Context: [2-3 sentences on why this needs to be decided now.]
Options considered: [Brief list.]
Recommended option: [What you're proposing.]
Key reasons: [Top 3.]
Main risks: [Top 2-3.]
What we need: [Approval, resources, a decision by a specific date.]

Keep it tight. Under 400 words. No unnecessary hedging.

After you get the draft, read it out loud. If anything sounds like something you don't actually believe, rewrite that part yourself. AI will write confidently even when you're not. Don't let the formatting do the thinking.


8. Map stakeholder tradeoffs

For the decision to [DECISION], different stakeholders will see different tradeoffs.

Stakeholders involved: [List them by role or team, not name.]
For each stakeholder, identify: What they gain from our recommended option, what they lose or give up, and what concern they're most likely to raise.

Don't invent quotes or political dynamics you don't know. Flag where you're speculating.

This prompt is good preparation for any decision that needs buy-in from people who weren't in the room when you made it. If you do proper AI-assisted research on your stakeholders beforehand, you'll get better output here.


9. Decide what you still don't know

Here is our current understanding of [DECISION]: [Brief summary of what you know and what you're leaning toward.]

What information would most change this decision if we had it? List the top 5 unknowns, ranked by how much they'd affect the outcome. For each, suggest one practical way to get better information before we commit.

This prompt is underused and deeply useful. Most teams make decisions with information they have, never stopping to ask which missing pieces actually matter. This forces that conversation. Pair it with data analysis work when the unknowns are quantitative.


10. Turn a meeting debate into a recommendation

Our team has been debating [DECISION] and hasn't reached agreement. Here are the main positions:

Position A: [Describe it and who holds it.]
Position B: [Describe it and who holds it.]
[Add more if needed.]

Help me write a recommendation memo that: acknowledges each position fairly, identifies where there's actual disagreement vs.different assumptions, and proposes a decision with a clear rationale. The goal is clarity, not a compromise that pleases no one.

How to get better output from each prompt

The templates above will get you somewhere. But there are a few habits that separate mediocre AI decision output from genuinely useful output.

Be specific about the audience. "Write a decision memo" gets you something generic. "Write a decision memo for a CFO who approved similar spend last quarter but rejected a larger version six months ago" gets you something you can actually use. AI can adjust tone, emphasis, and framing based on audience context. Give it that context.

Tell it what you've already ruled out. If two options got eliminated early, say so and say why. AI will sometimes resurrect them if you don't, which wastes your time and muddies the output. "We've already decided we're not building this in-house due to timeline constraints" saves you a loop.

Ask it to flag its own uncertainty. The default mode for most AI tools is confident. Left to its own devices, it will estimate, infer, and project without flagging where it's guessing. If you explicitly prompt it to "mark anything you're uncertain about" or "note where you're speculating rather than stating a fact," you get output that's actually more honest and more useful.

Iterate, don't accept. The first draft of any AI decision output is a starting point. Read it, identify the parts that feel wrong or incomplete, and prompt again. "The risk register looks thin on the people side. Add three more people or stakeholder risks, including any that might come from outside the immediate team" is a normal second prompt, not a sign the first one failed.

Good output usually takes two or three passes. That's not a flaw. That's how thinking works.

What AI should and shouldn't decide in this process

Here's a clean line to keep in your head.

AI is useful forHumans own
Structuring optionsChoosing between them
Writing comparison tablesWeighting what actually matters
Surfacing possible risksAssessing which risks are real
Drafting the memoSigning off on it
Playing devil's advocateDeciding when to stop debating
Listing unknownsDeciding what to do anyway
Generating stakeholder concernsActually talking to stakeholders

The thing AI can't do is be accountable. It doesn't have a job on the line. It doesn't know that the CFO will kill anything over $200K before Christmas. It doesn't know that two of your three options are politically toxic for reasons that never made it into any document. That context lives with you and your team, and human judgment in complex situations is exactly what makes the difference between a smart-looking memo and a decision that actually sticks.

For a full breakdown of what AI genuinely can and can't do with your thinking, this plain-language explainer covers it without the hype.

The rule: AI builds the structure. You fill it with the things that actually matter. Then you sign your name.

Once you've got your decision memo drafted, the implementation side needs its own structure. The project management prompts pick up right where this leaves off.

Frequently asked questions

Can AI make decisions for me at work?

No, and you shouldn't want it to. AI can organize information, surface options, draft memos, and flag risks, but it can't weigh the political, ethical, or relational factors that determine whether a decision actually works. The accountability stays with you. Use AI to think more clearly, not to outsource the call.

What's the risk of using AI for decisions involving sensitive business information?

It's real. Don't paste confidential strategy, customer data, employee information, financial details, legal matters, or unreleased product plans into any AI tool that hasn't been cleared by your IT or legal team. Anonymize everything. You can get 90% of the structural value without sharing anything sensitive.

What's a pre-mortem and why does it help with AI prompts?

A pre-mortem is an exercise where you imagine a decision has already failed and then work backward to figure out why. It bypasses the optimism that kills most planning sessions. When you use it as an AI prompt, you get a structured fictional failure report that's often more honest than anything a live team discussion produces.

How do I make sure AI decision output is accurate?

You verify it yourself. Check every fact, number, timeline, and assumption the AI cites. AI will fill gaps with plausible-sounding content when it doesn't have real information. Any output that will influence a real decision needs a human to confirm it before it gets shared or acted on.

How is this different from just googling my problem?

The structure. These prompts force you to clarify what you're actually deciding, what your constraints are, and what you need from the output. Google gives you information. A well-structured AI prompt gives you a thinking framework applied to your specific situation. The quality of the output depends entirely on how clearly you define the input.

What if my team disagrees with the AI's recommendation?

Good. The AI's recommendation is a starting point, not a verdict. If your team's disagreement is based on context, relationships, or judgment the AI didn't have, trust the team. If the disagreement is about assumptions you can test, test them. The point of the prompts is to make the disagreement more structured and productive, not to replace human debate with machine output.