Today’s complex businesses often find themselves groping for ways to better serve their customers amid long-standing practices that tend to segment services. What’s needed are standardized data systems that can be shared across a company’s divisions, governed by clear rules and procedures that will enable the organization to use the data to fulfill customers’ needs.
Companies with multiple product or service lines often find that their business has become siloed where each division has its own separate agenda, which tends to be production-oriented rather than customer-oriented, or skewed toward the division’s specialized view of its customers. As a result, the company does not have a clear picture of the total customer, and customers often feel they are dealing with several companies instead of just one.
A bank, for example, offers its customers loans and mortgages, savings accounts, credit cards, investment services, etc., and maintains customer data in each area. All of the separate customer activities are easily tracked, but to truly serve customer needs, the bank needs integrated data that shows the total picture of each customer.
So, what is standards-based, service-oriented governance?
Governance has to do with how an organization makes decisions about strategy, money, time, the use of resources, and other issues. Service-oriented means working to meet the needs of customers: What are their needs, how do you know you’re meeting them, and what metrics do they need to know to confirm that you’re doing a good job for them? Standards-based governance means having a methodology and standardization to guide functions of a similar nature across an organization.
Standards-based, service-oriented governance requires a formal structure whose members have a strategic-enterprise view of the customer that aligns the different divisions’ views. In many cases, a company takes a big step in this direction when it introduces an enterprise-wide resource planning application such as SAP, PeopleSoft, or Oracle.
Many organizations have had such software in place for a while, but they’re just now considering how to use it to make their operations service-oriented. They’re asking themselves such questions as: What’s best for the customer? How does that play across all the information we have for any given customer?
The Issues
A service-oriented business needs to stay on top of numerous issues that cut across product or functional divisions. Organization governance must pay careful attention to such questions as:
1. What are the rules for creating new services or modifying existing services? Any change that reaches across divisions has a potential impact elsewhere in the company. Rules are needed to help the divisions understand clearly what the other is doing. For example, if a cable company adds telephone service to the account of a customer who already has TV and Internet service, what does that mean for billing? How does it affect the line crew in charge of hookups?
2. Who is in charge of authorizing, identifying, and monitoring changes to the governance? For companies running one enterprise IT architecture, this responsibility generally falls to the enterprise architect. (Maybe they’re called a data architect or information architect in your firm.)
More complex systems maintained by teams of architects will require input from a wider group of people who can judge how the change will translate through all application sets, each systems owner, and perhaps each business owner, should be involved in the governance.
3. Who maintains the standards? Who will change them as needed? Generally, this should be the same entity that’s monitoring the changes. It could be a single person, a committee, or people from different IT architectures working together.
4. Who owns the data? A bank may have customer records in the loan system, the credit card system, etc., containing names, addresses, Social Security numbers, and other sensitive personal data. The enterprise owns the data, but someone, ultimately, is responsible for making sure it’s all accurate, consistent, and secure.
If a cable company cuts a customer’s service by mistake, the customer should be able to call one number and have the problem fixed promptly. There have been cases, however, when two or three departments of the same cable company, responsible for TV service, Internet service, and cable installation, have failed to communicate with each other, resulting in annoying delays. Standards-based governance can ensure better customer service in such cases.
5. Who has access to the data? The billing department might own customer records, but who else has the ability to use such potentially sensitive information? In the case of the cable company, there’s no reason that any customer information, other than the address, should be available to the line workers. It needs to be clearly established who has access to what.
IE 7
Firefox 2.0
•