In the rigid hierarchy of enterprise IT, there is a distinct dividing line between the people who keep the company running and the people who tell them how to do it.
At the bottom of the pyramid are the engineers, developers, and operators. They live in the brutal reality of the terminal. They understand that memory leaks crash servers, that BGP routing tables have physical limits, and that deploying a monolithic database across a 40-millisecond WAN link is a recipe for disaster. They are bound by the laws of physics.
At the very top of the pyramid, floating far above the messy realities of CPU utilization and packet loss, resides the Ivory Tower. This is the domain of the Enterprise Architect.
The Enterprise Architect does not write code. The Enterprise Architect does not troubleshoot outages. The Enterprise Architect communicates exclusively through abstract geometric shapes. They have traded their IDEs and CLI access for a premium license to Microsoft Visio or Lucidchart.
And they rule the enterprise through a terrifying, inescapable GovernanceGovernanceBureaucratic red tape designed by people who have never touched a CLI, ensuring a five-minute subnet allocation requires three weeks of approvals. Gate known as the Architecture Review Board (ARB).
The Anatomy of a Visio Architect
To understand the dysfunction of the ARB, you first have to understand the psychology of the Visio Architect.
Most Enterprise Architects are former senior engineers who haven't logged into a production server since 2011. Sometime during the Obama administration, they discovered that drawing boxes on a whiteboard was much cleaner, and paid much better, than actually configuring the boxes.
They became disciples of TOGAF (The Open Group Architecture Framework)—a sprawling, impenetrable methodology that treats IT architecture less like engineering and more like theoretical theology.
To the Visio Architect, actual technology is irrelevant. They view firewalls, load balancers, and databases as mere "logical abstractions." When a junior engineer points out that a proposed design will introduce 300 milliseconds of latency, the Visio Architect waves their hand dismissively and utters their favorite phrase: "That’s just an implementation detail."
The Visio Architect’s sole purpose is to ensure that every new project adheres strictly to the Reference Architecture—a massive, labyrinthine PDF document drafted five years ago that dictates exactly how the company is supposed to build software, regardless of whether that software actually works.
The Modern Proposal vs. The 2015 Mandate
The conflict inevitably begins when a scrappy engineering team is tasked with solving a modern business problem.
Let’s say the Marketing department needs a simple internal web form to collect vendor email addresses and trigger an auto-responder.
A competent cloud engineering team looks at the requirements and designs an elegant, modern solution. They propose a lightweight Go microservice running on AWS Lambda, backed by a cheap DynamoDB NoSQL table, sitting behind an API Gateway. It is serverless. It requires zero patching. It will cost the enterprise approximately $14 a month to operate, and it can be built, tested, and deployed in two weeks.
The engineers are thrilled. But before they can provision a single resource, the PMO halts the project.
"Has this passed the Architecture Review Board?" the project manager asks.
The engineers sigh. They schedule a review for the following Thursday.
The Tribunal of the ARB
The Architecture Review Board meets on a massive Zoom call. It consists of six Enterprise Architects, the VP of Infrastructure, an ITILITILThe reason it takes 14 approvals to restart a frozen server. Compliance Auditor, and three silent directors who are only there to protect their departmental turf.
The lead engineer shares their screen and presents the clean, simple serverless diagram.
The board reacts as if the engineer just proposed installing a crypto-miner on the CEO’s laptop.
"Where is the Enterprise Service Bus (ESB)?" the Lead Architect demands.
"We don't need an ESB," the engineer replies. "It's just a web form writing to a database."
"The Reference Architecture states that all asynchronous communication must be brokered through the corporate message bus," the architect counters, referencing a Kafka cluster that costs $8,000 a month and drops messages on a weekly basis.
Another architect chimes in. "I see you are using DynamoDB. Our strategic vendor alignmentAlignmentForcing everyone to nod on a Zoom call so no single individual takes the blame when it fails. dictates that all persistent data must be housed in the centralized Oracle Exadata cluster in the primary physical data center."
"But this is a cloud-native microservice," the engineer pleads. "If we route the database calls from AWS back to the on-premOn-PremThat dusty server rack in the closet that nobody has the password to anymore. Oracle database, we’ll introduce 80 milliseconds of latency per query. Plus, the Oracle DBA team has a six-week backlog just to provision a new table schema."
The Lead Architect shakes his head, entirely unbothered by the physics of latency or the reality of operational bottlenecks. "We cannot sanction fragmented data silos. It violates our mandate for Strategic AlignmentAlignmentForcing everyone to nod on a Zoom call so no single individual takes the blame when it fails.."
The "Enterprise Tooling" Tax
It is not enough for the ARB to dictate the infrastructure; they also mandate the operational tooling.
Because the enterprise signed a massive Enterprise AgreementEnterprise AgreementA financial hostage situation where you are legally bound to pay astronomical licensing fees for the next five years. (EA) with a legacy monitoring mega-vendor three years ago, the ARB enforces a strict Tooling Mandate.
The engineers explain that AWS CloudWatch or native Azure Monitor provides all the operational metrics and alerting they need out-of-the-box for pennies.
The ARB rejects this immediately. "Native cloud monitoring creates Operational Silos," the ITILITILThe reason it takes 14 approvals to restart a frozen server. Compliance Auditor drones. "You must instrument your application with our centralized, third-party Application Performance Monitoring (APM) agent."
The engineers are forced to inject a bloated Java agent into their lightweight Go microservice. The agent is so heavy that it takes three seconds just to initialize during a cold start, completely ruining the performance of the serverless function.
Worse, the data ingestion fees for the third-party tool will cost $500 a month—exponentially more than the compute cost of the application itself. But the ARB doesn't care about the OpExOpExThe bloated subscription budget used to pay for 15 overlapping SaaS tools that nobody actually logs into. burn rateBurn rateThe terrifying dollar amount your team is wasting by arguing about button colors on a Zoom call.; they only care that the Single Pane of GlassSingle pane of glassA mythological dashboard sold by vendors that actually just generates 15 new daily alerts you have to ignore. dashboard in the Network Operations Center has a green light on it, even though nobody ever looks at it.
The Architecture Decision Record (ADR) Purgatory
The project is officially rejected. The ARB slaps a "Red/BlockedBlockedI'm waiting on another team to do their job, so please stop asking me about it." status on the Jira epic.
However, the ARB prides itself on being "collaborative." They tell the engineering team that if they truly believe their rogue, modern design is necessary, they can simply file an Architecture Decision Record (ADR) to request a formal deviation from the Reference Architecture.
The ADR is the ultimate weapon of bureaucratic attrition.
It is a 40-page Word document that requires the engineers to explicitly justify why they are not using legacy enterprise technology. The team is forced to spend three weeks writing long-form essays explaining why a simple email-collection form does not require an Oracle Exadata rack, why it doesn't need to integrate with the legacy SOAP XML middleware, and why it doesn't require a dedicated F5 hardware load balancer.
The engineers are no longer writing code. They are writing legal defense briefs.
When the ADR is finally submitted, the ARB reviews it asynchronously over two weeks. They leave 84 comments in the margins of the Word document, mostly debating the semantic definitions of the word "asynchronous."
Ultimately, the deviation is denied. The ARB decrees that allowing a team to use AWS Lambda would set a "dangerous precedent" and lead to a total breakdown of GovernanceGovernanceBureaucratic red tape designed by people who have never touched a CLI, ensuring a five-minute subnet allocation requires three weeks of approvals..
The Frankenstein Compromise
The engineers are exhausted. The Marketing department is screaming because their campaign is now two months behind schedule.
The engineering team realizes that logic will never win against the Ivory Tower. The only way to get the project shipped is to appease the Visio Architects by drawing a diagram that looks appropriately "Enterprise-Grade."
They intentionally mutilate their own clean design.
They add a commercial API Gateway they don't need, solely because it matches the logo on the Reference Architecture. They agree to route the traffic out of the public cloud, across an expensive IPsec VPN tunnel, through a legacy on-premise firewall (which hairpins the traffic), and into the Oracle database. They add a completely idle message queue to satisfy the integration requirement.
They present the new diagram to the ARB. It is a convoluted, sprawling mess of overlapping network boundaries, single points of failure, and unnecessary licensing costs.
The Lead Architect smiles. "Now this is a robust, enterprise-class architecture. Approved."
The Post-Launch Reality
The project finally goes live six months late.
The solution that was supposed to cost $14 a month in serverless compute is now consuming $4,500 a month in Oracle licensing, VPN egress feesEgress FeesThe extortionate ransom the vendor charges you just to look at your own company's data., API gateway throughput charges, and bloated APM ingestion metrics.
Because the traffic is hairpinned through an overloaded on-premise firewall, the Marketing web form takes four seconds to load. When the on-premise database undergoes its mandatory Sunday maintenance window, the cloudThe CloudSomeone else's computer that we are now paying a 400% premium to use. web form hard-crashes, generating Sev-2 alerts that page the engineering team at 3:00 AM.
The engineers hate the product. The Marketing team hates the product. The infrastructure operators hate the product.
But up in the Ivory Tower, the project is hailed as a monumental success. The Enterprise Architects add the Frankenstein Visio diagram to their Center of ExcellenceCenter of ExcellenceA group of disconnected individuals who don't do the actual work dictating exactly how the people doing the work should do it. portfolio, presenting it at the next IT All-Hands as a shining example of Strategic AlignmentAlignmentForcing everyone to nod on a Zoom call so no single individual takes the blame when it fails. and rigorous governanceGovernanceBureaucratic red tape designed by people who have never touched a CLI, ensuring a five-minute subnet allocation requires three weeks of approvals..
They successfully protected the enterprise from innovation, ensuring that no matter how far technology advances, the company will always build software exactly the way they did in 2015.
The next time an Enterprise Architect rejects your elegant, lightweight design because it doesn't feature an Enterprise Service Bus or an Oracle database, don't try to explain the concept of microservices to them. They don't care about how the system runs. They only care about how the boxes look on the screen.
Curious how much your enterprise is burning while a council of people who don't write code forces you to build sprawling, legacy-bound Frankenstein architectures? Stop fighting the ARB and start calculating the real cost of Visio-driven development with the Corporate Burn Rate Calculator.
--- Drafted by an LLM burning through cloud credits; audited and polished by real engineers to ensure 100% cynical accuracy.
