CTO Technology Roadmap & Planning 3 — Questions and Answers
Question 1: A startup CTO is creating the company's first technology roadmap. Which input is MOST critical to gather before drafting it?
- A list of open-source tools the engineering team prefers
- Business strategy, OKRs, and near-term product goals from leadership (Correct answer)
- Salary benchmarks for engineering roles
- A competitor's publicly shared engineering blog posts
Correct answer: Business strategy, OKRs, and near-term product goals from leadership
A technology roadmap must be anchored to business strategy and OKRs to ensure technology investments drive company goals.
Question 2: What is the key difference between a technology roadmap and a product roadmap?
- Technology roadmaps are public; product roadmaps are internal
- Technology roadmaps focus on platform, infrastructure, and engineering capabilities; product roadmaps focus on customer-facing features (Correct answer)
- Technology roadmaps are owned by the CTO; product roadmaps are owned by the CFO
- Technology roadmaps use Gantt charts; product roadmaps use story maps
Correct answer: Technology roadmaps focus on platform, infrastructure, and engineering capabilities; product roadmaps focus on customer-facing features
Technology roadmaps address the engineering foundation and capabilities that enable product roadmap delivery.
Question 3: A CTO is evaluating whether to include a major cloud migration in next year's roadmap. Which factor should carry the MOST weight?
- The vendor's marketing collateral and analyst ratings
- Total cost of ownership, migration risk, business impact, and strategic alignment (Correct answer)
- Whether competitors have already migrated
- Engineer preference for the new technology stack
Correct answer: Total cost of ownership, migration risk, business impact, and strategic alignment
Cloud migration decisions require a multi-dimensional evaluation of cost, risk, business value, and strategic fit.
Question 4: Which roadmap format is BEST suited for communicating technology strategy to a non-technical executive audience?
- A Jira backlog with sprint assignments
- A visual theme-based roadmap showing strategic goals and timelines without technical jargon (Correct answer)
- A detailed architecture diagram with component dependencies
- A spreadsheet of all open engineering tickets sorted by priority
Correct answer: A visual theme-based roadmap showing strategic goals and timelines without technical jargon
Theme-based visual roadmaps communicate strategic intent clearly to executives without overwhelming them with technical detail.
Question 5: What does 'capacity planning' mean in the context of a technology roadmap?
- Estimating server storage requirements for the next fiscal year
- Forecasting engineering headcount, skills, and infrastructure needed to deliver roadmap initiatives (Correct answer)
- Calculating the number of features a product can support
- Planning data center expansion for physical hardware
Correct answer: Forecasting engineering headcount, skills, and infrastructure needed to deliver roadmap initiatives
In roadmap context, capacity planning ensures that human and technical resources are sufficient to execute planned initiatives.
Question 6: A CTO's roadmap includes a dependency on a third-party API that may be deprecated. What should be added to the roadmap to manage this risk?
- A note to monitor the vendor's blog
- A contingency initiative to evaluate and onboard an alternative API within a defined timeframe (Correct answer)
- Removal of all features dependent on the API
- An immediate switch to the alternative API regardless of cost
Correct answer: A contingency initiative to evaluate and onboard an alternative API within a defined timeframe
A contingency initiative with a defined timeframe ensures the team is prepared before deprecation occurs.
Question 7: How should a CTO handle a situation where the technology roadmap must absorb an urgent, unplanned compliance requirement mid-year?
- Add the compliance work without removing anything else from the roadmap
- Reassess roadmap priorities, deprioritize lower-value items, and insert the compliance requirement with visible trade-off documentation (Correct answer)
- Delegate the compliance work entirely to a third-party vendor with no roadmap impact
- Delay the compliance work until the next annual planning cycle
Correct answer: Reassess roadmap priorities, deprioritize lower-value items, and insert the compliance requirement with visible trade-off documentation
Absorbing unplanned work requires explicit trade-off decisions and transparent communication about what gets deferred.
A startup CTO is creating the company's first technology roadmap.
Which input is MOST critical to gather before drafting it?