<?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-21T17:18:03Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/70830" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/70830</identifier><datestamp>2026-06-06T01:06:03Z</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">Michael Cusumano</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Kotelly, Christopher Blade (Christopher Alexis Blade)</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">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2012-05-15T21:15:54Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2012-05-15T21:15:54Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2011</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2011</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/70830</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">793202189</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M. in Engineering and Management)--Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2011.</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.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">High tech startups can be exciting places to work. Unlike many large corporate environments, startups offer new challenges almost every day, innovation is a sine qua non, and the rewards can be colossal both from financial and intellectual perspectives. People in startups can make their own rules, and change them at will. It's not uncommon for startups to change significantly as each new hire is added, since the impact of a single person in a small organization is significant. However, if a startup doesn't pay attention to the elements that do make many large corporations successful, they risk falling into traps that can result in failure. This paper shows the problems facing a particular startup that had grown quickly because of the brilliance of the ideas behind their technology and the founder, and offers suggested remedies.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Christopher Blade Kotelly.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M. in System Design and Management</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">49 p.</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">M.I.T. theses are protected by &#xd;
copyright. They may be viewed from this source for any purpose, but &#xd;
reproduction or distribution in any format is prohibited without written &#xd;
permission. See provided URL for inquiries about 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 Systems Division.</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">When startups start down : how leadership, vision, strategy and design can enable a startup to breakdown the barriers killing the company</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">When startups start down : using leadership, vision, and strategy to transform the architecture killing a company</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">How leadership, vision, strategy and design can enable a startup to breakdown the barriers killing the company</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">Using leadership, vision, and strategy to transform the architecture killing a company</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="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</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="d613ce45-186f-4c8c-b15c-ace5ea80c5d3">
	&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>When startups start down : how leadership, vision, strategy and design can enable a startup to breakdown the barriers killing the company&lt;/Title>
   	&lt;Subtitle>When startups start down : using leadership, vision, and strategy to transform the architecture killing a company&lt;/Subtitle>
   	&lt;Subtitle>How leadership, vision, strategy and design can enable a startup to breakdown the barriers killing the company&lt;/Subtitle>
   	&lt;Subtitle>Using leadership, vision, and strategy to transform the architecture killing a company&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2011&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Kotelly, Christopher Blade (Christopher Alexis Blade)&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 Systems Division.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>High tech startups can be exciting places to work. Unlike many large corporate environments, startups offer new challenges almost every day, innovation is a sine qua non, and the rewards can be colossal both from financial and intellectual perspectives. People in startups can make their own rules, and change them at will. It&amp;apos;s not uncommon for startups to change significantly as each new hire is added, since the impact of a single person in a small organization is significant. However, if a startup doesn&amp;apos;t pay attention to the elements that do make many large corporations successful, they risk falling into traps that can result in failure. This paper shows the problems facing a particular startup that had grown quickly because of the brilliance of the ideas behind their technology and the founder, and offers suggested remedies.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>