At GCC, Architecture Became Coding. At HQ, Architecture Became IT Inventory. Neither Is Architecture.
- Sunil Dutt Jha
- Apr 30
- 6 min read
Updated: May 1
The Split We Created
In many large organizations, architecture has split into two incomplete roles.
At the GCC or offshore center, architects are called Solution Architects, Technical Architects, Cloud Architects, or Platform Architects. But much of their work is coding, service design, API design, deployment design, and platform implementation.
At headquarters, architects are called Enterprise Architects. But much of their work is IT governance, portfolio tracking, architecture review boards, technology standards, application inventory, and compliance checkpoints.
One side is deep inside construction. The other side is managing the construction register. Both are useful. But both are incomplete. Neither side is defining the actual architecture of the project.
What GCC Architects Are Actually Doing
At the GCC, the architect designs microservices, defines APIs, reviews code patterns, guides Kubernetes deployment, defines integration models, and supports delivery teams.
This sits largely in
P5: Implementation Tasks — the people and IT tasks that build, modify, configure, or deploy components. Some of it also touches
P6: Operations, where systems are run, monitored, scaled, and maintained.
This work is essential. But it does not automatically define the project. It defines how the system will be built.
Want to read more?
Subscribe to architecturerating.com to keep reading this exclusive post.
