{"course":{"slug":"prompting","title":"Getting Real Work out of a Model","url":"https://addaly.com/learn/prompting","level":"beginner","track":"start"},"lesson":{"slug":"showing-what-not-to-do","title":"Negative examples, and when they backfire","url":"https://addaly.com/learn/prompting/showing-what-not-to-do","position":24,"of":72,"minutes":8,"answer":"A bad example demonstrates the thing you are trying to prevent, so pair it with its correction and end on the good version, or replace it with a checkable list and a separate self-check.","keyIdea":"A bad example demonstrates the thing you are trying to prevent, so pair it with its correction and end on the good version, or replace it with a checkable list and a separate self-check."},"body":{"format":"markdown","text":"## The obvious idea, and its problem\n\nIf showing good output works, showing bad output should work too. Sometimes it does. Often it does something you did not want, and the mechanism is the one from the negative-instructions lesson: whatever you put in the context is in the context.\n\nPaste three examples of the flabby corporate writing you hate, labelled \"do not write like this\", and you have put three paragraphs of flabby corporate writing in front of the model immediately before asking it to write. The label helps. It does not fully counteract the demonstration.\n\nThe strongest form of this failure is with format. Show a malformed JSON example as a warning and you meaningfully raise the chance of getting malformed JSON, because the malformed structure is now the most recent structure in the prompt.\n\n## When negative examples do work\n\nThree conditions, and they need to hold together.\n\n**The bad and good versions are paired.** Never show a bad example alone. Show it next to its correction, so the transformation is what is demonstrated, not the flaw.\n\n```\nWeak:  \"We are pleased to announce the launch of our\n        innovative new solution.\"\nBetter: \"Our new invoicing tool is live from Monday.\"\nWhy:   name the thing, name the date, drop the announcement framing.\n```\n\n**The good version comes last.** Recency works for you here. End on what you want.\n\n**The flaw is specific and namable.** \"Too corporate\" is not a flaw a model can avoid. \"Opens with an announcement instead of the news\" is.\n\nUnder those three conditions, a before-and-after pair is one of the most efficient teaching devices you have, because it shows both the error and the repair in the space of one example.\n\n## The stronger alternative for most cases\n\nRather than showing bad output, name the specific things to avoid as a checkable list, and show only good output.\n\n> Do not use these words: leverage, robust, seamless, journey, unlock, solution (as a noun for a product), delve.\n>\n> Here is the tone we want:\n> [one real paragraph]\n\nA word list is checkable: you can search the output for each item. \"Not like the bad example\" is not checkable by anyone, including you.\n\n## A case where negatives are necessary\n\nSafety and correctness boundaries in automated systems. If a support bot must never promise a refund, \"never promise a refund\" plus a demonstration of the near-miss is more robust than either alone:\n\n```\nCustomer: \"Will I get my money back?\"\nCorrect:  \"I'll pass this to the team who can authorise refunds and\n           they'll reply today.\"\nNot:      \"Yes, we'll refund you.\" (never commit to a refund)\n```\n\nHere the risk of demonstrating the bad line is outweighed by the value of marking exactly where the line falls, and the correct version still comes first and last in the reader's attention.\n\n## The reverse trick that is often better\n\nInstead of showing bad output, ask for the critique as a separate step:\n\n> Draft the email. Then, below it, list anything in your draft that breaks these rules: [rules]. Then give the corrected version.\n\nThe model produces the flaw, identifies it, and fixes it, without you having supplied a single example of bad writing. This works well and costs one extra paragraph of output.\n\nIt is also honest about what is happening: the checking pass is doing the work, not a warning label attached to a demonstration.\n\n## The summary\n\nBad examples teach. That is the problem. Pair them with their corrections, end on the good one, name the flaw precisely, or skip them entirely in favour of a checkable list of prohibited specifics and a separate self-check pass.\n\n## A quick way to decide\n\nAsk what the bad example is for.\n\nIf it exists to mark a line (the thing that must never be said, the format that will break a downstream system) keep it, pair it, annotate it. The precision is worth the risk.\n\nIf it exists to express your taste (this writing is flabby, this design is ugly, this reply is too cold) take it out. Taste does not transfer through a labelled negative; it transfers through positive examples of what you do want, plus a handful of specifics you can search the output for.\n\nNearly all the negative examples people put in prompts are the second kind wearing the clothes of the first."},"check":{"question":"A developer's prompt includes a malformed JSON sample labelled \"NEVER output this\". Output failures increase. Why?","options":[{"text":"The label was ambiguous and the model treated it as an alternative acceptable format.","correct":false,"tempting":"Attributes it to a wording problem; the issue is the presence of the malformed structure, not the clarity of the warning."},{"text":"JSON validation is unreliable, so the failures were probably always there and merely became visible.","correct":false,"tempting":"Invents a measurement artefact rather than engaging with the change that was actually made."},{"text":"Adding any example increases output length, and longer outputs break structure more often.","correct":false,"tempting":"Length is not the mechanism, and a well-formed example of the same length would not produce this."},{"text":"The malformed structure is now a demonstrated pattern in the prompt, and demonstration outweighs the warning attached to it.","correct":true}]},"prev":{"slug":"rules-and-examples-together","title":"State the rule, then show it","url":"https://addaly.com/learn/prompting/rules-and-examples-together"},"next":{"slug":"capturing-a-voice","title":"Capturing a voice from three samples","url":"https://addaly.com/learn/prompting/capturing-a-voice"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Exam keys checked blind by a second model: 3,665 of 3,666 agreed. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'Negative examples, and when they backfire', in Getting Real Work out of a Model. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/prompting/showing-what-not-to-do (Accessed: 13 October 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"Negative examples, and when they backfire","courseTitle":"Getting Real Work out of a Model","module":{"index":3,"slug":"teaching-by-example","title":"Teaching by example"},"answer":null,"keyIdea":"A bad example demonstrates the thing you are trying to prevent, so pair it with its correction and end on the good version, or replace it with a checkable list and a separate self-check.","hero":{"kind":"plate","image":null,"alt":null,"caption":null},"blocks":[{"t":"h2","id":"the-obvious-idea-and-its-problem","runs":[{"text":"The obvious idea, and its problem"}]},{"t":"p","runs":[{"text":"If showing good output works, showing bad output should work too. Sometimes it does. Often it does something you did not want, and the mechanism is the one from the negative-instructions lesson: whatever you put in the context is in the context."}]},{"t":"p","runs":[{"text":"Paste three examples of the flabby corporate writing you hate, labelled “do not write like this”, and you have put three paragraphs of flabby corporate writing in front of the model immediately before asking it to write. The label helps. It does not fully counteract the demonstration."}]},{"t":"p","runs":[{"text":"The strongest form of this failure is with format. Show a malformed JSON example as a warning and you meaningfully raise the chance of getting malformed JSON, because the malformed structure is now the most recent structure in the prompt."}]},{"t":"h2","id":"when-negative-examples-do-work","runs":[{"text":"When negative examples do work"}]},{"t":"p","runs":[{"text":"Three conditions, and they need to hold together."}]},{"t":"p","runs":[{"text":"The bad and good versions are paired.","b":true},{"text":" Never show a bad example alone. Show it next to its correction, so the transformation is what is demonstrated, not the flaw."}]},{"t":"code","lang":"","label":"Text","text":"Weak:  \"We are pleased to announce the launch of our\n        innovative new solution.\"\nBetter: \"Our new invoicing tool is live from Monday.\"\nWhy:   name the thing, name the date, drop the announcement framing."},{"t":"p","runs":[{"text":"The good version comes last.","b":true},{"text":" Recency works for you here. End on what you want."}]},{"t":"p","runs":[{"text":"The flaw is specific and namable.","b":true},{"text":" “Too corporate” is not a flaw a model can avoid. “Opens with an announcement instead of the news” is."}]},{"t":"p","runs":[{"text":"Under those three conditions, a before-and-after pair is one of the most efficient teaching devices you have, because it shows both the error and the repair in the space of one example."}]},{"t":"h2","id":"the-stronger-alternative-for-most-cases","runs":[{"text":"The stronger alternative for most cases"}]},{"t":"p","runs":[{"text":"Rather than showing bad output, name the specific things to avoid as a checkable list, and show only good output."}]},{"t":"quote","runs":[{"text":"Do not use these words: leverage, robust, seamless, journey, unlock, solution (as a noun for a product), delve."}]},{"t":"quote","runs":[]},{"t":"quote","runs":[{"text":"Here is the tone we want:"}]},{"t":"quote","runs":[{"text":"[one real paragraph]"}]},{"t":"p","runs":[{"text":"A word list is checkable: you can search the output for each item. “Not like the bad example” is not checkable by anyone, including you."}]},{"t":"h2","id":"a-case-where-negatives-are-necessary","runs":[{"text":"A case where negatives are necessary"}]},{"t":"p","runs":[{"text":"Safety and correctness boundaries in automated systems. If a support bot must never promise a refund, “never promise a refund” plus a demonstration of the near-miss is more robust than either alone:"}]},{"t":"code","lang":"","label":"Text","text":"Customer: \"Will I get my money back?\"\nCorrect:  \"I'll pass this to the team who can authorise refunds and\n           they'll reply today.\"\nNot:      \"Yes, we'll refund you.\" (never commit to a refund)"},{"t":"p","runs":[{"text":"Here the risk of demonstrating the bad line is outweighed by the value of marking exactly where the line falls, and the correct version still comes first and last in the reader’s attention."}]},{"t":"h2","id":"the-reverse-trick-that-is-often-better","runs":[{"text":"The reverse trick that is often better"}]},{"t":"p","runs":[{"text":"Instead of showing bad output, ask for the critique as a separate step:"}]},{"t":"quote","runs":[{"text":"Draft the email. Then, below it, list anything in your draft that breaks these rules: [rules]. Then give the corrected version."}]},{"t":"p","runs":[{"text":"The model produces the flaw, identifies it, and fixes it, without you having supplied a single example of bad writing. This works well and costs one extra paragraph of output."}]},{"t":"p","runs":[{"text":"It is also honest about what is happening: the checking pass is doing the work, not a warning label attached to a demonstration."}]},{"t":"h2","id":"the-summary","runs":[{"text":"The summary"}]},{"t":"p","runs":[{"text":"Bad examples teach. That is the problem. Pair them with their corrections, end on the good one, name the flaw precisely, or skip them entirely in favour of a checkable list of prohibited specifics and a separate self-check pass."}]},{"t":"h2","id":"a-quick-way-to-decide","runs":[{"text":"A quick way to decide"}]},{"t":"p","runs":[{"text":"Ask what the bad example is for."}]},{"t":"p","runs":[{"text":"If it exists to mark a line (the thing that must never be said, the format that will break a downstream system) keep it, pair it, annotate it. The precision is worth the risk."}]},{"t":"p","runs":[{"text":"If it exists to express your taste (this writing is flabby, this design is ugly, this reply is too cold) take it out. Taste does not transfer through a labelled negative; it transfers through positive examples of what you do want, plus a handful of specifics you can search the output for."}]},{"t":"p","runs":[{"text":"Nearly all the negative examples people put in prompts are the second kind wearing the clothes of the first."}]}],"check":{"question":[{"text":"A developer’s prompt includes a malformed JSON sample labelled “NEVER output this”. Output failures increase. Why?"}],"options":[{"text":[{"text":"The label was ambiguous and the model treated it as an alternative acceptable format."}],"correct":false,"tempting":[{"text":"Attributes it to a wording problem; the issue is the presence of the malformed structure, not the clarity of the warning."}]},{"text":[{"text":"JSON validation is unreliable, so the failures were probably always there and merely became visible."}],"correct":false,"tempting":[{"text":"Invents a measurement artefact rather than engaging with the change that was actually made."}]},{"text":[{"text":"Adding any example increases output length, and longer outputs break structure more often."}],"correct":false,"tempting":[{"text":"Length is not the mechanism, and a well-formed example of the same length would not produce this."}]},{"text":[{"text":"The malformed structure is now a demonstrated pattern in the prompt, and demonstration outweighs the warning attached to it."}],"correct":true,"tempting":null}],"order":[1,2,3,0],"why":null},"prev":{"slug":"rules-and-examples-together","title":"State the rule, then show it","minutes":8},"next":{"slug":"capturing-a-voice","title":"Capturing a voice from three samples","minutes":9}}}