In 2011, Timothy J. Hitchens asked a simple question: why do brilliant technologists get stuck as order takers?
The answer became the LIT Framework, and the LIT Framework became the foundation for everything that followed.
Great technologists were getting promoted into CTO positions and then getting stuck. They could code brilliantly, architect systems, and ship products. But they weren't leading. They weren't influencing strategy. They weren't driving business outcomes.
The answer wasn't more technical skill. It never was. The answer was balance.
After studying technology leaders across dozens of organisations, a pattern emerged. The ones creating real impact weren't defined by any single strength. They moved fluidly between three distinct modes of operating. The ones who were stuck had over indexed on one mode and neglected the others.
Those three modes became the LIT Framework: Leader. Innovator. Technologist.
Each pillar demands different skills, different thinking, and different behaviours. The position requires all three.
Setting direction, building teams, creating clarity, and aligning the technology function with business strategy.
The Leader pillar is about people and direction. It's where you build trust with the executive team, develop your leaders, and create the conditions for everyone else to do their best work.
Driving change, enabling experimentation, managing risk, and finding better ways to solve problems.
The Innovator pillar is about progress and change. It's where you challenge assumptions, explore new approaches, and push the organisation to evolve its thinking about technology.
Understanding systems, making technical calls, building for scale, and maintaining the credibility that comes from deep technical knowledge.
The Technologist pillar is about depth and rigour. It's where you make the hard technical decisions and maintain credibility with your engineering team.
The difference between a technology leader who creates impact and one who just stays busy.
You shift between pillars depending on what the situation needs. Strategic conversation with the CEO in the morning. Technical architecture review after lunch. Coaching a senior engineer through a difficult decision in the afternoon.
Your team sees you as someone who understands the technology deeply but leads beyond it. You set direction. You create clarity. You're an Impact Maker.
You default to one pillar regardless of what the situation needs. Usually the Technologist pillar, because it feels safe and familiar.
Your CEO sees you as deep in the weeds but unable to connect technology to business outcomes. You're the smartest person in the room but nobody's following you. You're an Order Taker.
For over a decade, the LIT Framework helped individual CTOs see their imbalance and start to correct it. But in 2024, after working with 80+ organisations, something became clear.
Individual leaders can find their balance, but technology functions can't scale on the back of one person.
The real shift happens when the entire approach is systematic. When you know your CTO archetype and what pillar balance your business stage demands. When you can map capability gaps across 32 learning areas in People, Process, Product, and Profit. When you have a practical playbook of 7 core moves to build capability deliberately.
That's how the LIT Framework evolved into the Become CTO methodology. The framework is still the foundation. But now it sits inside a complete system for developing technology leaders and the teams around them.
Three pillars identified. Individual CTO coaching begins.
Full methodology: 7 Archetypes, 7 Moves, 4Ps, 32 learning areas.
Commercial practice applying the methodology with CEOs and CTOs.
Proven across startups, scaleups, and established technology teams.
The LIT Framework is where it started. Become CTO is the complete methodology. Techshin Partners is where it gets applied to real technology teams.