<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Business Plans in 2009</title>
	<atom:link href="http://www.jarche.com/2007/05/business-plans-in-2009/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jarche.com/2007/05/business-plans-in-2009/</link>
	<description>Life in Perpetual Beta</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:59:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Harold Jarche &#187; Business models looking back and forward</title>
		<link>http://www.jarche.com/2007/05/business-plans-in-2009/comment-page-1/#comment-193031</link>
		<dc:creator>Harold Jarche &#187; Business models looking back and forward</dc:creator>
		<pubDate>Wed, 06 Jan 2010 20:45:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.jarche.com/?p=1173#comment-193031</guid>
		<description>[...] 2007 I examined these predictions from the perspective of business planning and made these [...]</description>
		<content:encoded><![CDATA[<p>[...] 2007 I examined these predictions from the perspective of business planning and made these [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harold Jarche &#187; Workplace learning in ten years</title>
		<link>http://www.jarche.com/2007/05/business-plans-in-2009/comment-page-1/#comment-186872</link>
		<dc:creator>Harold Jarche &#187; Workplace learning in ten years</dc:creator>
		<pubDate>Sun, 01 Mar 2009 20:45:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.jarche.com/?p=1173#comment-186872</guid>
		<description>[...] the intervening decade I wondered about some of the technological changes. We now have practically unlimited digital storage; increasing bandwidth, almost ubiquitous [...]</description>
		<content:encoded><![CDATA[<p>[...] the intervening decade I wondered about some of the technological changes. We now have practically unlimited digital storage; increasing bandwidth, almost ubiquitous [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karyn Romeis</title>
		<link>http://www.jarche.com/2007/05/business-plans-in-2009/comment-page-1/#comment-121181</link>
		<dc:creator>Karyn Romeis</dc:creator>
		<pubDate>Tue, 22 May 2007 09:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.jarche.com/?p=1173#comment-121181</guid>
		<description>In all the countries I know about, there is this thing called curriculum, where a bunch of people have sat down and decided what a child needs to know by the time s/he is 18. I would love to have a conversation with this group of people to find out what their criteria are. On what do they base their decisions? How do they decide what subjects to include and what each syllabus will look like? What do &lt;b&gt;they&lt;/b&gt; think they are education kids &lt;b&gt;for&lt;/b&gt;?

If we can first have that argument, and resolve what the right answer to that question should be, then perhaps we can start again from scratch deciding what to teach kids at school!</description>
		<content:encoded><![CDATA[<p>In all the countries I know about, there is this thing called curriculum, where a bunch of people have sat down and decided what a child needs to know by the time s/he is 18. I would love to have a conversation with this group of people to find out what their criteria are. On what do they base their decisions? How do they decide what subjects to include and what each syllabus will look like? What do <b>they</b> think they are education kids <b>for</b>?</p>
<p>If we can first have that argument, and resolve what the right answer to that question should be, then perhaps we can start again from scratch deciding what to teach kids at school!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

