How do I give my team permission to just do it?

Question

Accepted Answer

Say explicitly which small, low-risk fixes need no approval, set a modest spend limit people can commit themselves, and protect anyone whose quick fix misfires. Chapter 4 of the book warns that burying easy wins under approval layers kills the Just Do It pathway, and with it the team's belief that it is trusted.

The Just Do It pathway in Chapter 4 only works if people believe they are allowed to use it. A JDI is the kind of fix anyone can see: the fault is plain, the remedy plainer, and little breaks if you get it wrong: the typo on the form, the phone number wrong on the website, the equipment sitting in the wrong place. The book's instruction to leaders is blunt: do not bury these wins under layers of bureaucracy and approval processes.

Permission has to be specific to be believed. Name the boundaries out loud: the kind of change people may make without asking, the modest spend they may commit, and the point at which they should check first because other teams are affected. Vague encouragement to be empowered, with every real decision still routed to you, teaches the opposite lesson within a month.

Then protect the first attempts. Someone will just-do something that turns out badly. If that person is punished, the pathway closes for everyone watching. Treat a failed JDI the way the book treats a PDCA miss: as learning, reviewed honestly, without blame. The message you are building is that this organisation trusts the judgement of the people closest to the work.

Why it matters is momentum. JDIs are the Do First quadrant of the priority matrix made real. A steady run of small, visible fixes, made by the team itself, is the fastest evidence a sceptical organisation gets that improvement is something it does, not something done to it.

How do I give my team permission to just do it?

Related questions