<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-19T23:48:56Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/121797" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/121797</identifier><datestamp>2022-01-13T07:55:19Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">Bruce G. Cameron.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Prouillet-Leplat, Jean-Michel.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Engineering and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Massachusetts Institute of Technology. Engineering and Management Program</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2019-07-18T20:30:18Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2019-07-18T20:30:18Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2019</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2019</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://hdl.handle.net/1721.1/121797</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">1103605641</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from PDF version of thesis.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (pages 73-74).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The pace of technology development shapes the landscape of almost every industry today. The words innovation, digital transformation, process automation are synonyms of success. The most successful corporations nowadays understand that technology should not be a standalone initiative gated within the IT department, to achieve an impact, technology must become a part of company's DNA along with its brand strategy or culture. The study examines the role of the CTO, which has been relatively poorly characterized by research to date. This research characterizes how CTOs view their job description, notably how they balance internally-focused attention with external responsibilities. This work draws on a quantitative analysis of 100 CTOs from Linkedln to understand their tenure duration and career history. We also collected primary data through interviews with 20 CTOs to understand their activities, responsibilities and the context that influences the span of impact. This work posits five Personas of CTOs: The Evangelist, the Anchor, the Coordinator, the Visionary, and the Strategist in various corporate settings. The study further examines the relationship between the career path of the CTO, his/her responsibilities and impacts in current role. The study indicates that the CTOs' responsibilities align most closely with the Coordinator and the Anchor personas. Both responsibilities and personas showed coherent distribution relative to the company maturity giving the opportunity to draw a CTOs' lifecycle where the Anchor is more likely to be found in early companies and the Coordinator in mature companies. Among the CTOs studied, 10% to 20% do not have a pure technical background, 40% are not involved in product delivery and only 36% had previously served as a CTO in another firm. The data also shows that CTOs would like to be highly collaborative and cross-functional, and desire proximity to the CEO.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Jean-Michel Prouillet-Leplat.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M. in Engineering and Management</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="collection" lang="en_US">S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">80 pages</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">MIT theses are protected by copyright. They may be viewed, downloaded, or printed from this source but further reproduction or distribution in any format is prohibited without written permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Engineering and Management Program.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">What defines a great CTO?</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">What defines a great chief technology officer?</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="imported" lang="en_US">2019-07-18T20:30:15Z</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="degree" lang="en_US">Master</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="department" lang="en_US">SysDes</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="c916abf6-1aef-4d3c-b55c-b5dd6fcbde24">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>What defines a great CTO?&lt;/Title>
   	&lt;Subtitle>What defines a great chief technology officer?&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2019&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Prouillet-Leplat, Jean-Michel.&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>Engineering and Management Program.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>The pace of technology development shapes the landscape of almost every industry today. The words innovation, digital transformation, process automation are synonyms of success. The most successful corporations nowadays understand that technology should not be a standalone initiative gated within the IT department, to achieve an impact, technology must become a part of company&amp;apos;s DNA along with its brand strategy or culture. The study examines the role of the CTO, which has been relatively poorly characterized by research to date. This research characterizes how CTOs view their job description, notably how they balance internally-focused attention with external responsibilities. This work draws on a quantitative analysis of 100 CTOs from Linkedln to understand their tenure duration and career history. We also collected primary data through interviews with 20 CTOs to understand their activities, responsibilities and the context that influences the span of impact. This work posits five Personas of CTOs: The Evangelist, the Anchor, the Coordinator, the Visionary, and the Strategist in various corporate settings. The study further examines the relationship between the career path of the CTO, his/her responsibilities and impacts in current role. The study indicates that the CTOs&amp;apos; responsibilities align most closely with the Coordinator and the Anchor personas. Both responsibilities and personas showed coherent distribution relative to the company maturity giving the opportunity to draw a CTOs&amp;apos; lifecycle where the Anchor is more likely to be found in early companies and the Coordinator in mature companies. Among the CTOs studied, 10% to 20% do not have a pure technical background, 40% are not involved in product delivery and only 36% had previously served as a CTO in another firm. The data also shows that CTOs would like to be highly collaborative and cross-functional, and desire proximity to the CEO.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>