Former MySQL CEO Mårten Mickos Talks About Managing Remote Workers (Video)
Millions of pixels have been used to talk about Yahoo! CEO Marissa Mayer's decision to ban telecommuting and her reasons for doing it. Today's interviewee, Mårten Mickos, built MySQL AB into a billion-dollar company with 70% of its workers, all over the world, telecommuting instead of working in offices. Now he's CEO of another young open source company, Eucalyptus, and is following a similar hiring pattern. Mårten says (toward the end of the video/transcript) that he believes people working out of their homes is entirely natural; that this is how things were done for thousands of years before the industrial revolution.
All you need is a method to accurately measure productivity.
These companies did it on purpose and planned for it, while it sounds like it just sorta "happened" at Yahoo, with management neither having a plan for how to manage it nor (apparently) really paying any attention at all to what remote workers were doing and how they were doing it.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
If you have a cool product, interesting things to do and hire interested people, you will have good employees.
Many technical people work in the field because they enjoy it, how many people work on FOSS in their spare time anyway?
Working on new, interesting, challenging things is fun! Maintaining 'legacy' stuff, not as fun. No disrespect to Yahoo but Flicker, Yahoo Mail, YUI, OMG! (please), for me it would be hard to be excited about maintaining these.
Additionally, working in a smaller company where one person can really help shape things is huge, being just another worker bee in a huge corporate environment can be depressing. (especially one with a declining public image)
Obviously, just my opinion.
What do you use for measuring "productivity"?
Lines of code? My happiest work days are when I end up removing more code than I put in. Also, this is really easy to game.
Bugs fixed? I usually end up working on the really nasty bugs...intermittent, only occur in customer sites, and under no circumstances can you shut down the system to debug it. Some bugs take weeks or months to track down.
Hours worked? Pointless, doesn't track if you're actually being useful during those hours.
While it's easy to measure productivity if you're making widgets, its *really hard* to measure productivity if you're doing creative stuff.