Picture this: same task, same model, twenty tries back to back. Attempt one gets a shrug of an answer, the kind you’d expect from AI on autopilot, vague, generic, the sort of thing you skim once and forget. By attempt twenty, this Redditor, u/od1sseass over on r/ChatGPTPromptGenius, had a result that read like a completely different assistant wrote it. Sharper structure, more specific language, actual substance instead of filler.
The wild part? The model never changed. Only the prompt did, and not by making it longer. The original poster kept the exact same task for all 20 rounds and rebuilt only the ask each time, chasing “smarter,” not “more words.” I read through the whole thread and honestly, the pattern this contributor landed on is one every AI user should steal. It’s the kind of thing that seems obvious once you see it written out, but almost nobody actually does it in practice.
Why It Matters 🎯
Most people blame the model the second an answer falls flat. Type the question, get something mediocre, decide “AI just isn’t that good,” and move on to the next tool, the next subscription, the next promise of a smarter chatbot. This experiment says that’s the wrong conclusion. The model stayed fixed across all 20 runs, same weights, same settings, same everything under the hood. What actually moved was how clearly the ask got framed.
If you’ve ever retyped the same question hoping for a better roll of the dice, this is why that never works. The dice were never the problem. You were asking the same underspecified thing twenty different ways and expecting a different outcome, when the real fix was never in the retyping, it was in the framing. Once you see that, it’s hard to unsee it in every mediocre AI response you’ve ever gotten.
How-To Steps 🛠️
The original poster narrowed the improvements down to five moves, and they build on each other, each one closing a gap the last one left open:
- Give the AI a role. Swap a bare question for “Act as a senior marketing strategist…” A role sets the tone, vocabulary, and depth before the model writes a single word. It’s the difference between asking a stranger on the street and asking someone whose job depends on getting it right.
- Explain the context instead of assuming it’s obvious. The AI can’t see your inbox, your team, or the six months of history behind your question. Brief it like you’re onboarding a new hire on day one, background, constraints, what’s already been tried, what failed.
- Define exactly what success looks like. Not “write me a plan,” but “write me a plan I could hand my team today and they’d know exactly what to do.” A concrete finish line beats a vague request every time, because the model stops guessing at your bar and starts writing to it.
- Set clear constraints. Length, tone, format, what to avoid entirely. Constraints don’t box the AI in, they do its thinking for it, cutting off the dozens of directions it could wander before it ever starts typing.
- Let the AI ask questions before it answers. This is the one that flips the whole interaction. Instead of guessing at what you meant, the model surfaces the gaps in your ask first, the assumptions you didn’t realize you were making.
Stack all five on one task and the output stops reading like a rough first draft. It starts reading like something a specialist actually sat down and wrote, with the context baked in instead of bolted on after the fact.
Tips & Tricks 💡
The comments turned up a technique that pairs perfectly with step 5. u/Busy_Astronomer_8230 shared a prompt built entirely around this idea: “From now on, don’t rush to give me answers. Ask a better question first, one that forces me to think more clearly about what I’m really asking.” Drop that into a chat and the AI stops handing you a quick answer and starts working the actual problem with you, more like a collaborator than a vending machine.
Another commenter, u/Sensitive-Egg-6586, made a solid point worth remembering: you don’t need to retype your role and context in every single prompt. Save the recurring pieces as a personalization setting or a reusable skill, then only write the task-specific part fresh each time. That alone saves the ten seconds of typing and, more importantly, keeps you from skipping the good habit when you’re in a hurry.
One more thing this Reddit user’s post makes clear: none of these five techniques require a paid tool, a plugin, or a smarter model. They’re free, they take about ten extra seconds to type, and they work in whatever chat window you already have open, no upgrade, no new subscription, no waiting on the next model release.
Try It Today 🚀
Next time you open a chat, don’t just ask. Give the AI a role, explain the situation, spell out what winning looks like, and see how far one better-built prompt can carry you.
Want more of these swaps? The full Reddit thread is full of prompts other users shared in the comments, worth a scroll if you’re building your own prompt library.
Frequently Asked Questions
Q: Do I need to use all 5 techniques in every single prompt?
Nope. Build the core techniques into a reusable system prompt or custom instructions, then just talk naturally day-to-day. Saves you from typing the same thing over and over.
Q: Are examples actually better than writing detailed prompts?
Some experienced users say examples let the AI extrapolate without all the extra instructions, the old-school approach but it still works. Real answer: test both with your actual tasks and see which gets you better results faster.
Q: How do I get the AI to ask clarifying questions instead of just answering?
Start with something like “Before you answer, ask me three questions that’ll help you understand what I’m actually trying to solve.” Sounds simple, but it pushes both you and the AI to dig into the real problem, not just surface stuff.
Q: Can I build these prompt techniques into a system prompt and reuse them?
Totally. Put your role assignments, constraints, and preferred working style into a system prompt once, then just mention what you need. The AI already knows how to communicate with you.
I tested the same prompt on ChatGPT 20 times. Here’s what I learned
by u/od1sseass in ChatGPTPromptGenius