<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Social Media Curation with Keepstream&#187; Startup</title>
	<atom:link href="http://blog.keepstream.com/category/startup/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.keepstream.com</link>
	<description>Insights into social media curation, marketing, and startups.</description>
	<lastBuildDate>Wed, 07 Sep 2011 19:46:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Hashable lessons learned: iteration, simplification, and social strategy</title>
		<link>http://blog.keepstream.com/2011/03/hashable-lessons-learned/</link>
		<comments>http://blog.keepstream.com/2011/03/hashable-lessons-learned/#comments</comments>
		<pubDate>Sat, 05 Mar 2011 08:31:14 +0000</pubDate>
		<dc:creator>Jim England</dc:creator>
				<category><![CDATA[Startup]]></category>

		<guid isPermaLink="false">http://blog.keepstream.com/?p=176</guid>
		<description><![CDATA[Last night, Keepstream co-founder Jim England took a few minutes to attend the Hashable Happy Hour in Austin, TX. CMO Emily Hickey and VP of Biz Dev Jane Kim were on hand to demonstrate their product and lead an engaging conversation on the future of...]]></description>
			<content:encoded><![CDATA[<p>Last night, Keepstream co-founder Jim England took a few minutes to attend the Hashable Happy Hour in Austin, TX. CMO Emily Hickey and VP of Biz Dev Jane Kim were on hand to demonstrate their product and lead an engaging conversation on the future of the company.</p>
<p>Hashable is a tool to keep track of new people you meet in the real-world and see who your friends are meeting. Typing in the Twitter handle of a newly-aquainted contact in the iPhone or Android app will generate a #justmet tweet mentioning both parties. Connecting in this fashion is more useful than simply exchanging business cards; both parties are exposed to inherent social pressure (the tweet is public) and have an incentive to continue the relationship.</p>
<p><img src="https://lh6.googleusercontent.com/GupHQRRz6yJZwzi5f4WWUQgmACWBI92S01-OZemjzfgnDNZShT4kRCKmA7l8OfQgFKdllnVjRYYY5sYWrkRzNcQclCofu2H-SpwSq6HCCjFWth1Z3y4" alt="" width="500px;" height="387px;" /></p>
<p>During the presentation, attendees were exposed to a candid history of Hashable and how the team developed the app over the past year. There were a number of actionable takeaways that other startups can utilize in the development of their products:</p>
<h3><strong>Iterate on early product concepts with small test batches</strong></h3>
<p>Before Hashable had a definitive product roadmap, the team would release simple prototypes to small groups of 20 people. Each release was given to a unique set of testers and engagement on the prototype was scrutinized in excruciating detail.</p>
<p>With an extremely constrained sample size, the team could quickly determine if they were onto something based on the active usage of just a few people. The team experimented for a few months before landing upon the #justmet concept.</p>
<h3><strong>&#8220;Nerdy&#8221; input methods are confusing for many users</strong></h3>
<p>In the early versions of Hashable, users could only make connections through specific #hashtag tweet syntax on Twitter. While it was a neat trick for power Twitter users, the command-line input method was complex and intimidating for many people. Hashable remedied this issue by providing web and (more recently) iPhone and Android apps for connection inputs.</p>
<p><img id="internal-source-marker_0.8176535528618842" src="https://lh5.googleusercontent.com/zRmHUp0EMEcUBC858-_6SoEVp13RSYUjzQFTUAT4EROGi5fqZYrOUqf5l_RocgXCjnucWTp8kzdtEuviwuAC9YrFMbJKpaFwHjWX7cnOo3HeVJFz9JI" alt="" width="500px;" height="202px;" /></p>
<p>Don’t always assume that the cool or unique way to interface with your app will work for everyone&#8230; simplify the process for non-early adopters.</p>
<h3><strong>Target key influencers in a calculated and strategic fashion</strong></h3>
<p>The Hashable team, like many other startups, created a list of the top influencers in the startup community: VCs, angel investors, popular startup co-founders, etc. Hashable went further, segmenting individuals into categories and adding lesser-known influentials to their lists. They generated a list that included more than the typical &#8220;elite&#8221; of Silicon Valley.</p>
<p>With an extensive list in hand, Hashable hustled to get the top-tier influencers signed up for the app. They were not as concerned with the level of activity of these users; Hashable wanted the “big names” in place for when they invited everybody else.</p>
<p>Getting “name-worthly” people in your system, even if they are light users of the app, can immensely help with the credibility of your startup and your brand.</p>
<p>&#8212;<br />
Hashable is looking to rock #SXSW this year; feel free to #justmet the Keepstream team if you meet us in person. Check out tweets from the Austin #HashyHour in the Keepstream collection below.</p>
<p><script src="http://keepstream.com/JimEngland/austin-hashtag-hashyhour-at-thinktiv.js" type="text/javascript"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.keepstream.com/2011/03/hashable-lessons-learned/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Evolution of Digg [SCREENSHOTS]</title>
		<link>http://blog.keepstream.com/2011/02/the-evolution-of-digg-screenshots/</link>
		<comments>http://blog.keepstream.com/2011/02/the-evolution-of-digg-screenshots/#comments</comments>
		<pubDate>Tue, 15 Feb 2011 17:07:24 +0000</pubDate>
		<dc:creator>Tim Gasper</dc:creator>
				<category><![CDATA[Startup]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[digg]]></category>
		<category><![CDATA[hackernews]]></category>
		<category><![CDATA[startups]]></category>
		<category><![CDATA[user interface]]></category>
		<category><![CDATA[wayback machine]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://blog.keepstream.com/?p=158</guid>
		<description><![CDATA[I had a thought cross my mind. I never really used Digg much &#8211; not now or in the past. So I never really got to see how the site evolved over time. So I dugg (haha.) back through web time using a really cool...]]></description>
			<content:encoded><![CDATA[<p><img class="size-medium wp-image-166 alignright" title="diggsite" src="http://blog.keepstream.com/wp-content/uploads/2011/02/diggsite-300x271.png" alt="Digg Site" width="144" height="130" />I had a thought cross my mind. I never really used Digg much &#8211; not now or in the past. So I never really got to see how the site evolved over time. So I dugg (haha.) back through web time using a really cool tool called The Wayback Machine at <a href="http://www.archive.org/web/web.php">http://www.archive.org/web/web.php</a>.</p>
<p><strong>Digg 1.0</strong><strong><br />
</strong><strong> </strong>It&#8217;s a barebones site with the core functionality and nothing more. Reminds me of Hacker News in some ways.</p>
<div id="attachment_159" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-07-01-2005.png"><img class="size-medium wp-image-159 " title="digg-07-01-2005" src="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-07-01-2005-300x182.png" alt="" width="300" height="182" /></a><p class="wp-caption-text">Digg v 1.0 - click to expand</p></div>
<p><strong>Digg 2.0</strong><br />
Now we start to see some familiar elements. Good &#8216;ol Helvetica. Yellow digg count boxes. Timestamps.</p>
<div id="attachment_160" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-08-01-2005.png"><img class="size-medium wp-image-160" title="digg-08-01-2005" src="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-08-01-2005-300x176.png" alt="" width="300" height="176" /></a><p class="wp-caption-text">Digg v 2.0 - click to expand</p></div>
<p><strong>Digg 2.1</strong><br />
The blue top bar appears. Digg pretends the Digg Spy is new even though it&#8217;s been around for over a year haha.</p>
<div id="attachment_161" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-01-01-2006.png"><img class="size-medium wp-image-161" title="digg-01-01-2006" src="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-01-01-2006-300x176.png" alt="" width="300" height="176" /></a><p class="wp-caption-text">Digg v 2.1 - click to expand</p></div>
<p><strong>Digg 3.0</strong><br />
Digg places categories at the top. They also put focus on two key features: the ability to filter by time (24 hours, 7 days, 30 days, etc.) and the ability to quickly bury a story.</p>
<div id="attachment_162" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-01-04-2007.png"><img class="size-medium wp-image-162" title="digg-01-04-2007" src="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-01-04-2007-300x161.png" alt="" width="300" height="161" /></a><p class="wp-caption-text">Digg v 3.0 - click to expand</p></div>
<p><strong>Digg 3.1<br />
</strong>Digg adds the media types to the top nav (news, video, images, podcasts). The site has so much traffic and quantity of stories now, so they add Upcoming to show stories that aren&#8217;t the most popular but are quickly trending upward.</p>
<div id="attachment_163" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-01-03-2008.png"><img class="size-medium wp-image-163" title="digg-01-03-2008" src="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-01-03-2008-300x162.png" alt="" width="300" height="162" /></a><p class="wp-caption-text">Digg v 3.1 - click to expand</p></div>
<p><strong>Digg 3.2<br />
</strong>I&#8217;m guessing Digg realized more clicks get driven through categories, so they make that the bigger, more prominent nav element. And search gets labelled as new even though it&#8217;s been around forever. Maybe they update the results page or the algorithm.</p>
<div id="attachment_164" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-10-18-2009.png"><img class="size-medium wp-image-164" title="digg-10-18-2009" src="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-10-18-2009-300x162.png" alt="" width="300" height="162" /></a><p class="wp-caption-text">Digg v 3.2 - click to expand</p></div>
<p><strong>Digg 4.0<br />
</strong>Digg hits the big four zero and like the rest of us, has a mid-life crisis. I do enjoy the cleaner look though.</p>
<div id="attachment_165" class="wp-caption alignnone" style="width: 310px"><a href="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-v4.png"><img class="size-medium wp-image-165" title="digg-v4" src="http://blog.keepstream.com/wp-content/uploads/2011/02/digg-v4-300x160.png" alt="" width="300" height="160" /></a><p class="wp-caption-text">Digg v 4.0 - click to expand</p></div>
<p>And so that&#8217;s the story of Digg as told by their user interface. I think what I find so interesting is that Digg was iterated over the course of 6 years. Digg had to deal with a lot of scaling and behind-the-scenes work, but I feel like many startups these days build similar feature sets much more rapidly. Maybe I&#8217;m just delusional. Or maybe today&#8217;s improved programming tools and APIs are making a huge difference.</p>
<p>What do are your thoughts on Digg&#8217;s evolution?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.keepstream.com/2011/02/the-evolution-of-digg-screenshots/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

