Eight things we believe about technology leadership
Not a checklist. Not a methodology. Just a set of convictions we’ve built over years of working inside technology functions, watching leaders succeed, watching them stall, and learning to tell the difference.
Where this comes from
TECHSHIN is an anagram of Hitchens. That’s not a coincidence. Timothy built this model from the inside out, not from academic research or consulting theory, but from being embedded in technology functions, watching what separates leaders who perform from leaders who plateau. The eight domains below are the result. They map to the letters of the name. More importantly, they map to the reality of what technology leadership actually demands.
We use these eight beliefs to guide every conversation we have, every engagement we take on, and every leader we work with. They are the lens through which we see technology leadership. If you share most of them, we will probably work well together.
The eight domains of technology leadership
Every letter in TECHSHIN stands for a domain. Every domain is a belief about what great technology leadership actually requires.
Thinking
We believe the quality of a leader’s thinking is the single biggest constraint on what their team can achieve. Strategy, judgement, systems awareness: these aren’t personality traits. They’re capabilities. And they can be developed.
Execution
We believe delivery is a discipline, not a personality trait. The gap between what a technology function plans and what it ships is almost always a leadership gap. High standards, follow through, and a genuine bias for getting things done are learnable, but only if someone is willing to hold the mirror up.
Clarity
We believe most leadership problems are communication problems in disguise. When a CTO can’t get buy-in, when a project loses scope, when a team moves in the wrong direction, trace it back and you’ll almost always find a clarity problem at the root. Vision that lives in your head isn’t a vision. It’s a secret.
Habits
We believe consistency compounds. A leader’s daily habits (how they use their time, what they repeat, what they let slide) are the most honest signal of their actual priorities. Good intentions without reliable habits produce the same result every time: nothing changes.
Structure
We believe the best leaders build systems so the work doesn’t depend on them being in the room. A technology function that only performs when the CTO is present isn’t a function. It’s a bottleneck. Structure (how the team is designed, how decisions are made, how work gets delegated) is what makes performance repeatable.
Harmony
We believe a team that can’t function without friction isn’t a team. It’s a group of people with shared calendar invites. Cross-functional relationships, emotional fluency, and the ability to build real cohesion: these are not soft skills. They are the difference between a function that performs and one that burns through people.
Innovation
We believe technology functions that stop asking “what’s possible” become a cost centre, not a competitive advantage. Innovation isn’t a brainstorming session or a hackathon. It’s a loop: customer feedback, product instinct, creative thinking, and market awareness. Leaders either build it into how they work or leave it out entirely.
Navigation
We believe technical brilliance without political awareness is a ceiling, not a foundation. The best technology leaders know how to manage upward, read the room, position themselves and their team, and build relationships with stakeholders who don’t speak their language. That’s not playing politics. That’s how you get things done.
How these beliefs show up in the work
We don’t use TECHSHIN as a scorecard. There’s no assessment tool, no report at the end, no percentile ranking. These eight domains are the lens we bring into every embedded engagement: the questions we’re asking, the patterns we’re watching for, and the areas we push on when we see gaps.
Most technology leaders are strong across three or four of these domains and have real gaps in two or three. That’s not a failure. It’s the starting point. The work is figuring out which gaps are limiting performance right now, and closing them in a way that sticks.
If you’re wondering where your technology leader stands, the fastest way to find out is a conversation. Not a questionnaire. Thirty minutes of real discussion tells us more than any diagnostic tool.
Find out where the gaps are
Most technology leaders know something isn’t working. They’re not always sure what. We usually can tell within the first conversation. If you want an honest read on where your technology function stands, that’s where we start.