A consulting firm failed to make any progress on converting a company's legacy data to a relational database over six months. Two months before launch, the company fired the firm and hired one of its competent subcontractors. The author then worked 7 days a week for two months, creating documentation to ensure the programmer had what was needed to complete the conversion on time. Through identifying and addressing the problem, devising a solution, and executing it with quality as the priority, the conversion was successful.
1. At Cigna, it was the Rio deJaneiro project. We had hired a nationally known consulting firm to convert our
data from legacy flat files to a relational database modeled with the new data structures. They had assigned
five people to the project and six months to complete it. Two months before go-live, we realized that the
consulting firm had made zero progress. One of the lynch pins to a successful conversion was the accurate
identification of a single patient based on multiple cases for that patient. Without this, no other data
conversion (ICD9 codes, procedure codes, etc.) would be meaningful. When we came to the realization
that no progress had been made, we fired the consulting firm and showed them the door that same
afternoon. I requested that they give me one of their programmers who happened to be a subcontractor
(not an employee of theirs) who I knew was competent. This was a Friday, and that next Monday morning
I sat this programmer down to explain our predicament, stressing the dour implications of not meeting the
go-live date. I then asked him to tell me what he needed from me to make this conversion happen in the
next 2 months. He told me in detail what he needed from a documentation standpoint in order to write the
software that would result in an accurate conversion. So I spent the next 2 months working 7 day weeks,
14 hour days, creating the documentation that the programmer needed to accomplish this task. I was
literally giving him the final documentation for the remaining tables as I boarded the plane for the trip to Rio.
The conversion went without a hitch because I:
1) Quickly identified and sized up the problem
2) Devised an approach to solving the problem
3) Executed that solution with the mindset that accuracy and quality were paramount, and above all
else, failure was not an option.