<?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"
	>
<channel>
	<title>Comments on: Lines in the sand</title>
	<atom:link href="http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/feed/" rel="self" type="application/rss+xml" />
	<link>http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/</link>
	<description>Philip Hutchison's technology journal, dedicated to exploring web technologies for website and e-learning development.</description>
	<pubDate>Mon, 06 Oct 2008 20:08:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Brian Dusablon</title>
		<link>http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/#comment-279</link>
		<dc:creator>Brian Dusablon</dc:creator>
		<pubDate>Mon, 31 Mar 2008 18:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/#comment-279</guid>
		<description>Brilliant post, man. I am struggling with the same issues - but I do believe there is room for everyone.

The key now is determining which projects require more in-depth A&#38;D (&#38;E, if we're lucky) work and maximizing ROI on both the small and the large projects.

Politics and money will play a big part in most companies in deciding which projects get the funding for the full ADDIE work.</description>
		<content:encoded><![CDATA[<p>Brilliant post, man. I am struggling with the same issues - but I do believe there is room for everyone.</p>
<p>The key now is determining which projects require more in-depth A&amp;D (&amp;E, if we&#8217;re lucky) work and maximizing ROI on both the small and the large projects.</p>
<p>Politics and money will play a big part in most companies in deciding which projects get the funding for the full ADDIE work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive Shepherd</title>
		<link>http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/#comment-278</link>
		<dc:creator>Clive Shepherd</dc:creator>
		<pubDate>Sun, 30 Mar 2008 08:28:22 +0000</pubDate>
		<guid isPermaLink="false">http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/#comment-278</guid>
		<description>Great post Philip. You're agonising about the same things as me. It will be interesting to see where this all leads.</description>
		<content:encoded><![CDATA[<p>Great post Philip. You&#8217;re agonising about the same things as me. It will be interesting to see where this all leads.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/#comment-277</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Sat, 29 Mar 2008 12:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://pipwerks.com/journal/2008/03/28/lines-in-the-sand/#comment-277</guid>
		<description>Funny story, Philip...

Yesterday, I'm pulled into an emergency phone call.  We have a variety of issues that pop up because even though we've standardized the use of Articulate to generate E-Learning, our ISDs are maturing in their E-Learning Design skills that they're now pushing the technical envelope of what you can do with Articulate... to the point where we have a small but pervasive set of repeatable issues with Articulate tracking in the LMS.

Articulate, as a Rapid E-Learning tool, is the gateway... um.. tool to another tool.  My people are self-identifying that Articulate can't be used for every E-Learning situation.  I could've directed them to a better tool at the same time as I introduced them to Articulate (or instead of it), but without that pain, they would not have learned for themselves the **why**.

The good news is that we're already on track for a collaborative tool (I'm currently fancying Unison, but I'm still pretty open to suggestions)  that can handle a larger array of design requirements.

The whole point is your whole point -- it takes time and effort to make something stick.  Garbage in... is garbage out.</description>
		<content:encoded><![CDATA[<p>Funny story, Philip&#8230;</p>
<p>Yesterday, I&#8217;m pulled into an emergency phone call.  We have a variety of issues that pop up because even though we&#8217;ve standardized the use of Articulate to generate E-Learning, our ISDs are maturing in their E-Learning Design skills that they&#8217;re now pushing the technical envelope of what you can do with Articulate&#8230; to the point where we have a small but pervasive set of repeatable issues with Articulate tracking in the LMS.</p>
<p>Articulate, as a Rapid E-Learning tool, is the gateway&#8230; um.. tool to another tool.  My people are self-identifying that Articulate can&#8217;t be used for every E-Learning situation.  I could&#8217;ve directed them to a better tool at the same time as I introduced them to Articulate (or instead of it), but without that pain, they would not have learned for themselves the **why**.</p>
<p>The good news is that we&#8217;re already on track for a collaborative tool (I&#8217;m currently fancying Unison, but I&#8217;m still pretty open to suggestions)  that can handle a larger array of design requirements.</p>
<p>The whole point is your whole point &#8212; it takes time and effort to make something stick.  Garbage in&#8230; is garbage out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
