<?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: Live review of higher education web sites #2</title>
	<atom:link href="http://nickdenardis.com/2008/10/17/live_review_of_higher_education_web_sites_2/feed/" rel="self" type="application/rss+xml" />
	<link>http://nickdenardis.com/2008/10/17/live_review_of_higher_education_web_sites_2/</link>
	<description>Web Dev. Higher Ed. Usability. Accessibility. Ninja.</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:38:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: George Sackett</title>
		<link>http://nickdenardis.com/2008/10/17/live_review_of_higher_education_web_sites_2/comment-page-1/#comment-34</link>
		<dc:creator>George Sackett</dc:creator>
		<pubDate>Sat, 18 Oct 2008 10:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://nickdenardis.com/2008/10/17/live_review_of_higher_education_web_sites_2/#comment-34</guid>
		<description>&lt;p&gt;Well done for a second effort. I find your video&#8217;s very instructional. We re-did our website trying to look at it from a user perspective. It is helpful to get another view on what a user might be looking for. There is always some room for interpretation on looks but your points about usability and what should be a priority is both reinforcing and helpful in expanding our thoughts. For example we are going to add links to the course descriptions to all the required course pages and your dialog helps re-inforce that we are doing the right thing.&lt;/p&gt;&lt;p&gt;My preference would be to do a single ten minute summary of the the steps that you use to evaluate a site. Not just an example but a tutorial sort of &#8230; and then a series of run-throughs showing what you find good and bad. The tutorial would be very helpful in itself and then the run-throughs would be good re-enforcement. Also keep the run-throughs to no more than two schools. 23 minutes is quite a long time to hold your audience&#8217;s attention.&lt;/p&gt;&lt;p&gt;When I get the updates done I may ask for your input on our progress. &#8211; - You may want to think about how to handle such requests in the future. It could be overwhelming &#8230; . . the easiest answer is no but it could be a great hook to expand your audience &#8230;&lt;/p&gt;&lt;p&gt;Best of luck and have fun at the wedding.&lt;/p&gt;&lt;p&gt;George&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Well done for a second effort. I find your video&#8217;s very instructional. We re-did our website trying to look at it from a user perspective. It is helpful to get another view on what a user might be looking for. There is always some room for interpretation on looks but your points about usability and what should be a priority is both reinforcing and helpful in expanding our thoughts. For example we are going to add links to the course descriptions to all the required course pages and your dialog helps re-inforce that we are doing the right thing.</p>
<p>My preference would be to do a single ten minute summary of the the steps that you use to evaluate a site. Not just an example but a tutorial sort of &#8230; and then a series of run-throughs showing what you find good and bad. The tutorial would be very helpful in itself and then the run-throughs would be good re-enforcement. Also keep the run-throughs to no more than two schools. 23 minutes is quite a long time to hold your audience&#8217;s attention.</p>
<p>When I get the updates done I may ask for your input on our progress. &#8211; &#8211; You may want to think about how to handle such requests in the future. It could be overwhelming &#8230; . . the easiest answer is no but it could be a great hook to expand your audience &#8230;</p>
<p>Best of luck and have fun at the wedding.</p>
<p>George</p>
]]></content:encoded>
	</item>
</channel>
</rss>

