The Outcome Matters

I've been playing engineer this week--trying to figure out the intracies of autoresponders (that slick software that automatically emails you after subscribing to a newsletter), merchant accounts, blog templates, and even messing with HTML code. I especially enjoyed changing the part of the code that creates my newsletter where my web designer stated explicitly "Don't touch anything above this point!" Oh well.

It's been awhile since I used my analytical skills so extensively. For those of you who don't know me well, I was a software engineer for 15 years and before that, a chemical engineer. Here's what I'm noticing:

• I can get really absorbed when I'm trying to solve a technical problem. Like forgetting to eat or put the kids to bed.

• I have to stay just as focused doing technical work as when I'm coaching. I was testing out the broadcast function of the autoresponder software while listening to a recorded call about marketing yourself. Why I thought this kind of multi-tasking would work, I have no idea. I ended up sending out the same broadcast message three times to a friendly group of users before I got it right.

• Strengths, based on talent, never leave you. Even if it's been years since you called upon that talent.

• Accuracy counts in technical work. Details matter.

These same things come up in my work as a coach--I get absorbed in the work, I must be focused to do it well, I use my talents, and details matter. The difference is that the outcome, the results are so much more satisfying. Instead of experiencing perfectly working systems, I see lives change, for the better.

I'm grateful that I have the engineering skills to get me through the systems part of my business. And I'm happy that I'm not an engineer any more.