A Tourism Fund, a Police Department, and a Bank Cannot Have the Same Enterprise Architecture
- Sunil Dutt Jha
- May 17
- 4 min read
Updated: May 18
The issue is not whether all three need Enterprise Architecture. The issue is whether their EA reflects the decisions they actually run on.
A tourism fund, a police department, and a bank may all have IT systems.
They may all have data platforms. They may all have applications. They may all have vendors. They may all have digital transformation programs. They may all have governance forums. They may all have architecture teams.
But they do not run on the same enterprise decisions.
A tourism fund does not operate like a police department. A police department does not operate like a bank. A bank does not operate like a tourism development fund.
So if all three receive similar EA deliverables — governance model, capability map, application view, technology view, roadmap, rationalization plan, review board, repository setup — then we have to ask a serious question:
Did the EA understand the enterprise, or only the architecture function?
Three enterprises. Three different decision systems.
A tourism fund runs on decisions such as:
investment eligibility, funding approval, disbursement triggers, portfolio monitoring, tourism impact, risk exposure, ecosystem coordination, partner alignment, and capital recycling.
A police department runs on very different decisions:
incident response, patrol deployment, investigation workflow, evidence handling, emergency escalation, public safety alerts, inter-agency coordination, case prioritization, and field operations.
A bank runs on another set of decisions:
credit approval, KYC exception handling, fraud alerts, payment exceptions, collateral valuation, risk thresholds, interest rate changes, regulatory reporting, and customer onboarding.
These decisions are not interchangeable.
They do not move through the same departments. They do not follow the same processes. They do not depend on the same system logic. They do not touch the same components. They do not create the same operational risk. So their Enterprise Architecture cannot be structurally identical.
Want to read more?
Subscribe to architecturerating.com to keep reading this exclusive post.
