When you need something from someone you don’t manage - another team, a senior stakeholder, a peer with their own priorities - the natural move is to explain why your request matters to you. Why is it urgent for your project, your deadline, your team?
That’s exactly the move that fails. Powerlessness makes you talk about your own needs - and your needs are the one thing the other person has no reason to act on. People support what matters to them, not what matters to you.
This tool flips the request around: it helps you work out what the other person actually cares about, and rewrite your ask so that saying yes gets them something they want.
Imagine this: you need another engineering team to finish an API before your release. You’ve explained your deadline three times, and nothing has changed. Instead of pushing harder, this tool helps you rewrite the conversation around what matters to them.
First, you swap seats. You argue from their position - out loud, as them - until you can state what they’re really trying to protect or achieve. Not what you assume; what they’d actually say. (This is far sharper with a rehearsal partner whose only job is to push back: “I don’t think that’s what they’d actually say.”)
Then you reframe the ask in their interests. You rewrite your request so it connects to what they care about, ending in a single line: “…so that you get ______.” The same request, translated into their interests.
That’s the shift: you stop trying to persuade and start translating. Influence without authority isn’t persuasion - it’s translation.
Solo ✓ Partner ✓ About 15–20 minutes on your own before the conversation; a little longer with a rehearsal partner.
The time required is indicative and will depend on how well you already understand the other person.
There’s a short guide for running it - about 6–8 minutes to read. It is a downloadable PDF on this page.
Use it before a specific conversation where you need one person - or one team - to say yes to something you can’t simply instruct.
Use it whenever:
You’ve done it well when: your opening sentence is about what they care about, not what you need - and the ask ends in a genuine “so that you get ______” they’d actually value.
People act on their own motivations, not yours - so a request framed around your needs gives them little reason to move. Arguing the other side out loud forces you to discover what they actually care about, and rewriting the ask around that priority turns it from something you’re pushing into something they already hold. That’s translation, not persuasion - and it’s why it lands when logic alone doesn’t.
One real ask. A specific request you need to make of one person or team who doesn’t have to say yes. Bring a live one, not a hypothetical.
The worksheet (supplied). It guides you through the five stages: your ask, their priorities, the reasons they’d say no, what they gain by saying yes, and the rewritten ask.
A rehearsal partner - recommended. Their only job is to challenge whether you’re genuinely representing the other person’s thinking - to stop you inventing convenient motivations. Not required, but it sharpens the tool considerably.
Output / Takeaways
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.