6096 comments
2357 subscribers
6254 on Twitter
Subscribe! Feed reader E-mail

On the other side of the (virtual) desk

If I’m going to take over the world, I need to learn how to delegate. ;)

It’s a simple matter of mathematics. There are only so many hours in the day. I can’t achieve infinite productivity. Scaling up means figuring out how to work with others and how to delegate.

The traditional way of learning how to delegate involves being promoted to a management role, and that takes time and opportunity. With a little of the money I’ve set aside for my Crazy Idea Fund, I can experiment with delegation and personal outsourcing now. (Naturally, I delegate only non-IBM-confidential things.)

I interviewed almost 10 candidates out of more than 40 who applied. I’ve hired five people on a trial basis and assigned them a few tasks. In the process, I learned so much already! <laugh>

  • 80% of success is showing up. Half of the applicants didn’t notice the timezones on my invitations to pick an interview slot, even though I chose a tool that made it easy for them to translate the timezones to their own. And I’d already picked really early and really late times to make it easy for them to fit it into their schedules! Result: Many candidates had to reschedule interviews, and I lost time and sleep while waiting around. Making this better: Next time, I’ll assume people don’t know anything about timezones and I’ll point out the feature for changing timezones.
  • I’m a personal-development kind of manager. I’m pretty flexible in the tasks I assign, and I like finding out what people’s strengths and passions are so that I can find the intersection between my needs and their interests. I like how oDesk lets me get a glimpse of how people work, and I offer suggestions based on that. I also encourage people to take some time to reflect on how to make things better.
  • I tend to underestimate the time other people need. I find things on the Web really quickly because I’m used to opening a gazillion tabs and using web clipping tools like del.icio.us to store quick notes. I also speed-read like anything. Most people aren’t like that. I need to either scale up my time estimates or help people develop their skills.
  • A two-hour chunk is too short a time, particularly considering people are still getting started. I need to give people at least four hours to do a task. Maybe they’ll even get into a flow state.
  • I should start with highly-focused tasks or give people more time to become familiar with something. Web research might be difficult for VAs because they’re not yet familiar with the terminology, and I remember how it takes a bit of browsing around to get a sense of what things are called and where to look for information.
  • Trying people on a temporary basis is good. One of the advantages of working with small tasks and a structure like oDesk is that instead of betting the farm on one VA, I can try several VAs in parallel and then pick one who’s really the best fit. This is probably more expensive up front, but I learn a lot more because of the variety. After a month, perhaps I’ll decide which VA to work with going forward.

So the next thing that would make this VA experiment better would be to give people a four-hour task (perhaps building on what they’ve already done), and then continue with those who can keep up. I can also reevaluate my budget for the experiment, maybe add some more so that I can give people longer tasks and get a better sense of how people work, and then go from there. I think it’s worth continuing to invest in learning how to delegate, and it would be awesome to eventually build a support structure that can help me scale.

I suspect that after a short trial, I won’t find anyone whose skills will blow me away–but that goes back to what I’ve reflected on before, with employers who expect that people will have all the necessary skills right off the bat.

Yes, some people will figure out what they want to learn and invest time in learning those things. It would be awesome if I come across someone like that – but then I would want them to do more in life than handle other people’s web research and calendars! ;) So in the long run, I think it makes sense for me to invest in improving people’s skills.

Managers and companies sometimes complain that the people they invest in end up moving on. It’s okay if people “graduate” from working with me and go on to do other things. That’d be terrific, and it would give me even more return on my effort! In the meantime, the training materials I build to help people learn how to work can help the next person, and the next person, and so on. In fact, having more newbies go through the system would be great for improving it.

Writing this blog post seems to have fleshed out my reasons for doing this experiment, and what I can do with it… Can’t wait to learn even more!

Short URL: http://sachachua.com/blog/p/5799
  • http://coevolving.com David Ing

    Of all of the skills to be developed, I think that it’s most important to learn to delegate up, rather than delegating down.

    There are some people who think that management is overhead. From a systems perspective, though, they have responsibility for a whole (team), and an individual is just one part. One motivation for collaboration is that activities may or may not be properly balancing the strengths (and availability) of individuals towards a collective task. The leader needs to play the resource investigator role (in the Belbin profiles).

    If you are your own resource investigator, you’ll need to figure out the roles that you want others to play. In particular, if you’re stronger in completer finisher skills than your delegatee, disappointment will ensue.

    In a knowledge economy and with creative class work, I think that delegation needs to be rethought. While I appreciate that the number of hours in a day is limited, I’m much more interested in collaboration than I am in delegation. I like to work with people who know their strengths, competences and deficiencies, and who are open to sharing their limits. Thus, I prefer to work with colleagues who have the potential of developing as friends, rather than having efficient and job-specific contracting relationships. The details will work themselves out.

    P.S. I doubt that you can (or should) delegate blogging.

  • http://rubyku.com Ruby Ku

    really looking forward to a post where you write about how you manage to read so fast! :)

On This Day...

  • 2013: Weekly review: Week ending February 22, 2013 — Blog posts Weekly review: Week ending February 15, 2013 Business experience report: Passing my first annual resolutions Transcript of my [...]
  • 2012: Experience report: Opening the RBC Small Business eAccount — Having a business bank account is good for separating business and personal expenses. Reconciling your books is easier when you [...]
  • 2011: Posted revised “Remote Presentations That Rock” presentation — Next week, I’m giving Remote Presentations That Rock in person at IBM 3600 Steeles Avenue on Monday. I decided to [...]
  • 2010: Winter — This winter feels a lot milder and happier than the others I’ve been through. A large part of that comes [...]
  • 2008: Weekly review – Week ending February 24
  • 2006: Had a blast! — I went up to IBM Cambridge today, and it was absolutely fantastic. I’m not sure if I can talk about what [...]
  • 2004: Apache James — JM Ibanez suggested looking at Apache James and writing a mailet. Nifty idea, if I can get my mind around it! (I [...]
  • 2004: SocialNetworkBot — This is where all the magic happens. Starting up the app for every arriving message is probably a bad idea. Better [...]
  • 2004: SocialNetworkBot — This is where all the magic happens. Starting up the app for every arriving message is probably a bad idea. Better [...]
  • 2004: Social network analysis — http://www.jibble.org/piespy/ I want to run something like this on the PLUG mailing lists. I can reuse their spring model and then build [...]
  • 2004: Common networking errors — Due 2004.02.23 11:59:59 PM: Source code and detailed notes on - changes made - problems encountered - solutions tried/found - outstanding problems - plans for [...]
  • 2004: Sample ArrayList code — Here’s sample code for ArrayLists, which is a Java class that can store any kind of object in an array that [...]
  • 2004: Sample ArrayList code — Here’s sample code for ArrayLists, which is a Java class that can store any kind of object in an array that [...]
  • 2004: Nvu, a WYSIWYG HTML editor for Linux — http://www.nvu.com/index.html
  • 2004: planner.el broken up into lots of little files — It should compile cleanly under Emacs 21.3 (CVS). I’m still trying to figure out how to install the fsf-compat package under [...]
  • 2004: Social networking diagram — Should be fun to run this on a mailing list, using the References: tag… - http://www.jibble.org/piespy - http://www.daimi.au.dk/~terryp/pics/emacs-current.png
  • 2003: done with highlighting my readings — Whew!
  • 2003: emacspeak and IRC — linux — I am beginning to realize just how wonderful speech is. I’ve added dtk-speak to erc-insert-pre-hook, and I can listen to #linuxhelp [...]
  • 2003: linux printing site — http://www.linuxprinting.com, if I forget

Get the highlights as a PDF!

Stories from my Twenties: Highlights from a Decade of Blogging

Free sample!