Case USA16: Why a State Education Board Mistook IT Centralization for Enterprise Architecture
- Sunil Dutt Jha
- Aug 10
- 1 min read
Updated: Oct 21
Overview
We repeatedly see shared services equated with architecture. Centralized hosting, single helpdesks, bulk licensing — but curricula, assessment, and district ops were never linked by an enterprise model.
P1–P6 Insight Preview: Centralization stabilized components (P4) and service delivery (P6 tech), but left strategy-to-district alignment (P1), academic/process design (P2), and system behavior (P3) fragmented. Implementation (P5) chased local variations.
Role Disconnects:
CEO/Superintendent: “We standardized IT” — instruction/admin still operate in silos.
CIO: “One stack, one bill” — many ungoverned workflows beneath.
Sales Head (Programs): “Stakeholder satisfaction is up” — until reporting season.
Chief EA: “Shared IT, unshared enterprise” — no modeled education anatomy.
Want to read more?
Subscribe to architecturerating.com to keep reading this exclusive post.
