CTO Technology Roadmap & Planning 4 — Questions and Answers
Question 1: What is the MAIN purpose of a technology radar in the context of roadmap planning?
- To monitor network security vulnerabilities in real time
- To visualize the adoption status of technologies across four quadrants: Adopt, Trial, Assess, and Hold (Correct answer)
- To track competitor technology investments on a live dashboard
- To document all APIs used in production systems
Correct answer: To visualize the adoption status of technologies across four quadrants: Adopt, Trial, Assess, and Hold
A technology radar (popularized by ThoughtWorks) categorizes technologies by readiness and adoption guidance for engineering teams.
Question 2: A CTO is preparing a 3-year technology roadmap for an enterprise that is still running significant on-premises infrastructure. What planning approach is MOST appropriate?
- Plan an immediate 'lift and shift' of all systems to the cloud in year one
- Design a phased hybrid cloud strategy that migrates workloads based on business priority and technical readiness (Correct answer)
- Maintain all on-premises systems unchanged for the full 3 years
- Outsource all infrastructure decisions to the cloud vendor's professional services team
Correct answer: Design a phased hybrid cloud strategy that migrates workloads based on business priority and technical readiness
A phased hybrid approach balances migration risk with business continuity while moving toward a target architecture.
Question 3: Which metric BEST indicates whether a technology roadmap is delivering business value over time?
- Number of roadmap items completed per quarter
- Business outcomes achieved (revenue growth, cost reduction, NPS improvement) attributable to technology initiatives (Correct answer)
- Lines of code written by engineering teams
- Number of new technologies adopted annually
Correct answer: Business outcomes achieved (revenue growth, cost reduction, NPS improvement) attributable to technology initiatives
Roadmap success should be measured by business outcomes, not output metrics like completion count or velocity.
Question 4: What is the role of 'enabling constraints' in technology roadmap planning?
- Budget and headcount limits that restrict which initiatives can be planned
- Guardrails such as security policies, compliance requirements, and architectural standards that shape how initiatives are executed (Correct answer)
- External market pressures that force pivots in technology strategy
- Time-boxing sprints to prevent scope creep
Correct answer: Guardrails such as security policies, compliance requirements, and architectural standards that shape how initiatives are executed
Enabling constraints are non-negotiable guardrails (compliance, security, architecture principles) that define the boundaries within which roadmap initiatives must operate.
Question 5: When should a CTO escalate a technology roadmap decision to the CEO or board?
- Whenever a new software library is selected
- When a roadmap decision has material business risk, significant budget impact, or strategic implications beyond the CTO's authority (Correct answer)
- After every quarterly planning cycle as standard practice
- Only when the technology roadmap falls behind schedule
Correct answer: When a roadmap decision has material business risk, significant budget impact, or strategic implications beyond the CTO's authority
Escalation is appropriate when decisions carry business risk or resource implications that exceed the CTO's delegated authority.
Question 6: A CTO wants to ensure the technology roadmap reflects input from engineering teams, not just top-down executive priorities. Which practice BEST achieves this?
- Allow engineers to self-assign to any roadmap item they prefer
- Run structured bottom-up planning sessions where engineering teams identify technical risks, opportunities, and debt alongside top-down strategy (Correct answer)
- Have engineers vote anonymously on roadmap items before finalization
- Rotate roadmap ownership to a different engineering team each quarter
Correct answer: Run structured bottom-up planning sessions where engineering teams identify technical risks, opportunities, and debt alongside top-down strategy
Bottom-up planning sessions surface critical technical context that executives lack while maintaining strategic alignment.
Question 7: What is 'roadmap drift' and why is it a concern for a CTO?
- When the roadmap shifts toward longer timelines due to Agile velocity improvements
- When executed work diverges from the planned roadmap due to ad hoc requests, scope creep, or poor change management (Correct answer)
- When cloud costs drift above the planned infrastructure budget
- When the roadmap template is updated to a new visual format mid-year
Correct answer: When executed work diverges from the planned roadmap due to ad hoc requests, scope creep, or poor change management
Roadmap drift erodes strategic focus as unplanned work accumulates, making it difficult to achieve original business objectives.
CTO Technology Roadmap & Planning 4
What is the MAIN purpose of a technology radar in the context of roadmap planning?