<?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: Design Presentation &#8212; Style vs. Accuracy</title>
	<atom:link href="http://www.refreshcleveland.org/2008/08/17/design-presentation-style-vs-accuracy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.refreshcleveland.org/2008/08/17/design-presentation-style-vs-accuracy/</link>
	<description>Refreshing the web, one city at a time</description>
	<pubDate>Tue, 06 Jan 2009 06:01:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Adam</title>
		<link>http://www.refreshcleveland.org/2008/08/17/design-presentation-style-vs-accuracy/#comment-2255</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 18 Aug 2008 14:22:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.refreshcleveland.org/?p=64#comment-2255</guid>
		<description>I understand your frustration with the anecdote you'd described - and while I haven't had quite the same experience, I have had one that's similar and also befuddled me.  We were working on a new site for a client - very minimal stuff, as they were not very tech savvy - and to relay some edits, they literally printed out every page and then commented on the way the information looked on the printed page.  Not that bad you say?  Here's the kicker - they were making design comments on what was essentially (at this point) the print style sheet! Stuff like "This header is redundant," (it was the Title Tag and the H1), or "I don't like the spacing between these images," (on the completely unstyled printout.)"  It was like they'd almost never even looked at the styled site on-screen!  Like I said - not exactly the same, but another case of "on-the-page/on-the-screen" not matching up and causing confusion.</description>
		<content:encoded><![CDATA[<p>I understand your frustration with the anecdote you&#8217;d described - and while I haven&#8217;t had quite the same experience, I have had one that&#8217;s similar and also befuddled me.  We were working on a new site for a client - very minimal stuff, as they were not very tech savvy - and to relay some edits, they literally printed out every page and then commented on the way the information looked on the printed page.  Not that bad you say?  Here&#8217;s the kicker - they were making design comments on what was essentially (at this point) the print style sheet! Stuff like &#8220;This header is redundant,&#8221; (it was the Title Tag and the H1), or &#8220;I don&#8217;t like the spacing between these images,&#8221; (on the completely unstyled printout.)&#8221;  It was like they&#8217;d almost never even looked at the styled site on-screen!  Like I said - not exactly the same, but another case of &#8220;on-the-page/on-the-screen&#8221; not matching up and causing confusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mead</title>
		<link>http://www.refreshcleveland.org/2008/08/17/design-presentation-style-vs-accuracy/#comment-2242</link>
		<dc:creator>David Mead</dc:creator>
		<pubDate>Mon, 18 Aug 2008 01:16:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.refreshcleveland.org/?p=64#comment-2242</guid>
		<description>Thanks for stepping in and posting this Chris.

My opinion is the design print out should be as good a quality as possible - It is a presentation after all.

Inconsistencies with the rendering can be addressed in subsequent meetings, where you can explain them easily, accompanied by screen-shots in a PDF.</description>
		<content:encoded><![CDATA[<p>Thanks for stepping in and posting this Chris.</p>
<p>My opinion is the design print out should be as good a quality as possible - It is a presentation after all.</p>
<p>Inconsistencies with the rendering can be addressed in subsequent meetings, where you can explain them easily, accompanied by screen-shots in a PDF.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
