<?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://sightlog.sightlinesconsulting.com/public/styles/etc/object.xsl" type="text/xsl"?>

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

<MySmartChannels Public="true" UserID="102297" dT="33" t0="1227190884160">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>118146</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Software and Technology for the SME (Small and Medium Enterprise)">102302</OwnerID>
        <CreatedByID ObjectClass="User" Title="tfoydel">102466</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="tfoydel">102466</ModifiedByID>
        <CreateTime Title="2006-03-09 08:34:44 EST">1141911284486</CreateTime>
        <ModifyTime Title="2006-03-09 08:34:44 EST">1141911284486</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Rethinking Email</Name>
        <Summary>New Research Raises Important Questions About Everyone's Favorite Tool</Summary>
        <Description>&lt;p&gt;Recently had the opportunity to read the research of a University of Chicago Business School &lt;a href="http://www.chicagogsb.edu/news/2006-02-16_epley.aspx"&gt;Professor Nicholas Epley on the subject of email&lt;/a&gt;, our expectations of it and what it actually delivers. &lt;/p&gt;&lt;p&gt;Essentially, though I think you should definitely check it out yourself because this is important, Epley's work comes to the conclusion that email is an extremely poor&amp;nbsp;medium for&amp;nbsp;emotional speech. By emotional speech Epley is not referring to ranting or off the charts emoting, but the more subdued inflections and nuances of the spoken voice, the emotions that we tend to take for granted since they are so common in our face-to-face or over the phone communications.&lt;/p&gt;&lt;p&gt;In an earlier post we discussed &lt;a href="http://sightlog.sightlinesconsulting.com/public/item/102792"&gt;Email's Negative Rate of Return&lt;/a&gt; to the business, the idea that a lot of corporate knowledge assets are buried in the Inbox, which naturally goes dark during normal staff attrition. After 10 years or so of using email, having it take over business life might be a better way to say it, many people have started to question the medium. Does it make sense to bury communications with customers in email Inboxes, from which it will never see the light of day, or more importantly will never be cultivated for the insight it might provide to the sales, service and overall relationship with customer?&lt;/p&gt;&lt;p&gt;Now there is another reason to really question email's monopoly on business communication. Are we speaking to the customer in a voice that they understand the same way we do? Face to face verbal communications are difficult enough, anyone who has been married will vouch for this, but Epley's research now questions whether or not we are actually communicating with the inflection and nuance that we think we are. His conclusions throw more suspicion on the whole email medium. &lt;/p&gt;&lt;p&gt;One of the ideas that Epley advocates as the result of his study to limit email to pure content and try to keep the emotional tones out of it to the greatest degree possible. I am not sure that this is even possible. We do very little that is not in some or many ways influenced by the dreaded emotions. And when we talk about Customer Relationship Management aren't we really acknowledging that we have an emotional connection to the customer that we need to nurture? If we think we are nurturing this over email we may be sadly mistaken.&lt;/p&gt;&lt;p&gt;So what's the alternative? There are now two hurdles that we must jump. First is the email Inbox issue and the imminent loss of corporate knowledge assets, and the second is the email medium's shortcomings as a rich communication medium. One alternative is the use of a business collaboration tool/service. We have started to use &lt;a href="http://www.customervision.com/"&gt;CustomerVision&lt;/a&gt;&amp;nbsp;at SightLines, inviting clients in as well. When we have the need for electronic communications and a phone call is not the best option, we'll write a post in the CustomerVision business wiki and, through email, the correct people are notified. They can then join the discussion and post a reply, etc..&lt;/p&gt;&lt;p&gt;What the difference between email and a business collaboration tool like CustomerVision? Well, first of all the communications are saved in an area you have created for this particular client relationship, forever. So no loss of knowledge. Second, because the medium is different and more public&amp;nbsp;users are inclined to speak appropriately and professionally. That is not to say that their posts are unemotional; to the contrary, they are emotional but in the same way that the spoken voice we adopt in business situations is emotional - with nuance and inflection.&lt;/p&gt;&lt;p&gt;It may not be the perfect answer but my guess is that management and staff are both starting to tire of the email Inbox and all if its attendant weaknesses, from embarrassment to lost customer loyalty. Services like CustomerVision will eventually handle the bulk of important corporate communications, while email will be used for notifications and updates on sports scores, and of course, spam.&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>business wiki</Keyword>

                 <Keyword>collaboration</Keyword>

                 <Keyword>email</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Emails Negative Rate of Return</Title>

                  <Synopsis>What happens when the Inbox goes dark?</Synopsis>

                  <URL>http://sightlog.sightlinesconsulting.com/public/item/102792</URL>

        </Link>

                 <Link>
                  <Title>When what you type isn?t what they read: the perseverance of stereotypes and expectancies over e-mail</Title>

                  <Synopsis>In short email does not work as well as we think</Synopsis>

                  <URL>http://www.chicagogsb.edu/news/2006-02-16_epley.aspx</URL>

        </Link>

       </Links>

      </CommonProperties>

               <RemoteInfo>
                <UserAgent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; YPC 3.0.1; (R1 1.5); .NET CLR 1.1.4322)</UserAgent>

                <RemoteHost>68.79.117.127</RemoteHost>

                <RemoteAddr>68.79.117.127</RemoteAddr>

                <RemoteUser>tfoydel</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">205861</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] Software and Technology for the SME (Small and Medium Enterprise)">102302</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/SightLines/web</Model>

                <Style/>

                <Scheme/>

       </View>

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

                <View>
                 <Name>blog</Name>

                 <Model>blogsite/SightLines/whatsnew</Model>

                 <Style/>

                 <Scheme/>

       </View>

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

                 <Model>blogsite/SightLines/web</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>left</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>right</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>wide</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

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