<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--Web 2.0 Content Powered by MyST Blogsite® (http://blogsite.com)-->
<!--A service of MyST Technology Partners, Inc. (http://myst-technology.com)-->
<?xml-stylesheet href="http://myst-technology.com/public/styles/etc/object.xsl" type="text/xsl"?>

<?myst-baseUrl http://myst-technology.com/public/?>

<MySmartChannels Public="true" UserID="125119" dT="82" t0="1268663477680">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>53612</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Into the MyST">214</OwnerID>
        <CreatedByID ObjectClass="User" Title="aseidl">21</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
        <CreateTime Title="2004-08-25 15:57:52 EDT">1093463872348</CreateTime>
        <ModifyTime Title="2008-02-02 14:11:55 EST">1201979515718</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>A Holy Grail: Effective Knowledge Capture, Persistence, Enhancement, and Transfer</Name>
        <Summary>Since the 1980s, the connotation of "knowledge management" morphed from exciting technology business opportunity to an idea that largely failed, in commercial terms, anyway.  But the underlying need for KM has not gone away; in fact, it has grown.</Summary>
        <Description>&lt;p&gt;I've been working with &lt;a href="http://budgibson.com/" target="_blank"&gt;Bud Gibson&lt;/a&gt;, a University of Michigan Business School professor, who is putting together what he is calling&amp;nbsp;the &lt;i&gt;BIT320 Distributed Learning Blogosphere&lt;/i&gt; as part of a course (BIT320) that he is teaching this Fall. Its an interesting idea and I'm eager to watch the course blogosphere evolve as the term unfolds.&amp;nbsp; (Bud is considering making the space public; I'll post a link if that turns out to be the case.)&lt;/p&gt;&lt;p&gt;Along the way, Bud, I, and others have had various discussions in an attempt to develop a clear mission statement, not only for the course itself, but for how the course relates to the larger world of knowledge-related issues.&amp;nbsp; This really goes to the heart of what Bill French and I have been working on for the past four years&amp;mdash;initially while running the &lt;i&gt;&lt;a href="http://www.google.com/search?hl=en&amp;lr=&amp;ie=UTF-8&amp;newwindow=1&amp;safe=off&amp;q=Elmer+%22F.+Andy+Seidl%22" target="_blank"&gt;Elmer&lt;/a&gt;&lt;/i&gt; project for Starbase Corporation (which as since been acquired by Borland), and more recently, as MyST Technology Partners.&lt;/p&gt;&lt;p&gt;Here are the basic ideas in a nutshell (okay, several nutshells):&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Knowledge is a &lt;a title="Thanks for the (Corporate) Memories" href="item/7238" target="_blank"&gt;key asset&lt;/a&gt;, if not &lt;i&gt;the &lt;/i&gt;key asset, of most organizations. &lt;/li&gt;&lt;li&gt;In the KM world, a Holy Grail is effective capture, enhancement, persistence, and transfer knowledge. (The goal of the BIT320 course is more modest, but it is a step in this direction&amp;mdash;specifically, to develop an appreciation of why this grail is, in fact, holy.) &lt;/li&gt;&lt;li&gt;Successful solutions will be those that emerge organically through small, incremental behavior changes of knowledge workers rather than asking them to use some new &amp;quot;KM System&amp;quot;&amp;mdash;history has shown the latter approach fails far more often than not. &lt;/li&gt;&lt;li&gt;Emergent systems must provide low-friction scenarios for knowledge to traverse &amp;quot;the last mile&amp;quot; in both directions, i.e., knowledge capture and knowledge dissemination &lt;/li&gt;&lt;li&gt;Capture must occur anywhere (and eventually, everywhere) a knowledge worker is already working&amp;mdash;in Word, in Excel, in e-mail, in web browsers, on PDAs, on cell phones, etc. &lt;/li&gt;&lt;li&gt;Dissemination mechanisms must similarly deliver the &lt;i&gt;right&lt;/i&gt; information into the &lt;i&gt;right&lt;/i&gt; context at the &lt;i&gt;right&lt;/i&gt; time. This is essential for extracting &lt;i&gt;knowledge&lt;/i&gt; (i.e., capacity to act wisely) from the &lt;i&gt;information tsunami&lt;/i&gt; (i.e., enormous and ever-growing volumes of data) that is already overwhelming knowledge workers. This implies there must be many dissemination mechanisms&amp;mdash;RSS, smart tags, search, research services, e-mail notifications, pager messages, cell phone notifications, IM, and so on, as well as new, &amp;quot;smart&amp;quot; ways to help &lt;i&gt;workers find stuff&lt;/i&gt; and&amp;mdash;perhaps more importantly&amp;mdash;&lt;i&gt;stuff find workers&lt;/i&gt;. There is no one-size-fits-all solution.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;What will it take to get there?&amp;nbsp; That is, more or less, the question Bill and I have been focusing on for years.&amp;nbsp; Here are a few essential ingredients&amp;mdash;there are, no doubt, many more, but I'm convinced these are all critical.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;We need unifying knowledge meta spaces (it is impractical to imagine that existing information systems will someday all integrate with each other).&amp;nbsp; Further, it must be possible to automatically merge (or virtually merge) multiple meta spaces to create&amp;nbsp;larger spaces. &lt;/li&gt;&lt;li&gt;We need a formalized concept of &lt;i&gt;information object identity&lt;/i&gt;. &lt;/li&gt;&lt;li&gt;We need a pervasive security and permissions model.&amp;nbsp; This model must be enforced for &lt;i&gt;all&lt;/i&gt; information access.&amp;nbsp; (Consider, what should someone find when looking for information about &amp;quot;layoff planning&amp;quot;?&amp;nbsp; Clearly, the answer depends on who is asking the question.) &lt;/li&gt;&lt;li&gt;We need plug-in architectures to define new business logic for not-yet-understood (or even invented) requirements.&amp;nbsp; New business logic should automatically inherit core capabilities such as object identity, security, etc. &lt;/li&gt;&lt;li&gt;We need plug-in architectures for new (not-yet-invented) capture and dissemination technologies.&amp;nbsp; Again, these should inherit all core capabilities. &lt;/li&gt;&lt;li&gt;We need complete separation of (knowledge) content from (presentation) form. &lt;/li&gt;&lt;li&gt;We need international standards (like XSL) to describe transformation of information from one form to another. &lt;/li&gt;&lt;li&gt;We need international standards (like topic maps) for the representation and interchange of meaning. &lt;/li&gt;&lt;li&gt;We need international standards (like XML, SOAP, HTTP, etc.) for platform-neutral machine-to-machine communication.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;The exciting part of all of this is that we, as an industry, are getting tantalizingly close to having all the building blocks.&amp;nbsp; At MyST, we've already done a number of interesting &amp;quot;KM&amp;quot; applications based on the MyST Web Services Platform and the MySmartChannels Weblog Application Server, one of which is Bud's course blogosphere.&amp;nbsp; We're always on the lookout for new, interesting knowledge-related applications to attack.&amp;nbsp; Feel free to &lt;a title="Contact MyST" href="/contact"&gt;contact us&lt;/a&gt;&amp;nbsp;with ideas.&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>Andy Seidl</Keyword>

                 <Keyword>Bill French</Keyword>

                 <Keyword>Bud Gibson</Keyword>

                 <Keyword>Elmer</Keyword>

                 <Keyword>KM</Keyword>

                 <Keyword>knowledge capture</Keyword>

                 <Keyword>knowledge management</Keyword>

                 <Keyword>knowledge transfer</Keyword>

                 <Keyword>Starbase</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Thanks for the (Corporate) Memories</Title>

                  <Synopsis>When employees leave, vital institutional knowledge may be lost forever.</Synopsis>

                  <URL>item/7238</URL>

        </Link>

                 <Link>
                  <Title>The High Cost of Not Finding Information </Title>

                  <Synopsis>The opportunity costs associated with not finding information when its most needed is difficult to calculate.</Synopsis>

                  <URL>item/24373</URL>

        </Link>

                 <Link>
                  <Title>Can a blog post contain knowledge?</Title>

                  <Synopsis>At the risk of oversimplifying: Yes!</Synopsis>

                  <URL>item/10801</URL>

        </Link>

                 <Link>
                  <Title>Distributed KM: A Case for Weblog-based Knowledge Management </Title>

                  <Synopsis>This paper contains a number of useful observations and ideas concerning knowledge management and weblogs.</Synopsis>

                  <URL>item/48085</URL>

        </Link>

                 <Link>
                  <Title>Blogging Envelope Opens to Knowledge Management</Title>

                  <Synopsis>As we push the blogging envelope, it becomes clear that this stuff is good for KM.</Synopsis>

                  <URL>item/37513</URL>

        </Link>

                 <Link>
                  <Title>Blogging Inward</Title>

                  <Synopsis>Chad Dickerson's 'Blogging To Ourselves' article articulates a use case for blogs that has been in use for more than a year at MyST Technology Partners.</Synopsis>

                  <URL>item/36887</URL>

        </Link>

       </Links>

      </CommonProperties>

               <RemoteInfo>
                <UserAgent>Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)</UserAgent>

                <RemoteHost>127.0.0.1</RemoteHost>

                <RemoteAddr>127.0.0.1</RemoteAddr>

                <RemoteUser>aseidl</RemoteUser>

                <ForwardedFor>68.40.167.222</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
        </ContentDocument>
       </Resource>
       <Shares/>
       <Subjects/>
       <UserPermissions>
        <CanDelete>false</CanDelete>
        <CanDiscover>true</CanDiscover>
        <CanEdit>false</CanEdit>
        <CanEditPermissions>false</CanEditPermissions>
        <CanRead>true</CanRead>
       </UserPermissions>
       <CommentInfo>
        <CommentChannelRef AllowAnonymous="true" Inherited="true">
         <ChannelID ObjectClass="Channel" Title="[Public] Public Comments">190014</ChannelID>
         <UserPermissions>
          <CanCreateChannelItem>false</CanCreateChannelItem>
          <CanDelete>false</CanDelete>
          <CanDiscover>true</CanDiscover>
          <CanEdit>false</CanEdit>
          <CanEditPermissions>false</CanEditPermissions>
          <CanPublish>false</CanPublish>
          <CanRead>true</CanRead>
         </UserPermissions>
        </CommentChannelRef>
        <Comments/>
       </CommentInfo>
       <Views>
        <SourceID ObjectClass="Channel" Title="[Weblog] Into the MyST">214</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/MySTHome/web</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>edit-item</Name>

                <Model>blogsite/MySTHome/web</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>left</Name>

                <Model>blogsite/MySTHome/left-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>right</Name>

                <Model>blogsite/MySTHome/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>wide</Name>

                <Model>blogsite/MySTHome/wide-content</Model>

                <Style/>

                <Scheme/>

       </View>

      </Views>
        <Views>
         <SourceID ObjectClass="Channel" Shared="true" Title="[Public] What's New">192423</SourceID>

                <View>
                 <Name>blog</Name>

                 <Model>blogsite/MySTHome/whatsnew</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>edit-item</Name>

                 <Model>blogsite/MySTHome/web</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>left</Name>

                 <Model>blogsite/MySTHome/left-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>right</Name>

                 <Model>blogsite/MySTHome/right-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>wide</Name>

                 <Model>blogsite/MySTHome/wide-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

      </Views>
        </Item>
       </GetChannelItem_Result>
      </MySmartChannels>
