March 16, 2010
I was reminded recently of one of my long view axioms – workarounds don’t work (for long).
Workarounds have a finite duration for which they will enable correction/detection of an existing problem. This is because they require extra effort for what is usually an infrequent problem. Thus, as humans, we tend to forget, begin to believe it is unnecessary (it doesn’t really matter), or it was simply too much effort (not worth it to me), so it just does not happen.
I was reminded about this axiom last week when my 16-year-old daughter passed her driver’s license exam. Although she passed, she couldn’t get her license because the Department of Motor Vehicles (DMV) computer system had a known counting error that indicated that she was two days short of her required permit duration, yet the workaround had been forgotten.
The time-based requirement for teenagers to receive a full license is that they must have held their permit a minimum of six months. My daughter received her permit on 09/09/2009. She scheduled and passed for her driving exam on 03/09/2010 – exactly six months later. So, how could she be two days short?
It turns out if you assume that SIX MONTHS = HALF-YEAR = 365/2 DAYS = 182.5 DAYS and then assume that a minimum of 183 DAYS is the appropriate standard to apply to ensure completion, then the criteria FAILS six-months of the year: March, April, May, June, July, and August, (see graphic) for the condition when a teenager schedules their six-month driving appointment exactly six-months out (date to date). This happens because there are only 181-182 cumulative days in the six-month periods, falling immediately after February, which has only 28 days.
Can you imagine how frustrated and aggravated the two of us were?! She was quite disappointed at not receiving her license and thus not being able to drive her planned excursion the following day, not to mention it was rather anti-climactic to return two days later to get her license. I was aggravated on her behalf and because of the hassle of having to go to the DMV twice in two days.
I was sufficiently aggravated about the situation to contact Gary, the Drive columnist in my local paper, to help me get the problem fixed. Gary successfully got to the right folks at the DMV. The DMV confirmed that the problem was a known counting issue (the computer had been programmed with a 183 DAY threshold rather than programmed for six MONTH threshold). The DMV agent also informed me that a fix was in the queue to convert the counting from DAYS to MONTHS (but there wasn’t any priority for it) AND that there was a workaround in place to allow the field offices to allow a DMV manager override the system but that my local office had forgotten the procedure. (My daughter should have been able to get her license on the day she passed her driving exam.)
Although the DMV representative was very apologetic and promised to write a memo to all the field offices reminding them of the workaround, I was disheartened by the futility. How much work was created because because they did not expeditiously fix this known problem and allowed a persistent workaround? For example they could simply change threshold from 183 days to 181 days – one line of computer code! What’s the risk – a teenager sneaking in to get his/her license a few days early in November? How many managers at the hundreds of field offices will have to read another memo about the workaround and remind their staff to override when needed? Of course, all will be forgotten come September and experienced again come March!
My long view advice:
- Expeditiously fix problems – workarounds don’t work.
- Do not allow workarounds to persist for any more time than it takes to solve the problem permanently. (It costs more than you are probably aware.)
Are you avoiding workarounds in favor of solutions?
March 31, 2009
When I was running with my friends Sunday morning, the headwind at the outset was strong. Our progress slowed to a crawl along the trail. As we chatted, inquiries as to the condition of my ankle (six weeks post-sprain) heard reports of recovery – even a wobble on Friday’s run “righted” perfectly as pre-injury. And then, as we continued to chat about the economy and technology, I realized that the P’s of overcoming obstacles for running apply to technology business too.
- Keep Perspective: When there is a headwind out, there will be a tailwind on return (and sure enough, we flew back).
- Be Patient: My friends continue to commend me for taking the long view and being patient with my ankle. I did not run for 4 weeks, I rehabilitated through swimming and targeted exercise, and when I returned to running, I slowly increased distance with time.
- Maintain Persistence: I worked hard to regain proprioception by strengthening my ankle with balance (wobble) boards.
- Create Positivity: My friends enjoy and encourage a positive attitude; we see the glass as half-full.
On Technology Business:
- Keep Perspective: When there are technical challenges, it is important to recognize that they are competitive opportunities. Each solution becomes a barrier-to-entry for competitors.
- Be Patient: In a desperate economy, there will always be significant pressure to attempt to do too much too quickly. However, doing too much is foolish because it dilutes resources and increases the risk for success in any single effort. The long view encourages prioritization and sequencing of effort to achieve the greatest productivity and opportunity for success.
- Maintain Persistence: Key insights are achieved by diligence, being mentally prepared to recognize when key insights have been realized, and acceptance of breadth (be open to “not invented here” – look to other technologies for similar problems and generalize solutions).
- Create Positivity: Staff, customers, investors, and the media are human and thereby obey the law of attraction (subject of ch. 2, How to Be Useful: A Beginner’s Guide to Not Hating Work by Hustad). Authentically projecting positivity and confidence about your technology will encourage others to do the same!