I'm on the road this week, visiting another office for development meetings. I've been trying to post something on Mondays, Wednesdays and Fridays. The trip has been very busy and the only alone time I've had is when sleeping, so that schedule did not work. I have some downtime now, so I'll knock something out fast.
This trip has been an excellent illustration of the importance of communication. You can exchange e-mails all day with someone, or talk to them on the phone now and again, but nothing beats being there in person, face-to-face with someone. That kind of high bandwidth communication removes all kinds of barriers where things can be mis-read or lost in translation.
More things were decided in a few days of meetings than happened in months remotely. Yet, there is often a reluctance to incur the expense of travel. Penny wise, pound foolish.
Showing posts with label meetings. Show all posts
Showing posts with label meetings. Show all posts
Thursday, March 27, 2008
Wednesday, March 12, 2008
Oh, the irony (one of many)
As a software developer for many years I often wondered what the management people were thinking. My patron saint (St. Dilbert) mocked them mercilessly and I found solace in the humor. I picked up Scott Adams' first book "The Dilbert Principle" and read it from cover to cover and thought it was pure, distilled genius. One thing that stuck out to me then, even more than the other items, was his supposition that the person doing the work of the company - the hands-on person (like me, the software developer) - is central to the company, and the process of creating policies is one step removed from hands-on work.
Damn straight, thought I. If I'm not here to write this code what are they going to do? Write it themselves? Ha!
Fast forward some years. I have been done one-on-ones (O3s) with my direct reports for a while now, once a month for an hour each time. I moved from a once a week O3 format because of how cluttered it made my schedule and because some of my folks did not think it was very useful. After switching to the once a month format, however, I found that a month was a long time to get O3 time with some of my people, in particular my remote people, so I wanted to move back to once a week 30 minute sessions. But, I wanted to get some feedback first.
I called a meeting.
Once everybody who was on-site came into the meeting it hit me suddenly that I was not only having a meeting (which most people do not like) about a policy (one step removed from REAL work), but I was having a meeting about TWEAKING a policy I'd already changed, back to the way it was previously. How far removed from real work was I?
The sheer irony of it was overwhelming.
Apparently, fate has a sense of humor.
Damn straight, thought I. If I'm not here to write this code what are they going to do? Write it themselves? Ha!
Fast forward some years. I have been done one-on-ones (O3s) with my direct reports for a while now, once a month for an hour each time. I moved from a once a week O3 format because of how cluttered it made my schedule and because some of my folks did not think it was very useful. After switching to the once a month format, however, I found that a month was a long time to get O3 time with some of my people, in particular my remote people, so I wanted to move back to once a week 30 minute sessions. But, I wanted to get some feedback first.
I called a meeting.
Once everybody who was on-site came into the meeting it hit me suddenly that I was not only having a meeting (which most people do not like) about a policy (one step removed from REAL work), but I was having a meeting about TWEAKING a policy I'd already changed, back to the way it was previously. How far removed from real work was I?
The sheer irony of it was overwhelming.
Apparently, fate has a sense of humor.
Subscribe to:
Posts (Atom)