For the bulk of today I’ve been steadily working on fantabulous handouts for my contracting gig. One of the handout jobs was just to format something that was already content-ready. The other handout (the actual fantabulous one) is nearly ready but I had to stop. I was overcome by a feeling of embarrassment for the system. Yeah, I was embarrassed for a piece of software. It happens.
It is a long story but I’ve contracted with the state since late 1998 (on a full- and part-time basis). I’ve been there for the “dark” days of the software product. I was there when it was so unstable that we had to regularly cancel the afternoon portion of a class. I’ve also been there when huge strides have been made and am actually proud of several things that have changed about the system. Really. I will actually stop a class to tell folks how happy I am that some functionality or another is now available. When I write Help topics and training documentation, I try to let that enthusiasm peek into the equation without ruining the professionalism of whatever it is I’m writing.
Today, though, I had to stop because I was embarrassed about two sections of the software that are coming out later this year. I’m a little thankful that I’m not on the training schedule for these two items.
My boss laughed when I talked to her on the phone this afternoon and told her I’d have to pick it up tomorrow. She feels my pain. The bottom line is that we’re there to train the system not design it. We’ll train whatever the system has to offer–good or not so good.