<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Did Darwin Skip Over Email?</title>
	<atom:link href="http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/</link>
	<description>Foundry Group</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:18:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ryan Webb</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17473</link>
		<dc:creator>Ryan Webb</dc:creator>
		<pubDate>Tue, 26 Apr 2011 18:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17473</guid>
		<description>I believe the future of email is more about filtering out the emails that matter to that particular user.nnhttp://www.scrubly.com</description>
		<content:encoded><![CDATA[<p>I believe the future of email is more about filtering out the emails that matter to that particular user.nnhttp://www.scrubly.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thinkingman.com</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17409</link>
		<dc:creator>Thinkingman.com</dc:creator>
		<pubDate>Wed, 10 Nov 2010 05:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17409</guid>
		<description>The current approach to email is so dated it&#039;s not even funny. I find myself not using client apps anymore because they don&#039;t evolve quickly enough to meet my demandsu2026 email definitely needs to become more social. Iu2019d like to start a thinktank based on this concept, actually, because itu2019s constantly on my mind, and is a major part of how we do businessu2026</description>
		<content:encoded><![CDATA[<p>The current approach to email is so dated it&#8217;s not even funny. I find myself not using client apps anymore because they don&#8217;t evolve quickly enough to meet my demandsu2026 email definitely needs to become more social. Iu2019d like to start a thinktank based on this concept, actually, because itu2019s constantly on my mind, and is a major part of how we do businessu2026</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: t.a. mccann</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17287</link>
		<dc:creator>t.a. mccann</dc:creator>
		<pubDate>Sun, 02 Nov 2008 07:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17287</guid>
		<description>Chris,

I am looking forward to discussing this with you and the group at &lt;a href=&quot;http://www.defragcon.com. &quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt; &lt;a href=&quot;http://www.defragcon.com&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;www.defragcon.com&lt;/a&gt;. &lt;/a&gt; I think you have clearly identified many of the key issues and directions that are required for the next gen communications solution.  We think we have a good start at &lt;a href=&quot;http://www.gist.com. &quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt; &lt;a href=&quot;http://www.gist.com&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;www.gist.com&lt;/a&gt;. &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>I am looking forward to discussing this with you and the group at <a href="http://www.defragcon.com. " target="_blank" rel="nofollow"> </a><a href="http://www.defragcon.com" target="_blank" rel="nofollow">http://www.defragcon.com</a>.  I think you have clearly identified many of the key issues and directions that are required for the next gen communications solution.  We think we have a good start at <a href="http://www.gist.com. " target="_blank" rel="nofollow"> </a><a href="http://www.gist.com" target="_blank" rel="nofollow">http://www.gist.com</a>. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Pease</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17286</link>
		<dc:creator>Robert Pease</dc:creator>
		<pubDate>Fri, 16 May 2008 17:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17286</guid>
		<description>Great post.  Will be interesting to watch the evolution as no one seems to have cracked this just yet and I believe the ultimate solution will have to include &quot;channels&quot; beyond email. &lt;br /&gt;</description>
		<content:encoded><![CDATA[<p>Great post.  Will be interesting to watch the evolution as no one seems to have cracked this just yet and I believe the ultimate solution will have to include &#8220;channels&#8221; beyond email. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Harrison-Broni</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17285</link>
		<dc:creator>Keith Harrison-Broni</dc:creator>
		<pubDate>Tue, 06 May 2008 02:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17285</guid>
		<description>My comment above seems to have been scrambled due to markup.   See here for clearer text and fuller explanation: &lt;br /&gt;
 &lt;br /&gt;
&lt;a href=&quot;http://www.ebizq.net/blogs/it_directions/archives/2008/05/ny_times_descri.php &quot; rel=&quot;nofollow&quot;&gt;http://www.ebizq.net/blogs/it_directions/archives...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>My comment above seems to have been scrambled due to markup.   See here for clearer text and fuller explanation: </p>
<p><a href="http://www.ebizq.net/blogs/it_directions/archives/2008/05/ny_times_descri.php " rel="nofollow">http://www.ebizq.net/blogs/it_directions/archives&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Yeh</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17284</link>
		<dc:creator>Chris Yeh</dc:creator>
		<pubDate>Thu, 01 May 2008 22:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17284</guid>
		<description>The lack of innovation in email is astounding.  We still haven&#039;t got a good solution for searching in email, let alone advanced features like metrics on most common senders and recipients.  As long as Outlook is the default, we&#039;re stuck waiting for MSFT to truly open their APIs (announcement nonwithstanding, I&#039;m not holding my breath).  Here&#039;s hoping for a change!</description>
		<content:encoded><![CDATA[<p>The lack of innovation in email is astounding.  We still haven&#039;t got a good solution for searching in email, let alone advanced features like metrics on most common senders and recipients.  As long as Outlook is the default, we&#039;re stuck waiting for MSFT to truly open their APIs (announcement nonwithstanding, I&#039;m not holding my breath).  Here&#039;s hoping for a change!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Harrison-Broni</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17283</link>
		<dc:creator>Keith Harrison-Broni</dc:creator>
		<pubDate>Tue, 29 Apr 2008 02:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17283</guid>
		<description>&lt;p&gt;The real problems with email stem from it being a low-level protocol that was  &lt;br /&gt;
never intended to support collaborative human work processes. Hence, tinkering  &lt;br /&gt;
with the UI can only ever deliver minor improvements. Making the most of email  &lt;br /&gt;
requires a step back in order to see the wood for the trees.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Email is the key workplace tool that enables &quot;human-driven processes&quot; -  &lt;br /&gt;
adaptive, innovative, collaborative human work. This is the domain of &lt;br /&gt;
&lt;a target=&quot;_blank&quot; href=&quot;&lt;a href=&quot;http://www.human-interaction-management.info&quot; rel=&quot;nofollow&quot;&gt;Human &quot;&gt;http://www.human-interaction-management.info&amp;quot...&lt;/a&gt; &lt;br /&gt;
Interaction Management&lt;/a&gt; (aka HIM). Software based on HIM fixes the real  &lt;br /&gt;
problems of email:&lt;/p&gt; &lt;br /&gt;
&lt;ul&gt; &lt;br /&gt;
&lt;li&gt;Discussions that fizzle out, fragment among different colleagues, or  &lt;br /&gt;
lose their purpose&lt;/li&gt; &lt;br /&gt;
&lt;li&gt;Attachments scattered all over your file system&lt;/li&gt; &lt;br /&gt;
&lt;li&gt;No way of ensuring use of a specific version of an attachment, or even  &lt;br /&gt;
of knowing what version your colleagues are using&lt;/li&gt; &lt;br /&gt;
&lt;li&gt;Actions that cannot be tracked, or for which you are not sure if anyone  &lt;br /&gt;
has even taken responsibility&lt;/li&gt; &lt;br /&gt;
&lt;li&gt;Doing work without knowing what value anyone is getting from it&lt;/li&gt; &lt;br /&gt;
&lt;li&gt;Having to spend too much time assembling audit trails for work carried  &lt;br /&gt;
out&lt;/li&gt; &lt;br /&gt;
&lt;/ul&gt; &lt;br /&gt;
&lt;p&gt;The next generation productivity tool is a Human ...&lt;/a&gt;.&lt;/p&gt; &quot;&gt;http://humanedj.com&quot;&gt;HumanEdj&lt;/a&gt;.&lt;/p&gt; &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>The real problems with email stem from it being a low-level protocol that was  <br />
never intended to support collaborative human work processes. Hence, tinkering  <br />
with the UI can only ever deliver minor improvements. Making the most of email  <br />
requires a step back in order to see the wood for the trees.</p>
<p></p>
<p>Email is the key workplace tool that enables &quot;human-driven processes&quot; &#8211;  <br />
adaptive, innovative, collaborative human work. This is the domain of <br />
<a target="_blank" href="<a href="http://www.human-interaction-management.info" rel="nofollow">Human &#8220;></a><a href="http://www.human-interaction-management.info&#038;quot..." rel="nofollow">http://www.human-interaction-management.info&#038;quot&#8230;</a> <br />
Interaction Management (aka HIM). Software based on HIM fixes the real  <br />
problems of email:</p>
<p></p>
<ul></p>
<li>Discussions that fizzle out, fragment among different colleagues, or  <br />
lose their purpose</li>
<p></p>
<li>Attachments scattered all over your file system</li>
<p></p>
<li>No way of ensuring use of a specific version of an attachment, or even  <br />
of knowing what version your colleagues are using</li>
<p></p>
<li>Actions that cannot be tracked, or for which you are not sure if anyone  <br />
has even taken responsibility</li>
<p></p>
<li>Doing work without knowing what value anyone is getting from it</li>
<p></p>
<li>Having to spend too much time assembling audit trails for work carried  <br />
out</li>
<p>
</ul>
<p></p>
<p>The next generation productivity tool is a Human &#8230;.</p>
<p> &#8220;><a href="http://humanedj.com" rel="nofollow">http://humanedj.com</a>&#8220;>HumanEdj. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deva Hazarika</title>
		<link>http://www.foundrygroup.com/wp/2008/04/did-darwin-skip-over-email/comment-page-1/#comment-17282</link>
		<dc:creator>Deva Hazarika</dc:creator>
		<pubDate>Mon, 28 Apr 2008 13:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://test.foundrygroup.com/wp/?p=13#comment-17282</guid>
		<description>Lots of great points here, Chris.  When we started ClearContext a few years ago, one of the first things we did was compare email clients to email clients we used 10 years prior.  It was amazing to see how little they had changed (and still haven&#039;t), still oriented around working with each incoming message as an individual atomic unit.  The volume of email no longer makes that practical for many of us.  That&#039;s one area in need of improvement - simply managing the flow of information.  Once that&#039;s done, exposing all the relationships between messages, contacts, attachments, and all the other information passing through the messaging system is the next untapped opportunity.  Putting structure around those data relationships is the core of what we&#039;re focused on at ClearContext.  The third area, where we&#039;re starting to put more focus on, is around handling different types of email in different, more intelligent ways.  Email clients for the most part today handle all emails the same - whether it&#039;s an email asking you to lunch, a picture of your friend&#039;s baby, or a notification that a friend has added you on Facebook.  That doesn&#039;t make sense.  We&#039;re hoping to provide integrated solutions encompassing all three of these areas.   My post from a few months back describing my email and inbox thesis echoes many of the points you make: &lt;a href=&quot;http://www.emaildashboard.com/2008/01/my-email-and-in.html &quot; rel=&quot;nofollow&quot;&gt;http://www.emaildashboard.com/2008/01/my-email-an...&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Lots of great points here, Chris.  When we started ClearContext a few years ago, one of the first things we did was compare email clients to email clients we used 10 years prior.  It was amazing to see how little they had changed (and still haven&#039;t), still oriented around working with each incoming message as an individual atomic unit.  The volume of email no longer makes that practical for many of us.  That&#039;s one area in need of improvement &#8211; simply managing the flow of information.  Once that&#039;s done, exposing all the relationships between messages, contacts, attachments, and all the other information passing through the messaging system is the next untapped opportunity.  Putting structure around those data relationships is the core of what we&#039;re focused on at ClearContext.  The third area, where we&#039;re starting to put more focus on, is around handling different types of email in different, more intelligent ways.  Email clients for the most part today handle all emails the same &#8211; whether it&#039;s an email asking you to lunch, a picture of your friend&#039;s baby, or a notification that a friend has added you on Facebook.  That doesn&#039;t make sense.  We&#039;re hoping to provide integrated solutions encompassing all three of these areas.   My post from a few months back describing my email and inbox thesis echoes many of the points you make: <a href="http://www.emaildashboard.com/2008/01/my-email-and-in.html " rel="nofollow">http://www.emaildashboard.com/2008/01/my-email-an&#8230;</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

