AKF Partners

Abbott, Keeven & Fisher PartnersPartners In Hyper Growth

How Technical Should The CTO Be?

One of our earliest post was the Path To CTO/CIO, where we focused on not only the “path” but the path that would make you successful once you arrived in that position. One of the necessary skills that we mentioned you must gather along the way is “great technical experience”. We promised to revisit this topic in a later post so I thought I’d come back to this question of how technical does the CTO/CIO need to be? This is especially relevant for those individuals coming from a non-technical background but I think it is a question often asked by technologist as well. Do you need to have engineering and operations experience? Can you come from QA and become a CTO? Do you have to know how to code?

CTO and CIO jobs come in all shapes and sizes. In some businesses the CTO is the chief architect and not a manager, in others it is the VP or SVP of all technology teams. For the purpose of this discussion I’ll define the CTO/CIO as the role that has the technology organizations (such as engineering, quality assurance, operations, etc) reporting to them.

To be upfront about answering the question in the title of this post, I think a CTO should be very technical. I don’t think there is a prescribed path to the top technology job in a company and you don’t necessarily have to come up the technology ranks. I do, however, believe that possessing certain technical skills and experiences are far more likely to land you in that role than if you do not have them. More importantly, while these skills and experiences won’t guarantee your success in that role, they lack of them almost ensure problems or even failure. The skills and experiences that I mentioned fall into two categories, broad and deep.

Deep experiences and skills are ones that are most likely gained early in your career and should bring you proficiency in a subject area. For some this might be programming in a specific language, automating testing on a specific tool, or administering an operating system. If you believe Malcolm Gladwell in Outliers this process takes about 10,000 hours. Thinking of this in terms of travel or language, these deep experiences and skills are the kind you gain by living in a foreign country and becoming immersed in the culture and able to speak the language fluently. Deep experiences and skills are important because they develop in you a strong knowledge foundation that can be built upon when broadening your experiences. This deep foundation allows you to learn other technologies easier, similar to how proficiency in one foreign language makes the next one easier to learn. These deep experiences also give you a base of confidence that when peered with other experts provides credibility and when faced with uncertainty provides a history of solutions.

Broad experiences and skills are ones that are somewhat superficial but serve to give you a general understanding. Continuing our travel and language analogy, broad experiences and skills are the ones you acquire by spending a few weeks in another country and being able to get by asking for directions and food. The broad experiences that a CTO/CIO should have are working with multiple technology disciplines (engineering, quality assurance, architecture, operations, etc.) as well as business disciplines (marketing, finance, legal, etc). These experiences should serve to give you an understanding of their responsibilities, their day-to-day jobs, and most importantly their perspectives on technology and product development. You don’t have to have a job in each of these departments to gain this experience. Other ways to gain these include, acting as a liaison, serving on joint boards, working together on special projects, or volunteering to stay late to help the other teams accomplish their work.

Perhaps not prerequisites but rather as identifiers that will set you apart and prepare you well for the top technology role, look for establishing first deep skills and experiences. Once that foundation is firmly built then begin to broaden those through interdisciplinary work. Don’t forget that this is focusing of the technical skills and experiences. There are still other skills such as leadership, management, communication, and business that must be developed as well if you not only want the top technology job but want to keep it and do a great job while you are there. It’s not unusual for the most technical CTO’s to be the ones who need the most management and business coaching.

Having thrown down the gauntlet that a CTO must be technical it is only fair to address those who didn’t rise up through technology roles and are currently CTO’s or desire to be CTO’s.  We’ll save this for a future post but in the mean time break out a coding book.

Comments RSS TrackBack 4 comments

  • Jason Howe

    in June 23rd, 2012 @ 15:26

    I couldn’t agree with you more. We’re just getting out from under a 10 reign of a completely non-technical CIO. Its been a near disaster for the IT organization. First all IT meeting they said, “I know nothing about anything any of you do…” Yeah, it went about as well as you’d expect from there.

  • fish

    in June 23rd, 2012 @ 22:46

    Jason, thanks for the comment. Wow, I can’t imagine hearing that from a CIO. What a great way for a new boss to lose the respect of their team.

  • PLNDR Codes

    in October 31st, 2012 @ 02:21

    Looking forward to reading more. Great article post.Thanks Again. Fantastic.

  • Can a CIO be successful without IT experience? Define your terms!

    in November 23rd, 2012 @ 01:42

    […] Michael Fisher, “How Technical Should The CTO Be?” […]