Get out of your "shell" and exercise your people muscles for fun and profit

As programmers, we often have the luxury of focusing on interesting and challenging technical problems, without having to worry too much (depending on your work arrangement) about the external factors that make this kind of sheltered life possible. However, it turns out there are some big pluses to developing our people networking skills and getting out and meeting folks. This is especially true when we move out on our own (or become part of a very small team). These advantages include:

• More business,
  
• Unexpected opportunities,
  
• Great product ideas and directions, and
  
• Improved health and life satisfaction.
  

(There's a longer list here.) Most of these advantages stem from the basic ideas that 1) we humans thrive in a more deeply connected world, and 2) opportunities for new ideas, new projects, and additional work can come from surprising places, once you start putting energy into expanding your network. The down side? You may have to develop some new skills, you have to put in time and energy to meet folks, and you have to stay open to possibly unexpected opportunities (i.e., to be ready to say yes).


So how does one go about growing her network? I started with three books, which jump-started my efforts:

• Love Is the Killer App: How to Win Business and Influence Friends by Tim Sanders,
  
• Never Eat Alone: And Other Secrets to Success, One Relationship at a Time by Keith Ferrazzi and Tahl Raz, and
  
• How to Make People Like You in 90 Seconds or Less by Nicholas Boothman

Why these three? First, Sanders' book is inspirational, and encourages us to freely share our knowledge, our network, and our compassion. This can be hard for us, especially the knowledge bit, because as Susan Jeffers puts it (from Feel the Fear and Do It Anyway):

So much of what we learn in life comes to us with great difficultly. And, for some reason, we have a tendency to want to see others struggle as much as we did. Turn this around and begin giving others as much help as you can possibly give them.

As a programmer, I think of this book as how to look at others as partners in work and life, and how helping them ultimately helps me and my business.


In the second book, Ferrazzi and Raz teach us about the good kind of networking, i.e., the kind involving unselfish giving, not the kind in which I stand at the exhibit hall and pass out 300 business cards. Again, as geeks, this book shows us that networking is very powerful, and demonstrates how to get started.

Finally, Boothman's work gives us some crucial skills on establishing rapport with people in the early seconds of a relationship, which apparently matter quite a bit. It covers mysteries like eye contact, body mirroring, and asking open-ended questions when first meeting someone. As a technical type I found myself thinking "Where the hell was this book when I was in high school!?" Think of it as a social skills user manual.


Great. So given all that, how do we put this into practice? As with anything new, there will be trial and error, and - as with anything social - "error" can feel uncomfortable at first. One strategy I found useful was to start by being conscious of each personal interaction, and looking at these as little opportunities to get to know the other person.

For example, I used to interact with people only when necessary, and only for the minimal time needed to deal with the task at hand. Very much Just the Facts. Say I needed to talk with a user. I'd spent a few seconds in obligatory "How you doing?" mode, then jump right into the fray - "Which version of the JDK are you using?," "Is the server running?," etc. However, I now spend a little time asking about the person either before or after the technical stuff - things like how they like their jobs, where they live, what their passions or issues are, etc. While some folks are all business (can't help that!), most welcome the chance to talk about themselves. And guess what? That connection persists, both in my mind and theirs. (Early on I forgot to do this, so I called the person back, apologized for being so hasty, and asked to hear a bit about her life. She was fine with it.)

The bottom line? Brush up those social muscles, dust off your English (non-programming) language skills, and reboot yourself a bit. You never know what a connection with someone might bring, either to you or (better yet) to them.

Congratulations to Frank (Mr. "What's the next action") on his two year GTD anniversary!

Frank Meeuwsen, author of the terrific What's the next action GTD blog is reflecting on two years (!) of practicing GTD. Frank kindly invited me to share in his accomplishment - in my small way - by contributing some thoughts on the topic.

• I'm still relatively new to GTD: The first record I have (one of the nice things about keeping a detailed professional log - it's easy to look things up) are some references from January, 2005. But I started my implementation (I wrote about it in Actually getting things done with Getting Things Done! Surprises and learnings from my implementation) in May, so I've only been practicing a year and a half.
  
• Applying these ideas of self-management is a practice, and it takes time to make the changes stick. As George Leonard writes in his wonderful little book Mastery: The Keys to Success and Long-Term Fulfillment, mastering anything (be it a sport, writing, or painting) takes time and practice, and GTD is no different.
  
• Where am I on the belt scale? Somewhere between the last three, I suppose. Though for my clients I prefer my "operationalized" version found in GTD Workflow Assessment/Tips Checklist.
  
• My technology hasn't changed much - I'm still paper-based, having started with the Hipster PDA then moved to a traditional paper planner with tabs for contexts (see Matt's Idea Blog: Fare thee well Hipster PDA - I barely knew ye).
  
• I still have some next actions that sit around longer than I'd like, becoming a bit smelly.
  
• I still don't do the weekly review every week.
  
• I still have anxiety about some of my actions - but I still do them!
  
• I use the "turnkey" contexts, partly because as I'm explaining this to others it helps to
  
• Regarding my technical work, I haven't yet integrated extreme programming and GTD. There's a big opportunity there, I believe. (You might enjoy Robert Peake's two articles on GTD and programming, and GTD and project management.
  
• To keep the practice fresh I do three things: a) teach it to others (see The crucible of teaching: Want to learn in a hurry? Teach!), b) "return to the well" by continuing to read everything I can on the topic, esp. the GTD forum (my RSS feeds are here, FYI), and c) looking for connections wherever I see them, this time by reading as much varied non-fiction as possible (see How to read a lot of books in a short time).

To sum things up, GTD's made a tremendous impact in my life, and has opened many, many new doors. In addition to the personal improvements I experienced (e.g., curing my insomnia, losing 15 pounds, starting a blog, and fixing a severe back problem), I'm switching careers to coaching others in this stuff.

It's been huge, and, as Mark Forster pointed out in my interview with him, this might not be such a surprise:

Time management and personal organization have ramifications for the whole of one's life

Put another way, It's not about productivity: Real change focuses not on techniques but on the way people think about themselves, their colleagues, and their work.

Is GTD perfect? No - there are a number of weaknesses I continue to probe and document. But having studied dozens of books on time management and personal productivity, as well as some major competing systems, I still think Allen's work is one of the tightest and most complete ones out there. But it does take work to implement, and to stay with.

That Frank has done this and created a great blog in the process is extremely inspiring to me - Congratulations!