<?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="103" t0="1337594291951">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>24373</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Into the MyST">214</OwnerID>
        <CreatedByID ObjectClass="User" Title="bfrench">24</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
        <CreateTime Title="2004-03-16 10:08:56 EST">1079449736431</CreateTime>
        <ModifyTime Title="2004-04-26 10:03:41 EDT">1082988221343</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>The High Cost of Not Finding Information</Name>
        <Summary>As an accountant, I learned about opportunity cost and ways to measure it. The opportunity costs associated with not finding information when its most needed is more difficult to calculate.</Summary>
        <Description>
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;As indicated in the 
&lt;/FONT&gt;&lt;A 
href="http://www.kmworld.com/publications/magazine/index.cfm?action=readarticle&amp;amp;Article_ID=1725&amp;amp;Publication_ID=108"&gt;&lt;FONT 
face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;article&lt;/FONT&gt;&lt;/A&gt;&lt;FONT 
face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;FONT size=2&gt; of the same title (by 
&lt;/FONT&gt;&lt;A href="mailto:sfeldman@idc.com"&gt;&lt;FONT size=2&gt;Susan 
Feldman&lt;/FONT&gt;&lt;/A&gt;&lt;FONT size=2&gt;), knowledge worker output is difficult to 
measure, so it's not surprising that opportunity costs relative to information 
resources are also tough to quantify. However, it's pretty easy to measure how 
information workers use their time. A friend of mine (&lt;/FONT&gt;&lt;A 
href="mailto:carlos@caballero.cc"&gt;&lt;FONT size=2&gt;Carlos Caballero&lt;/FONT&gt;&lt;/A&gt;&lt;FONT 
size=2&gt;) has developed a worksheet that helps you (and your firm)&amp;nbsp;identify 
how much time you spend on information-work&amp;nbsp;that can be directly related to 
the cost of not performing tasks.&amp;nbsp;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;"&lt;EM&gt;There is a 
problem experienced by every overworked executive, manager and staff alike: the 
cost of not doing certain tasks just because the overhead required renders it 
anti-economic, or obsolete by the time it is completed. That problem is more and 
more common as a result of shrinking IT resources, the elevated cost of 
customized applications, and the long backlog faced by IT. Information workers 
face the need to do what they can with what they have, and that tends to 
sacrifice the more resource-intensive tasks, regardless of how critical they are 
for corporate missions&lt;/EM&gt;." -- Carlos Caballero&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Verdana size=2&gt;The&amp;nbsp;objective&amp;nbsp;[it seems] in creating a 
more operationally efficient information framework is to adopt tools and 
processes that lower the overhead of&amp;nbsp;performing&amp;nbsp;tasks critical to the 
business. That overhead must be just a skinch less than 
&lt;EM&gt;&lt;U&gt;anti-economic&lt;/U&gt;&lt;/EM&gt;. Some tasks are extremely anti-economic while 
others are probably borderline cases (i.e., low-hanging fruit that can be picked 
by adopting a few simple changes). &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Verdana size=2&gt;By encouraging your staff to CC a single important 
email message&amp;nbsp;per week to an information repository&amp;nbsp;you will begin to 
build a useful knowledge base of information that would otherwise vanish from 
corporate awareness.&amp;nbsp;Following this basic (and&amp;nbsp;frictionless) policy 
a&amp;nbsp;team of 25 people will generate 1,250 information objects that are 
preserved and searchable and will raise&amp;nbsp;your corporate&amp;nbsp;&lt;A 
href="http://radio.weblogs.com/0105910/2003/05/13.html"&gt;knowledge 
continuity&lt;/A&gt;.&lt;/FONT&gt;&lt;/P&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>Carlos Caballero</Keyword>

                 <Keyword>knowledge continuity</Keyword>

                 <Keyword>opportunity costs</Keyword>

                 <Keyword>Susan Feldman</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Capturing Ideas and Advice</Title>

                  <Synopsis>Quite often solutions to what seem to be complex problems are a bit simpler than we think. One way to capture great ideas and advice from your employees is to simply ask them.</Synopsis>

                  <URL>item/16549</URL>

        </Link>

                 <Link>
                  <Title>KMWorld: The high cost of not finding information</Title>

                  <Synopsis>In an increasingly information-based world, we turn out complex products that are less tangible than they are knowledge-based.</Synopsis>

                  <URL>http://www.kmworld.com/publications/magazine/index.cfm?action=readarticle&amp;Article_ID=1725&amp;Publication_ID=108</URL>

        </Link>

                 <Link>
                  <Title>Operational Efficiency</Title>

                  <Synopsis>I recently purchased a robot - I turn it on; it vacuum's my floor.</Synopsis>

                  <URL>item/15257</URL>

        </Link>

                 <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>Knowledge Continuity Management</Title>

                  <Synopsis>Where knowledge management concerns capturing and sharing know-how valuable to colleagues performing similar jobs throughout a company, knowledge continuity management focuses on passing critical knowledge from exiting employees to their replacements.</Synopsis>

                  <URL>http://radio.weblogs.com/0105910/2003/05/13.html</URL>

        </Link>

       </Links>

      </CommonProperties>

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

                <RemoteHost>68.42.141.35</RemoteHost>

                <RemoteAddr>68.42.141.35</RemoteAddr>

                <RemoteUser>aseidl</RemoteUser>

      </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>

