Score a Business-Unit CTO on Four Dimensions
Business-Unit CTO
Companion to The CTO You Actually Need · Updated 2026-09-29
| Dimension | Hiring evidence | 90 days | 180 days | One year |
|---|---|---|---|---|
| Unit business outcome | Led technology close to a P&L or customer mission | Unit priorities and constraints are understood | Agenda affects unit decisions and delivery | Technology contributes to unit growth, margin, customer, or resilience goals |
| Enterprise navigation | Improved local outcomes without bypassing shared obligations | Federal boundary and key dependencies are mapped | Real enterprise decisions move faster | Exceptions, shared services, and local autonomy have healthier economics |
| Relationship with group functions | Worked across CIO, CTO, CISO, data, and finance | Shared decisions and escalation are explicit | Recurring conflicts use the system | Unit and enterprise leaders trust the role to represent both truths |
| Local leadership | Built technology capability inside a business | Team and leadership gaps are credible | Necessary changes are underway | Unit has strong leaders and less dependency on enterprise rescue |
Critical failure examples. Optimizes local speed by transferring risk, becomes an enterprise policy messenger, or uses the matrix as an excuse for every delay.