Technical risk threatens project success. Architects must identify, assess, and mitigate risks before they become problems.
Risk Categories
Technical:
- Unproven technology
- Integration complexity
- Performance uncertainty
Organizational:
- Skill gaps
- Team availability
- Vendor dependency
External:
- Regulatory changes
- Market shifts
- Supply chain
Risk Assessment
Rate each risk:
| Risk | Likelihood | Impact | Priority |
|---|---|---|---|
| DB scaling issues | Medium | High | High |
| API breaking changes | Low | High | Medium |
Mitigation Strategies
Avoid: Don't take the risk Transfer: Insurance, contracts Mitigate: Reduce likelihood or impact Accept: Live with it
Spikes and Proofs of Concept
Reduce uncertainty through experimentation:
Spike: Can we achieve 10k requests/second?
Timebox: 2 days
Success criteria: Documented approach
Risk Monitoring
Track risks throughout the project. New information changes risk profiles.