Competency Model¶
Architect's Competency Model¶
| Developer | Architect & Lead Developer | Cross-Domain Architect | Chief Architect (Enterprise Architect) |
CTO | |
|---|---|---|---|---|---|
| Uncertainty | Low | Low | Middle | High | Very high |
| Business Know-How | Low or Middle | Middle | Middle | High | Very High |
| Technical Breadth | Limited | Middle | Middle or Broad | Broad | Comprehensive |
| Communication | Minimal | Middle | Middle | Extensive | Intensive |
| Technical Depth | Low or Middle or Deep | Middle or Deep | Middle or Deep | Middle | Middle |
| Execution Details | High | High | Middle | Less | Less |
| Project Delivery | Simple | Simple | Complex | Complex | Simple |
| Management Breadth | - | Small | Small | Middle | Large |
| Management Complexity | - | Low | Low | Middle | Large |
| Scope of Focus | Moduleļ¼ Current Requirements | Single Domain, Current Issues | Multiple Domains, Current Issues | Technical Department, Long-term goals | Company, Current + Future |
| Work Priorities | Code Design | Whole domain design | Cross-Domain Optimization | Global Technologies | Management &Strategy |
| Core Competencies | Structured Design | Solving horizontal Issues | Resolving Cross-Domain Conflicts | Making long term decision | Company Survival |