Comprehensive CTO Advisor

Strategic technology leadership frameworks covering technical strategy, team scaling, architecture decisions, tech debt management, vendor evaluation, and engineering culture — designed for CTOs and VPs of Engineering.

When to Use

Use these frameworks when:

• Making build vs buy vs partner decisions
• Scaling an engineering team (10 → 50 → 200+)
• Managing tech debt alongside feature delivery
• Evaluating technology stack changes
• Preparing technical strategy for board presentations

Use operational tools when:

• Day-to-day sprint management → Agile/Scrum tools
• Individual code review → code review tools
• Incident response → on-call playbooks

Quick Start

Technical Strategy Document

Copy
## Technical Strategy: {Year}

### Current State
- Team: {size} engineers across {n} teams
- Stack: {primary technologies}
- Infrastructure: {cloud/on-prem, key services}
- Tech debt: {severity assessment}
- Key metrics: deploy frequency, MTTR, change failure rate

### Strategic Priorities
| Priority | Objective | Investment | Timeline |
|----------|-----------|-----------|----------|
| 1. {priority} | {what success looks like} | {team, $} | Q1-Q2 |
| 2. {priority} | {what success looks like} | {team, $} | Q2-Q3 |
| 3. {priority} | {what success looks like} | {team, $} | Q3-Q4 |

### Technology Decisions
| Decision | Options | Recommendation | Rationale |
|----------|---------|---------------|-----------|
| {decision} | A, B, C | {choice} | {why} |

### Tech Debt Plan
| Debt Item | Impact | Effort | Action | Timeline |
|-----------|--------|--------|--------|----------|
| {item} | H/M/L | H/M/L | Fix/Accept/Mitigate | Q{n} |

Build vs Buy Decision Framework

Copy
## Decision: {capability}

### Criteria Scoring (1-5)
| Criteria | Build | Buy | Weight |
|----------|-------|-----|--------|
| Core differentiator? | {1-5} | {1-5} | 3x |
| Time to value | {1-5} | {1-5} | 2x |
| Total cost (3 year) | {1-5} | {1-5} | 2x |
| Team capability | {1-5} | {1-5} | 1x |
| Maintenance burden | {1-5} | {1-5} | 1x |
| Integration complexity | {1-5} | {1-5} | 1x |

### Recommendation: {Build/Buy/Partner}
### Rationale: {2-3 sentences}

Core Concepts

Engineering Team Scaling

Team Size	Structure	CTO Focus	Key Hire
1-5	One team, CTO codes	Architecture + coding	Senior engineers
5-15	2-3 teams, tech leads	Architecture + process	Engineering managers
15-50	Squads, guilds	Strategy + culture	VP Engineering
50-200	Departments, platform teams	Strategy + org design	Directors, Staff engineers
200+	Business units	Vision + executive alignment	SVPs, Distinguished engineers

Tech Debt Management

Type	Example	Strategy
Code debt	Duplicated logic, poor abstractions	20% sprint capacity for cleanup
Architecture debt	Monolith that should be microservices	Quarterly investment projects
Infrastructure debt	Manual deployments, no monitoring	Platform team ownership
Knowledge debt	Undocumented systems	Doc sprints, pair programming
Dependency debt	Outdated libraries, EOL frameworks	Automated dependency updates

DORA Metrics

Metric	Elite	High	Medium	Low
Deploy frequency	On demand	Daily-weekly	Monthly	< monthly
Lead time	< 1 day	1 day - 1 week	1 week - 1 month	> 1 month
Change failure rate	< 5%	5-10%	10-15%	> 15%
MTTR	< 1 hour	< 1 day	< 1 week	> 1 week

Configuration

Parameter	Description
company_stage	Startup, Growth, Enterprise
team_size	Current engineering headcount
primary_stack	Core technology stack
deployment_model	Cloud, hybrid, on-prem
dora_targets	Target DORA metric levels
debt_budget	% of capacity for tech debt

Best Practices

1. Allocate 20% capacity for tech debt — it compounds if ignored, but 100% debt cleanup stalls features
2. Build what differentiates, buy everything else — internal auth systems don't win customers
3. Hire engineering managers before you need them — scaling without management creates chaos
4. Measure DORA metrics — they correlate with both engineering effectiveness and business outcomes
5. Make reversible decisions quickly — only deliberate on architecture decisions that are hard to undo
6. Communicate strategy to the whole team — engineers make better decisions when they understand the why

Common Issues

Feature delivery slows as team grows: Add platform teams to handle cross-cutting concerns. Implement clear team boundaries and APIs. Reduce inter-team dependencies.

Tech debt is out of control: Classify by impact and effort. Fix high-impact, low-effort items first. Make debt visible with a tech debt register that leadership reviews quarterly.

Can't hire fast enough: Invest in employer branding. Speed up the interview process (< 2 weeks). Offer competitive compensation. Consider remote/distributed teams.