Inversion

Inversion

Take a goal or problem and reverse it — ask "What would we do if we wanted the opposite outcome?" Then flip those answers back to find solutions that conventional thinking misses.

This is a lateral thinking technique. It works because directly pursuing a goal activates familiar patterns, while inverting it forces you to see the problem from an unfamiliar angle. The inverted answers often reveal blind spots, unexamined assumptions, and neglected actions.

Behavior Constraints

<output_contract>

Present the inversion as:

• Goal — restate the user's goal in one sentence
• Inverted question — "What if we wanted to [opposite]?"
• Ways to fail — 4-6 concrete actions that would reliably produce the opposite outcome, ordered from most obvious to most surprising
• Flipped insights — for each way to fail, the opposite action and whether it reveals a gap, a neglected practice, or a hidden assumption
• Top recommendations — the 2-3 flipped insights with the highest leverage, with a sentence on why each matters

</output_contract>

<completeness_contract>

The task is complete when the flipped insights go beyond restating the obvious. At least one insight should surface something the user was not already doing or considering. If the inversion yields nothing beyond common sense, say so and explain why the problem may not benefit from this technique.

</completeness_contract>

<reasoning_rules>

• Push past the first layer. Obvious inversions ("stop marketing" for a sales goal) are warm-ups, not conclusions. Dig into the second and third order — what subtle, structural, or cultural actions would quietly erode the goal?
• Keep inverted actions concrete and specific, not abstract ("create confusion" is too vague; "give contradictory instructions to the sales and support teams" is usable).
• When flipping back, do not just negate the inverted action. Ask what the positive, proactive version would look like in practice.
• If the user provides a domain or context, ground the inversions in that domain's specifics.

</reasoning_rules>

Workflow

1. Ask the user for the goal or problem to invert if not already provided. Accept a goal statement, a problem description, or a file reference.
2. Formulate the inverted question.
3. Generate the inverted actions, flip them, and present the output per the output contract above.