<?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-18T19:48:24Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/34858" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/34858</identifier><datestamp>2022-01-28T19:10:59Z</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">Daniel E. Whitney and Janice Klein.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">McGill, Eric Andrew</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Leaders for Manufacturing Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Leaders for Manufacturing Program at MIT</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Sloan School of Management</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2006-11-08T16:50:31Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2006-11-08T16:50:31Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2005</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2005</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/34858</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">63201263</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (M.B.A.)--Massachusetts Institute of Technology, Sloan School of Management; and, (S.M.)--Massachusetts Institute of Technology, Engineering Systems Division; in conjunction with the Leaders for Manufacturing Program at MIT, 2005.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 132-133).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Product development processes are inherently complex sets of activities that involve a vast number of connections between participants. Engineers, designers, marketers, financial analysts, and manufacturers all have to receive information, process it, and distribute their decisions back into the system. These paths create information loops that are hidden from the participants on a long time scale and generate non-linear feedback. An analysis of the closures product and process development tasks at a major US automaker prompted the creation of new tools to optimize the ordering, identification of coupled blocks, prioritization of interactions, allocation of resources, and modeling of multiple projects. Ultimately, the analysis predicted a reduction in the average completion time of [approx.] 80%, a reduction in standard deviation of [approx.] 95%, and potential savings of -[approx.] $5B. Unfortunately, many of the suggestions from the analysis run headlong into the organization's structural, political, and cultural environment. Structurally, the automaker is a matrix organization split along functions and program lines, constantly attempting to balance between being a strong component designer and a quality assembler. However, the functional divisions create trouble in viewing and communicating across the entire system, whether that system is the vehicle to be designed or the organization itself. Politically, the atmosphere is dominated by a strong functional orientation, authoritative traditions, and a rigid hierarchy. Culturally, the people seem to be jaded and somewhat fatalistic about the company's future.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">(cont.) Managing change in this environment requires effort from the top and bottom of the organization, and must draw on those people inside the organization that can provide an outsider's perspective when addressing both the macro and micro challenges that will appear. Success will require using the organization against itself in order to create the initial changes that will ultimately bring about a long-term turnaround.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Eric Andrew McGill.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">M.B.A.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">172 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">10671241 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">10678474 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">Sloan School of Management.</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">Leaders for Manufacturing Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Optimizing the closures development process using the design structure matrix</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="faad055f-4927-4792-86aa-d260098f2904">
	&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>Optimizing the closures development process using the design structure matrix&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2005&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>McGill, Eric Andrew&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>Sloan School of Management.&lt;/Keyword>
    &lt;Keyword>Engineering Systems Division.&lt;/Keyword>
    &lt;Keyword>Leaders for Manufacturing Program.&lt;/Keyword>
   	&lt;Abstract>Product development processes are inherently complex sets of activities that involve a vast number of connections between participants. Engineers, designers, marketers, financial analysts, and manufacturers all have to receive information, process it, and distribute their decisions back into the system. These paths create information loops that are hidden from the participants on a long time scale and generate non-linear feedback. An analysis of the closures product and process development tasks at a major US automaker prompted the creation of new tools to optimize the ordering, identification of coupled blocks, prioritization of interactions, allocation of resources, and modeling of multiple projects. Ultimately, the analysis predicted a reduction in the average completion time of [approx.] 80%, a reduction in standard deviation of [approx.] 95%, and potential savings of -[approx.] $5B. Unfortunately, many of the suggestions from the analysis run headlong into the organization&amp;apos;s structural, political, and cultural environment. Structurally, the automaker is a matrix organization split along functions and program lines, constantly attempting to balance between being a strong component designer and a quality assembler. However, the functional divisions create trouble in viewing and communicating across the entire system, whether that system is the vehicle to be designed or the organization itself. Politically, the atmosphere is dominated by a strong functional orientation, authoritative traditions, and a rigid hierarchy. Culturally, the people seem to be jaded and somewhat fatalistic about the company&amp;apos;s future.&lt;/Abstract>
   	&lt;Abstract>(cont.) Managing change in this environment requires effort from the top and bottom of the organization, and must draw on those people inside the organization that can provide an outsider&amp;apos;s perspective when addressing both the macro and micro challenges that will appear. Success will require using the organization against itself in order to create the initial changes that will ultimately bring about a long-term turnaround.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>