Hacker News new | ask | show | jobs
by dacracot 2020 days ago
I'll caveat my remarks first by admitting that I nearly completely ignorant of Google's 20% policy, but since it was widely advertised, my workplace made a similar statement that one half of each Friday should be dedicated to learning something new to benefit the team and thereby our careers. All I could ever think of after this proclamation was that I was to do as I was told 85% of the time and innovate 15%. As a developer, I offended that my innovations are devalued to a time slot. I was under the impression that I was expected to innovate continuously within the confines of the deadlines given. My two cents.
3 comments

Did you consider that maybe setting Friday up for everyone was to allow everyone who wanted to participate to work together without scheduling challenges or conflicts with their hired roles/team obligations?

This is like saying a Hackathon is devaluing creativity because it occurs at a scheduled time...

I get your point, but without paragraphs of explanation, I doubt I could persuade you. I can say this... It was meant as a solitary exercise, not as a group.
Bu then, if everyone stops to work alone at different times, you have a problem scheduling work things... I.e: if you want to take Tuesday afternoon to do your things, but then they need you for meetings/work on something else.
Don't you innovate during the other 85%? Likewise, couldn't you spend that remaining 15% doing rote, uninteresting work of your choosing?

To me, the concept of 20% time is the freedom to choose what you're working on, not how you should be working.

oh i love this! unintended consequences always arise - this is one of those reasons why I asked the question. thank you for sharing how this felt.