Executive Summary

The main problem in this situation is the attempt to produce and launch a new product by a set deadline during a budget crunch.

There appears to be no teamwork which is evidenced by the bickering emails back and forth between Kelly and Pat. They have their own thoughts and opinions on how things should operationalize.

All communication has also occurred via email. There were no meetings set up so that issues could have discussed face to face.

One solution would be to postpone the development of producing the iScanner for the retail market until the company's financial situation has improved. Other methods in which the iScanner could be used should be looked at.

Another solution would be for Cliff to set up a meeting with Chris, Pat and Kelly. They all need to meet in order to be on the same page. If they had ongoing meetings during this time, ideas could have been discussed and progress development updates could have been given. This would have alleviated any personal feelings of undermining and undercutting from the employees. Team work could have been established if ongoing meetings took place.

My recommendation would be to expand on the current capabilities of the iScanner instead of developing a new product. It is unrealistic to make a new product during a budget crunch. Making a new product is risky and could cause a larger financial deficit. Other innovative ways to use the current capabilities of iScanner should be explored. According to Pat's personal notes, Chris initially wanted to use the iScanner for extended security applications: banks, government offices and other vertical markets. Once revenues are increased and the company is no longer in a budget crunch, a new product should then be decided on. Another recommendation would be to have ongoing face to face meetings between the company's key players to plan and discuss ideas for new products.