<?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: Only Run Digital Strategy As Far As You Can Run Back</title>
	<atom:link href="http://blog.michaelleis.com/2009/09/only-run-digital-strategy-as-far-as-you-can-run-back/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.michaelleis.com/2009/09/only-run-digital-strategy-as-far-as-you-can-run-back/</link>
	<description>In bite-sized servings</description>
	<lastBuildDate>Thu, 04 Mar 2010 20:34:46 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Lang</title>
		<link>http://blog.michaelleis.com/2009/09/only-run-digital-strategy-as-far-as-you-can-run-back/comment-page-1/#comment-543</link>
		<dc:creator>Ben Lang</dc:creator>
		<pubDate>Mon, 21 Sep 2009 23:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelleis.com/?p=479#comment-543</guid>
		<description>Hey Michael, Nice to meet you on Twitter.&lt;br&gt;Regards.</description>
		<content:encoded><![CDATA[<p>Hey Michael, Nice to meet you on Twitter.<br />Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mleis</title>
		<link>http://blog.michaelleis.com/2009/09/only-run-digital-strategy-as-far-as-you-can-run-back/comment-page-1/#comment-541</link>
		<dc:creator>mleis</dc:creator>
		<pubDate>Wed, 02 Sep 2009 09:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelleis.com/?p=479#comment-541</guid>
		<description>All good points Dan. I&#039;m definitely making the assumption that in order to do this, one would create a framework of communication between the site and the platforms, and a mix of manual techniques and API or widget-based integration. It doesn&#039;t have to be difficult, much like the Disqus component here for commenting and sharing simultaneously.</description>
		<content:encoded><![CDATA[<p>All good points Dan. I&#39;m definitely making the assumption that in order to do this, one would create a framework of communication between the site and the platforms, and a mix of manual techniques and API or widget-based integration. It doesn&#39;t have to be difficult, much like the Disqus component here for commenting and sharing simultaneously.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Thornton</title>
		<link>http://blog.michaelleis.com/2009/09/only-run-digital-strategy-as-far-as-you-can-run-back/comment-page-1/#comment-540</link>
		<dc:creator>Dan Thornton</dc:creator>
		<pubDate>Tue, 01 Sep 2009 18:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelleis.com/?p=479#comment-540</guid>
		<description>Interesting point - I&#039;ve certainly seen a number of companies invest in the time and resource to run a flashy social media campaign on an external social network, and ignore the one that&#039;s sat on their own site, gathering weeds and being ignored.&lt;br&gt;I definitely think there are interesting ways to bring external content into your main website, wether it&#039;s by aggregating tweets, or by running campaigns on Facebook or Flickr, for example, to generate content - the important thing is to make sure it&#039;s clear that the content will also end up on the main site, and to also remember that you need to also be rewarded that external community, rather than just using them to create content, harvesting the best bits, and then rubbing off again!&lt;br&gt;Tools like APIs are also useful, in allowing people to share previously uploaded content for other sites with yours when they register or want to add to their profile on your site - nothing worse than wanting to share a picture with a group of people and having to download it from somewhere else and than re-upload it again. And these days, it&#039;s almost totally uneccessary.</description>
		<content:encoded><![CDATA[<p>Interesting point &#8211; I&#39;ve certainly seen a number of companies invest in the time and resource to run a flashy social media campaign on an external social network, and ignore the one that&#39;s sat on their own site, gathering weeds and being ignored.<br />I definitely think there are interesting ways to bring external content into your main website, wether it&#39;s by aggregating tweets, or by running campaigns on Facebook or Flickr, for example, to generate content &#8211; the important thing is to make sure it&#39;s clear that the content will also end up on the main site, and to also remember that you need to also be rewarded that external community, rather than just using them to create content, harvesting the best bits, and then rubbing off again!<br />Tools like APIs are also useful, in allowing people to share previously uploaded content for other sites with yours when they register or want to add to their profile on your site &#8211; nothing worse than wanting to share a picture with a group of people and having to download it from somewhere else and than re-upload it again. And these days, it&#39;s almost totally uneccessary.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
