AIPrompt Engineering

Giving AI the right context, not more context

Most professionals assume that longer, more detailed prompts produce better AI outputs. The real skill is something narrower: identifying which specific context actually changes the answer, and leaving everything else out.

🎙️

Listen to the podcast

4 min

There is a common instinct when working with AI systems: if the output is not quite right, add more information. More background, more caveats, more explanation of your situation. The prompt gets longer, the output gets more generic, and the interaction starts to feel like drafting a legal brief just to ask a question. The concept worth understanding here iscontext precision, the discipline of selecting only the context that materially shapes the model's response, and treating everything else as noise.

This is not a minor productivity tip. It is the difference between using a capable tool well and fighting it constantly.

Why context precision matters for professionals specifically

Large language models like GPT-4o, Claude 3.5, and Gemini 1.5 Pro do not process context the way a human colleague does. A colleague who knows you builds a mental model over months. An LLM processes your entire prompt simultaneously, weighing every token in relation to every other token within its context window. This means that irrelevant information does not just sit quietly in the background. It competes for the model's attention with the information that actually matters.

Research from Stanford's Human-Centered AI group has documented what practitioners call "distraction effects," where adding loosely related context to a prompt measurably reduces the accuracy of the model's response on targeted tasks. The model is not ignoring the extra text. It is integrating it.

For a professional operating under time pressure, this has a direct cost. You spend more time writing prompts, the outputs require more editing, and you develop a false sense that the tool is less capable than it is. In many cases, a 40-word prompt with the right three pieces of context will outperform a 300-word prompt stuffed with background the model did not need.

How context precision actually works

The mechanics are straightforward once you understand what "context" is doing in a prompt. It is performing one of four jobs: establishing the model's role, defining the task, constraining the output format, or providing reference material the model cannot otherwise access. That is the complete list.

Consider a practical example. A strategy director at a consumer goods company wants Claude to help draft talking points for a board presentation on a supply chain diversification proposal.

A typical over-contextualized prompt might read: "I work in strategy at a large FMCG company, we have been dealing with supply chain issues since the pandemic, our board is quite conservative, we have had previous presentations rejected, our CFO is skeptical of capital-heavy proposals, the CEO joined two years ago from a tech background, we are proposing moving 30% of our sourcing from single-region suppliers to a dual-source model across three geographies, we want to show this is financially sound..."

That paragraph contains at least five pieces of information the model cannot usefully act on (the CFO's personality, previous rejections, the CEO's background) mixed in with the two pieces that genuinely matter: the proposal itself and the audience's decision-making frame.

A precise version would be: "You are preparing board-level talking points. The proposal: shift 30% of sourcing to a dual-region model. The audience prioritizes capital efficiency and downside risk management over growth narratives. Give me five talking points, each under 40 words."

The second prompt is shorter and will produce a more focused, usable output. The model has a clear role, a concrete subject, and one meaningful constraint about the audience's values. The rest is editing, not prompting.

The principle here is to ask yourself, before adding any piece of context: if I removed this sentence, would the answer change in a meaningful way? If the answer is no, cut it.

When to use it and when not to: the honest tradeoffs

Context precision works best for discrete, clearly scoped tasks: drafting a document, analyzing a specific dataset, reformatting structured information, generating options within defined parameters. These are cases where the task has edges and the model needs to stay within them.

It is less suited to exploratory or open-ended work, where giving the model more latitude actually serves you better. If you are trying to pressure-test a business strategy and genuinely want the model to surface assumptions you have not thought of, a tight prompt is the wrong tool. In that mode, broader framing helps.

There is also a category of tasks where reference material is genuinely necessary and there is no substitute for volume. If you are asking a model to summarize a 50-page contract or identify inconsistencies across a set of financial statements, you are not padding the prompt with irrelevant context. You are providing the primary material. The principle does not apply to source documents.

One honest limitation: developing context precision requires you to know what you want before you prompt. That sounds obvious, but many professionals use AI as a thinking-out-loud partner precisely because they have not clarified their own objective yet. That is a legitimate use case, and it will produce messy outputs. The solution there is not to write a tighter prompt. It is to recognize that you are in an exploratory mode and adjust your expectations accordingly, then move to precise prompting once the objective is clear.

A useful working habit: write your first draft of a prompt, then read it back and delete every sentence that describes your company history, your past experiences with the topic, or contextual color that does not directly shape what you need the model to do. Most of the time, you will cut 40 to 60 percent of what you wrote, and the output will improve.

Context precision is a discipline of knowing what information does work in a prompt versus what just feels relevant. The professionals who internalize that distinction spend less time editing AI outputs and more time using them.

Finished reading?

Validate your read to earn XP and feed your radar.