As operations manager, it was my responsibility to purchase software for my unit. We outgrew our in-house Filemaker database and had to get a real lab management system. Over six years we went through three different systems, each vendor costing more than the last.
By the time we started talking to Justin at Workflow Products, my colleagues and I had a great deal of experience with the whole process and we knew a few things for certain.
• Buying software is hard.
• Switching over to the new software is time consuming.
• Training on new software is time consuming.
• Making changes to software is a slow process.
• Vendors cannot be trusted to deliver on everything they promise.
And then there was Justin. I've done three of these switchovers and every problem that we had encountered previously was sidestepped by this new plan. For example, there was no training budget. The plan was, if training was needed, then the program needs to be adjusted to either work more like the current system or it needs instructions embedded into the screen. It felt too good to be true but also seemed like it could work. The risk was that it would take too long and never get completed, but I could evaluate the risk with a small trial. Then, if the program wasn't done within the budget, I would avoid a lot of work on yet another failed project.
I was harder on them than any prior company, but my experiences proved it was justified. We talked on and off for months after that. Can he deliver? I don't know, but it was the plan that stuck in my head. It was a good plan.
Sometimes he said the right things, sometimes he over-promised and my experience told me not to believe him. Eventually we agreed to move forward, but we weren't going to do the switchover unless I got full support from the staff.
The new system was basically the old system, but faster. There were bugs, and after an hour we shut it down. We tried again a week later and there were more bugs. On the fourth try all the staff gave approval. Several staff asked when the switch would occur because at least this system was faster.
It went well, but I was not on board. My experience told me that everything was moving way to fast. We had found lots of problems with past systems that didn't crop up until days or weeks later. However, the staff was all in agreement and the new system was, at least, faster. It made sense to move forward.
We turned off the old system and made the switch. The plan was that we needed many changes to the system as soon as possible.
It took much less time on the phone to request changes compared to prior developers. Sometimes I would have Justin show up on site and take requests from staff directly. That saved me a lot of time.
I want to emphasize one thing above all others. All previous vendors had failed to live up to their obligation to import the data from the previous systems. Justin had all the data from the current system in the new system on day one of the switchover. The other three systems went quickly, I think about two weeks and they were all imported and verified by staff. We were able to remove four software programs from staff computers and remove four servers from the maintenance schedule.
It turns out switching over to a new software package doesn't have to be time consuming. Training is not a necessary part of switching. Making changes to software can be a short conversation followed by a short wait. And some vendors can, in fact, be trusted. But buying software remains hard. I would never buy software again if Justin could take the project.
H. SAENZ
Operations Manager [Retired]
UNT Center for Human Identification