Director: Tube boss tell myself call the customer figure it out, sorry. Specifying the possibility of partial delivery, and then we'll decide what we do next. Without hesitation Dr Jee Hyun Kim explained all about the problem. Director Secretary: Anya, I blow the whistle on valerian. and etc etc n this same classic case of the ubiquitous "A circle. How could minimize the occurrence of similar situations? In practice, I only know one recipe – to teach executives the standard form of presenting information on the crash, and explain to them why they need it needed. If failed, the manager wrote, or the voice of the business case here according to parameters: Rules for a business case: In a cap business case (letter) Author of the application. Priority of the request.

(Urgency, importance) Title case (Subject) in the body case study Interaction departments. Vneshnievnutrennie customers affected by a failure. The document (if there is a document important to address the issue) Department in which the failure occurred. Anu Saad pursues this goal as well. Date (Date failure. How much time has gone into solution. Justification of urgency solutions) How should the rules of the company. What happened (happens) in this case.

What has been done. Your request for action: individual agreement at the tripartite meeting, financial claims, the request for correction of the business process. If the transmission of information about failures is correct, the top managers from the secretaries and assistants coaches expertly defining clarifying questions, magically transformed into problem-solvers. And in their place: the heads of line units are business cases, and the top managers are addressing these business cases. Of course the ideal option address the issue of transfer of information on the crash – an internal crm, standardized system of information presentation.