I hate uncertainty
For several weeks in January, our company was struggling with the implementation of a new database. I had been spearheading the data conversion, a process that had straddled several months. Long story short, it wasn't everything we had imagined. We spent about a week flip-flopping between forging ahead with the new database, or backtracking to stay with the old one. Ultimately, due to various technical and licensing issues, the decision was made for us.
This period was incredibly stressful for me. Not knowing from day to day which system we were going to use was intolerable. It nearly brought me to a productivity standstill. Once the outcome - thought not necessarily ideal - was determined, I could relax and get back to work.
Lesson learned:
Find out ahead of time exactly what the implications of a given action are. And, find out if there is an option for changing the chosen course. Don't allow for uncertainty as a result of unexpected consequences.
I trust people too much.
I assume that 'professionals' and 'experts' in a given field know what they're doing. In February, this has applied to a) a countertop installer, and b) an accountant. In the first instance (detailed in my Queercents blog post), the work was being done for me - and done wrong. In the second instance, I let ignorance lead the way and assumed that "I can use this software even though I haven't used it in 8 years" meant she really could. I was mistaken.
Lessons learned (there are two):
1) Watch closely, or people will screw you - whether with malice or just through lack of effort. Nobu oversaw most of our kitchen installation, asked ton of questions, and watched every move the contractors made - and the job was done right. Me, I just sat back and let the guy do his job, and regretted it.
2) Ask LOTS of questions. In dealing with the accountant, I took too many things for granted. I thought I had got things covered, but I didn't focus on the most important details. I now know ask things like: "What version of the software have you used?", "When was the last time you used this software?" and "Did you do that on the job, or just in school?" The phrase 'familiar with' can mean a lot of different things. And, the DOS version of ACCPAC is not the same as the Windows version...
I suck at confrontation (or the anticipation of it)
When I had to call the installer to get him back in to fix the crooked countertop, I felt guilty. It was so hard for me to make that phone call. And when it wasn't certain when or if he was going to come back, waiting for him to return my call tied a knot in my stomach for most of the day. This refers back to my first point - I hate uncertainty - but I was also worried about having to argue my point or get into some sort of confrontation.
If one of the candidates employed by us doesn't work out, making the phone call to tell them what they have done wrong - addressing a performance issue or the like - is painful. I don't want to be the bad cop. Even if I'm angry at them for doing something stupid enough to get themselves fired, telling them that is really difficult.
Lessons learned (three this time!)
1) Don't apologise so much. Even when the mistakes aren't mine, I have a (typically Canadian?) tendency to say "Sorry". This is going to be a tough habit to break.
2) Don't let it be personal. The crooked countertop wasn't about me, or the installer - it was about a poorly done job. When I have to tell a candidate they were fired, it's not about them personally, it's about some action - or inaction - on their part. I have to focus on the issue, not the individual.
3) Keep a record of what was said. I'm usually a pretty good record keeper, especially when money is involved. However, what gets said during a conversation is often pretty subjective. I'm actually starting an Excel spreadsheet to keep track of conversations with customer service reps. (I know, I'm a total geek.)
I was feeling very broody today, and thought getting this stuff down on paper, so to speak, would help alleviate that a bit. Any feedback or insights from anyone? Anything you've learned from your experience in 2009? I trust March to be something entirely different!
