<?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-19T16:52:46Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/29149" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/29149</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">Daniel Whitney.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Goran, James L. (James Leo), 1964-</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Shashlo, Michael L., 1964-</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Wickenheiser, Francis J. 1967-</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">2005-09-27T20:54:29Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-09-27T20:54:29Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2000</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2000</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/29149</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">44893297</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of System Design &amp; Management, 2000.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 157-161).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Manufacturing-intensive companies like Ford Motor Company have come to the realization that they need to have a strong consumer focus to survive in today's competitive world. Ford has just recently announced steps to further align its program team centers more strongly with their consumers, yet the lower levels of the teams will still remain aligned around a standard part decomposition that finds its roots back to Henry Ford's vertical integration methodology. In today's information age, with the growing expectations of the consumer, as well as product complexity, it has become essential for product teams to share and communicate efficiently. It is no longer adequate for the program manager to be the sole focal point, where the voice of the consumer meets the voice of part engineering. As complex as it sounds, the consumer voice must be decomposed for delivery throughout the program team as the driving force by which the parts are engineered. Herein outlines an approach which has been called 'enabling a consumer headset in product development,' that illustrates the possibility of handle this complexity using today's tools. Bottom line: Industry is ready to take this one on. Needs analysis has established a focal point at the program team decompositional structure, product development process, and the driving management metrics and engineering specifications. Suggested are concepts that lead to a more natural and efficient way of delivering that consumer headset and these concepts are applied on three implementation projects: 1) a MIT course exercise; 2) a new Docu-Center architecture program at Xerox; and 3) a forward model 200X Mustang program. Findings are summarize into a final recommendation for future Ford program applications. The conclusion of this thesis recommends three items: 1) Introduces the Role of Architects, 2) Aligns the Organization Around the Consumer, 3) Transitions Engineering Focus to Interface Specifications.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by James L. Goran, Michael L. Shashlo [and] Francis J. Wickenheiser.</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">161 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">13682738 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">13682491 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">Enabling a consumer headset in product development</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="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="98091b61-9321-4ec8-98a4-7a9b440c9341">
	&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>Enabling a consumer headset in product development&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2000&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Goran, James L. (James Leo), 1964-&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
      	&lt;Author>
        	&lt;DisplayName>Shashlo, Michael L., 1964-&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
      	&lt;Author>
        	&lt;DisplayName>Wickenheiser, Francis J. 1967-&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>Manufacturing-intensive companies like Ford Motor Company have come to the realization that they need to have a strong consumer focus to survive in today&amp;apos;s competitive world. Ford has just recently announced steps to further align its program team centers more strongly with their consumers, yet the lower levels of the teams will still remain aligned around a standard part decomposition that finds its roots back to Henry Ford&amp;apos;s vertical integration methodology. In today&amp;apos;s information age, with the growing expectations of the consumer, as well as product complexity, it has become essential for product teams to share and communicate efficiently. It is no longer adequate for the program manager to be the sole focal point, where the voice of the consumer meets the voice of part engineering. As complex as it sounds, the consumer voice must be decomposed for delivery throughout the program team as the driving force by which the parts are engineered. Herein outlines an approach which has been called &amp;apos;enabling a consumer headset in product development,&amp;apos; that illustrates the possibility of handle this complexity using today&amp;apos;s tools. Bottom line: Industry is ready to take this one on. Needs analysis has established a focal point at the program team decompositional structure, product development process, and the driving management metrics and engineering specifications. Suggested are concepts that lead to a more natural and efficient way of delivering that consumer headset and these concepts are applied on three implementation projects: 1) a MIT course exercise; 2) a new Docu-Center architecture program at Xerox; and 3) a forward model 200X Mustang program. Findings are summarize into a final recommendation for future Ford program applications. The conclusion of this thesis recommends three items: 1) Introduces the Role of Architects, 2) Aligns the Organization Around the Consumer, 3) Transitions Engineering Focus to Interface Specifications.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>