How to Write Better AI Prompts: The CONTEXT Method

Why most prompts fail: the three root causes

Before learning what to do, it helps to understand what goes wrong. Prompt failures cluster into three root causes, and nearly every disappointing AI interaction traces back to one of them.

The first root cause is insufficient context. The user knows what they mean, but the AI does not have enough information to produce a targeted output. "Write a marketing email" fails because it provides no information about the product, the audience, the goal, the tone, or the constraints. The AI fills in the blanks with generic defaults, producing generic output. This is the most common failure and the easiest to fix — you simply provide the context that the AI cannot guess.

The second root cause is ambiguous objectives. The user knows they want something but has not articulated what success looks like. "Help me with my presentation" could mean: write the slides, critique the content, suggest a structure, coach my delivery, or design the visuals. When the objective is ambiguous, the AI picks one interpretation (often the wrong one) or produces a vague, catch-all response that is not particularly useful for anything.

The third root cause is missing format specifications. The AI produces good content but in the wrong format — a wall of prose when you needed bullet points, a 2,000-word essay when you needed a 200-word summary, an academic tone when you needed conversational. Format is not a minor detail; in professional contexts, the right information in the wrong format is nearly as useless as the wrong information.

The CONTEXT Framework addresses all three root causes systematically. Each element of the framework targets one or more of these failure modes, ensuring that your prompts provide sufficient context, clear objectives, and explicit format expectations. The result is a dramatic and consistent improvement in output quality — not because the AI becomes smarter, but because your instructions become clearer.

The CONTEXT Framework: six elements of an effective prompt

CONTEXT is an acronym that structures the six elements every effective prompt should include. Not every prompt needs all six elements (a simple request might only need two or three), but knowing all six ensures you never omit something critical.

**C — Circumstance.** The background situation that the AI needs to understand. Who you are, what your role is, what industry you are in, and what has happened leading up to this request. "I am a marketing director at a B2B SaaS company launching a new product next month" gives the AI critical context that shapes every aspect of its response.

**O — Objective.** What you want the AI to accomplish. Be specific about the deliverable. "Write a product launch email" is better than "help with marketing," and "Write a product launch email announcing our new analytics feature to existing customers, emphasising the time-saving benefit" is better still.

**N — Nuance.** The subtle requirements that prevent the output from being generically correct but specifically wrong. Constraints, exceptions, things to avoid, sensitivities to respect. "Do not mention competitor names. Avoid technical jargon — our audience is non-technical. Do not promise specific performance numbers we have not verified."

**T — Tone.** The voice and register of the output. "Professional but conversational," "formal and authoritative," "warm and encouraging." Tone is especially important for customer-facing content, where the wrong register can undermine an otherwise excellent message.

**EX — Examples and eXpectations.** What the output should look like — format, length, structure, and ideally an example of similar work you consider excellent. "Format as a 200-word email with a subject line. Here is an example of a launch email I liked: [paste example]." The more specific your expectations, the closer the first draft will be to your final version.

These six elements work together as a checklist. Before submitting any important prompt, scan through C-O-N-T-E-X-T and ask yourself whether you have addressed each element. The elements you are missing are almost certainly the reason your previous prompts underperformed. For a deep dive into each element with extended examples, visit the dedicated [CONTEXT Framework page](/context-framework).

Before and after: real prompts transformed

Theory is only useful if it changes practice. Here are three real-world prompts, shown before and after applying the CONTEXT Framework, with the specific improvements noted.

**Example 1: Content Creation.** Before: "Write a blog post about AI in healthcare." After: "I am the content manager for a healthtech startup that provides AI-powered diagnostic tools to NHS trusts. Write a 1,200-word blog post arguing that AI should augment clinical decision-making, not replace it. Our audience is hospital administrators and clinical leads who are interested but cautious about AI adoption. Tone: authoritative but accessible — no jargon, no hype. Structure: hook, 3 main arguments with supporting evidence, a 'what this means in practice' section, and a conclusion. Do not reference specific competitor products." The before prompt would produce a generic overview that could appear on any website. The after prompt produces a targeted piece that speaks directly to the company's audience and supports its market position.

**Example 2: Data Analysis.** Before: "Analyse this sales data." After: "Here is our Q1 2026 sales data [attached]. I need a board-ready analysis covering: revenue vs. target by region, the 3 most significant trends you identify, any anomalies that warrant investigation, and a one-paragraph executive summary. Format as a structured report with headers. Flag any data quality issues you notice. Our board is particularly interested in the EMEA expansion — give that region additional depth." The transformation is clear: the before prompt gives the AI no direction, so it produces whatever analysis it defaults to. The after prompt specifies the audience, the priority areas, the format, and the quality expectations.

**Example 3: Email Writing.** Before: "Write an email to decline a meeting request." After: "Write an email declining a meeting request from a potential vendor who wants to demo their product. I am a CTO and receive 15+ vendor requests weekly. Tone: polite but firm — do not leave an opening for follow-up. Acknowledge what they offer without criticising it. Suggest they send a one-page overview if they want to stay on my radar. Keep it under 100 words." The constraint "do not leave an opening for follow-up" is the kind of nuance that transforms a polite-but-ineffective decline into one that actually accomplishes its purpose. These before/after patterns are practised extensively in the [Essentials level](/school/essentials) of the curriculum.

Advanced techniques: chain-of-thought and few-shot prompting

Once you have mastered the CONTEXT Framework, two advanced techniques will further improve your results on complex tasks: chain-of-thought prompting and few-shot prompting.

Chain-of-thought prompting asks the AI to show its reasoning step by step before arriving at a conclusion. The simplest version is adding "Think through this step by step" to your prompt, but more effective versions provide a specific reasoning structure: "First, identify the key variables. Then, analyse how they interact. Then, consider what could go wrong. Finally, make your recommendation." This technique dramatically improves accuracy on tasks that require multi-step reasoning — financial analysis, strategic decisions, debugging, and any scenario where the answer depends on correctly processing several interconnected factors.

Why does this work? Large language models generate text one token at a time, and each token is influenced by the tokens that came before it. When you ask for a direct answer, the model jumps to a conclusion based on surface patterns. When you ask it to reason step by step, each intermediate step provides context for the next, resulting in more accurate and more nuanced conclusions. Research consistently shows that chain-of-thought prompting reduces errors by 30-50% on complex reasoning tasks.

Few-shot prompting provides examples of the input-output pattern you want the AI to follow. Instead of describing what you want in abstract terms, you show the AI two or three examples of inputs paired with ideal outputs, then provide your actual input. The AI pattern-matches from your examples and produces output that follows the same structure, style, and quality level. This is particularly effective for: consistent formatting across multiple items, maintaining a specific writing style, classification tasks (show examples of each category), and any task where "I'll know it when I see it" makes description difficult.

These techniques are not alternatives to the CONTEXT Framework — they are additions. A well-structured CONTEXT prompt with chain-of-thought reasoning for complex analysis, or with few-shot examples for style-specific content, produces results that consistently surprise people with their quality. The [Prompt Grader tool](/tools/prompt-grader) can help you evaluate whether your prompts effectively employ these techniques.

Common mistakes even experienced users make

Even professionals who use AI daily fall into patterns that limit their results. Five mistakes are particularly persistent.

**Accepting the first output.** The single most impactful habit change is treating every AI response as a first draft. The magic of AI interaction is in the iteration — "Make the opening more compelling," "Add specific numbers to support that claim," "Restructure the argument to lead with the strongest point." Professionals who iterate three or four times consistently produce output that is two to three times more useful than those who accept the first response.

**Being too polite (or too vague).** "Could you maybe try to write something about our Q3 results?" is a prompt, but barely. AI does not have feelings to hurt. Be direct: "Write a 300-word executive summary of our Q3 results. Lead with the headline number. Include year-over-year comparison. Tone: confident but honest about the miss in EMEA." Directness is not rudeness — it is clarity.

**Not providing reference material.** Asking the AI to write about your company, product, or industry from its training data is asking for a generic output peppered with potential inaccuracies. Instead, provide the material: paste in your website copy, upload your product documentation, share previous examples of content you liked. The AI works best when it processes your specific information, not when it guesses.

**Using the same prompt structure for every task.** Research, writing, analysis, brainstorming, and editing are fundamentally different tasks that require fundamentally different prompt structures. A research prompt should ask for sources and evidence. A writing prompt should specify tone and format. An analysis prompt should define the criteria and framework. A brainstorming prompt should specify the number of ideas and constraints. Using a one-size-fits-all approach limits every output.

**Forgetting to specify what to exclude.** "Do not include generic advice," "Do not use the word 'delve,'" "Do not add a summary at the end" — negative instructions are surprisingly powerful. The AI has strong default patterns, and without explicit exclusions, those patterns dominate the output. If you have ever received an AI output that felt formulaic, the fix is usually a specific exclusion in the prompt. Learn to build these habits systematically through the structured curriculum at the [School of Enigmatica](/school).

Building a personal prompt system

The professionals who get the most value from AI do not write prompts from scratch every time. They build and maintain a personal prompt library — a collection of tested, refined prompts for their recurring tasks, organised by category and continuously improved.

Start by identifying your 10 most frequent AI-assisted tasks. For each, write a prompt using the CONTEXT Framework, test it, iterate until the output quality is consistently high, and save the refined version. Store your prompts in a readily accessible location — a dedicated note, a document, a bookmark folder, or a tool like the [Prompt Template Library](/tools/prompt-library). The key is that your best prompts should be reusable with minimal modification, not re-invented each time.

Build a prompt refinement habit. Every time you use a saved prompt and find yourself making the same adjustment to the output, update the prompt to prevent that adjustment in the future. Over weeks and months, your prompts become increasingly precise and your first-draft output quality steadily improves. This is a compounding investment — 10 minutes spent refining a prompt you use weekly saves hours over the course of a year.

Organise prompts by workflow, not by tool. "Client reporting prompts," "Content creation prompts," "Meeting preparation prompts" are more useful categories than "ChatGPT prompts" or "Claude prompts." Good prompts are largely tool-agnostic — the CONTEXT Framework works equally well across any major AI assistant.

Share effective prompts with your team. When you discover a prompt that consistently produces excellent results for a common task, share it. This is one of the simplest ways to scale AI productivity across a team without formal training — though it works even better when combined with structured learning. Prompt sharing also creates a feedback loop: colleagues test your prompts in different contexts, discover edge cases, and contribute refinements that improve the prompt for everyone.

The endgame is not memorising frameworks or accumulating prompt templates. It is developing an intuition for what makes AI instructions clear and effective — an intuition that becomes second nature with practice. The frameworks and templates are scaffolding; the skill is the building. Start with the CONTEXT Framework, build your personal prompt library, refine continuously, and within weeks you will find yourself writing excellent prompts instinctively. For a structured path through this skill development, the [Essentials level](/school/essentials) curriculum covers prompt engineering from fundamentals through advanced techniques.

Related Terms