The Become CTO Methodology
Three pillars to balance, seven core moves to develop, and four domains where capability must be built. This is the complete model for technology leadership.
How it fits together
Become CTO is built on a simple observation: the best technology leaders aren't the most technical. They're the ones who understand the full picture of what the position demands and can move fluidly between different modes of leadership.
Over 15 years of research across 80+ technology organisations, a clear pattern emerged. Technology leaders get stuck being order takers because they don't have a model for what "strategic" actually means in practice. They know they should be more strategic, but nobody has shown them what that looks like day to day.
The Become CTO methodology gives you that model. It's made up of four interconnected parts, and they work in sequence. The LIT Framework shows you the three pillars to balance. The 7 Archetypes reveal which balance you need for your stage. The 7 Moves are how you develop the capability. And the 4Ps map the 32 specific learning areas where development happens.
The LIT Framework
Every technology leader must balance three pillars: being a Leader, an Innovator, and a Technologist. Created in 2011, the LIT Framework helps you understand which pillar you're operating from and when to shift.
Deep dive into LIT →The 7 Archetypes
Seven distinct CTO leadership profiles from Founder through Alchemist. Your archetype determines the pillar balance you need and your starting point across the 32 learning areas.
Explore the 7 Archetypes →The 7 Moves
Seven core capabilities that high performing technology leaders demonstrate consistently. These aren't abstract ideas. They're practical moves you can develop and apply.
Explore the 7 Moves →The 4Ps
People, Process, Product, and Profit. Four domains where technology leadership capability must be built. Each contains eight specific learning areas for a total of 32.
Explore the 4Ps & 32 Areas →The 4 Domains
Technology leadership spans four domains. You need capability across all of them, not just the technical ones.
People
Team capability, hiring, performance, culture, coaching, and developing leaders beneath you.
Process
Operating rhythm, decision making, governance, delivery cadence, and how the team actually works.
Product
Technical strategy, architecture, quality, innovation, and connecting technology to business outcomes.
Profit
Cost management, ROI, business value, efficiency, and demonstrating technology's impact on the bottom line.
Each domain contains 8 specific learning areas for a total of 32 capabilities across the methodology.