Live data from Hacker News

Measure results, not hours

mobile.nytimes.com

41–50 of 84 posts

Re: Measure results, not hours

#41
post #20

"committed" "dedicated" "hard worker" None of these address intelligence nor even competence - and I think it is a mistake to assume a good manager wouldn't realize that. If a star performer showed up late, left early and never arrived to a meeting on time but they were doing amazing work, they'd be given a lot of leeway to do that - again, by a good manager. That is how sales works. Top salesmen do whatever they wan…

Being late for meetings is incompatible with doing good work. Either you are interfering with other people's work by stiffing them when they need to talk to you, or you are interrupting your productivity by showing up at all.

10x engineers don't do it on short hours. They do it by working harder in an environment where everyone is smart. Cf Claude Shannon ("achievement is exponential, working 10% longer has a compounding effect, like interest in a bank account") or Randy Pausch ("if you want me to tell you the secret of my success, call me any Friday night at my office")

Re: Measure results, not hours

#42
post #12

Earlier quoted context omitted.

Private schools are mostly the same structurally, they just have better tracking/pace since class sizes are smaller, and they can exclude disruptive students.

!!! Tracking, pace, small class sizes, and excluding disruptive students makes ALL the difference. It's the difference between a bespoke education delivered by an excellent teacher, and a shit cookie cutter education delivered by a scantron machine.

I don't disagree with you. Buy private shools aren't bespoke tutoring in the tradition of the European aristocracy or student-driven explorations of the world, they are the same lecture/ work/ small project/ test structure of public schools.

Re: Measure results, not hours

#43
If I got the projects assigned to me done in 10 hours, I would just be assigned more projects instead of being allowed to take the rest of the week off. That seems to be the culture of my company: productivity is punished with more work, rather than rewarded with extra time off. My boss jokes about it all the time by saying "no good deed goes unpunished around here" but he doesn't realize that it's not a joke. It's reality. :(

Re: Measure results, not hours

#44
I completely agree with this. Measuring productivity solely by hours in front of a screen is completely useless.

On the other hand, tracking hours can be really benificial too, if done correctly. I love using DeskTime.com for personal use (for company use it seems counterproductive) since it lets me easily track how much time I've spent on productive apps/web sites compared to unproductive apps/web sites.

Yesterday I had a great work day for example, I spent 14 hours in front of the computer screen. 11 hours of those were spent in productive apps/websites, like my text editor, FTP, terminal, API-documentation sites, CRM, admin backend etc and 1h 30m in unproductive apps/websites like Hacker News and Reddit.com.

I got quite a lot done, so I was really satisfied with my day. On the other hand I spent over 3 hours trying to fix what turned out to be a missing comma in a configuration file. If I had spotted the error faster I could have spent more than 3 hours less time working, while still being just as productive. If I had more experience with the things I did yesterday I could probably have done as much in half the time.

Just goes to show that even "productive hours" isn't the most important thing, the only thing that matters in the end is the results.

Re: Measure results, not hours

#45
Speaking for myself, I'm most productive when I work roughly a 3 day week, with 4 days to chill and goof off. So I do that (when customer stuff and my travel schedule allows), and I hope that my employees who feel similarly would do the same. Sort of the opposite of staying late to set an example.

Re: Measure results, not hours

#46

I completely agree with this. Measuring productivity solely by hours in front of a screen is completely useless. On the other hand, tracking hours can be really benificial too, if done correctly. I love using DeskTime.com for personal use (for company use it seems counterproductive) since it lets me easily track how much time I've spent on productive apps/web sites compared to unproductive apps/web sites. Yesterday I…

You might find the Personal Software Process to be of interest.

Re: Measure results, not hours

#47
post #6

The hourly rate thing has always bothered me. At my internship at Bloomberg the maximum amount of billable hours per week was 40 and usually they'd expect you to put in 8 hours a day. More often than not, I'd finish an assigned task before the day or week was through or I'd be 'direction blocked' where I would be waiting for approval in a design/architecture decision from my mentor or manager while they were busy wit…

I'm a freelancer and, from time to time, my billable hours come to a screeching halt when I can't get the client to tell me what they want done next.

It's a risk of the model. Part of why freelancers cost more per hour.

Re: Measure results, not hours

#48

Carol Dweck says we should praise effort, not success, if we want people to love challenges and practice persistence. So, praise effort, measure results, but don't worry about time spent at a desk.

This is true for teaching children the value of persistence and effort.

In a work environment, however, it teaches everyone that all that is valued is wasteful heroics.

Re: Measure results, not hours

#49
post #42

Earlier quoted context omitted.

!!! Tracking, pace, small class sizes, and excluding disruptive students makes ALL the difference. It's the difference between a bespoke education delivered by an excellent teacher, and a shit cookie cutter education delivered by a scantron machine.

I don't disagree with you. Buy private shools aren't bespoke tutoring in the tradition of the European aristocracy or student-driven explorations of the world, they are the same lecture/ work/ small project/ test structure of public schools.

The extra teaching resources are there and available for students that want or need them. Most students just care not to.

Re: Measure results, not hours

#50

How do you square this sort of mindset with the well-known demands of entrepreneurship? In other words, if it's possible to do great work in short amounts of time, why do most successful entrepreneurs end up working very long hours to make their companies succeed? If it's possible to check out at 5pm M-F and still excel, why do investors look for the highest possible levels of commitment from the founders in whom the…

How do you square this sort of mindset with the well-known demands of entrepreneurship?

Because the 'well-known demands' are mostly socially constructed myths rather than reality. Because people are really bad at tracking stuff-done and find tracking hours-worked and looking at stuff-to-do much easier to think about. Because people a really fucking awful at figuring out how productive they are.

I have been a team coach multiple times where I have demonstrated by, weirdly, actually tracking the amount of work done that teams working fewer hours were producing more work. The amount of push back from these sorts of results from management and the team is incredible.

People know that if they only stayed a bit later they would get more done despite lots of evidence, by our tracking stories completed, bug reports, user satisfaction, etc. all went down the more hours people worked.

Tired people make mistakes. Tired people work slowly. You can be tired without 'feeling' tired. In anything but the very short term (and I'm talking days, maybe a week or two tops) trying to do hard intellectual, creative work for more than 30-40 hours a week will make you slower overall - not faster.

Hell - Ford promoted the 40 hour week as the maximum productivity point for physical labour on a production line... and we somehow imagine that working 60 hour weeks is going to make us do more.

People still seem to conceptualise 60 hour weeks as 40 normal hours + 20 extra. In fact it's 60 hours of being knackered where you're probably being half as productive as you would be if you were fully rested - but you're too damn tired to realise it.

Post reply on HN