follow awadallah at http://twitter.com

March 5, 2013

What does a CTO do?

Posted in Category: Work — amr @ 9:53 pm | link | | comments (3)
Share

I frequently get asked this question, and it is a question that I sought out to find an answer for a little less than a year ago (when I became full time CTO at Cloudera). I did a bunch of online research and talked to a number of enterprise software CTOs whom I look up to (listed at end). I summarize my findings by answering four core questions: (1) what is the CTO Mission? (2) how to measure the CTO? (3) How should the CTO split his/her time internally vs externally? then finally (4) what are the specific responsibilities of the CTO towards the main constituents inside the organization?

Note that this role description is focused on pure CTOs, as opposed to CTOs whom still own the operational aspects of the engineering organization, it is also biased towards enterprise CTOs vs other domains.

1. What is the Mission of the CTO?

The Mission for the CTO can be summarized across three axes:

A) Fiduciary for Long-Term Technical Strategy:

  • The CTO must effectively hold, develop, articulate, and continually evolve the company’s strategic technical direction.
  • The CTO is responsible for making sure the company continues to have the best technology offering in a dynamically-evolving highly-competitive space.
  • The CTO brings the proper balance between business and technology strategy by effectively connecting the outside world with the inside through distilling information into the key trends that indicate where the company needs to go next, thus aligning the company’s technology strategy with its business strategy.

B) Technical Evangelist:

  • The CTO must inspire/excite people internally around the long-term vision of the company, as well as convince outsiders that this is where the world is going to be, and that his/her company is the best choice to take them there.
  • The CTO must speak with authority about the market needs, must be credible with customers, and must be able to articulate the business value and ROI to a variety of audiences.

C) Spiritual Leader for the engineers and maintainer of the technical culture:

  • The CTO must rally the engineering organization towards the long-term technical goals of the company.
  • The CTO must be able to inspire new engineers to join the engineering organization and must help in the sourcing/identification of such talent.
  • The CTO must help set and maintain the technical culture to make sure the company can continue to retain and attract top technical talent.

2. How to measure the CTO performance?

I could think of three metrics which I outline below:

A) Tech Strategy Alignment:

This is a binary metric, if the company misses a key tech trend then counts against. Also, if there is a significant misalignment between the business and technology strategies then counts against. Towards that end, I highlight this quote which is attributed to Greg Papadopolous [x-CTO of Sun]:

“The CFO is not responsible for making revenue every quarter, but if there is a big surprise, fire her. Similarly, the CTO isn’t responsible for delivering products every quarter, but if he misses a key technical inflection point (e.g. the internet), fire him.”

B) Health of Engineering Culture:

This can be measured by doing a survey of the technical organization to ensure that they are productive and happy at same time. A lagging indicator is significant attrition of top engineering talent, or inability to attract new top talent to the company.

C) Internal CSAT:

In many ways the CTO, similar to the CFO, is a service center to all the other organizations in the company (more on these responsibilities later). Thus an appropriate metric is a weighted customer satisfaction score across these organizations (aka CSAT). If these internal organizations don’t feel they are getting value add out of the CTO, then it is time to fire him.

3. How should the CTO split his/her time internally vs externally?

There is no perfect answer for this one, but the right answer is a bit of both. The CTO will not be able to do a good job inside without having knowledge of the outside, and vice versa. The mix of external/internal is ultimately something that should come out of how the CTO can be of most help to the business. Also there’s travel/family to consider, you have to work sustainably, so find your own sweet spot. The answer will also change as a function of what stage the company is at. With that background this is how I split my time today:

A) External: 70% of time

  • Sales/Customers 35%
  • Marketing/Evangelism/Analysts 20%
  • Business Development/Partners 15%

B) Internal: 30% of time

  • Digest the info collected externally then funnel that knowledge to the appropriate internal teams.
  • Continuously connect engineering, product & business to ensure that the vision articulated publicly is where the company indeed is going, and that the technology roadmap aligns with that vision (especially for new initiatives).
  • Support the marketing team with collateral/white-papers that articulate the company vision.
  • Stay on top of engineering culture, processes, and retention.
  • Shepard for the Intellectual Property portfolio.

4. So what are the CTO’s specific responsibilities for each organization within the company?

 There are five main constituents that the CTO serves: (1) CEO/Strategy, (2) Engineering/Product, (3) Sales, (4) Business Development, and (5) Marketing. Below I list some of the key responsibilities towards each of these constituents.

A) CEO/Strategy

  • Predict and stay ahead of any technical inflection points that might significantly affect the company.
  • Advise the CEO (and CFO/COO) on the long-term technical strategic direction of the company and where to, or to not, make large strategic technical bets.
  • Provide the CEO with different “options” on the technical direction of the company and provide sufficient information for deciding what is the best option to take at any given time.
  • Be a sounding board for the CEO by providing a neutral view which puts the company’s long-term interests above all else. The CTO, similar to the CFO, is in a unique position to do this effectively since he/she doesn’t directly own significant business resources per se.

B) Engineering/Product:

  • Though the CTO isn’t responsible for the day-2-day tactical delivery, he should work closely with the VPs of Products & Engineering to make sure that the overall development direction is well aligned with the company’s strategic technical vision.
  • The CTO should influence the prioritization of resources across large strategic technical bets, but should not be involved in the daily execution once the priorities are set. In fact, it is important to let go entirely of obsessing over the day-2-day execution (which can be hard to let go of), but that is essential so you can focus on the long-term strategic thinking without being encumbered by the immediate constraints.
  • One of the key challenges for the CTO is how to champion people, projects and ideas without stepping on the toes of Product/Engineering management. This is why it is necessary that you seek training to become a strong influencer, and be very selective regarding which ideas you plan to focus your energy on (pick your battles).
  • You need to be a sounding board for the VP of Engineering, allow him to vent, and help him with brainstorming about the different challenges that the development team is facing. In many ways, the CTO and the VP of Engineering need to be bonded at the hip, it is a very critical relationship, so spend significant time on this.
  • Help with the recruiting/retention efforts (this includes ties to Academia).
  • Continuously optimize across the whole organization to avoid any duplication of effort and encourage cross-department fertilization.
  • Ensure alignment of the greater technical organization and, when necessary, arbitrate techno-centric turf scraps, architecture conflicts, etc.
  • Foster innovation by organizing periodic hackathons and by being a steward of innovation in the early stages.
  • Serve as master architect across product lines. I don’t do much of this at Cloudera though, we have a number of truly amazing engineers who are way better architects than I am, so best I can do is to simply get out of their way! (I only get involved if there is a strong conflict, which luckily is rare at Cloudera).

C) Sales:

  • Partner with the sales organization to effectively close customer accounts.
  • Partner with the sales organization to effectively close customer accounts.
  • Partner with the sales organization to effectively close customer accounts.
               (3x replication intended for emphasis)
  • Support the sales organization by building strong relationships with peers at strategic customer accounts.
  • Participate in customer meetings to articulate the long term technology road map hence strengthening the customer’s confidence that our company is leading the industry.
  • Speak with authority about the market; listen to customer needs; quickly understand their issues; and give good advice on the company’s products to the customers.
  • This is very important: know when to say “I don’t know”, then connect the customer with the proper resource whom can go deeper on the question being asked. A good CTO should never ever make shit up on the fly :)

D) Business Development and Partnerships:

  • Support the business development team in strategic partner engagements and maintain good relationships with peers at these organizations.
  • Provide technical due diligence of partner technologies and acquisition targets to make sure they properly fit with the company’s platforms, offerings, and culture.
  • The CTO should keep track of all the technology startups in the same space, and have them stack ranked based on what he/she can glean about their prospects. The CTO should have clear thoughts about: possible acquisition targets, what expertise is the company missing? which companies are doing the best work across all of the ancillary areas? which companies have the best technical teams? what could competitors buy that would hurt the company? etc. I rely significantly on my cofounder (Jeff Hammerbacher) for this part. 
  • Represent the company at select technical associations to re-enforce the company’s presence and voice with partners.
  • Predict if a new partner technology would have significant impact on the long-term technological roadmap for the company (e.g. a new type of storage or compute device).
  • Predict long-term competitive trends due to the constant shifts in the market.

E) Marketing:

  • Serve as public face of technology for the company.
  • Evangelize the company vision and technical direction through conferences, speaking engagements, and press/media/analyst activities.
  • Maintain good relationships with designated key industry analysts.
  • Support the marketing team in building a large active community around the company’s products (meetups, hackathons, industry conferences, etc).
  • Social engagement marketing through twitter, blog posts, articles/whitepapers, etc.

In summary, a great CTO can be invaluable for their organization as he/she has the luxury to step back and see the forest through the trees, and the ability to be the voice of the customer and of the employee. Whether you are a budding CTO, or a CTO veteran, I really hope you find this article useful. Please don’t hesitate to let me know if you disagree with any of the concepts presented here, or if there are major areas of responsibility that you think I overlooked.

Cheers,

— amr

PS: I would like to acknowledge the following folks/references:

 PPS: A good CTO must also know how to be an active participant in the VIM :)

 

Share

• • •

3 Comments »

  1. One area that I would change is that a CTO also needs to be a CPO. Mixing Engineering/Product is wrong and causes the failure of many CTOs. A truly great CTO is also a product visionary, know how to marry a great product with technology and how to utilize technology to create great products. CTOs that are just engineering focus tend to simply over engineer. You need to be part of the products, helping to define them, review them, question them, care about the interaction design, how every pixel looks and generally care about the product. A great CTO is also a great Chief Product Officer.

    Comment by David — March 8, 2013 @ 4:49 am
  2. Most comprehensive and structured description of what a CTO does. I think the duties and proportions change based on type of company. For instance a startup vs a big corporation.

    Comment by Abbas — May 11, 2013 @ 4:03 pm
  3. I’m not a CTO and I know that I want be but I found that this post works with even CEOs in the terminology of what they do?
    Also I understood what a CTO responsibilities and how S/he should look for a position in a company.

    Comment by Samar Ali — December 8, 2014 @ 6:50 am

Comments RSSTrackBack URI

Leave a comment

Powered by: WordPress • Шаблон: ADMIN-BG • 31 queries. 0.528 seconds.