#246: Permission Tunnel, Permission Structure & the Forgiveness/Permission Principle
3 Ideas in 2 Minutes on Getting Permission
I. Permission Tunnel
In IT, a Permission Tunnel is like a “Trojan horse” for access rights. Instead of asking for high-level admin power that triggers alarms, an attacker secures tiny, low-risk permissions: “I just need access to that printer folder. No big deal.” Once that “tunnel” is approved and trusted, it’s used as a bridge to sneak through more dangerous commands or harvest sensitive data.
In daily life, you see this in the shape of the Foot-In-The-Door Technique. A colleague might ask to be “just cc’d” on a minor project for “visibility”. No big deal. But they’ve built a legitimate pathway into your workflow. Later, they use that established presence for nefarious purposes. Weigh in on a major decision. Claim credit for it. Expand their influence. Take over your project. Drive you out of the job. Move into your house…
You get the point. But don’t fall for the Deception Dilemma. Not everyone asking to be cc’d in an Email is after your job. I think.
II. Permission Structure
A Permission Structure is a way of allowing people to change their minds without losing face. People often hesitate not because they don’t want something, but because they’re unsure if it’s “okay” to go for it. A permission structure removes that friction by signalling that the behaviour fits the situation.
In practice, it’s a matter of Framing. You give someone a reason that legitimises the action. This could be timing, norms or shared expectations:
Many people in your situation are now buying a second Lamborghini.
I once thought like you. But then I learned that, with all that new tech, you can drive one and have the other drive itself.
Giving people a Permission Structure reduces perceived risk and makes the decision feel natural instead of pushy or awkward. As long as you keep the reasons practical and realistic.
III. Forgiveness/Permission Principle
It’s often easier to ask for forgiveness than to ask for permission.
—Grace Hopper
I’m sure you’ve run into this idea attributed to computer programming pioneer Grace Hopper. Whether at work or in everyday life, instead of waiting around for approval, you take action and deal with the consequences if they come. It’s less about being reckless and more about not getting stuck in endless hesitation.
Why does it work? Asking for permission creates friction. People default to caution, delay, or outright “no”. But once something is already done (especially if it works), others are much more likely to accept it or go along with it. Had you asked first and got a “no”, this opportunity would have been gone.
Of course, this only makes sense when the downside is limited. If the cost of being wrong is small and reversible, acting first can save a lot of time. But when the stakes are high, irreversible and could damage trust, asking first is probably the smarter move. 🐘
Have a great week,
Chris
themindcollection.com