The Reversal of Perspective

Ask the question directly in the same thread, as its own turn: "before we try again - what did you understand me to be asking for?" The thread still holds your original prompt, so it can look back at its own reading. Keep the diagnosis and the retry separate; combined into one message, the model skips the diagnosis and just produces a better answer, which fixes this prompt and teaches you nothing. If you keep hitting the same ambiguity, the fix belongs in Custom Instructions.

• Diagnose in one turn, retry in the next. Never combined.
• Ask "what would any reader assume?", not "why did you fail?".
• Refuse the apology; you want the ambiguous word named.
• A recurring ambiguity belongs in Custom Instructions.
• The explanation is a plausible reconstruction, not a readout.

**Turn 1 - the reversal.** Send this on its own, in the same thread as the prompt that disappointed you:

Stop before trying again. I want the diagnosis, not a better draft.

Looking back at my last prompt: what tone and style did you understand me to be asking for, and which specific words told you that? Quote them.

Then: if you had to guess what I actually wanted - given that this is a charity initiative and I am putting it on social media - what would that be, and where does it conflict with what I asked for? I think I may have asked for two incompatible things without noticing.

Do not apologise and do not tell me the prompt was fine. Name the word that did the damage.

**What you are likely to be told:** "professional and buttoned-up" pulled it toward a press release, and a press release is the one register in which nobody shares news about charity. The word was doing a job you did not intend - you probably meant "do not be flippant", and it was read as "be corporate".

**Turn 2 - the corrected prompt:**

Let us try again, and I now see the problem with how I briefed it.

Write a social media post about our new charity initiative.

Tone: inspiring and warm. Not corporate, not a press release, no "we are pleased to announce". I want someone scrolling past to feel something and want to pass it on.

The goal is a reader feeling good about the brand and sharing the news - not a formal record of the announcement.

Lead with the people it helps, not with our company. Keep it short enough to read without tapping "more". One clear line about how someone can get involved.

Give me three versions at different levels of warmth so I can see the range - I clearly do not yet know where my own line is.

**Worth doing once:** if you find yourself writing "professional" and meaning "not sloppy", put a line in Custom Instructions saying what you mean by it. That ambiguity will otherwise follow you into every brief you write.

**Turn 1 - the reversal.** This is the case the technique was made for: a word that is precise inside your team and ambiguous everywhere else.

That is not what I meant. Before you revise anything:

In my prompt "improve the velocity of my engineering team" - what did you take "velocity" to mean? Give me every reading you considered, not just the one you went with, and say which you chose and why.

And tell me what else in my prompt was underspecified. Did you have any way to know whether I meant a specific Agile metric, general speed of delivery, or something about morale and momentum?

Do not blame yourself for this. I want to know what my sentence actually communicated to a reader who does not work at my company.

**What you are likely to be told:** at least three readings - the Agile sprint metric of story points per sprint, general shipping speed, and a loose sense of team energy. All three are defensible from your sentence, and the plan you got was probably aimed at the vaguest of them. The missing information is not just the definition of velocity but what you are measuring now and what is actually slowing you down.

**Turn 2 - the corrected prompt:**

Let me be precise. In Agile software development terms, I need a plan to improve my engineering team's sprint velocity - story points completed per two-week sprint.

Context: [team size] engineers, currently averaging [X] points per sprint, aiming for [Y]. Our main complaints internally are [the real bottleneck - code review queues, unclear requirements, interruptions, flaky tests].

Give me a plan that distinguishes clearly between three things:
1. Changes that genuinely increase throughput.
2. Changes that only inflate the number - looser estimation, splitting tickets, counting differently. Name these explicitly so I can avoid them, because they are the easiest way to hit my target and learn nothing.
3. What I should measure alongside velocity so I notice if quality is paying for the speed.

If you think velocity is the wrong thing for me to be optimising given the bottleneck I described, say so first. I would rather be told that than get a competent plan for the wrong goal.

**Turn 1 - the reversal.** Note that this prompt is not vague at all. It is detailed, specific, and still wrong - which makes it the most instructive of the three. The error is in the goal, and no amount of added detail would have found it.

This outline is not persuasive and I want to understand why before I ask again.

Based on my prompt: what did you understand the single most important goal of this presentation to be? Say it in one sentence, as you inferred it.

Then: which part of my prompt made you think that? And - this is the real question - if you were advising me rather than taking instructions from me, what would you say the goal of a first meeting with a potential client should be? Where do those two answers differ?

Be direct about it. My prompt was specific, so I assumed it was good. Tell me what it specified that it should not have.

**What you are likely to be told:** your prompt names its goal explicitly - include all the technical specs of three models - and that was followed faithfully. The goal of the meeting, though, is almost certainly to get a second meeting. A specs-led presentation is what you give someone who has already decided to buy. The detail in your prompt was all pointed at the wrong target, which is why a more detailed version of the same prompt would not have helped.

**Turn 2 - the corrected prompt:**

The primary goal of my presentation is to persuade a major construction client in Hyderabad to book a live demonstration. Nothing else matters as much as that single outcome.

My company sells drone-based surveying equipment. The audience is a large construction company - likely a mix of project managers and someone from finance.

Create a persuasive outline that focuses on benefits rather than features. Build it around how our technology saves time, reduces cost and improves safety on large construction sites - framed as what a survey currently costs them in days of delay, not as what our drones can do.

Technical specifications go in a single appendix slide, referenced only if asked.

For each slide: the one message it must land, and the question it should leave the audience wanting to ask.

End with the ask for the demonstration, made specific - a date, a site, a named person.

And before the outline, tell me the one thing I have still not given you that would make this better.