A couple of years ago I outlined an idea for the staff at Education Technology Services that would allow for mini sabbaticals. The idea was met with lots of nodding and lots of questions — it was fairly simple … you share an idea and how much time you need to work on it and I figure out a way to turn you lose with it. The only caveats were that it couldn’t be more than a week and you had to come back with a product to share. Lots of people threatened to actually take me up on the offer, but in the end exactly zero people did.
I always wondered why. I still don’t know. Maybe it is time to dust off the idea?  I was reminded about it after reading, NPR tries something new: A day to let managers step away and developers play.  I really wonder what would happen if we twisted it so it wasn’t about some sort of structured approach and instead something more like what NPR is doing?
NPR is experimenting with something called “Serendipity Day,†wherein everyone on the technology side abandons their day jobs to work on…whatever they want. Bugs that need squashing, scratches that need itching — the ideas that never get to the top of a to-do list. The managers step back, available only if the workers need anything. (I need a designer, I need a room, I need a bagel.) The only rule: In the end, you have to share your work.
“It turns out that that one day of pure, undiluted autonomy has led to a whole array of fixes for existing software, a whole array of ideas for new products, that otherwise had never emerged,†Pink says in the talk. He argues that motivation derives from autonomy, mastery, and purpose: the desire to control one’s own destiny, to get better at something, and to serve a greater good.
Clearly we’d have to do some planning, just as NPR has done, but I wonder what kind of participation I would see in my own organization. Seriously, it is a great idea and I wonder if I’d have any takers?
This post also appears at my PSU Blog. Sorry for any multiple linking.