Is Outside-In Architecture Right for Your Company?Deloitte Debates |
/us_Blueprint_200x200_101612.jpg)
|
| Subscribe to receive updates when new Debates are released: | |
 Receive emails |  RSS (What is RSS?)
|
|
Outside-in architecture connects partners, suppliers and other external parties to a company’s ecosystem. While this design is growing in popularity, does the ability to share information with third parties justify the cost of replacing your current centralized architecture?
Recently, increased competition has led some companies to embrace an emerging IT architecture model that supports information sharing among internal and external parties. Advocates of this “outside-in architecture” approach argue that it will soon become an essential element of business results. Yet this notion meets with resistance from companies that have invested heavily over the years in creating and maintaining a traditional, centralized IT architecture. Their reaction is understandable and it raises the question of whether companies should divert resources toward a new architectural model that has yet to mature and demonstrate its longer-term value to the enterprise.
Explore all sides below by clicking on each button:
 |
|
| We’ve invested too much in centralized architecture to change right now. We’ve achieved scale, security and consistency of approach around the globe. Why would we spend even more to reinvent the wheel? |
Your current architecture may no longer support new transaction types. Global business has evolved with many transactions making control difficult, if not impossible, in a centralized approach. And, oftentimes, transactions no longer have a defined beginning, middle and end. |
| Our supply chain works fine as is. We have worked very hard over the past 30 years to streamline our supply chain by consolidating spend and tightly controlling quality and pricing. |
Your approach to supply chain management is becoming outdated. Future supply chain models are likely to feature vastly expanded networks of business partners. Traditional “control” exercised in centralized IT is giving way to an ecosystem model. |
| We’ve already adopted a service-oriented architecture (SOA). Our current architecture delivers everything we could achieve with an outside-in approach. |
Outside-in architecture can bring added value to existing service-centric platforms. Outside-in architecture can be deployed in organizations that have either enterprise application integration or service-oriented architectures. |
| If this architecture is so important, why is the enterprise software industry not talking about it? There are no large enterprise software vendors identified currently as having product offerings that support outside-in. |
Current trends suggest that soon they will talk about it – a lot. The need to share information is beginning to outweigh the need to own the information. Emerging business practices suggest that enterprise application vendors will likely embrace outside-in architecture in the near future in an effort to remain relevant. |
My take
Eric Openshaw, Principal, Vice-Chairman of Technology, Deloitte Consulting LLP
Outside-in architecture should be on the CIO’s radar now. The growing need to share information – not just internally, but externally with partners, vendors and clients – is leading companies to think beyond traditional centralized IT architecture models. Indeed, they will likely need to tie multiple, and in some cases thousands, of autonomous entities into a single IT ecosystem where they can move and share data freely.
With this in mind, CIOs should consider experimenting with outside-in architecture to get a better idea of how it could support their company’s strategic goals and, potentially, add value. Perhaps they could implement the model on a small scale in an environment that has many of the characteristics and needs of the larger ecosystems, such as supporting a new product, or as part of a geographic expansion. One of the features/benefits about outside-in architecture is that, unlike centralized architecture which requires a large investment to achieve scale, it can be implemented incrementally. As a result, you can pay – and learn – as you go.
The potential benefits of taking an incremental approach can be formidable, while the cost of failure can remain modest. However, the cost of doing nothing could be high. Competitive pressures are forcing companies in virtually all sectors to expand toward much larger ecosystems of specialized providers. Increasingly, small companies are leveraging this model to expand their scope of services. Large companies are assessing it as a potentially cost-effective alternative to centralized models. The question, then, is likely to change from “if” they will embrace outside-in architecture, to “when” – and for some companies the answer may likely be “now.”
Related content
Library: Deloitte Debates
Services: Consulting
Overview: Technology
By participating in this poll, you consent and acknowledge that your responses may be disclosed without attribution by Deloitte in future publications and you are authorized to respond to the poll on behalf of your company.
Please review the guidelines before providing your comments.*
*Guidelines
Conversations on this debate may lead in many directions. We encourage spirited debate and varying perspectives but honesty, decency and mutual respect are essential. Please remember:
-
Keep your entries succinct and on topic.
-
Don’t post confidential information.
-
Don't use names of companies or individuals.
-
Use appropriate language and refrain from attacking others.
-
Comments will be reviewed prior to posting.
-
We reserve the right to edit, remove or not publish comments at our discretion.
As used in this document, “Deloitte” means Deloitte LLP and its subsidiaries. Please see www.deloitte.com/us/about for a detailed description of the legal structure of Deloitte LLP and its subsidiaries. Certain services may not be available to attest clients under the rules and regulations of public accounting.
Is outside-in architecture right for your company?
(107.71 KB)
