- AI Business Insights
- Posts
- Tell Claude how hard to think
Tell Claude how hard to think
Claude has a thinking dial, and almost nobody has touched it
In partnership with
Opus 4.8 shipped with effort control. You can tell it how hard to think before it answers. Most people read that as a longer-output toggle and moved on. I did too, for about a week.
Then I read a r/PromptEngineering thread where someone had wired it into a decision prompt, and it had already caught two real mistakes for them. Real as in, the person had already decided, the logic felt clean, and the prompt found the hole anyway. So I tried it on a call I'd quietly made the week before. It did the same thing to me.
Here's what I learned, and the exact block you can paste in tonight.
AI agents now read your docs almost as much as humans do.
Mintlify analyzed 790 million requests across its documentation platform. The finding: AI coding agents account for 45.3% of all traffic, nearly tied with traditional browsers at 45.8%.
Two tools are driving almost all of it:
Claude Code: 25.2% of total traffic, more requests than Chrome on Windows
Cursor: 18% of total traffic
Together they account for 95.6% of all identified AI agent traffic
The rest of the field, OpenCode, Trae, ChatGPT, and NotebookLM, is showing up but nowhere close.
One caveat: OpenAI's Codex doesn't send an identifiable user-agent header, so the real agent percentage is likely even higher.
The takeaway for anyone maintaining developer docs: your documentation now serves two audiences. Structure and machine-readability matter as much as clarity for human readers.
*Ad
What effort control actually changes
Default Claude is agreeable. You say you're leaning toward X, and it helps you do X well. That's not a bug. The model is optimizing for being helpful in the direction you're already pointing.
Max effort Claude points somewhere else. It reasons through a few approaches before it answers, and it tells you where it's uncertain instead of just confirming what you walked in believing.
Picture a pricing change. You explain your reasoning, and standard Claude walks you through the rollout. Max effort Claude comes back with something like: "Your assumption that users stay at the higher price depends on retention data you haven't mentioned. If churn is above a certain line, this math breaks." Standard mode doesn't skip that to be lazy. It skips it because you didn't ask it to challenge you. You asked it to help.
Extended thinking existed before this. What Opus 4.8 changes is how cleanly you can invoke it, and how much it shifts the output when you do. The gap between "Claude helps you execute the plan" and "Claude audits whether the plan is sound" is now a single line in your prompt.
The prompt structure
This comes from the r/PromptEngineering thread. The trick is that it forces Claude into decision-review mode, not thinking-out-loud mode:
Maximum effort on this. Don't rush it.
I'm deciding: [the decision]
I'm leaning toward: [your option] because [reasons]
Argue against me first. What am I not seeing?
What assumption am I making that, if wrong, changes everything?
Tell me where you're certain and where you're not.
Then your honest call: proceed, reconsider, or get more info.
Three things make it work:
It asks Claude to argue against you first, not just think more. That reframes your reasoning as a hypothesis to stress-test instead of a direction to follow. Different task, different output.
It separates certainty from uncertainty. Most AI answers sound either confident across the board or hedge everything equally. Forcing the split tells you which parts to verify and which to trust.
It ends with a forced call, not a summary. "Here's what I found" is filler. "Reconsider" is something you can act on.
That last one is the underrated piece. The decision gate is what stops Claude from rambling and makes it commit to a judgment.
We’re running a super short survey to see if our newsletter ads are being noticed. It takes about 20 seconds and there's just a few easy questions.
Your feedback helps us make smarter, better ads.
*Ad
Why "argue against me first" is doing the heavy lifting
Take that one line out and Claude goes right back to building on your framing. Leave it in and you've told the model to treat your reasoning as something to break, not something to extend.
In the original thread, both mistakes it caught were cases where the person had already decided. The logic felt solid from the inside. The prompt found the crack anyway. That's the whole value. You can't see the assumption you're standing on, and the agreeable default will never make you look at it.
The certainty line matters for the same reason. When Claude tells me it's confident about the timeline but admits it's guessing about adoption rates, and adoption is the thing that actually drives the timeline, that's a flag I'd have missed. You can't manage a risk you can't see.
Where I actually reach for it
Not everywhere. Routine choices between familiar options don't need it. I save it for the decisions I'd genuinely regret getting wrong:
Any business call I've already half-made. The ones where I'm looking for confirmation, not input.
Pricing or positioning changes before they go live.
Hiring or partnership calls where I'm leaning yes.
Technical architecture choices where the switching cost is brutal.
Contract or deal terms I'm about to sign without a second opinion.
The common thread is confirmation bias being the real risk. If your own certainty is the thing most likely to hurt you, this is the prompt.
Hiring in 8 countries shouldn't require 8 different processes
This guide from Deel breaks down how to build one global hiring system. You’ll learn about assessment frameworks that scale, how to do headcount planning across regions, and even intake processes that work everywhere. As HR pros know, hiring in one country is hard enough. So let this free global hiring guide give you the tools you need to avoid global hiring headaches.
*Ad
The five-minute version you can run tonight
Pick something you've already decided. Something you're pretty sure about. Run this before you commit:
Maximum effort on this. Don't rush it.
I'm deciding: [the decision]
I'm leaning toward: [your option] because [reasons]
Argue against me first. What am I not seeing?
What assumption am I making that, if wrong, changes everything?
Tell me where you're certain and where you're not.
Then your honest call: proceed, reconsider, or get more info.
Use it as a pre-mortem, not an abstract "what could go wrong." Feed it the specific decision, your specific reasoning, and let it tell you where you're wrong. That specificity is the difference between a useful answer and a generic one.
You get one of two outcomes. Confirmation you're on the right track, or the hole you were about to walk into. Both are worth five minutes. And if it comes back with "proceed," you move forward with more confidence than you started with. That's not nothing either.
The part nobody tells you
The reason this works isn't the effort setting. It's that you finally asked Claude to do a different job than it's wired to do by default.
Left alone, the model wants to help you win the argument you're already having with yourself. This prompt makes it switch sides for five minutes. That's uncomfortable on purpose, and the discomfort is the point. The decisions that hurt are never the ones that felt shaky going in. They're the ones that felt solid, right up until they didn't.
Tonight, take the call you're most sure about. The one you've basically already made. Paste the block, drop your real reasoning in, and run it on max effort. Best case, you confirm it. Worst case, you find the crack while it's still cheap to fix.