Core Competencies
Friday, January 23rd, 2009
Few things sicken me more than corporate jargon. I know a few corporate-to-the bone types. They’re most comfortable in khakis and use terms like “execute the spend” when they’re talking about buying something. They’re just despicable, revolting individuals. I have it on competent authority that they are deathly afraid of being exposed as actual human beings and count on their daily embrace with Satan to see them through. Nevertheless, there is a term they use that I have found surprisingly relevant to my own life: core competency.
A company’s core competency is a thing that it does well, that sets it apart from other companies and bolsters the expandability of their business. Something like that. In my own life, I’ve reduced the term to mean the things that I do well that are not a burden to me while I do them. I do a number of things well. Many people do. I make music, play several instruments, I write, I communicate, I engineer and produce audio recordings. I truly enjoy these things. One test I use to determine my own core competencies, as it were, is whether or not I lose track of time while engaging in those activities and whether the loss of that time matters to me.
So far this year I’ve eliminated certain things from my life that did not represent a core competency for me. The first was my checkbook database. A few years ago, I created a database in Access that I used to track my checking account transactions and later, those of my savings account. I created it because I thought my requirements for such a program were small and did not warrant the purchase of an off-the-shelf application for that purpose. I struggled with my little software design idea and through my infamous tenacity, I built something that worked. My skills in programming are what an actual software developer would consider comic at best, but I bent the thing to my will and haven’t kept a written checkbook register since.
I never could get the reconcile part to be easy. It always required a certain amount of data massage to get the downloaded stuff from my bank into my program. I always managed to make it work, but it was always a black sinkhole of time. Finding errors was even harder. At the end of 2008, I decided that I didn’t want to be a software developer. I didn’t have to be a software developer. It wasn’t a core competency. I should just forget it. I could buy a program to do this stuff and spend my time doing something else. So that’s what I did.
Up until this week, I was playing keyboards for my friend’s cover band. He’s an old friend of mine and when he needed someone to replace his keyboard player, I wanted very much to help him out. I thought that at the same time I could increase my keyboard skills. I did both, but very recently I noticed that my other musical priorities were being neglected. Those that were far more dear to me. I started spending so much time learning songs and programming my synthesizer to get the sounds right that I was overwhelmed and (hint hint) really noticing the hours that were passing as I worked. Could I program my synth and copy records? You bet. Did my own music get pushed back? Yes. The alarm started to sound. Playing in a cover band is not my core competency. Making records is. With a heavy heart, I told my friend that I couldn’t continue with the band. That was hard, but I feel like I’m back on track and have my musical priorities more in order. I’m now devoted completely to original music, which is where I must be.
I find that I apply the same core competency reasoning to even the smallest events in my life. I got an eye exam this week. As I was waiting for the doctor to come in to the examination room, I wondered what it must be like to be a doctor. I thought of the studying and the challenges. I was always a great student and enjoy the challenge of learning something new. Would I be up to that?
I noticed a poster on the wall that featured detailed illustrations of the anatomy of the human eye. There were callouts all over it, pointing out more detail than I ever knew existed. My first instinct was to absorb as much of it as I could. If this stuff was knowable, why then shouldn’t I know it? This is an old, ridiculous habit of mine. In some respects, the tendency has gotten me to where I am today. This time though, I surprised myself when I got the distinct feeling that I wasn’t enjoying learning about the eye at all. I just wanted to see better and I needed an eye exam to get new glasses. Knowing about the eye wasn’t important to me at all. I turned away from the poster and started to think about getting back to my studio.
Could I learn all about the eye? Sure. Is it beyond my understanding? Absolutely not. But medicine is not my core competency. I looked at my watch a bunch of times while I waited for that doctor. She took a long time and it bothered me. The poster wasn’t helping me to forget about it.
It was such a feeling of relief when I decided that I didn’t have to absorb that entire eye poster while I waited. This probably sounds absurd, but this is actually how I think. I’m constantly putting myself to the test. Can I be better, smarter or more skilled?
Over the last 8 years or so, I’ve learned the most important test questions of all. Can I be happier? Could I be more miserable? I think those questions take priority over everything. I find that by constantly examining my core competencies and sticking to what I do well and enjoy the most, I can more often answer No and Yes.



