<?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-24T06:13:50Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/9347" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/9347</identifier><datestamp>2022-01-13T07:54:36Z</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">Don Clausing.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Hull, John Andrew, 1974-</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Dept. of Mechanical Engineering.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Mechanical Engineering</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2005-08-22T20:29:56Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-08-22T20:29:56Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">1999</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">1999</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/9347</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">44421188</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Mechanical Engineering, 1999.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 139-140).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">In product development organizations, the front end of product development is usually confined to planning within business units for product families and individual products. This can pose a problem for businesses, as individual business units and development teams do not think in terms of the big picture of the company. Business units are responsible for only their market and product strategies, and are relatively unconcerned about those of other business units. Because of this, there is the potential for product offerings across business units to overlap in the marketplace, thereby wasting development resources and confusing customers with multiple offerings of similar value propositions. There is also the potential to have gaps in the marketplace, where no business units have product offerings, which can be a prime niche for competitors to introduce products to gain a market foothold and precious market share. The purpose of this research was to "extend" the front end of the development process upward across all business units in order to understand the market relationships across the entire product-offering portfolio. This allows the company to see how its products are related across markets, and to observe the strengths and weaknesses in il'> competitive positions. The result is a better understanding of which markets and products should be prioritized when making investment decisions. This thesis develops and discusses several concepts and tools, namely those of the Core Benefit Proposition and Vector of Differentiation, that are necessary in order to identify the gaps and overlaps within a product portfolio. A basic approach was developed that combines these concepts and tools into a framework for identifying gaps and overlaps. This approach was then applied and demonstrated with a case study involving the product portfolio of the Xerox Company.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by John Andrew Hull.</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">187 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">14205726 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">14205484 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">Mechanical Engineering.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">The identification of gaps and overlaps in the product portfolio</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="9edffa44-ce13-46c7-a31a-d62fa0185c7b">
	&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>The identification of gaps and overlaps in the product portfolio&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>1999&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Hull, John Andrew, 1974-&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>Mechanical Engineering.&lt;/Keyword>
   	&lt;Abstract>In product development organizations, the front end of product development is usually confined to planning within business units for product families and individual products. This can pose a problem for businesses, as individual business units and development teams do not think in terms of the big picture of the company. Business units are responsible for only their market and product strategies, and are relatively unconcerned about those of other business units. Because of this, there is the potential for product offerings across business units to overlap in the marketplace, thereby wasting development resources and confusing customers with multiple offerings of similar value propositions. There is also the potential to have gaps in the marketplace, where no business units have product offerings, which can be a prime niche for competitors to introduce products to gain a market foothold and precious market share. The purpose of this research was to &amp;quot;extend&amp;quot; the front end of the development process upward across all business units in order to understand the market relationships across the entire product-offering portfolio. This allows the company to see how its products are related across markets, and to observe the strengths and weaknesses in il&amp;apos;&amp;gt; competitive positions. The result is a better understanding of which markets and products should be prioritized when making investment decisions. This thesis develops and discusses several concepts and tools, namely those of the Core Benefit Proposition and Vector of Differentiation, that are necessary in order to identify the gaps and overlaps within a product portfolio. A basic approach was developed that combines these concepts and tools into a framework for identifying gaps and overlaps. This approach was then applied and demonstrated with a case study involving the product portfolio of the Xerox Company.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>