You asked for a concise 3-bullet summary without conversational filler, but ChatGPT gave you four long paragraphs starting with “Sure, I would be happy to help!” When an AI model appears to overlook explicit constraints, the problem is rarely that it “refused”—it is almost always an issue of attention weighting, negative constraint traps, or prompt structure.
The 8 Most Common Causes of Ignored Instructions
-
The Negative Constraint Trap (“Don’t do X”):
Language models process text as attention tokens. When you write “Do not include an introduction”, the tokens “introduction” and “include” still trigger semantic activations. The fix: State constraints positively. Write “Begin immediately with bullet 1” instead of “Don’t write an intro”.
-
Instruction Dilution (Burying Rules in the Middle):
Research on transformer architectures demonstrates the “lost in the middle” phenomenon: models pay the highest attention to tokens at the very beginning and very end of the prompt window. The fix: Place critical output format requirements at the bottom of your prompt, immediately before the submission.
-
Conflicting Directives:
Asking for “a comprehensive, exhaustive analysis” while also requesting “under 150 words” creates conflicting optimization targets. When constraints fight, the model usually defaults to its default conversational verbosity.
-
Lack of Structured Delimiters:
If instructions, context, and sample text run together in one paragraph, the model struggles to parse boundary lines. Use triple quotes (
"""), XML tags (<context>,<instructions>), or clear markdown headers. -
Chat Context Window Accumulation:
If you have been chatting in the same thread for 20 messages, earlier instructions and output examples degrade in attention weight. Start a fresh conversation when switching tasks or enforcing strict formatting.
-
Weak Role Framing:
Generic prompts receive generic conversational behavior. Assigning a precise operational role (“Act as a strict database schema validator”) primes the model for obedience to structural rules.
-
Example Absence (Few-Shot Prompting):
Describing a format in words is never as effective as showing one concrete input-output example. Providing a single “few-shot” example increases formatting compliance by over 60%.
-
System Instructions vs. User Overrides:
Chat models have underlying safety and politeness guidelines that prioritize conversational tone unless explicitly instructed with direct output tokens (e.g., “Output raw JSON only with no markdown backticks”).
Weak Prompt: “Summarize this article for me, make it quick, don’t write a long intro, and give me key takeaways.”
TASK: Extract exactly 3 key findings from the text below. OUTPUT RULES: - Start directly with finding #1 (no greeting, no summary intro). - Each finding must be exactly one sentence under 25 words. - Format: Bold keyword followed by colon and finding. TEXT: [Paste your article text here] OUTPUT:
Result: By moving constraints to an explicit list and ending with the anchor OUTPUT:, formatting accuracy reaches near 100%.