Do a Google Image search for "atari breakout"
images.google.com
images.google.com
Damn you Google!
I wonder Google came up with that list.
What makes me sad about this is how this kind of stuff is perceived by the rest of the community. People seem to follow the cargo cult of "Google has 20% time, so should we", thinking that it's the 20% time that makes Google special. I think copying this behavior until you are flush with cash is dangerous. I tried to implement it with the previous team I ran and it was more or less a disaster. It became an entitlement which you couldn't take away, but did not produce any direct or even indirect positive results no matter how we spun it. Productivity actually suffered as a result, while the 20% projects were completely unusable.
Has any startup been able to get away with this kind of thing, and if so how did you do it?
Edit: I should add that my previous team was a mess on many levels. While we had brilliant individuals, getting the company to move in lockstep in one direction was close to impossible, so there are many confounding factors to my experience. Perhaps a happy team that hadn't been terrorized by the upper management for a year and a half would have done better.
http://www.codinghorror.com/blog/2012/08/today-is-goof-off-a...
This gets tricky with companies that are no longer startups, but are not the 800 lb gorilla in their space either. Do you derive more efficiency from fostering X% time, or by getting your team to focus on the problem at hand?
I suppose that in the end, if your team is unhappy with the overall direction of your company, throwing them an occasional carrot will not fix things. You need to actually fix the underlying problem.
Messing around with a new framework or some prototype in your current language of choice means that you won't be (or won't have to) trying some new stuff on a production-class project. As an individual it is a great opportunity to hone your skills and knowledge, and help find the fun again in what could otherwise be a bland job.
This is actually iteration zero of a project, dedicated not to hopeful production of worthwhile deliverables, but production of the minds that will make (other) projects happen. Because when you will start working on iteration one of a new project, a new feature, then it is too late to mess around.
It just happens that sometimes great things could come out, but they're a statistical oddity.
http://blog.rescuetime.com/2010/05/24/the-tragic-cost-of-goo...
previous previous discussion https://news.ycombinator.com/item?id=5701553
If intentional, any specific significance?