Great post. Hours are bullshit because "measuring hours" is a proxy for results, and a bad one at that. At Highgroove, we're a ROWE -- a Results Only Work Envi

Great post. Hours are bullshit because "measuring hours" is a proxy for results, and a bad one at that. At Highgroove, we're a ROWE -- a Results Only Work Environment. We have no hours, and our vacation policy is two words: "Be Reasonable." This is actually a lot harder than having hours, because we have to define what the results are, together (and top-down for some). For githubbers, those results might be tangible things like: "Release 3 new Features a Week." or "Blog once a day." Without those tangible results (instead of just tracking hours), you risk the sludge from others who are able to get more work done in less time -- and alleviate the worry that even good workers have: "Am I working hard enough?" Good stuff! I'd be curious to hear how those "managers" you allude to are handling the "flexibility" you guys have in your next articles.