Slashdot Mirror
Independent Developer Projects in the Workplace?
An anonymous reader asks: "My company wants to increase creativity and innovation, we our thinking of implementing a Google like policy of 20% of your time for independent projects but I can't find any details on how Google actually implements this. I am curious how they divvy up their time (1 day a week or 1 week a month)? How do you keep your real project from impacting it? At what point are the projects reviewed? Has anybody experienced other successful ways to stimulate creativity at their workplace?"
And then when they see the results they usually are quite happy.
If you have management that will actually allow you to do this, then it's real simple. The project manager will take projected timelines for your required projects, and add 20%. If you work efficiently, you'll end up with 20% of your time free to work on independent projects.
As for managing your own time, it's easy: The required projects always come first. If you slack on your required projects, or you badly underestimate your timeline, then you don't get any time to work on your independent stuff. On the other hand, if you bust your ass on your required project and end up ahead of schedule, then you may get more than 20% of your time to work on independent projects.
After that, the only difficult thing is to convince upper management that it's worthwhile to let people work on independent projects rather than just piling on more requirements when it looks like people are ahead of schedule. Depending on the upper management, this may range from easy to completely impossible to do.
Of course, if they're starting their own business on company time with company equipment, even if the activity is nominally "independent," they'll soon find out that their new side business is actually their employer's new side business.
If you do this, you need to make it crystal clear ahead of time who will own the results of their time spent noodling. Ordinarily, what you do with company resources on company time while an employee belongs to the company. The situation of a company formally giving employees "permission" to do whatever they want might muddy the waters legally, but it certainly muddies them in people's minds. Put the policy in writing and make people sign off on it.
Likewise, you need guidelines for what kinds of projects they can spend that 20% on; i.e. obvious dead-ends with no value to the company?, surfing the web?, etc.
http://alternatives.rzero.com/
It's the poor carpenter who blames his tools.
Some might say it's an equally poor carpenter who tries to get through the day with lousy tools.
Google has a bit of a specialized workforce--people who are creative and smart. I'm not sure how well it would work elsewhere, with people who are just punching the clock and holding no interest in work-related projects.
You're both right.
Bureaucracies are a way of slamming everybody to a common standard with reasonable reliability. It is a low, but predictable level of capability, and frankly, that has its uses. It is also easy to set up, and we seem to have some almost instinctual knowlegde of how to set them up.
They aren't optimal in all situations and they are overapplied, but they have their place. I for one wouldn't care to have a criminal justice system that wasn't a bureaucracy; predictability in a legal system is very important. Yes, even when it is wrong... then you at least know something needs to be fixed. To use a Slashdot-type example, at least we know the patent system is broken. If the rulings were more random (at all levels, from the Patent Office to judges), it would be even harder to tell... and ultimately we'd be even worse off and the first order of business would be to establish some consistency! (Consistency is one of those things that you can have contempt for because you're so used to it, you don't realize how important it is; "familiarity breeds contempt". I'd rather have the current system than a random one, and I hate the current system. For instance, a random system would give an even greater advantage to the deep-pocketed company; they could just keep re-trying various suits until the dice came up their way. The system as it is allows some of that, but you'd see even more in a random world.)
The big problem with Bureaucracies is that one of the biggest counter-indications for its use is "managing a creative enterprise", and that's where we hear most of the bitching about it. The problem here, ultimately, isn't truly Bureaucracy itself; it is working as it always does. It is the application of an inappropriate organization system; you always pay for that, no matter what. Unfortunately, all other forms are more expensive (thought of in the proper economic terms, even Anarchy is more expensive; the communication issues necessary to behave in a coordinated fashion become intractable), and like I said, we seem to have some sort of Bureaucracy instinct, so they also have to be learned explicitly, which is another barrier to their use.
But ultimately, "[large bureaucracies evolved] as a way of extracting valuable workproduct from extremely mediocre talent" and "they prevent work and progress which results in 'mediocre talent.'"... when misused, which they probably are a majority of the time.