Nice post, Chris.
DJ Adams


I like the JFDI method when boot strapping and this is where explicit permission comes into its own. People when I talk to them think that explicit permission is about them doing the thinking and always directing people to do things. The model I think of for explicit permission is where you frequently talk to your team and your management, through this discourse the things that need solved become apparent pretty easily. Then you as the engaged individual you are take it upon yourself to look at a problem initially and come back with an idea. That is then evaluated between you and others and progressed or abandoned, but it is explicitly permitted to continue.

If you do not maintain a regular discourse with your team and your management, then the idea of explicit permission becomes a top down driven thing and requires a lot of effort from others to ‘direct and let you do things’. We are, in my opinion, ahead of the curve in our use of collaboration tools like Slack — it enables us to talk a lot and work out what we think needs looked at and easily bootstrap a prototype or an idea to take internally and get our permission. Although there is still improvements we could make in the process etc.. but nothing is perfect.

Show your support

Clapping shows how much you appreciated Chris Kernaghan’s story.