Your written AI policy says, “Use caution.” (I mean, that is if you even have one....)
Your system says, “Sure, connect EVERYTHING!! YOLO! What could go wrong?”
This is the operational equivalent of putting Tobias Fünke in charge of subtlety.
On paper, everything looks responsible. In practice, the permissions are standing in the middle of the office painted blue, wearing denim cutoffs, and wondering why everyone suddenly looks concerned.
“People will often make better decisions if they are provided with better information, clearer feedback, and timely reminders.” — Richard Thaler and Cass Sunstein
Choice architecture can look like:
But, keep in mind that leaving every permission wide open is also choice architecture. It has the err of Tobias’ bad judgment of auditioning for the Blue Man Group after seeing one flyer.
When leadership leaves those questions unanswered, employees build their own policies from whatever buttons appear, something a coworker heard in March, and the deeply authoritative statement, “I think Kevin uses it.”
Kevin has now become the Chief AI Governance Officer. Kevin does not know this.
Tobias insists that he is fully dressed because the denim cutoffs never come off. Some organizations treat their AI policy the same way.
“People will eventually gravitate to the least demanding course of action.” — Daniel Kahneman
Some friction deserves to stay.
Those pauses give human judgment time to put on pants and enter the room.
The warning also needs to arrive before the damage, because a privacy message that appears after the shared drive has been connected has Mrs. Featherbottom energy: dramatic entrance, broken coffee table, very little improvement to household tidiness.
Damien’s video on the Gemini Privacy Hub and data settings shows the level where this work needs to happen.
We help businesses examine three layers together:
The fix may involve:
Next-Level AI Workshops can help your team understand the tools, data boundaries, and judgment calls.
Fractional COO/CTO support can connect those expectations to permissions, ownership, workflows, and business risk.
Tobias can keep the cutoffs. Everyone else gets clearer instructions.