Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why can't I get reliable results, even with a good prompt?

You treat the model like a vending machine. Put in the right words, get the right answer out. When the answer is wrong, you assume the prompt was wrong, so you throw it out and write a new one from scratch. But you never examine what came back. You don't ask which part failed, or why it failed that way. You just discard and retry, hoping the next attempt lands by luck. That is not a prompting problem. That is a missing habit. The skill you lack has a name: look at the output, find exactly where it diverges from what you needed, change one thing to close that gap, try again. Do this enough times and you stop guessing. You start knowing.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The fix is mostly a habit to build through repetition, so coaching outweighs the small amount of explanation needed about how feedback loops work.
How the two dials adapt to you →
What’s really going on

You are not bad at prompting. You are missing a feedback loop. You write, you get something back, and you move on without asking what was wrong or why. Build the habit: look at the output, name the gap, change one thing. That is the entire skill.

🔒 What you’ll build togetherUnlock by starting
A moveAfter every output, write one sentence naming exactly what is wrong with it — not 'this is bad,' but what specifically missed.
A moveChange only one part of your prompt before trying again. If you rewrite everything, you learn nothing.
A moveKeep a short running note of what changes worked. Stop relearning the same lesson every week.
A moveWhen an output confuses you, ask the model to explain its own reasoning. Treat it as something you question, not something you obey.
A moveRevise what you have instead of starting over. Starting over hides the pattern you need to see.

What changes unlock by starting

  • Within two tries, you can tell whether a bad result is the model's limit or your unclear ask.
  • You need fewer attempts to get work you can actually use.
  • You build a written record of what kind of instruction this model responds to.
  • You stop blaming yourself or the tool, and start adjusting instead.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.