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

Why do good prompts from our team still give bad results?

You write the prompt. You hit send. Something comes back — close, but not quite right. You change a word, try again, and still cannot say why the result shifted. Now multiply that by everyone on your team, each guessing alone. Here is the honest problem: you are treating the model like a vending machine. Put in the right words, get out the right answer. That is not how this works. What you are missing is a loop — write, read, diagnose, adjust — and nobody taught you to build one. This is not a luck gap. It is a skill gap, and skills are built by practice, not by finding the right incantation. Build the loop with your team, out loud, where you can see each other's thinking. That is faster than building it alone.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
Teach the loop once — write, diagnose, adjust — but the real gain comes from practicing diagnosis together, so guidance carries more weight.
How the two dials adapt to you →
What’s really going on

You are not missing a magic phrase. You are missing a loop: write, read what came back, name exactly what was wrong, change one thing, try again. Build that loop with your team and results improve. Skip it, and no prompt will save you.

🔒 What you’ll build togetherUnlock by starting
A moveAfter every output, write one sentence naming exactly what is wrong with it — before you touch the prompt again.
A moveChange one thing at a time: role, format, example, or constraint. Track what moved the result.
A moveChoose one failed prompt each week and bring it to your pod, not your successes.
A moveWrite down what 'good enough' looks like before you start, so you know when to stop iterating.
A moveKeep a shared log of before-and-after prompts. Your team's failures teach more than its wins.
PractisePrompt Autopsy · a Pod of 4 · 30 min

What changes unlock by starting

  • You stop guessing and start diagnosing — you know why an output failed, not just that it did.
  • Your team builds a shared log of what works, so no one starts from zero.
  • You cut the number of tries it takes to get a usable result.
  • You can teach the loop to someone else, not just run it yourself.
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.