You decide the most prudent course of action is to document the bug, retrain the staff and start work immediately on a patch for the software. It's costly to you, but your employees are handling the stress well.

The hospital, on the other hand, is concerned. They don't like the idea that there is a bug in KAREL which could cause major problems. However, you have reassured them that you will retrain the staff to handle the situation and that you, personally, will be on call at any time if there are any problems.

Since you have acted in good faith throughout this whole process, the hospital can not do very much more. They accept the conditions, but urge you to get to work on the software patch.

In the following four months, your team completes the software patch. KAREL has not acted up at all during this time, but the hospital feels much more confident now that KAREL is up to specifications.

Your competitors working on LOGO the Medic, however, are not as happy. They have also run into production problems and are considering dropping the product.


During the next year and a half, you release KAREL II, at about the same time as LOGO the Medic comes out. Both products are comparable, but KAREL II is more succesful, owing much to the glowing recommendation from the local hospital. Building off of the success of KAREL the Nurse, KAREL II becomes tremendously succesful and brings you more wealth than you ever imagined.

Ten years later, you retire early and move next doors to Bill Gates, where you taunt him constantly about his failed LOGO the Medic.

Life is good.