Play the people who'll say no, then answer every objection with “why not?” to find the way through.
When people resist an idea, they usually give reasons: “it'll cost too much,” “clients won't like it,” “we tried that once.” Why Not? takes those reasons seriously. You role-play the people who might block you, let them make their case in full, and then meet each objection with a simple question: “Why not?”
Asking why not pulls out the assumption hiding under each objection. Some turn out to be outdated or simply feared. Some are fair and point to a real flaw you should fix. Either way you learn how the other side thinks, rehearse the tough conversation before it's real, and walk in with answers, changes and evidence ready.
Use it when an idea keeps meeting resistance, when you're about to propose a change to people who could say no, or when two groups disagree and you need to understand what each one is really protecting.
Each objection hides an assumption. Asking “why not?” turns it into a question you can answer or a flaw you can fix.
Who could block, slow down or argue against this idea, and who will play each of them?
Speaking as this person, what are your objections, and what do you really care about?
When an objection lands hard, stop the scene: why did you say that, and what would change your mind?
For each objection, ask “why not?”: what would have to be true for it to stop being a problem?
For each objection, what change to the idea, piece of evidence or offer would clear it?
Most objections rest on an assumption nobody has said out loud. Playing the objector lets you hear it; asking “why not?” lets you test it.
“That'll never work here” usually means “that won't work if X is true.” Often X is outdated, partly true or simply feared. Asking “why not?” drags the assumption into the open, where you can check it or design around it.
People rarely state their deepest concerns in a meeting. When a colleague plays the objector, freed from politeness and politics, the worries behind the position come out: lost status, extra work, a bad experience last time.
Hearing the toughest objections in a safe rehearsal means none of them catch you off guard later. You walk into the real conversation with answers, changes and evidence ready, instead of getting defensive.
“Why not?” works in both directions. Some objections expose flaws in the idea, and some expose assumptions you made yourself. Either way the plan that survives is stronger, and the people who objected can see they were heard.
Write the idea in one sentence, plus what you need to happen next: approval, a trial, agreement between two groups. Everyone should know exactly what's being tested.
List the people who could block or disagree. Ask colleagues who know them to play each role, and brief them with a few notes on that person's position and pressures.
Let each role state their objections in character, fully and without interruption. If two roles disagree, let them argue it out. Write every objection down.
Pause the scene at key moments. Ask the role-player why their character reacted that way and what they're protecting. Replay a moment with a different approach if it helps.
Step out of role. For each objection, ask why not and find the assumption underneath. Is it true, partly true or out of date? Put your own assumptions through the same test.
Decide how to answer each objection: change the idea, gather evidence, run a small test, or offer something that meets the real interest. Agree who does what before the real conversation.
Three to six people willing to play roles, a few notes on each blocker's position, and a board split into Objection and Why not? With AI, the prompt below can play the roles.
Team: a 12-person operations team. Idea: replace the Monday meeting with short written updates and a 20-minute Q&A. Next step: get the department head to agree to a one-month trial.
“I'll lose sight of problems.” Why not? It assumes problems only surface out loud. Response: a blockers box at the top of every update, read first.
“Nobody reads written updates.” Why not? Because they're usually long. Response: a five-line template, due by 10 a.m. Monday.
“Monday is my only chance to ask questions.” A fair point the idea had missed. Response: keep the Q&A and give each new hire a buddy.
“Decisions will stall without a meeting.” Why not? Most Monday decisions turned out to be small. Response: big ones get their own short meeting.
We assumed everyone hated the meeting. In role, two people valued it for team spirit, so a monthly team coffee was added.
Every objection got a response, and two of them changed the plan. The proposal went to the department head with the answers built in.
A one-month trial: five-line written updates due by 10 a.m. Monday, blockers listed first, a 20-minute Q&A, buddies for new hires and a monthly team coffee. The team reviews it with the department head at the end of the month.
The hardest part of Why Not? is finding people who can play your critics convincingly. AI can play every role: the cautious boss, the overloaded colleague, the skeptical client. It stays in character, pauses when you ask, and helps you dig out the assumption behind each objection. You know the real people, and you decide how to respond.
Have AI list who might object and what each one cares about most.
Who might object to replacing our status meeting with written updates? Give each a role and a core worry.
Pitch to a role-played blocker and let them push back hard.
Play our department head. I'll pitch written updates. Push back the way a busy, cautious boss would.
Pause the role-play and ask what's really behind the objection.
Pause. Out of character: what is the department head really worried about, and what would reassure them?
Turn each objection into the assumption it depends on, then test it.
For each objection so far, name the assumption behind it and how I could test whether it's true.
Describe your idea and who might block it, pick a mode, then copy the prompt into Claude, ChatGPT, Gemini or Copilot. In coach mode the AI plays each objector in turn, pauses when you ask, and helps you answer every objection.
The “Open in” links put the prompt in the web address. If your challenge includes anything sensitive, copy and paste instead.
After the session, click one to copy it, then paste it into the same chat.