Back to Blog

The gap between people who get extraordinary output from AI and people who get generic, disappointing results isn't usually about which model they're using. It's about how they talk to it. A vague prompt gets a vague answer. A well-structured prompt — one that gives the AI a clear role, enough context, a specific task, format requirements, and explicit guardrails — gets output that often surpasses what most people could produce on their own in twice the time. This is learnable. It takes about an hour to get the basics, and the payoff compounds every day you use it.

This guide covers seven specific techniques. Each one has a before-and-after example you can use as a template. By the end, you'll also see what they look like combined into a single, complete prompt — which is where the real power is.

Why Prompting Is a Skill, Not a Search

Most people's first instinct with AI is to treat it like a search engine: type in a few keywords and see what comes back. The difference is that a search engine retrieves information that already exists. An AI model generates a response calibrated entirely to what you give it — its "understanding" of your request shapes every word of its output.

The Right Mental Model

Prompting AI isn't like typing a search query. It's like briefing an exceptionally capable colleague who just started on Monday and knows nothing about your company, your audience, your constraints, or your preferences. The more precisely you brief them, the better the work. Skip the briefing, and you get something technically correct but completely useless for your actual situation.

That mental model matters because it changes what you put in a prompt. You stop thinking "what keywords will give me the right result" and start thinking "what does this AI need to know to do this job well?" The seven techniques below are the answers to that question, each one addressing a different dimension of what an AI needs to produce excellent work.

The 7 Techniques

01
Role Assignment — Tell It Who to Be

AI models contain multitudes — they've been trained on writing from doctors, lawyers, novelists, marketers, engineers, teachers, and every other profession. Without a role, the model produces a generic average. With a role, it draws from the specific domain expertise, tone, and perspective you need. This is often the single highest-leverage thing you can add to any prompt.

Before — Generic Write a cover letter for a Marketing Director role.
→ You get a template that sounds like every other cover letter ever written.
After — Role Assigned You are an experienced HR director who has hired for senior marketing roles at growth-stage tech companies for 15 years. Write a cover letter for a Marketing Director role at a Series B fintech startup. The candidate has 8 years in B2B demand generation, managed a $3M annual ad budget, and tripled pipeline at their last company. Tone: direct, confident, human — not corporate.
→ You get a letter that sounds like it was written by someone who knows how hiring works.
Use it when: you need domain expertise, a particular professional perspective, or a specific tone. Almost every prompt benefits from a role. Make it specific — "experienced B2B copywriter" beats "copywriter," which beats nothing.
02
Context Loading — Give It What It Needs to Know

AI can only work with what you give it. When you paste in an email without context, you get a response calibrated to the email text alone. When you also explain your relationship with the sender, your goal, the history, and what you're trying to avoid — you get something actually useful. Context is free. Omitting it is the most common reason AI outputs miss the mark.

Before — No Context Help me respond to this email. [pastes email]
→ Technically a response. Not calibrated to you, your situation, or what matters.
After — Loaded Context Help me respond to this email. Context: I'm a project manager at a digital agency. The sender is a senior client stakeholder who has a pattern of requesting scope additions at the last minute. We are 3 weeks from launch. My goal is to firmly decline the new feature without damaging the relationship — this client is up for renewal in 90 days. The email: [paste email]
→ A response that actually navigates your situation.
Use it when: the AI doesn't know your audience, your relationship with someone, your company's situation, or the background of what you're working on. Relevant context = dramatically better output.
03
Format Specification — Tell It Exactly What to Produce

Without format instructions, AI defaults to paragraphs — or whatever structure it thinks is appropriate. That almost never matches what you actually need. Specifying format is one of the easiest improvements you can make and produces immediately usable output instead of something you have to restructure after the fact.

Before — No Format Tell me about the US housing market for a first-time buyer.
→ Seven paragraphs of general information you'll spend 10 minutes reformatting.
After — Format Specified Summarize the current US housing market for a first-time homebuyer, age 28, $75K income, looking in a mid-size city. Use this exact structure: — Bottom line (2 sentences, maximum) — 3 key things to know (bullets, each under 20 words) — The biggest risk right now (1 paragraph, under 80 words) — One action they can take this week (1 sentence)
→ Something you can paste directly into your email to a client or friend.
Use it when: you have a specific use for the output — a slide, an email, a doc section, a social post. Specify length (word counts or sentence counts), structure (bullets vs. prose vs. table), and what should come first.
04
Negative Instructions — Tell It What NOT to Do

AI models have been trained on every cliché ever published on the internet. They will default to "results-driven professional," "game-changing solution," "seamlessly integrated," and "passionate team" unless explicitly told not to. Negative instructions are often the difference between output that sounds like a person wrote it and output that reads like a press release from 2009. Banning what you don't want is faster and more effective than trying to describe the positive alternative.

Before — No Guardrails Write a product description for a task management app for freelancers. 100 words, App Store.
→ "Revolutionize your workflow with this powerful, intuitive, game-changing solution…"
After — Negatives Added Write a product description for a task management app for freelancers. 90–110 words for the App Store. Do NOT use: revolutionary, game-changing, seamless, intuitive, powerful, robust, boost, streamline, leverage, or "take control of." Do NOT use passive voice. Do NOT open with "Are you tired of…" or a question. Sound like a real person talking to another real person.
→ Something that sounds like a human being actually wrote it.
Use it when: you know what you hate in the output. Writing, marketing copy, bios, social posts, emails — anything where clichés are a risk. The more specific the prohibition, the cleaner the result.
05
Chain-of-Thought — Make It Reason Before It Concludes

AI generates text sequentially — each word is predicted from what came before. When you push it to a conclusion immediately, it shortcuts the reasoning process. Asking the model to think through a problem in steps before answering — chain-of-thought prompting — produces dramatically better results on any complex, analytical, or judgment-dependent task. This is especially important for decisions, evaluations, plans, and anything where nuance matters.

Before — Rush to Answer Should I accept this job offer?
→ Generic pros-and-cons list with zero relevance to your actual situation.
After — Chain-of-Thought I'm deciding whether to accept a job offer. Before giving a recommendation, do this in order: 1. Ask me the 5 questions you'd need answered to give genuinely useful advice. 2. After I answer, summarize what you understand about my situation in a few sentences — ask if you have it right. 3. List the 3 strongest arguments FOR accepting and 3 strongest AGAINST. 4. Then give your honest recommendation, labeled clearly, with one concrete next step. Complete each step fully before moving to the next.
→ A structured analysis built around your actual circumstances.
Use it when: the question is complex, has multiple valid considerations, or involves a judgment call. Anytime a conclusion without reasoning would be useless. Also useful for debugging: "Walk me through your reasoning step by step before you answer."
06
Few-Shot Examples — Show It Rather Than Describe It

Describing a tone or style to AI is hard — the words you'd use to describe "warm but professional" or "punchy but not gimmicky" are ambiguous. Showing examples is almost always more effective than describing. Paste in two or three pieces of writing that match what you want and tell the AI to match them. This technique — called few-shot prompting in research contexts — is particularly powerful for brand voice, writing style, and any task where you have approved examples to reference.

Before — Describe Style Write a LinkedIn post announcing our new product. Keep it warm but professional, punchy but not gimmicky, with personality but not trying too hard.
→ AI's interpretation of "warm but professional" — which may not match yours at all.
After — Examples Provided Write a LinkedIn post announcing our new product. Match the tone and structure of these posts I've written and approved: [Example 1:] [paste a post you liked] [Example 2:] [paste another post] New announcement: We just launched [product name] — [one sentence description]. Key benefit: [benefit].
→ Output that sounds like your voice, not AI's default voice.
Use it when: you have examples of what "good" looks like — past emails, approved copy, writing you admire. Even one example helps. Two or three is ideal. For anything involving brand voice, this technique is non-negotiable.
07
Precise Iteration — The First Draft Is Never the Final Draft

Prompting is a conversation, not a one-shot command. The first output is a starting point. The single most common mistake is either accepting the first result or giving feedback so vague that the next version isn't better. "Make it better" tells the AI nothing. "The opening sentence is too weak, the second paragraph repeats the first, and the tone in the third section sounds corporate — fix those three things specifically" tells it exactly what to do.

Weak Follow-Up That's pretty good but can you make it better and more engaging and maybe shorter?
→ Marginally different output that isn't actually better in a specific way.
Precise Follow-Up Good start. Three specific changes: 1. The opening sentence is generic — rewrite it to open with the specific customer problem, not our product. 2. Cut the second paragraph entirely — it repeats what the first paragraph said. 3. The closing CTA is weak ("reach out to learn more") — replace with a specific, friction-free action. Give me the revised version only, not an explanation of the changes.
→ A second draft that actually addresses what was wrong.

Two iteration habits that accelerate good output: first, tell the AI to give you only the revised content (not an explanation of what it changed — that wastes your reading time). Second, limit each round of feedback to 3 specific changes at most. More than that and the AI tries to fix everything at once and often breaks something that was already working.

Use it when: always. Every AI output is the start of a conversation, not the end of one. Build the habit of at least one round of precise revision on anything that matters.

The output ceiling isn't the AI's ability. It's the quality of your prompt. The techniques above remove the ceiling.

Putting It All Together — A Full Example

A master prompt layers multiple techniques simultaneously. Here's what a fully assembled prompt looks like, with each component annotated. This is for someone who needs to write a product-launch email to a customer list:

Complete Prompt — Annotated
[ROLE] You are an expert email copywriter who specializes in SaaS product launches. You've written launch emails that have achieved open rates above 35% and click rates above 8%. [CONTEXT] I'm a founder at a small project management SaaS. Our customer list is 4,200 small agency owners. They are busy, skeptical of hype, and care about saving time and impressing their clients. We've had three previous product emails this quarter — readers are slightly fatigued. [TASK] Write a launch email announcing our new AI-powered meeting summary feature. It automatically generates client-ready meeting notes within 60 seconds of a call ending. [FORMAT] Subject line + preview text + email body. Body: 150–200 words. Structure: 1 hook sentence → 1 problem sentence → feature + key benefit → social proof (I'll add the specific quote) → single CTA button. No headers or bullet points in the body copy. [CONSTRAINTS] No jargon: zero use of "game-changing," "revolutionize," "seamlessly," "robust," or "powerful." Do not start the body with "We're excited." Avoid exclamation points in the body copy. [CHAIN-OF-THOUGHT] Before writing, identify in one sentence: who is the reader, what is the single emotion we want them to feel, and what one action we want them to take. Then write the email.

Notice what that prompt does: it gives the AI expertise it needs (role), the context to calibrate to (customer segment, fatigue, company size), a precise deliverable (task), an exact structure (format), explicit prohibitions (constraints), and a reasoning step before writing (chain-of-thought). The output from a prompt like this is typically usable with minimal editing. Without those components, you'd be rewriting from scratch.

The 5 Most Common Prompting Mistakes

Being too vague about the task. "Help me with my presentation" could mean outline, draft, speaker notes, design suggestions, or feedback. Be specific: "Write speaker notes for slides 3–6 of a presentation on our Q2 results to a board audience. Each slide's notes should be under 60 seconds to deliver aloud."
Not specifying the audience. "Explain machine learning" produces a different answer for a data science PhD than for a VP of Marketing. Always identify who will read or use the output — their level of familiarity, what they care about, and what action you want them to take.
Accepting the first output. AI's first response is optimized for the average interpretation of your prompt, not your specific situation. Almost everything important deserves at least one precise revision round. Think of the first output as a draft, not a deliverable.
Asking for too many things at once. "Write me a blog post, a Twitter thread, an email newsletter, and a LinkedIn version of this content" produces four mediocre outputs instead of one excellent one. Complete the most important task well first, then adapt.
Treating AI feedback as fact. AI will confidently answer questions it doesn't actually know the answer to. If a prompt asks for statistics, legal information, medical information, or specific claims — verify them independently before publishing or acting on them. The techniques in this guide produce better outputs; they don't make AI immune to hallucination on factual questions.

Which AI to Use

Every technique in this guide works with any major AI assistant. The differences between them matter less than the quality of your prompt — a well-structured prompt to any of the four major assistants will outperform a vague prompt to the best model available.

ChatGPT (OpenAI) — The most widely used. GPT-4o is capable at the free tier; Plus ($20/mo) and Pro ($200/mo) add priority access, higher limits, and access to newer models. Best all-around generalist. The "Custom Instructions" setting lets you save a default role and context so you don't have to re-enter them every session.
Claude (Anthropic) — Particularly strong at writing quality, nuanced reasoning, and following complex multi-part instructions. Free tier is generous; Pro is $20/mo. Excellent for long-context tasks — you can paste a full document and Claude will work with all of it reliably. The "Projects" feature lets you maintain persistent context across conversations.
Gemini (Google) — Strong integration with Google Workspace. If you live in Docs, Sheets, or Gmail, Gemini can work directly inside those apps. Gemini Advanced ($20/mo via Google One AI Premium) enables the most capable model. Good for research-adjacent tasks.
Microsoft Copilot — Built into Word, Excel, Teams, and Outlook in Microsoft 365. If your organization uses Microsoft 365, Copilot Pro ($20/mo) means AI works directly inside the documents you're already editing. Less powerful for standalone writing tasks; strongest for working inside existing Office documents.

One practical note: for tasks involving confidential business information, research which tier of each service uses your inputs for AI training and which doesn't. Enterprise and team tiers of all four services above offer contractual data privacy protections that free tiers do not. For anything genuinely sensitive, check before you paste.

Conclusion
This Is the Skill. Learn It Now.

What separates AI power users from everyone else is not access to better tools. It's the habit of telling the tool what it needs to know before expecting it to do good work. Role, context, task, format, constraints, reasoning steps, and precise iteration — layer these together and the output changes from generic to genuinely useful.

Pick one prompt you use regularly — maybe a weekly status email, a project brief, a customer reply — and rebuild it using the five anatomy components: role, context, task, format, constraints. Run it. Compare the output to what you've been getting. That comparison will make the argument better than anything written here.

Then iterate once. That's the whole lesson. Two steps: build a real prompt, then revise it precisely. Do it enough times and it becomes reflex.

S
Sheldon Valentine
Founder · Dear Tech

Sheldon writes about AI tools, prompting strategy, and the practical skills that matter in an AI-augmented workplace. Dear Tech is committed to concrete, jargon-free guidance that works on Monday morning — not just in theory.

Share
Back to Blog