Technology Strategy
How a CTO builds a technology strategy that serves business strategy: diagnosis, guiding policies, coherent actions, a one-page strategy and how to keep it alive.
Executive explanation
A technology strategy explains how technology will create advantage for the business over the next 2–3 years, and what the company will and will not do to get there. Using Richard Rumelt's structure (Good Strategy Bad Strategy), it has three parts: a diagnosis of the challenge, a guiding policy for dealing with it, and coherent actions. A list of goals or technologies is not a strategy.
Business scenario
A B2B logistics company (hypothetical) is losing deals to software-first competitors. Its platform was built for one country, releases quarterly, and sales promises custom integrations that engineering cannot deliver.
Decision framework: one-page technology strategy
| Section | Content for the scenario |
|---|---|
| Business context | Win mid-market shippers in 5 new countries; target 40% revenue from software subscriptions |
| Diagnosis | Monolithic single-country platform, bespoke integrations per customer, slow releases, no data products |
| Guiding policies | 1) Productize integrations (APIs and connectors, no custom code per customer). 2) Multi-country, multi-tenant platform. 3) Buy commodity (billing, CRM, identity), build differentiation (routing optimization, visibility). 4) Data as a product for customers |
| Coherent actions (12–18 months) | Public API platform + partner connectors; tenancy and localization framework; move to cloud landing zone; launch shipment visibility data product; reorganize into domain-aligned product teams |
| Metrics | Time to onboard a customer (90 → 14 days), release frequency (quarterly → weekly), % revenue from subscriptions, infra cost per shipment |
| What we will not do | Custom code branches per customer; build our own billing; multi-cloud |
Keeping it alive
Review quarterly against metrics, tie funding decisions to it, communicate it repeatedly (teams should be able to explain the guiding policies), and update it when the business strategy changes.
Example
[!FACT] Amazon's 2002-era internal mandate that all teams expose data and functionality through service interfaces (widely reported from a memo attributed to Jeff Bezos) is often cited as a technology policy that enabled both internal agility and, later, AWS.
CTO interview questions and model answers
How do you create a technology strategy in your first 100 days?
Listen first: business strategy and economics with the CEO/CFO, customer pain with sales and support, technical reality with engineers (architecture, debt, incidents, delivery metrics). Diagnose the two or three critical challenges, propose guiding policies, socialize them, then publish a one-page strategy with measurable outcomes and a first-year roadmap.
How do you balance innovation with keeping the lights on?
Make the allocation explicit (for example 60% roadmap, 20% platform and debt, 10% reliability, 10% exploration), adjust based on metrics like incident load and delivery speed, and protect exploration with time-boxed bets that have clear kill criteria.