I could say we're doing 100% time in my company. We don't have offices or office hours, and no micro-management. Myself and the other coder/designer do what we do because we want to, and because we're damn proud of designing the best damn product (and making a good bit of money at it).<p>I've found, in practice, that I do my best work when doing what I really want to do. So, being the project manager as well as a programmer, I've set up the management structure so that we commit to doing 6 user-visible items per week (split into 3 mini-iterations, times 2 people). Our business guy (who happens to be the CEO, sort of.. but we don't like titles) is happy, since he get (at least) six new things to show users and get feedback on each week. We're happy, since we get to spend our time working on the bits that we really care about, or that we feel need attention, whether visible or not.<p>In practice, I work extremely hard on this business, but not because of working hours. As an example, on Saturday I spent about half a day doing a fairly significant refactoring of a part of our Flex code. This morning I spent a few hours building a connection status monitor. All of these are tasks that could take forever if they were "official" tasks in a more structured environment, but because I want to do them they take comparatively little time, and are literally given birth to in a rush of caffeine and enthusiasm.<p>Anyway, boiling it down to a point: if you've done your hiring (for lack of a better word) right and motivated your team well, you can just set things up so they'll spend 100% of their time doing whatever the hell they want, and you'll get brilliant results. The minute you find yourself counting hours, you've failed miserably.