<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Marion, Craig</title>	<link>http://tc.eserver.org/authors/Marion,_Craig</link>
	<description>A bibliography of works by Marion, Craig in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Marion, Craig</title>
		<link>http://tc.eserver.org/dir/Marion,_Craig</link>
	</image>
	<item>
		<title>What is Interaction Design, and What Does It Mean to Information Designers?</title>
		<link>http://tc.eserver.org/28245.html</link>
		<guid>http://tc.eserver.org/28245.html</guid>
		<description>Where did the term interaction design come from? What exactly does it mean? And what do the people who call themselves interaction designers actually do?</description>
	</item>
	<item>
		<title>From Online Help to Integrated User Assistance: One Company’s Journey Beyond the Online Help Paradigm</title>
		<link>http://tc.eserver.org/18766.html</link>
		<guid>http://tc.eserver.org/18766.html</guid>
		<description>For usability’s sake, the development group at Strohl Systems created a navigational coach that embedded user assistance within the company&apos;s flagship product. Now we&apos;re redesigning the product and building it around the user assistance.</description>
	</item>
	<item>
		<title>Attributes of Performance-Centered Systems: What Can We Learn from Five Years of EPSS/PCD Competition Award Winners?</title>
		<link>http://tc.eserver.org/14245.html</link>
		<guid>http://tc.eserver.org/14245.html</guid>
		<description>Reviews briefly the systems that Gery presented in &lt;i&gt;Electronic Performance Support Systems&lt;/i&gt; and then focuses on the 19 attributes she subsequently developed to elucidate them. Then examines the 1997–2001 competition award winners in light of these attributes. Doing so, it turns out, both clarifies the attributes and suggests a few new ones.</description>
	</item>
	<item>
		<title>EPSS: What Does It Mean to You</title>
		<link>http://tc.eserver.org/11821.html</link>
		<guid>http://tc.eserver.org/11821.html</guid>
		<description>Electronic Performance Support System(s), or EPSS, automates three types of traditional performance support for software users: training, documentation, and help desks. Integrating these support mechanisms into software--using wizards, clear and simple interfaces, and various forms of embedded user assistance--allows novice users to perform competently with minimal help from training, documentation or calls to help desks. </description>
	</item>
	<item>
		<title>Quality, Usability, and the Ontological Argument for the Existence of God</title>
		<link>http://tc.eserver.org/11779.html</link>
		<guid>http://tc.eserver.org/11779.html</guid>
		<description>I’ve been involved with the usability movement for about five years. It’s occurred to me more than once: what’s the difference between &apos;usable&apos; software and just plain &apos;software that works the way it’s supposed to?&apos; The answer—for both quality and usability, I believe—hinges on the meaning of &apos;works the way it’s supposed to.&apos; Once, processes just evolved. They were changed sometimes, but they were never systematically evaluated. Having standards applied made them quality processes.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Marion,_Craig.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>