EA for an Airline Is Not EA for a Telecom Operator. So Why Do the Deliverables Look Identical?
- Sunil Dutt Jha
- 6 days ago
- 7 min read
Updated: 5 days ago
The issue is not whether EA consulting was completed.The issue is whether the EA understood the real operating logic of the industry.
An airline and a telecom operator may both have enterprise systems, digital platforms, data programs, applications, vendors, infrastructure, and architecture teams.
Both may receive EA frameworks. Both may receive governance models. Both may receive capability maps. Both may receive application views, technology views, roadmaps, rationalization plans, and architecture review structures.
The deliverables may look professional. But there is a deeper problem.
An airline does not run like a telecom operator.
An airline runs on schedules, aircraft, crews, airports, passengers, maintenance, safety, disruption recovery, revenue management, baggage, and flight operations.
A telecom operator runs on networks, spectrum, capacity, subscriptions, activations, billing, service assurance, roaming, outages, SLAs, towers, devices, and customer usage.
These are not the same enterprise decisions.
So the real question is simple:
If the operating logic is different, why do EA consulting deliverables often look identical?
Want to read more?
Subscribe to architecturerating.com to keep reading this exclusive post.
