Why IT Itself Doesn’t Matter, but Enterprise Architecture Does
The article argues that while IT itself has become a commodity, lasting competitive advantage now stems from how companies design and integrate their digital business technology platforms, emphasizing dynamic enterprise architecture, strategic component selection, and holistic data and collaboration practices.
Nicholas G. Carr’s “IT Doesn’t Matter” argues that electronic data processing has become a commodity, and buying IT no longer yields strategic advantage.
Strategic advantage now depends on how a company’s digital business technology platform is built and sustained.
When companies undergo digital transformation, they assess how the platform can directly or indirectly generate revenue or added value for customers. The more purchasable components (including services for maintenance, support, and optimization) a company uses, the lower the risk of achieving evergreen, sustainable, and agile operations.
The true differentiator is the composition of the digital business technology platform and how it aligns with the company’s important strategies, processes, and tools.
Enterprise architects must adopt a dynamic approach, taking responsibility for the successful fusion of business and IT. Successful architects share common traits:
They are “Rockstar” enterprise architects who view architecture as a means to drive substantive organizational change, anchored in transformation processes, and distinct from business architects.
They take an industry‑centric view, purchasing components that support most vertical‑specific processes and selecting vendors with domain expertise.
They employ evergreen application architecture, managing upgrade risks by isolating changes, balancing complexity with sustainability, and distinguishing essential from incidental complexity.
They pursue thorough technical integration, choosing proven, interoperable components and partners with integration experience.
They never underestimate master data management, ensuring data protection, consistency, accuracy, and accountability across the organization.
They prioritize workforce experience, ensuring rapid adoption and high‑quality user experience, sometimes requiring change‑management tracking.
They foster collaboration, bringing together diverse stakeholders and aligning interests, often identifying ambassadors with T‑shaped skills.
If a company has a Rockstar enterprise architect who follows these practices, the architect is undeniably important.
Architects Research Society
A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.