Sometimes these events are completely out of our control. Tight capital budgets require us to extend infrastructure beyond its useful life. External events or changes in corporate strategy cause timelines to be revised. Unanticipated scope creep can derail the best budget planning.

When bad things happen, does it help to point fingers at the external world, customers or senior management? Is any crisis alleviated by getting angry with staff or stakeholders? How about making excuses? In my years of experience, I've found that blame, emotions and excuses do not work.

Here's my advice for crisis management when things go wrong and resolving the problem becomes your responsibility.

1. When a crisis occurs, encourage openness and transparency in your staff. Don't shoot the messenger. By empowering everyone to communicate the events objectively, you'll get to the root cause more rapidly. Your actions will set the tone. Being calm and encouraging with your staff will reduce tensions between staff and stakeholders.

2. When the root cause is found, determine what can be done to improve the organization rather than blaming anyone. Instead of firing people, expend your energy figuring out which systems and processes should be improved. For example, if an unannounced change was made that caused serious downtime, what controls can be put in place to prevent such ad hoc changes in the future?

3. Broadly communicate the issue in terms of the lessons learned and continuous quality improvement. Many IT projects are cutting-edge and require incremental fine-tuning. We try, we evaluate, we revise, and we try again. Boards and senior management understand that perfection is a journey. If you have a sound plan that is broadly communicated, and a bad outcome occurs that teaches the organization how to do better in the future, all will be forgiven.

4. Do not hide information or sugarcoat the events. It is far better to be open from the beginning than it is to deny the truth and then have to backtrack later. In a world of instant communication via e-mail, IM, blogs and Twitter, assume that everyone knows the facts as soon as they happen. When CareGroup suffered a network outage in 2002, I learned not to be overly optimistic about restoration of service. It's better to apologize for the disruption and say that you don't know when the problem will be fixed but that you have all resources focused on the effort.