SOA transformation in the mobile industry

My partners and I are in the final stages of implementing our Supply Chain Synchronization suite at a global leader in logistics services and distribution for the wireless / mobile industry. Our solution is based on a service-oriented architecture, so this article by Kevin Wei Wang, an associate principal in McKinsey’s Shanghai office, caught my eye because it explains how Shanghai Mobile transformed its IT architecture with SOA “to create a smarter, more efficient system.” That concept is one that resonates with my partners and me.

Here is the introduction to Creating competitive advantage with IT architecture: An interview with Shanghai Mobile’s CIO

“In early 2008, Shanghai Mobile’s general manager of information technology, Xie Qin, knew that his company's "complex legacy architecture presented competitive problems that would create even greater stumbling blocks in the new era. First, the company’s IT systems were largely siloed by customer channels—local branch stores, call centers, and online stores—which had inconsistent business policies for common processes, such as approving a subscriber’s eligibility for new prices or services. That translated into costly duplication for writing and maintaining software applications and increased spending on IT infrastructure. Second, the complex IT systems were very challenging to maintain. Under the existing IT architecture, for example, it was difficult to monitor system performance issues and to diagnose root causes. IT normally took a long time to resolve service breaks.

“By the spring of 2008, Xie launched what would turn out to be a ten-month overhaul of Shanghai Mobile’s IT systems to improve its sales and service capabilities and to make the system easier to maintain. The transformation required Shanghai Mobile to dismantle the existing architecture and to replace it with a new IT blueprint based on service-oriented architecture (SOA), which created a unified business-service layer for different front-end channel systems and allowed the channels to share customer information. The result: improved sales and service capabilities for the channel systems; an optimal use of program developers, data centers, and other resources of the IT infrastructure; and a more maintainable system.

“Although Xie’s goals were straightforward, implementing SOA within a business in flux can be risky. In this interview with McKinsey’s Kevin Wei Wang, Xie explains how he executed the strategy and how it has changed the carrier.”

Following are some of the key insights shared by Xie:

Two main reasons change was required

1. Market was becoming increasingly competitive
2. More and more difficult to differentiate product offering

Three key management lessons involved with process transformation

1. Clearly articulate business value
2. Realign roles to ensure people stick with new approach
3. Implement risk mitigation to minimize disruption to the business

Four results of moving to SOA

1. Reduced time to market by 30%
2. Reduced development effort by at least 50 %
3. Improved customer experience
4. Reduced system performance diagnosis from an average of 2 hours to 2 minutes

Three key IT problems addressed

1. Inconsistent business logic
2. Lack of information sharing across channels
3. Disconnected system monitoring

Most importantly, Xie clearly understood that while the IT benefits of switching to SOA were substantial, a project of this size and importance would only be funded and achieve success if it had the full backing of the entire business. Xie answered the question “An SOA transformation often means change and uncertainty in the business units. How did you convince them to go along?” this way:

Xie Qin: “We had to present the business case in a tangible way. We got the buy-in by addressing the real business issue—inconsistent business logic and lack of information sharing across channel systems—which is a real concern for the customer experience across our channels. While an SOA transformation also reduces IT costs and improves system performance, I don’t think we would have gotten our business team as excited by addressing these two factors alone.”

He is right. For those CIOs and IT execs working to fund and launch projects of similar scale, these are words of wisdom.

The complete article at McKinsey is available here.