<?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: UIEtips Article: Visible Narratives: Understanding Visual Organization</title>
	<atom:link href="http://www.uie.com/brainsparks/2006/10/31/uietips-article-visible-narratives-understanding-visual-organization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2006/10/31/uietips-article-visible-narratives-understanding-visual-organization/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<pubDate>Fri,  8 Aug 2008 18:20:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Todd O'Neill</title>
		<link>http://www.uie.com/brainsparks/2006/10/31/uietips-article-visible-narratives-understanding-visual-organization/#comment-32579</link>
		<dc:creator>Todd O'Neill</dc:creator>
		<pubDate>Thu, 02 Nov 2006 22:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=372#comment-32579</guid>
		<description>I think the quote from Stanford (''We find that people quickly evaluate a site by visual design alone.'' -- Stanford Guidelines for Web Credibility, 2002") needs to be interpreted correctly.
DISCLAIMER: I have not read their study.
I come to the web discipline from the film and video discipline. In that world we refer to what Stanford is referring to as "production value." 
Think about channel surfing on cable. You hit the local public access channel then click again and hit one of the big networks. Chances are you won't click back to the public access channel because the production values (the program look and feel) aren't as good, therefore the programming has less credibility.
Did I miss Luke's reference to this effect? Only after your site's "production value" captures an audience can you expose them to your message, credible or not.
Int eh web world we so often discuss the "micro" design of web content that we often miss the "macro" design. I think the perceived difference between film/video and the web is that the former is a thought of as "broadcast" and the latter as "narrow-cast." 
All web content/presentation/functionality is "broadcast" due the ubiquitous and border crossing nature of the Internet. No matter what, if it ain't "ready for prime time" it ain't ready, no matter how much thought went into the micro design.</description>
		<content:encoded><![CDATA[<p>I think the quote from Stanford (&#8221;We find that people quickly evaluate a site by visual design alone.&#8221; &#8212; Stanford Guidelines for Web Credibility, 2002&#8243;) needs to be interpreted correctly.<br />
DISCLAIMER: I have not read their study.<br />
I come to the web discipline from the film and video discipline. In that world we refer to what Stanford is referring to as &#8220;production value.&#8221;<br />
Think about channel surfing on cable. You hit the local public access channel then click again and hit one of the big networks. Chances are you won&#8217;t click back to the public access channel because the production values (the program look and feel) aren&#8217;t as good, therefore the programming has less credibility.<br />
Did I miss Luke&#8217;s reference to this effect? Only after your site&#8217;s &#8220;production value&#8221; captures an audience can you expose them to your message, credible or not.<br />
Int eh web world we so often discuss the &#8220;micro&#8221; design of web content that we often miss the &#8220;macro&#8221; design. I think the perceived difference between film/video and the web is that the former is a thought of as &#8220;broadcast&#8221; and the latter as &#8220;narrow-cast.&#8221;<br />
All web content/presentation/functionality is &#8220;broadcast&#8221; due the ubiquitous and border crossing nature of the Internet. No matter what, if it ain&#8217;t &#8220;ready for prime time&#8221; it ain&#8217;t ready, no matter how much thought went into the micro design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sleep2death.blog(); &#187; 如何组织视觉内容（Understanding Visual Organization 翻译）</title>
		<link>http://www.uie.com/brainsparks/2006/10/31/uietips-article-visible-narratives-understanding-visual-organization/#comment-32532</link>
		<dc:creator>Sleep2death.blog(); &#187; 如何组织视觉内容（Understanding Visual Organization 翻译）</dc:creator>
		<pubDate>Thu, 02 Nov 2006 11:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=372#comment-32532</guid>
		<description>[...] UIEtips Article: Visible Narratives: Understanding Visual Organization&#8221; href=&#8221;http://www.uie.com/brainsparks/2006/10/31/uietips-article-visible-narratives-understanding-visual-organization/&#8221; rel=&#8221;bookmark&#8221;&#62; Understanding Visual Organization [...]</description>
		<content:encoded><![CDATA[<p>[...] UIEtips Article: Visible Narratives: Understanding Visual Organization&#8221; href=&#8221;http://www.uie.com/brainsparks/2006/10/31/uietips-article-visible-narratives-understanding-visual-organization/&#8221; rel=&#8221;bookmark&#8221;&gt; Understanding Visual Organization [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hawkins</title>
		<link>http://www.uie.com/brainsparks/2006/10/31/uietips-article-visible-narratives-understanding-visual-organization/#comment-32468</link>
		<dc:creator>Chris Hawkins</dc:creator>
		<pubDate>Thu, 02 Nov 2006 01:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=372#comment-32468</guid>
		<description>Oy! As I read this, I am reminded how so often Visual Design means something different to everyone, even within UE circles. Conversations get pretty muddy when using this overloaded phrase.  This creates problems, especially in promoting the UE process, design and the skills sets required.   It's a pet peeve, and one of the most aggravating growing pains as a UE discipline we have right now.  It helps, in part, to perpetuate the lipstick-on-the- pig mentality.

Ok, now that I've ranted  - the deal is that any good UE person knows there are TWO VERY DIFFERENT components to Visual Design.  And we need words around this to discuss it intelligently.  

Component 1 - Layout, alignment and use of color or shape to guide or inform users.  This is about whether a button is green or yellow, or if information is aligned for easier scanning, or if a button is placed where a user will find it.   It's all about supporting the user interaction.  THIS is VERY different than 

Component 2 - Aesthetics - how colors compliment each other and how pretty the buttons are.

I  suggest we cut to the chase in our discussions around Visual Design, and immediately define the context,  before talking any further.   I propose we start using these words/definitions based around these aspects:

1) (Visual) Layout and Form, "user experience as function" and
2) (Visual) Look and Feel "Aesthetics" - beauty.

#1, Layout and Form is part of supporting the interaction design and subordinate to #2, prettying it up.   Of course, there is conflict and overlap at times, but bottom line "Form follows function." Doesn't mean you should ignore aesthetics - I believe it is VERY important -  but lets' keep it in context, shall we?  

Without this granularity, we muddy things up, for example, in delegating proper resources.  Layout &#38; form decisions differ from aesthetic decisions.  ANd interaction/workflow specialists are not always great at Layout &#38; form.  Graphic artists (primarily aestheticians) often do not understand how the presentation - layout, form, button placement - must work IN CONJUNCTION with a dynamically changing, often task-based situation - as they work with static screens and often do not have user experience training.  

My two cents,
Chris Hawkins
chris@usermatters.com
designer :: manager :: rabble rouser</description>
		<content:encoded><![CDATA[<p>Oy! As I read this, I am reminded how so often Visual Design means something different to everyone, even within UE circles. Conversations get pretty muddy when using this overloaded phrase.  This creates problems, especially in promoting the UE process, design and the skills sets required.   It&#8217;s a pet peeve, and one of the most aggravating growing pains as a UE discipline we have right now.  It helps, in part, to perpetuate the lipstick-on-the- pig mentality.</p>
<p>Ok, now that I&#8217;ve ranted  - the deal is that any good UE person knows there are TWO VERY DIFFERENT components to Visual Design.  And we need words around this to discuss it intelligently.  </p>
<p>Component 1 - Layout, alignment and use of color or shape to guide or inform users.  This is about whether a button is green or yellow, or if information is aligned for easier scanning, or if a button is placed where a user will find it.   It&#8217;s all about supporting the user interaction.  THIS is VERY different than </p>
<p>Component 2 - Aesthetics - how colors compliment each other and how pretty the buttons are.</p>
<p>I  suggest we cut to the chase in our discussions around Visual Design, and immediately define the context,  before talking any further.   I propose we start using these words/definitions based around these aspects:</p>
<p>1) (Visual) Layout and Form, &#8220;user experience as function&#8221; and<br />
2) (Visual) Look and Feel &#8220;Aesthetics&#8221; - beauty.</p>
<p>#1, Layout and Form is part of supporting the interaction design and subordinate to #2, prettying it up.   Of course, there is conflict and overlap at times, but bottom line &#8220;Form follows function.&#8221; Doesn&#8217;t mean you should ignore aesthetics - I believe it is VERY important -  but lets&#8217; keep it in context, shall we?  </p>
<p>Without this granularity, we muddy things up, for example, in delegating proper resources.  Layout &amp; form decisions differ from aesthetic decisions.  ANd interaction/workflow specialists are not always great at Layout &amp; form.  Graphic artists (primarily aestheticians) often do not understand how the presentation - layout, form, button placement - must work IN CONJUNCTION with a dynamically changing, often task-based situation - as they work with static screens and often do not have user experience training.  </p>
<p>My two cents,<br />
Chris Hawkins<br />
<a href="mailto:chris@usermatters.com">chris@usermatters.com</a><br />
designer :: manager :: rabble rouser</p>
]]></content:encoded>
	</item>
</channel>
</rss>
