IT Employment

Ask something
Discussion Locked

Value proposition

0 helpful
1 reply

by dryfus

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm currently working to develop the value proposition of our Web site applications and static content. These will be validated by the business internal clients and used to determine the requirements for disaster recovery platform. I can look at site statistics etc., to show traffic patterns on content but what is the value if there is no direct top line revenue or bottom line dollar savings to correlate? Customer satisfaction and brand integrity are almost impossible to measure.

1 reply

by prefbid ii

Start with the business need of the site in the first place. Is it revenue generating, critical business communication, important business communication, or just informational?

As you noted, revenue generating is the easy topic. Everything elseis harder to figure out. So begin by exploring the questions: what happens if the site is missing for one hour? 24 hours? One week? One month? Three months? If you get to 3 months and the business will not be impacted by the loss more than "inconvenienced", then there is a good chance that you don't need a DR plan.

When evaluating the impact, remember to consider: stock holders and the information they get, public relations impact, public perception on the company's technical prowess,printing of "backup" forms, manual data entry of routine information, increased search time, help desk complaints, and other intangible problems. Rate each area for each time period as "out-of-business", "greatly impacted", "impacted", "inconvenienced", and "no impact".

From there it gets trickier because it depends on the type of company you work for as to what they will accept as "proof" of need.

This discussion is closed to new replies.