Enterprise Architecture Value Model - Build your architecture team with real software engineering capabilities
Enterprise Architecture Value Model
Chapter 40. Build your architecture team with real software engineering capabilities
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Engineering Capability | Requires architects and engineers who can design, build, operate, automate, and support complex horizontal platforms. |
| Delivery Credibility | Builds trust with delivery organizations by demonstrating full-lifecycle technical fluency rather than advisory distance. |
| Architecture/Engineering Convergence | Recognizes that modern architecture increasingly exists in code, platforms, automation, and operational systems. |
Quick Q&A
Question: Why must architecture develop software engineering capability?
Read More Below
The Level 4 architecture function requires a staffing profile that is genuinely different from the traditional architecture team, and it requires your deliberate investment to create. Architects who are skilled at governance documentation, framework development, and stakeholder advisory work are valuable — but they are insufficient for an organization that owns and operates a portfolio of horizontal engineering platforms. You need practitioners who can design, implement, build, package, deploy, instantiate, operate, administer, and support complex technical platforms.
The Software Engineering Capability Requirement
Software engineers who focus on horizontal and foundational platforms bring a specific combination of capabilities to your architecture function. They are accustomed to designing systems that serve many consumers simultaneously rather than a single application or domain. They understand the trade-offs between generality and optimization that come with building shared infrastructure. They have the operational discipline — SLAs, incident response, change management, release engineering — that managing a platform with broad organizational dependencies requires. And they bring the mathematical rigor, systems thinking depth, and implementation fluency that makes their architectural thinking concrete and actionable rather than conceptual and advisory. A software engineer who has designed and operated a complex horizontal platform at scale commands a different kind of organizational credibility than one who has reviewed designs from an advisory distance — and that credibility compounds across the delivery and vertical portfolio teams your architecture function needs to influence.
Building the Capability
You do not need to replace your existing architecture team to develop this capability. The most effective approach is to identify the practitioners in your current architecture function who have the strongest engineering instincts and the deepest delivery credentials, and to invest deliberately in developing their platform engineering and software engineering capabilities through targeted assignments, training, and partnership with engineering-capable practitioners recruited from outside the function. Your first horizontal platform ownership — whatever you choose it to be — will serve as the most effective training ground for the engineering capability you need to develop. There is no substitute for the learning that comes from being accountable for building and operating a real system that real people depend on.
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. Build your architecture team with real software engineering capabilities | Enterprise Architecture Value Model. https://if4it.org/best-practices/enterprise-architecture-value-model/build-your-architecture-team-with-real-software-engineering-capabilities/ (accessed 2026-07-23).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers