The only publication dedicated to OSS Volume 1, Issue 4 - August 2004 |
|
Sending the Right OSS Message (cont'd) Fact #4 You Must Understand the Mindset of your Customer To make matters worse, many times the people making the case are the same ones who were responsible for the existing systems. One can imagine how unpleasant it is for a manager to go to an executive with the message that says the systems they bought four years ago are no longer good enough. More experienced executives will ask the next logical questions: “Will these systems give me any competitive advantage? Will they provide me more reliable or better quality service? Will they allow me to provide more revenue generating services with fewer people at a lower cost?” OSS vendors must be prepared to answer these questions as they relate to a particular business case. The justifications made in response to these questions are very powerful. More and more executives understand the need to spend money for better quality services, for lower MTBF and MTTR , to reduce capital expenditures, and to reduce overall operating expense. If the case for new or updated systems is made in these terms, the value proposition becomes much clearer to an executive whose mantra is “increase revenues, decrease costs.” The Executive Message
The last point is one that bears some examination. This is one more element of the value proposition that needs to be addressed, and it is perhaps the most difficult one to describe, manage, and monitor. Many companies and their executives bought into the Customer Relationship Management (CRM) vendor claims that these systems would provide happier customers who would buy more and cost less to service. In a few instances they were right, but in many others were wrong. The difference amounted to a simple principle – it ' s necessary to control the cost to acquire and install the systems, and to monitor and report the actual benefits received. Over and over projects fail or are canceled due to outrageous cost overruns and the failure to account for the true cost of implementation. Even in successful projects, if the actual benefits are not measured and reported, the best part of the new story can be lost. Projects that get executive attention are ones where accurate regular reports of costs and benefits in understandable terms - preferably dollars - are regularly generated and reviewed. Properly determining and documenting all of the costs to implement, train for and maintain new systems, as well as measuring the benefits received in cost, capital savings, and network improvements that can be traced to higher revenue and lower customer churn is all critical in making the strongest case for the value of OSS.
© 2004, All information contained herein is the sole property of Pipeline Publishing, LLC. Pipeline Publishing LLC reserves all rights and privileges regarding the use of this information. Any unauthorized use, such as copying, modifying, or reprinting, will be prosecuted under the fullest extent under the governing law. |