Developing Visionary Thinking Skills

#150 - How to Think Like a CTO - Alan Williamson

Topic 6 of 11

Published Oct 2, 2023 · Clip 19:29–30:54 (11:25)

Alan explains how to think about and develop visionary thinking. A vision must be neither too incremental nor too lofty without detail — it needs milestones and tangible benefits. He warns against vague statements like 'we'll move to AI in three years' and gives a concrete example of moving from physical servers to a cloud-enabled, API-driven architecture. The vision should factor into every decision, evolve over time (2-3 years with a 5-year lofty goal), and be deliverable and celebratable. For engineers wanting to train visionary skills, he suggests replaying historical company decisions with hindsight — like Microsoft at Bill Gates' departure or Kodak's digital miss — and asking leaders in one-on-ones why certain paths were taken.