Claude Code's Creator Says We're Overcomplicating AI Prompts
For years, people have been told that getting better results from artificial intelligence requires mastering the art of prompt engineering. Detailed instructions, carefully structured requests and elaborate step-by-step directions have become common recommendations for anyone trying to use AI effectively.
But Boris Cherny, the creator of Claude Code at Anthropic, is suggesting that the approach may be getting unnecessarily complicated.
In advice reported by Business Insider on October 7, 2026, Cherny argued that as AI models become more capable, users should spend less time micromanaging how they complete tasks and more time explaining what they actually want to accomplish.
His recommendation comes down to three principles: tell AI what you want it to do, tell it how much effort to spend, and tell it how to verify its work.
For businesses increasingly incorporating AI into everyday operations, that distinction could change how employees approach everything from research and reporting to marketing and financial analysis.
Why More Instructions Aren't Always Better
Early AI models often needed substantial guidance to complete complicated tasks reliably. Users learned to break work into smaller steps, specify exactly how responses should be structured and provide detailed instructions to keep the model on track.
Those techniques can still be useful. But Cherny's argument is that increasingly capable models can make more of those decisions themselves.
Consider the difference between asking an employee to achieve a result and telling them precisely how to perform every action along the way.
An experienced employee can often work more effectively when given a clear objective, relevant context and enough freedom to choose an appropriate approach. Cherny believes a similar principle increasingly applies to advanced AI models.
That doesn't mean providing less information about the task. It means distinguishing between information the model genuinely needs and instructions that unnecessarily restrict how it works.
Rule 1: Tell AI What You Want It to Do
The first principle is straightforward: clearly describe the outcome you're trying to achieve.
For a business owner, that might mean asking AI to identify opportunities to improve profitability, evaluate customer feedback or develop a plan for entering a new market.
The important part is explaining what a successful result should look like.
For example, "analyze our sales" leaves too much open to interpretation. It doesn't explain the business objective, the period being examined or what decisions the analysis should support.
A more useful request would be:
"Analyze our last 90 days of sales and identify the three biggest opportunities to improve profitability. Explain your recommendations in plain English."
This provides a clear direction without dictating every calculation, comparison or analytical step.
The model has an objective, but it also has room to determine how best to approach the work.
Rule 2: Tell AI How Much Effort to Spend
Not every task deserves the same level of investigation.
Rewriting a short email may require only a quick response. Evaluating a company's financial performance, researching competitors or comparing expansion opportunities demands considerably more attention.
Cherny recommends making that expectation clear.
Instead of assuming the AI knows how deeply to investigate, users can explicitly request a quick answer, a thorough analysis or deeper research and reasoning.
For example, a business owner might ask for a brief summary of customer feedback before a meeting. But when evaluating a significant investment, that same person could ask AI to investigate multiple options, compare their advantages and disadvantages, and identify risks before reaching a recommendation.
The distinction matters because a response can appear polished without being sufficiently researched.
By communicating the required level of effort, users give AI a better understanding of the importance and complexity of the task.
Rule 3: Tell AI How to Verify Its Work
The third principle may be the most important for businesses.
An AI-generated answer can sound convincing even when it contains incorrect calculations, outdated information or unsupported conclusions.
Cherny's recommendation is to explain how the result should be checked.
For financial analysis, that could mean verifying calculations against the original spreadsheet. For market research, it could mean checking claims against credible sources.
For an operational recommendation, it might involve identifying assumptions and highlighting information that is still missing.
A practical request could include:
"Check all calculations against the source data, identify any assumptions you make and flag conclusions that cannot be verified."
This doesn't guarantee accuracy, and AI reviewing its own work isn't a substitute for independent verification when the stakes are high.
But defining verification requirements gives the task a clearer standard for completion.
For businesses, the goal should be to receive work that can be examined and trusted, rather than simply accepting the first confident-sounding response.
What Better Prompting Looks Like in Practice
Imagine a business owner wants to understand why profitability has declined over the last quarter.
A vague request might be:
"Analyze our sales."
At the opposite extreme, the owner might write a lengthy prompt dictating every calculation, requiring twelve specific charts and prescribing the exact sequence of the analysis.
Neither approach is necessarily ideal.
The first doesn't explain what the business needs. The second may spend too much effort controlling the process instead of communicating the objective.
A stronger alternative would be:
"Analyze our last 90 days of sales. Identify the three biggest opportunities to improve profitability. Investigate thoroughly, verify your calculations against the original data and explain your recommendations clearly."
This request covers all three of Cherny's principles.
It establishes the outcome, specifies the level of effort and explains how the result should be verified.
The examples are illustrative rather than prompts quoted from Cherny, but they demonstrate how his advice can be applied to everyday business decisions.
Anthropic Has Been Simplifying Its Own Instructions
Cherny's October comments weren't the first time he made this argument.
In a July 2026 discussion, he described how Anthropic had removed approximately 80% of
Claude Code's system prompt as its models improved.
System prompts are the underlying instructions that guide how an AI application behaves.
They can define its role, expectations and operating rules.
The reduction reflected a broader idea: instructions that were helpful for less capable models may become unnecessary, or even restrictive, as models improve.
This doesn't mean AI applications no longer need guardrails or carefully designed workflows. Rather, it suggests that some of the complexity previously required to guide a model can be replaced by the model's improved ability to understand and execute a task.
The same thinking underlies Cherny's advice to everyday users.
Simple Prompts Still Need Good Context
There is an important distinction between simplifying a prompt and making it vague.
A business owner asking AI to develop a marketing strategy still needs to explain the company, its customers, its goals and any meaningful budget or operational constraints.
Someone requesting financial analysis still needs to supply accurate data and explain which decisions the analysis should support.
And repeatable business processes may still require detailed instructions to ensure consistency, compliance and predictable outputs.
In legal, financial and other high-stakes situations, human review and independent checks remain essential.
Cherny's advice isn't an argument against precision. It's an argument against unnecessary micromanagement.
The most effective prompt may contain substantial business context while leaving the model flexibility to determine the best approach.
Better AI Results Start With Better Objectives
The growing accessibility of AI has created an unusual challenge for businesses. Employees can now delegate increasingly complex tasks to software, but many still approach those tasks as though they need to describe every individual action.
Cherny's advice suggests a simpler approach.
Define the result you need. Explain how thoroughly the work should be performed. Establish how the result should be checked.
Then allow the model to determine an appropriate way to complete the task.
As AI becomes more capable, the advantage may shift away from knowing complicated prompting techniques and toward knowing how to define business problems clearly.
The skill isn't necessarily writing longer prompts. It's knowing what outcome matters and how to recognize a good result.
Sources
Business Insider, October 7, 2026: Claude Code creator Boris Cherny's AI prompting advice
Boris Cherny, July 2026: We Cut 80% of Claude Code's Prompt


