HQ Called the GCC an Architecture Center. But Funded It Like a Delivery Center.

The Comfortable Story

Headquarters says the GCC is our architecture hub. We have 12 Enterprise Architects and Solution Architects. They work with 100 solution architects, Azure architects, cloud architects, data architects, security architects, and platform architects.

The org chart looks mature. The designations look impressive. The billing looks justified.

But when we look at the work, most of it is still implementation.

The Real Pattern

The 12 so-called EAs and SAs are not defining P1–P4. They are reviewing solution designs ((component implementation details). They are approving cloud patterns. They are aligning deployment models. They are checking API designs. They are coordinating with 29 tool and platform specialists.

This is useful. But this is not architecture. This is P5 (Implementation) coordination.

Headquarters created the illusion by putting architecture labels on implementation roles. Then it acted surprised when architecture did not deliver business value.

The Automotive Pricing Example

Take a premium automotive company launching a new electric vehicle.

The price must reflect model variant, battery configuration, market incentives, dealer commission, financing structure, after-sales package, warranty, subscription services, and regulatory conditions.

This is not a coding problem. This is a decision anatomy problem. But HQ asks the GCC to build systems.

So the GCC creates pricing services, dealer APIs, customer app integrations, finance modules, after-sales package components, and cloud deployment pipelines.

Everything is built. But the pricing decision is still fragmented. Dealer pricing differs from customer app pricing. Finance calculations do not align with after-sales bundles. Market incentives are interpreted differently by region. Manual overrides increase. Discounting absorbs inconsistency.

The brand looks premium. But the decision behaves like patchwork.

Where HQ Went Wrong

HQ treated architecture as a staffing category. It created EA and SA roles without asking what those roles must define.

It funded architects based on system delivery. It measured architects through program progress. It rewarded architects for implementation visibility.

So the role became inflated. The title said architecture. The work remained P5.

HQ is not innocent here. HQ approved this structure. HQ funded this structure. HQ scaled this structure. HQ accepted architecture decks that were mostly system design (component implementation details) decks.

Then HQ complained that architecture was not giving business clarity.

Financial Impact

The financial impact is direct.

1. IT budgets rise because every business change becomes a system change.

2. Margin falls because pricing, incentives, bundling, and exceptions are not governed as one decision.

3. Revenue leaks because upsell and cross-sell logic is inconsistent across dealer, app, finance, and after-sales channels.

4. Cost of change rises because each change requires discovery across services, teams, integrations, and environments.

The GCC becomes larger. But decision control does not improve. That is not a GCC failure alone. That is an HQ definition failure.

What This Signaled to Headquarters

Headquarters did not debate definitions. They responded to outcomes. They saw increasing budgets, increasing number of architects, and increasing system complexity.

At the same time, they saw inconsistent behavior within the same project, rising cost of change, and slower response to business needs.

So they adjusted engagement.

Architecture discussions were treated as system discussions. Decision conversations moved elsewhere.

Architects were involved in building systems, not in defining how the system should behave.

They used GCC for delivery. They handled enterprise decisions elsewhere. They did not depend on architecture roles for cross-department logic.

The title remained. But the role was bypassed. It was no longer part of enterprise

decision-making.

Correction

HQ must stop treating architecture as a designation problem. The issue is not whether someone is called Enterprise Architect, Solution Architect, Platform Architect, or Cloud Architect.

The issue is whether the role defines P1–P4 before P5 begins.

For each project, HQ must ask:

1. Has the outcome been defined?

2. Has the decision sequence been defined?

3. Has the system and sub-system logic been defined?

4. Have the components been defined before implementation begins?

If not, the project does not have architecture. It has implementation leadership.

And calling implementation leadership as architecture is how HQ keeps funding the wrong thing.

One Enterprise. One Anatomy.