Historical technology adoption patterns as analogues for enterprise Artificial…

Historical technology adoption patterns as analogues for enterprise Artificial Intelligence capability building

2026-04-24 · governance-policy workforce-skills ai-architecture · medium · source → · wiki →
key claims
  1. The personal-computing and broader Information Technology (IT) evidence shows that enterprise value came from complementary organisational change, process redesign, training, and decision-right redesign, not from workstation deployment aloneBrynjolfsson (n.d.)MIT Sloan Management Review (n.d.)European (n.d.)DORA (2025)
  2. ERP retrospectives repeatedly identify executive sponsorship, process fit, user training, change management, and stakeholder participation as the dominant determinants of value realisation, which means ERP underdelivery was mainly organisational rather than technicalSpringer (n.d.)Systematic (n.d.)
  3. Cloud transformations underdelivered when firms treated migration as infrastructure relocation, because realised value depended on business-outcome alignment, governance-at-scale, skill development, and platform-style operating modelsAWS Prescriptive Guidance (n.d.)PwC (n.d.)
  4. RPA produced visible pilot wins but weak enterprise scale because brittle processes, fragmented ownership, support gaps, and missing Center of Excellence (CoE) mechanisms turned automations into maintenance burdens instead of reusable capabilityVerint (n.d.)Henri (n.d.)BusinessWire (n.d.)
  5. Electronic trading in financial services scaled only with central testing, monitoring, risk controls, change approval, and senior-accountability structures, which shows that faster automated decision cycles increase the need for shared control mechanisms rather than reducing itFinancial (n.d.)Bis (n.d.)
  6. The repeated failure modes across all five waves are best explained as predominantly structural, although technology maturity, vendor-market evolution, and regulation affect their severity in each waveBrynjolfsson (n.d.)Springer (n.d.)AWS Prescriptive Guidance (n.d.)Henri (n.d.)Financial (n.d.)
  7. For enterprise AI, the best-supported reusable capability is a shared enterprise layer for policy, evaluation, internal context, platform tooling, and talent systems, while use-case delivery should remain federated near business domainsDORA (2025)Stanford (2025)Github (n.d.)
  8. Because AI adoption is already widespread while incidents and regulation are rising, organisational absorption capacity is a likely current bottleneck, which makes capability building more urgent than additional tool proliferationDORA (2025)Stanford (2025)

Research Question

What can organisations learn from retrospectives of prior technology introductions, specifically personal computing, Enterprise Resource Planning (ERP), cloud computing, Robotic Process Automation (RPA), and electronic trading systems in financial services, about the organisational, governance, and operating model failures that prevented individual productivity gains from translating to enterprise-level value, and what patterns of successful capability building are observable in hindsight for enterprise Artificial Intelligence (AI)?

Findings

Executive Summary

Key Findings

  1. High confidence: The personal-computing and broader Information Technology (IT) evidence shows that enterprise value came from complementary organisational change, process redesign, training, and decision-right redesign, not from workstation deployment alone.
  2. High confidence: ERP retrospectives repeatedly identify executive sponsorship, process fit, user training, change management, and stakeholder participation as the dominant determinants of value realisation, which means ERP underdelivery was mainly organisational rather than technical.
  3. High confidence: Cloud transformations underdelivered when firms treated migration as infrastructure relocation, because realised value depended on business-outcome alignment, governance-at-scale, skill development, and platform-style operating models.
  4. High confidence: RPA produced visible pilot wins but weak enterprise scale because brittle processes, fragmented ownership, support gaps, and missing Center of Excellence (CoE) mechanisms turned automations into maintenance burdens instead of reusable capability.
  5. High confidence: Electronic trading in financial services scaled only with central testing, monitoring, risk controls, change approval, and senior-accountability structures, which shows that faster automated decision cycles increase the need for shared control mechanisms rather than reducing it.
  6. Medium confidence: The repeated failure modes across all five waves are best explained as predominantly structural, although technology maturity, vendor-market evolution, and regulation affect their severity in each wave.
  7. Medium confidence: For enterprise AI, the best-supported reusable capability is a shared enterprise layer for policy, evaluation, internal context, platform tooling, and talent systems, while use-case delivery should remain federated near business domains.
  8. Medium confidence: Because AI adoption is already widespread while incidents and regulation are rising, organisational absorption capacity is a likely current bottleneck, which makes capability building more urgent than additional tool proliferation.

Assumptions

Analysis

Risks, Gaps, and Uncertainties

Open Questions

  1. Which financial-services firms have published enough detail to compare centralised versus federated enterprise AI shared-enterprise layers directly rather than by analogy?
  2. How should enterprises sequence capability building when they already have substantial cloud and data-platform maturity but weak AI evaluation maturity?
  3. Which operational measures best detect when AI adoption is creating duplicated governance, support, and integration friction faster than the organisation is building shared rails?

sources


Connected items

Loading…

View full knowledge graph →