Wednesday, June 9, 2010

Day 2 (#215800): The Day Job

I sat down at my computer ten minutes ago, certain that I had intended to actually do something specific. It took those ten minutes and a review of tweets from the folks that I follow for me to realize that I need to begin the work of writing my 800 words today.

I went for a run yesterday after work. Four miles. I was pleased to discover that it is becoming easier, and I was able to trim 15 seconds off of my best time this year. At the AAW retreat Eddy Mann and I discussed how running for us is a time of quiet reflection and praise. For me, it is a time to consider my actions, my place in life, my relationship with Christ, my relationship with my family, my performance at work, etc.

Yesterday, I spent a great deal of time contemplating the vast subject matter available for me to address when I write. What came to my mind again and again was this: sin. I considered how I sin and the form it takes. I wrote a healthy number of words in my head during that run. I hope that, in the near future, I’m brave enough to discuss that in public forum; however, since this is only Day 2, I have chosen to reserve that discussion for a later date.

So today’s subject is a simple one. I’m going to write a brief description of my day job – tomorrow I’ll describe what I consider my real job.

I work for a small company (less than 50 people) in Vancouver, WA. While we provide an array of services, my position is focused on consulting. Actually, I’m the manager of the consulting group.

OK, I find the term “consulting” to be vague. It means many things to many people. My father-in-law worked for Bayer Chemical for 23 years – two years from full retirement. He was laid off by a consultant, evidently to save the company the cost associated with paying his benefits for the rest of his life. I’m NOT that kind of consultant.

I work with public agencies, generally small government (cities, counties, states) and utilities. I shepherd them through the steps necessary to procure and implement software to support their organization. Ii don’t sell software. I don’t pick the software for them. I provide the method and the objective voice that ensures they are successful.

My wife used to think my job was ridiculous. Why do people need help buying software? Why would they want to pay somebody to do it? That’s a fair response. It used to be my response. Here’s the deal, though: most companies don’t do it well. There are millions of dollars at stake. There are competing priorities. It is quite easy to screw it up. And when you’re a public agency, an expensive and/or failed project gets you in the papers. Essentially, I’m a reasonably priced insurance policy.

My wife gets it now. Her company has been dealing with a nightmare software implementation project for several years now. She has come to appreciate the objective approach to software selection that my company promotes. Her previous boss decided that, rather than purchase a proven system that was more expensive initially, she would go for the cheapest product available – a product that was not fully developed and not implemented anywhere. Poor judgment, trust me.

So where are they now? Three years later, the application still isn’t fully implemented. It’s buggy, slow, poorly designed, and unstable. They are trying to renegotiate the contract with the developer (there’s only one!). He’s got them over a barrel, because he owns the code and they have sunk so much time and money into the solution that they aren’t willing to just walk away from it.

Anyway, that’s a quick story about my job. There’s a lot to it. I could write many days about it, but since I don’t expect anyone to read this on a good day, I really don’t expect anyone to slog through an entry about consulting and software procurement. I know that I would not get through it. Seriously, most of us don’t take the time to read 200 words in an online sitting, let alone 800.

Today I will be driving with one of our partners to kick-off a new project. We’ve worked with them once in the past. They are a challenging and demanding group. I say this not in a pejorative sense – it’s just a statement of fact. We’ll likely be engaged with this company for at least 18 months. To be honest, I am somewhat anxious about this project. The previous work for them was met with some criticism. Though we delivered a quality product, the message we delivered was not the message they wanted to hear. Unfortunately, my job is to be objective and speak the truth as I see it. I am blessed that most of my clients are open to hear my message. Occasionally, though, I have to tell you that “your baby is ugly”.

I’m over 800 words now. I’m not too impressed with this entry today, but I suppose it’s like writing the exposition of a book – not a lot is occurring, but the information given is necessary to grasp the context of the story to follow. When I’m reading back on this, I might find it helpful to recall just where I was in mind and spirit in June 2010.

No comments: