Prompting for Executives: How to Get Useful Work Out of AI in 30 Minutes
Most executive disappointment with AI is a prompting problem in disguise. A small set of techniques — learnable in half an hour — is the difference between a novelty and a genuinely useful tool. And the most important of them is really a governance skill.
There’s a common, quiet verdict among senior people who’ve tried AI: “It was fine. Not the revolution I was promised.” Almost always, the tool wasn’t the problem. The request was. AI mirrors the quality of the instruction it’s given, and most first attempts are vague, so the answers are vague. The encouraging part is how quickly that’s fixed — the core techniques take about thirty minutes to learn and change the experience entirely.
This isn’t about becoming a “prompt engineer.” It’s about a handful of habits that turn a flat tool into a sharp one — and one principle that matters more than all the techniques combined.
The shift: from question to instruction
The beginner’s mistake is treating AI like a search box — short, vague queries that get generic, hedge-everything answers. The fix is to treat it like a capable colleague you’re briefing: give it a role, context, the specific output you want, and the standard it’s being held to. Compare “what do you think of this plan?” with “act as a sceptical CFO; here is the plan and the numbers; identify the three weakest assumptions and what would have to be true for it to fail.” Same tool, completely different value.
A few techniques that change everything
Assign a role. Telling AI who to be sharpens everything it does. “Act as a cautious legal reviewer,” “act as a commercial sceptic,” “act as a risk analyst.” The role focuses the response far more than any amount of polite phrasing.
Refuse to be flattered. This is the big one, and it’s worth dwelling on. Ask AI “show me why I’m right about this” and it will dutifully build your case — a confident, useless echo. Ask it “argue the strongest possible case against this decision, then tell me what I’m not seeing,” and you get something genuinely valuable. The model didn’t get smarter between those two prompts. You framed it to be honest rather than agreeable. The lesson generalises: a loaded question gets a loaded answer.
Convene a panel. For any real decision, ask several roles at once: “Review this as a CFO, then as a legal reviewer, then as a red-teamer whose only job is to find what breaks.” You get a rounded critique instead of a single flat take — closer to a good leadership team than a chatbot.
Make it check itself. AI can be confidently wrong. Adding “now verify that answer, show your reasoning, and flag anything you’re not sure about” catches a surprising amount of nonsense before it reaches your decision.
Spot what should become a script. If you find yourself giving AI the same judgement task repeatedly with the same rules, that’s a signal it should become a fixed, repeatable process rather than a fresh ask each time — more reliable, and no longer dependent on the model’s mood.
The principle that matters most: prompting is governance
Here’s the idea that elevates all of this from technique to discipline. How you frame a request to AI doesn’t just shape the style of the answer — it shapes its honesty. “Show me why I’m right” and “show me why I might be wrong” are not two phrasings of one question. They’re a choice between comfort and truth.
For a decision-maker, that’s not a writing tip. It’s governance. The framing you habitually use determines whether AI functions as a yes-man that launders your existing opinions, or as an honest adviser that improves your decisions. The problem people call “AI bias” is, in practice, very often just poor objective framing. Learn to frame for honesty and you’ve learned the single most valuable AI skill there is.
The leadership question
When you put a real decision to AI, ask yourself first: am I framing this to be challenged, or to be confirmed? If it’s the latter, you’ll get a comfortable answer and learn nothing.
Try these prompts
Three you can use today. For an honest critique:
Act as a sceptical, experienced [CFO / operations director / legal reviewer]. Here is a decision I’m leaning towards: [describe it]. Argue the strongest case against it, identify the assumptions I haven’t tested, and tell me what would have to be true for this to go badly. Do not reassure me.
For a rounded review:
Review this from three perspectives in turn — a commercial sceptic, a risk and compliance reviewer, and a red-teamer whose only goal is to find the flaw. Give me each view separately, then the single biggest concern overall.
To catch confident errors:
Now verify your previous answer. Show your reasoning, identify anything you’re uncertain about, and flag any claim I should independently check before acting on it.
What to do next
Spend thirty minutes putting one real decision through those three prompts. The experience tends to convert sceptics faster than any demo, because the value is immediate and it’s on their own problem. For many teams the natural next step is a short, hands-on prompting session so the whole leadership group shares the same habits — particularly the framing-for-honesty discipline, which is too important to leave to chance.
In closing
AI isn’t underwhelming. Most people just haven’t been shown the half-hour of technique that makes it sing — and the one principle, that prompting is governance, that makes it trustworthy.
If your leadership team would value that half-hour as a practical, hands-on session, Savant and Axulu can run it. It is low-friction, immediately useful, and often the gateway to the bigger conversation about doing AI properly.