What is a permission trap?
A permission trap is the habit of asking permission for things you don't need permission for: 'Can I share something?' 'Is it okay if I sit here?' In the book, each request builds a gate where there was an open road and hands someone else the key. The fix is plain statements instead of requests.
A real example
You, writing to your manager before a planning meeting.
What's being used on you
- 1The permission requestCipher 13 The Permission Trap. 'Would it be okay if I shared' asks for approval nobody required. Before you asked, nothing stopped you from sharing your thoughts. Now Dave has been handed the role of gatekeeper, and he is deciding whether you may speak.
- 2The hedgeCipher 13 The Permission Trap. 'Kind of wondering' and 'only if you have time' are what the book calls micro-permission requests. Each one apologizes in advance for having an opinion. Strip them out and the idea has to stand on its own, which is where it belongs.
- 3Asking instead of tellingCipher 16 The Status Switch. The Status Switch contrasts people who ask 'What's the plan here?' with people who describe the situation and invite a response. The example hands Dave the entire decision. A statement like 'I have two points on the rollout' lets him respond instead.
What most people do
People assume softening every request is polite, and sometimes it is. The trouble is that the habit never switches off. You use it with people who have claimed no authority over you, and on things that were yours to do anyway. You come across as unsure, and your actual idea arrives with an apology stapled to it. Overcorrecting into demands fails too: the goal is calm statements, not pressure. Think of how you'd speak to a peer you respect. You state your point, and you leave room for theirs.
Three replies that hold your ground
Hi Dave, I have a couple of thoughts on the rollout. Do you have ten minutes before Thursday's meeting?
Dave, I have two points on the rollout. I'll send them over today so you have them before Thursday.
Dave, I see a risk in the rollout timeline and I want it on the agenda Thursday. Here is the short version: [your point in one sentence].
How to handle it
- Catch the phrase: 'Can I,' 'Is it okay if,' 'Do you mind if.'
- Ask yourself whether this person actually controls the thing. If not, drop the question.
- Turn the question into a statement: 'I want to share something.'
- Cut the hedges: 'kind of,' 'maybe,' 'I don't know if this is right, but.'
- Say it slowly and warmly. A calm statement is not a demand.
When it isn't manipulation
Asking permission is correct when someone really holds the say: their time, their budget, their space, their data, their consent. Asking a colleague if they have ten minutes is respect, not weakness. The test is simple: if they said no, would you actually stop? If yes, ask. If you would go ahead anyway, you were asking for show. The same goes for a stranger's chair or a friend's calendar: those are theirs, so ask. Your own idea in your own meeting is yours.
Got a message like this?
Paste it into Cipher Operator. It names the move, points to the cipher, and writes three replies. 3 free reads a day, no account.
Decode my message, freeQuestions
Is asking permission always a mistake?
No. Ask when the person truly controls the thing: their time, money, property, or consent. Skip the question when it is your own opinion, your own seat, or your own next step.
How do I stop doing it without sounding rude?
Say it as a statement in a warm tone. 'I'm going to sit here,' said with a smile, reads as comfortable, not rude. The book is clear that this is about framing and tone, not about ignoring other people's boundaries.
Does this apply to email and text too?
Yes. Written hedges are easy to spot: 'sorry to bother you,' 'just wondering,' 'if that's okay.' Read your message once before sending and delete every phrase that asks for approval you don't need.
Related ciphers
Cipher 16, The Status Switch. Cipher 11, The First Move. Cipher 25, The Power of No. Cipher 5, The Slow Blade.