<?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-18T21:55:32Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/9752" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/9752</identifier><datestamp>2025-10-27T18:00:46Z</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">Woodie C. Flowers.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Ritchie, Shawn W., 1965-</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2005-08-19T19:55:49Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-08-19T19:55:49Z</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/9752</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">42769659</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 1999.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (leaves 80-81).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">This research involves the identification and definition of"Endangered Knowledge" and outlines a tool that a firm can use to identify, capture, and reutilizes endangered knowledge. Endangered knowledge (EK) is valuable knowledge firms acquire during product development that has a high potential to be erased from a firm's memory. Two primary factors contribute to endangered knowledge. First, the firm does not believe the knowledge has future value, or does not take the time to correctly assess the value of the knowledge. Product development teams are usually under a great deal of time and financial pressures, and once a particular piece of knowledge has been acquired and applied to a specific process, it is quickly discarded. Second, an individual in a firm may realize that a piece of knowledge could have value to their team or another team in the future, but have no system in place which will enable them to effectively store and communicate that knowledge. In both cases, the knowledge is lost, ultimately costing the firm time and money to replace the lost learning.  This paper can be broken up into four sections. The first section includes an introduction to endangered knowledge and provides two case studies where different product development teams wasted time and money because they were unable to access knowledge acquired by other members in their firm. The second section defines the terminology, (knowledge vs. information, learning vs. teaching, transfer vs. transform) and highlights knowledge management (KM) initiatives in existence today. The third section outlines five essential steps a knowledge management system must address in order to be effective. The final section introduces a new methodology product development teams can use to capture and reuse, or "rescue" endangered knowledge.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Shawn W. Ritchie.</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">81 leaves</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">6170909 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">6170670 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">Rescuing endangered knowledge : a systems approach</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="2a0ef693-87b7-490a-9876-4e27686de13d">
	&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>Rescuing endangered knowledge : a systems approach&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>1999&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Ritchie, Shawn W., 1965-&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>This research involves the identification and definition of&amp;quot;Endangered Knowledge&amp;quot; and outlines a tool that a firm can use to identify, capture, and reutilizes endangered knowledge. Endangered knowledge (EK) is valuable knowledge firms acquire during product development that has a high potential to be erased from a firm&amp;apos;s memory. Two primary factors contribute to endangered knowledge. First, the firm does not believe the knowledge has future value, or does not take the time to correctly assess the value of the knowledge. Product development teams are usually under a great deal of time and financial pressures, and once a particular piece of knowledge has been acquired and applied to a specific process, it is quickly discarded. Second, an individual in a firm may realize that a piece of knowledge could have value to their team or another team in the future, but have no system in place which will enable them to effectively store and communicate that knowledge. In both cases, the knowledge is lost, ultimately costing the firm time and money to replace the lost learning.  This paper can be broken up into four sections. The first section includes an introduction to endangered knowledge and provides two case studies where different product development teams wasted time and money because they were unable to access knowledge acquired by other members in their firm. The second section defines the terminology, (knowledge vs. information, learning vs. teaching, transfer vs. transform) and highlights knowledge management (KM) initiatives in existence today. The third section outlines five essential steps a knowledge management system must address in order to be effective. The final section introduces a new methodology product development teams can use to capture and reuse, or &amp;quot;rescue&amp;quot; endangered knowledge.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>