Posts Tagged‘productivity’

The Burden of Efficency.

Today’s workplaces value the appearance of being productive rather than actual productivity. This seemingly nonsensical behaviour stems from the inability of many companies to accurately define performance metrics or other assessable criteria on which to judge someone’s productivity and thus they rely on the appearance of someone being busy as a judge instead. This is what leads many to engage in activities which, on the surface, make you appear busy but are either outright wasteful or horribly inefficient. As someone who has spent the vast majority of his professional career working himself out of a job I’ve found this behaviour particularly abhorrent, especially when it comes back around to bite me.

bigstock-efficiency-in-the-work-place-a-15768824

You see for anyone who is highly effective at their job there’s a tendency to get through your work faster than what would be usually expected and, consequently, they will often seek additional tasks to fill the rest of their working week. The trouble is that once their baseline job functions have been satisfied the tasks remaining are usually the low priority ones that either don’t really require the attention of a highly effective worker or won’t produce any meaningful outputs. Indeed I found this out the hard way many times as my investment in automating many of my routine tasks would often see me doing mundane things like updating documentation templates or reorganising file structures. Such tasks are a killer for highly effective workers and new research from Duke University, University of Georgia, and University of Colorado finally adds some scientific evidence to this.

First the researchers looked at how people would assign tasks to different workers based on a single attribute: self control. Predictably the participants in the study assigned more work to those with better self control with the rationale that they would be more effective at completing the work. Whilst that might not be a revolutionary piece of research it sets the foundation for the next hypothesis: does that additional work burden said efficient worker? Because for a work environment where all are rewarded at the same level doing more work for the same benefit is a burden to efficient workers and that’s what the second piece of research sought to find out.

In a study of 400 employees it was found that effective employees were not only aware of the additional burden placed on them they often felt that their boss and fellow employees weren’t aware of the burden that it placed on them. The end result of this study was to conclude that efficient workers should not be rewarded with additional work but instead with opportunities or better compensation. Engaging in the other behaviour instead encourages everyone to do the least amount of work required to fulfill their duties as there’s no incentive to be efficient nor productive beyond that. Again this might seem like an obvious conclusion but the current zeitgeist of today’s working environments still runs contrary to this conclusion.

I do feel incredibly lucky to be working for a company which adheres to this ethos of rewarding efficiency and actual productivity rather than the appearance of being busy. However it took me 7 years and almost as many jobs to finally come across a company that functions in this regard so the everyman’s workplace still has a long way to go. Whilst research like this might not have much of an effect on changing the general workplace environment hopefully the efficient workers of the world can find solace in the fact that science is on their side.

Or, at the very least, realise that they should work that system to their advantage.

The Idiocy of Idolizing Over-Time.

My fellow IT workers will likely be familiar with the non-standard hours our work can require us to keep. Since we’re an essential service any interruption means that other people are unable to work so we’re often left with no choice to continue working long after everyone has left. Thankfully I moved out of doing that routinely long ago however I’ve still had my fair share of long weeks, weekend work and the occasional all-nighter in order to make sure a job was done properly. I’ll never work more hours simply for the sake of it though as I know my productivity rapidly drops off after a certain point, meaning the extra hours aren’t particularly effective. Still though there seems to be something of a worship culture around those who work long hours, even if the results of doing so are questionable.

Stressed woman in office

My stance has always been that everyone should be able to complete their work in the standard number of work week hours and if goals aren’t being met it’s a fault of resourcing, not the amount of effort being put in. Too often though I’ve seen people take it upon themselves to make up for these shortcomings by working longer hours which feeds into a terrible cycle from which most projects can’t recover. It often starts with individuals accommodating bursts of work which falsely set the expectation that such peaks can be routinely accommodated. Sure it’s only a couple extra hours here or there but when each member of a team of 20 does that you’re already a resource behind and it doesn’t take much to quickly escalate from there.

The problem, I feel, stems from the association that hours worked is equal to the amount of contribution. In all cases this is simply not true as many studies have shown that, even with routine tasks with readily quantifiable output, your efficiency degrades over time. Indeed my highly unscientific observations, coupled with a little bit of online research, shows that working past the 8 hour mark per day will likely lead to heavy declines in productivity over time. I’ve certainly noticed that among people I’ve worked alongside during 12+ hour days as the pace of work rapidly declines and complex issues take far longer to solve than they would have at the beginning of the day.

Thus the solution is two fold: we need to stop idolizing people who put in “long hours” and be steadfast when it comes to taking on additional work. Stopping the idolization means that those who choose to work longer hours, for whatever reasons, are no longer used as a standard by which everyone else is judged. It doesn’t do anyone any good to hold everyone to standards like that and will likely lead to high levels of burnout and turnover. Putting constraints around additional work means that no one should have to work more than they need to and should highlight resourcing issues long before it becomes a problem that can’t be handled.

I’m fortunate to work for a company that values results over time invested and it’s been showing in the results that our people have been able to deliver. As someone who’d worked in organisations where the culture valued hours and the appearance being busy over everything else it’s been extremely refreshing, validating my long held beliefs about work efficiency and productivity. Working alongside other agencies that don’t have this culture has provided a stark reminder of just how idiotic the idolization of overtime is and why I’ll likely be sticking around this place for a while to come.

Doing Twitter Wrong = Doing Producivity Right.

While I’ve been a user of Twitter for well over a year I didn’t really get ituntil about 6 months ago. Initially I found it just to be a curiosity as its open API provided integration opportunities between applications that would otherwise not talk to each other (namely this blog and Facebook). Lately however I’ve actually been using it for what it was originally intended, I.E. blasting seemingly inane crap onto the Internet in close to real time. That hasn’t detracted from its real value as a communication platform however and I now find it invaluable for keeping up to date on people and things that I find interesting. I guess you could say that I use it mostly as a discovery tool.

Still this hasn’t stopped people from telling me that I’m still doing it wrong. You see, whilst I understand what I’m about to say is rather cliche, I’m actually quite a busy man. Usually the only times I have free to check up on my Twitter feed are on the trip into work and the time I spend waiting around to pick up my beautiful wife after work. Whilst I feel its ok to reply or retweet something many hours after its original posting time it seems my more active Twitter buddies are rather perturbed by my actions. I’ve also missed quite a few tweets from people who were looking to catch up with me because of this, but I’ve found the alternative to be rather…destructive.

Last weekend was one of the first in a while where I made some solid progress on Geon (which is now a codename thanks to every reasonable domain being taken). The topic of my flaunting of the accepted Twitter etiquette came up at a dinner I had had with some of my fellow twitterers the night before, so I decided to try their way of doing things for a day. In the morning I turned on my pc, loaded up Visual Studio and Firefox and kept the Twitter homepage open on one monitor whilst I bashed away at my code on the other. Whilst things were off to a great start a worrying trend started to appear.

That “X new tweets” button was the worst thing for my productivity since YouTube.

You see whenever something requires my attention, like say a new email or something like that, I always feel compelled to action it as soon as I can. If I’m doing some long task and another quick task comes my way I’ll usually put the larger task on hold to knock the smaller one out of the way so I don’t have to remember to do it later. It appears that this same behaviour is triggered by the new tweets alert popping up on the Twitter homepage as I usually only have maybe a dozen or so tweets appear every 5 minutes or so. Still because of this almost obsessive compulsive habit I have I was compelled to look them over to ensure that there was nothing in there that I might want to check out or might aid my current endeavours.

Any programmer will tell you that an interruption whilst you’re coding is a sure fire way to delay any useful work for at least 15 minutes. It’s not so much that we can’t work without distraction more that when you’re right in the middle of a problem or implementing an algorithm an interruption breaks your immersion. It’s akin to trying to find the page you were on in a book that the bookmark fell out of, you know where you were up to but you’re not going to land on that page instantly. Using Twitter in real time is devastating to this kind of work and soon after I begun the experiment it ended so that I could continue making progress.

The argument can be made that there’s a happy middle ground between the two ways I used Twitter and I’ll agree with that. The realtime option is devastating to real work and long times between uses renders the core ideal of Twitter meaningless. Still there are times when being on it constantly are worth it like my real time stream of Eurovision commentary and events that I’m interested in yet can not attend. In the end however whenever I’m trying to get something done Twitter will have to take the back seat, at least until I need to add value to what I’m doing.