I’m Called a Business Architect. But My Outputs Serve the CIO, Not the Enterprise.

The Work Looks Enterprise-Facing

I’m called a Business Architect. My work looks enterprise-facing.

I create business capability maps. I create value streams. I create process views. I create customer journey maps. I create operating model diagrams. I create transformation roadmaps. I create business requirement views.

I support enterprise programs. This sounds like Business Architecture.

But who actually uses my outputs?

Very often, the primary consumer is the CIO organization.

The CIO uses my work to understand business needs. The technology team uses my work to plan systems. The portfolio team uses my work to prioritize programs. The IT team uses my work to map applications. The delivery team uses my work to shape implementation.

This is useful.

But if my outputs mainly serve the CIO, then I may not be defining the enterprise.

I may be translating the business for IT and not for CEO or business heads.

Want to read more?

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

Subscribe Now