Discussion Locked

Translate technology into a strong business case

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

How do you translate highly technical designs in terms that nontechnical managers and executives can understand? What do you think of Mike Talon's suggestions about addressing business impact without going into the technology or using industry regulations to help justify DR systems? Share your thoughts about translating technology into a strong business case, as discussed in the Oct. 28 Disaster Recovery e-newsletter.

If you haven't subscribed to our free Disaster Recovery e-newsletter, sign up today!
http://nl.com.com/acct_mgmt.jsp?brand=techrepublic

3 replies

by wirelessmgr

I agree with Mike.
What can help is if you use the ITIL Methodology as a foundation for your business case.

The ITIL methodology provides a framework with details (loosely) such as:

Use your SLA with your organisations business units as the driver for the DR Systems business case. As this is what the business says they must have to operate !

you should have a Service Catalogue which details all services that you provide to the business and along with the SLA the type,level of service etc., that they require from your IT Organisation.

You should do a risk analysis and the subsequent management exercise to describe mitigation strategies to accept, eliminate or reduce the identified risks posed to the services or systems.
You should highlight the VBF Services (Vital Business Functions).

You should then identify the remedial options and the associated costs. This should be shown in business terms such as revenue loss per hour, damage to brand, effect on customers, effects on the customer contact centre or any other business defined variables.

This will assist the business to support and understand your proposal as long as you have done the necessary awareness campaign and have Senior Management Support!

This discussion is closed to new replies.