Technology Architecture
The infrastructure and platform standards underneath every application in the enterprise's portfolio.
9.3.1Definition
Technology architecture defines the infrastructure, platforms, and technical standards an organization builds on — approved cloud providers, deployment platforms (7.8), database standards, and security baselines — providing a consistent technical foundation across every application (9.2) rather than each team choosing independently.
9.3.2Why It Exists
Every team independently choosing its own cloud provider, database, and deployment platform produces an organization with no economies of scale, no shared operational expertise, and a security posture that varies unpredictably system to system. Technology architecture exists to establish deliberate, shared standards, so operational knowledge, security practices, and vendor relationships compound across the organization rather than fragmenting.
9.3.3Core Standards Areas
| Area | What it standardizes |
|---|---|
| Cloud/hosting | Approved providers and deployment platforms (7.8) |
| Data | Approved database technologies (5.1) and data governance rules |
| Security | Baseline security requirements (5.14) every system must meet |
| Integration | Approved patterns for inter-system communication (9.2) |
9.3.4Common Mistakes
- No enforced technology standards, resulting in dozens of teams independently choosing incompatible tools with no shared operational knowledge between them.
- Standards so rigid they block legitimate exceptions, forcing teams to work around governance rather than through it when a genuine edge case arises.
- Standards defined once and never updated, eventually mandating outdated technology long after better options exist.
9.3.5Best Practices
- Define technology standards with a clear, lightweight exception process for legitimate edge cases, rather than absolute rigidity.
- Review and update standards on a regular cadence as the technology landscape evolves.
- Tie standards explicitly to real benefits (security baseline, shared expertise, vendor leverage) so teams understand the rationale, not just the rule.