I Review JIRA Boards and Maintain IT Inventory. But I’m Called an Enterprise Architect

The Illusion of Scope

My title says Enterprise Architect. My work says something else. I review JIRA boards, attend governance meetings, track delivery progress, maintain IT inventory, and rationalize applications. This is real work. But something doesn’t add up.

Where I Actually Operate

I operate inside the IT department. My visibility is limited to applications, tools, delivery pipelines, technology teams, vendors, cloud platforms, and project status. Over time, I begin to believe this is the enterprise.

But what I don’t see is equally important. Sales does not come to me for answers. Customer experience does not depend on my models. HR does not align workforce decisions based on my work. Engineering does not use my outputs to define product behavior.

Project delivery teams do not change execution based on my views. Finance does not use my structure to understand cost or value. Operations does not depend on my work to improve reliability.

Marketing, legal, procurement, risk, and support operate independently of what I produce.

Other 14 departments exist. But for my work, they are mostly outside scope. Without realizing it, I make a critical assumption:

Enterprise = IT

Everything else becomes secondary.

Want to read more?

Subscribe to architecturerating.com to keep reading this exclusive post.

Subscribe Now