Enterprise Architecture Value Model - Define the engineering roles of your Level 4 architecture function
Enterprise Architecture Value Model
Define the engineering roles of your Level 4 architecture function
The Level 4 architecture function requires specific engineering roles that complement and extend the traditional architect profile. Your Chief Architect and Head of Software Engineering are jointly responsible for defining these roles clearly and staffing them with the right people.
Platform Architects
Platform architects design your architecture function’s horizontal platforms at the enterprise level — their technical architecture, API design, integration model, and multi-year evolution strategy. They think both vertically (the internal design of each platform) and horizontally (how each platform serves its diverse consumer base without being optimized for none of them). They work with platform engineers to ensure that platform designs are implementable, maintainable, and evolvable.
Platform Engineers
Platform engineers build and operate the platforms that platform architects design. They write the code, the configuration, and the infrastructure-as-code that brings architectural intent into operational reality. They manage releases, operate the CI/CD pipelines for the platforms themselves, respond to incidents, and maintain the operational health of the platforms your architecture function owns. These are not advisory roles. They are engineering roles with full operational accountability — the practitioners who turn your architecture function’s vision into organizational infrastructure.
Solutions Architects with Delivery Credentials
Solutions architects in your Level 4 architecture function are the practitioners who engage at-risk and high-risk initiatives at Level 3, carrying delivery accountability into the most consequential programs your enterprise runs. They bridge the Level 3 and Level 4 engagement models — embedding in crisis programs as the elite task force when needed, and contributing to horizontal platform ownership when those engagements conclude. Their delivery credibility makes your architecture function credible to the delivery organization. Their architectural depth makes their program engagement substantively valuable rather than merely managerially accountable.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers