As we were leaving the apartment this morning Flo told the dog that we were going āto work.ā
Iāve spent weeks teaching him that work is something you do, not somewhere you go. We were going āto the office.ā
As we were leaving the apartment this morning Flo told the dog that we were going āto work.ā
Iāve spent weeks teaching him that work is something you do, not somewhere you go. We were going āto the office.ā
Traditional proclemations aside, you may have read an article or two earlier in the year saying that Google has killed it’s “20% time” policy.
If you’re unfamiliar and you don’t feel much like clicking the above link, 20% time is…
“…a well-known part of our philosophy here [at Google], enabling engineers to spend one day a week working on projects that aren’t necessarily in our job descriptions.”
It’s well publicised that 20% time has been a significant contributing factor in giving us some of the Google products that we know and love today, so I hope for that reason that these rumors aren’t true. Regardless of that though, 20% time does seem at odds with the way the modern world works.
I’ve blogged a couple of times about ROWE so I’ll do my best not to digress into a further soliloquy about its merits here, but suffice to say I don’t measure my work in terms of time anymore. Allotting 20% of my time to projects that aren’t necessarily in my job description would be nearly impossible for me – not necesarilly because my organization wouldn’t allow it, but because I don’t know that I could figure out what 20% of my time is.
I’ve never worked somewhere with a policy of 20% time similar to Google, but that’s irrelevant. ROWE offers me something much better. I’m essentially free to use my time however I wish as long as the work gets done, and for me “20% projects” areĀ absolutely a part of that.
Just because these 20% projects (as I’ll keep referring to them) aren’t right out of my job description doesn’t mean they aren’t work related, but they do offer me the freedom to try new things without fear of failure, and that leads to some great innovation (it leads to some failures and dead ends too, but that’s the point – it doesn’t matter).
I plan to blog some more about the gritty technical details in the not too distant future, but I’ve recently built a dashboard web-app on top of SharePoint using jQuery and SPServices. People love it, and it’s greatly increased my stock at work over the last few days. If my boss had come to me and asked me in a formal setting to develop this I don’t know if I’d have touched it. If it were a formal project from the start we’d have had to get IT to build it for us, probably at great expense. I, by contrast,Ā learned how to do this stuff as I went along, and when I started work on it I had no idea if I’d be able to bring things to a successful conclusion.
My hope for my organization as ROWE becomes more of a popularised concept and way of working is that it encourages and enables other people to try new things – filter out the noise, spend less time doing and more time thinking. It worked for me, and it can work for you too.
So, itās been a little over three months since I posted my original thoughts on ROWE, and with several of my colleagues away today at a ROWE learning session with Jody Thompson now seems like as good a time as any to follow up.
What ROWE means to each of us is a highly person thing ā and so it should be ā but during the past months I’ve developed a much clearer picture of what ROWE means to me. I wonāt bore you by documenting how I spend a typical day because the whole point is thatās a detail for each of us to figure out on our own, but I’ve settled into something of a routine that I think works best for me. I believe Iām more productive as a result. I didn’t feel stressed before so Iām not sure Iād say that ROWE has helped in that regard, but I would say that ROWE has helped me drive an internal focus on whatās really important ā I now do whatever it is thatās the highest priority for me in any given moment. If itās 10am on a Tuesday then thatās usually a work related task, but if it isn’t and itās more important to me to spend time with my girlfriend or take some me time and watch a movie then I donāt feel guilt about doing that either.
Most crucially (and unexpectedly to me) what ROWE has given me is increased confidence in myself and my approach to my work. Previously when I received an email asking me to help with something they believed to be āon fireā I would jump on it, probably to make myself look good, and I could end up filling my entire day with little items of that type. Now I stick to my own priorities and help with others when I have time to. This sounds like a bad thing and that I’ve made myself into less of a team player, but as it turns out that really doesn’t seem to be the case. I donāt mean that I stick stubbornly to the plan I formulated my day first thing that morning ā I allow my priorities to shift and I react to whatās going on around me ā but in my (admittedly still limited) new-found experience things that are āon fireā never turn out to be as important as they first appeared and taking some time to gather my thoughts before taking action almost always leads to a better approach to a problem anyway. In a nutshell, it turns out Iām most effective when I concentrate my efforts on big things that are important rather than small things of questionable priority. Of course this seems obvious when I articulate it in this way but for some reason it just wasn’t clear to me before I made a conscious effort to embrace the ROWE guideposts.
The largest contributing factor to the success of ROWE from my personal standpoint is by far the support of my leaders. Not only do they talk about supporting ROWE, but I see from their actions that this is true and, more than that, theyāre embracing the same methods of thinking about their work that I am.
The largest challenges represented by ROWE are, for me at least, still the technology ones. I’ve never wanted my organization to provide me with a cellphone, but now I find myself envious of those that have one because they can step away from their computers without cutting themselves off from the world of work. That being said, I’ve come up with the best solutions I can on my own ā I have lync on my personal phone, I’ve changed the settings on my voicemail so that I get an email alert to my personal phone if somebody leaves me a message and my outgoing message now advises and lets callers press 0 to try reaching me in a location independent way. I achieved this by getting a new phone number especially for the purpose from a third-party provider. When you call it my desk phone, cell phone and home phone all potentially ring simultaneously, and I can configure the exact behavior from a control panel online. I updated the phone number listed for me in the corporate directory to this new one. The ability to check my work email from wherever I happen to be is really the only thing missing.
And I still fall down at “every meeting is optional.” I get the concept, but it’s going to take quite some time for me to buy in to that one, I think.
Along with a few of my colleagues I’ve recently started reading āWhy Works Sucks and How to Fix It.ā Iām only a few chapters in, but I wanted to share my initial thoughts, get peopleās input, and also post something I can return to once I’ve learned more to see if/how my initial observations change.