<?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-20T10:41:50Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/34807" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/34807</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">Paul Carlile.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Gilbert, Steven M. (Steven Michael), 1975-</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="date" qualifier="accessioned">2006-11-08T16:41:26Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2006-11-08T16:41:26Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2004</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2004</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/34807</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">57554565</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, System Design &amp; Management Program, 2004.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 87-88).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Change is an absolutely essential component of product development. However, some changes are too difficult to manage. It is contended that the difficult changes stem from the emergence of novelty. The significance of novelty is that it is not immediately apparent and can be overlooked. It is a common element in disruptive technology, knowledge management, and firefighting research. This work examines the effects of emergent novelty in a complex product development system. In order to do this a framework is developed to categorize potential types of novelty that are encountered. In addition, a unique perspective on the concept of organizational capability is introduced. What makes it unique is the idea that organizational capability is composed of the capacity to do work and the ability of actors to use that capacity. "Organizational infrastructure" is used to speak more concretely about organizational capability. These conceptual models are used to analyze the events of three case studies developed from actual projects in the Imaging &amp; Printing division of Hewlett-Packard. Through the case analysis it is shown there is significant pressures to approach development as if all novelty is understood. However, by doing so almost guarantees problems late in development if latent novelty exists. It is speculated that the addition of excess capacity to the organizational infrastructure will allow for greater novelty detection. This in turn should decrease the complications from resolving issues related to the emergence of novelty.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Steven M. Gilbert.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">88 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">3994691 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">4004422 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</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 copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri">http://dspace.mit.edu/handle/1721.1/7582</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">On infrastructure for resolving novelty in product development : a view from the fast paced world of imaging and printing</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="8e3cd521-496f-48d0-a1c1-353947f6b9ea">
	&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>On infrastructure for resolving novelty in product development : a view from the fast paced world of imaging and printing&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2004&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Gilbert, Steven M. (Steven Michael), 1975-&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>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>Change is an absolutely essential component of product development. However, some changes are too difficult to manage. It is contended that the difficult changes stem from the emergence of novelty. The significance of novelty is that it is not immediately apparent and can be overlooked. It is a common element in disruptive technology, knowledge management, and firefighting research. This work examines the effects of emergent novelty in a complex product development system. In order to do this a framework is developed to categorize potential types of novelty that are encountered. In addition, a unique perspective on the concept of organizational capability is introduced. What makes it unique is the idea that organizational capability is composed of the capacity to do work and the ability of actors to use that capacity. &amp;quot;Organizational infrastructure&amp;quot; is used to speak more concretely about organizational capability. These conceptual models are used to analyze the events of three case studies developed from actual projects in the Imaging &amp;amp; Printing division of Hewlett-Packard. Through the case analysis it is shown there is significant pressures to approach development as if all novelty is understood. However, by doing so almost guarantees problems late in development if latent novelty exists. It is speculated that the addition of excess capacity to the organizational infrastructure will allow for greater novelty detection. This in turn should decrease the complications from resolving issues related to the emergence of novelty.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>