
Enterprise Architecture Review & Decision Framework
Evaluate complex enterprise architectures with structured decision frameworks
What You Can Do
You systematically analyze multi-layered enterprise architectures, identify critical trade-offs across scalability, cost, and risk, and generate documented decisions that align technical choices with business strategy. This skill produces comprehensive architecture reviews that expose hidden dependencies, quantify implementation trade-offs, and deliver prioritized, actionable recommendations backed by formal Architecture Decision Records.
Features
Evaluate your full technology stack across infrastructure, platform, application, and data layers to identify bottlenecks, inefficiencies, and technical debt.
Compare architectural options side-by-side across scalability, cost, operational complexity, and risk dimensions with quantified metrics.
Generate formal ADRs that document the context, alternatives evaluated, chosen solution, and consequences of major architectural decisions.
Identify single points of failure, vendor lock-in risks, data flow vulnerabilities, and technology debt hotspots that could impact reliability or growth.
Compare build-vs-buy options with total cost of ownership analysis, integration effort, operational overhead, and strategic fit assessment.
Create phased implementation plans with sequenced changes, rollback procedures, effort estimates, and success metrics for architectural transitions.
Map technical recommendations to business outcomes, compliance requirements, budget constraints, and strategic objectives across leadership.
Rank architectural improvements by business impact, implementation effort, risk reduction, and resource requirements to focus investment decisions.
Example Output
Architecture Review Excerpt
Current State Risk Assessment
- Monolithic backend with 15 partially extracted microservices
- PostgreSQL with read replicas (no sharding strategy)
- Scaling limit at ~100k RPS; manual failover process
- Risk Score: 7/10 (high coupling, inconsistent reliability)
Key Trade-off: Monolith vs. Full Microservices
| Criterion | Current Monolith | Microservices |
|---|---|---|
| Time to Scale | 6-12 months | 12-18 months |
| Team Autonomy | Limited | High |
| Operational Complexity | 2/10 | 8/10 |
| Cost @ 100k RPS | $180k/year | $220k/year |
| Deployment Frequency | Weekly | Daily per service |
Architecture Decision Record: Event-Driven Order Processing
- Context: Order latency increasing with transaction volume
- Decision: Implement Kafka-based async order queue
- Consequences: +8 weeks effort, -40% p99 latency, +$25k/year operations
- Alternatives rejected: AWS SQS (vendor lock-in), cron jobs (insufficient throughput)
- Status: Approved, Q3 2026 execution
Ranked Recommendations
- Extract payment microservice (Q3 | Business Impact: revenue protection | Effort: 8 weeks)
- Implement read scaling strategy (Q4 | Impact: -$40k annual cost | Effort: 4 weeks)
- Standardize API gateway (Q1 2027 | Impact: 20% ops reduction | Effort: 6 weeks)
What's Included
- Current State Architecture Analysis: Comprehensive documentation of existing layers, interdependencies, technical debt, and risk scoring.
- Multi-Option Evaluation Workbook: Detailed trade-off matrices comparing 3-5 architectural approaches across cost, complexity, reliability, and strategic fit.
- Executive Summary Report: Business-focused recommendations with ROI estimates, strategic implications, and alignment with organizational goals.
- Formal Architecture Decision Records: Complete ADRs for each major decision including context, alternatives evaluated, rationale, and implementation consequences.
- Phased Implementation Roadmap: Sequenced execution plan with effort estimates, resource requirements, dependencies, and rollback procedures for each phase.
- Risk & Dependency Assessment: Failure mode analysis, single point of failure identification, vendor lock-in assessment, and mitigation strategies ranked by priority.
Who It's For
- Enterprise & Solutions Architects
- VP/Director of Engineering
- Technical Program Managers
- CTO/Technology Leaders
- Engineering Leaders Evaluating Build-vs-Buy Decisions
Best For
- Architecture reviews before major system refactors or migrations
- Vendor and technology platform evaluation
- Scaling decisions when technical limits are approached
- Cross-team alignment on multi-year technical strategy
- Risk assessment and technical debt prioritization







