<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BlockQuote &#187; Usability</title>
	<atom:link href="http://blockquote.be/facet/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blockquote.be</link>
	<description>a blog for webmasters practicing Information Architecture</description>
	<lastBuildDate>Tue, 17 May 2011 15:31:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>&#8220;click here&#8221; a relic from the past</title>
		<link>http://blockquote.be/2011/05/06/click-here-a-relic-from-the-past/</link>
		<comments>http://blockquote.be/2011/05/06/click-here-a-relic-from-the-past/#comments</comments>
		<pubDate>Fri, 06 May 2011 10:00:59 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[IA]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[clickhere]]></category>
		<category><![CDATA[seo]]></category>

		<guid isPermaLink="false">http://blockquote.be/?p=914</guid>
		<description><![CDATA[2.060.000.000 result from Google. That&#8217;s a lot. All those results are pages about &#8220;click here, do this, do that&#8221;. Why do people still use that on a website? &#8220;Click here&#8221; is one of those text fragments that seem to stick &#8230; <a href="http://blockquote.be/2011/05/06/click-here-a-relic-from-the-past/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>2.060.000.000 result from Google. That&#8217;s a lot.</p>
<p>All those results are pages about &#8220;click here, do this, do that&#8221;. Why do people still use that on a website?</p>
<p>&#8220;Click here&#8221; is one of those text fragments that seem to stick around. Webdesigners and <a href="http://www.useit.com/alertbox/designmistakes.html" title="Top 10 Web Design Mistakes of 2005 (Jakob Nielsen's Alertbox)">usability experts</a> recommend not using it and still, everyone does, including Adobe. Adobe Acrobat reader is the first item on <a href="http://www.google.com/#&amp;q=click+here">Google SERPs for &#8220;click here&#8221;</a>. Simply because it is used in plenty of links on a huge number of sites.<br />
<span id="more-914"></span><br />
All I can see is that people are using it, and that there is no tendency that tells me it is dying.<br />
So why not?  Why do people still use it? Dismissing it as stupidity or lack of knowledge is too easy. There must be some reason why people still use it even though there are plenty of reasons not to.</p>
<p>Content-editors still use it because it&#8217;s clear. It is clear what a visitor must do. Not what the visitors will get after the click. But that really doesn&#8217;t matter because through all the noise (the internet) this person found your website, scanned it thoroughly, found what he was looking for, and followed the instruction. What&#8217;s behind the link, who knows? Does anyone care?</p>
<p>The text fragment works more or less like an embedded command: <strong>&#8220;When you <a href="#clickthis" id="clickthis">click this</a> link, you will know more about the subject than others do.&#8221;</strong> The link becomes more attractive: it states what you should do. </p>
<p>People scan for underlined blue text. The link text &#8220;click here&#8221; enforces the concept of the link and the click becomes a jump into the unknown. </p>
<p>To click is to believe. </p>
<p>I have trained around 200 editors and I repeated it a thousand times:</p>
<ul>
<li>that the text of the link should be an indication of the subject of the referring page,</li>
<li>that it is is not good for usability/accessibility and SEO,</li>
<li>that it is uninformative</li>
</ul>
<p>&#8220;Click here&#8221; as link text is not going away in the near future even though it is disregarded as bad practice by practitioners of IA, usability and SEO. The concept is too easy to understand. It almost feels natural. </p>
<p>Links should be informative about where you&#8217;ll take the visitor, but it seems that using verbs as links is very powerful.</p>
<h2>Tell them what to do</h2>
<p>And then you get this facebook button: &#8220;like&#8221;. It&#8217;s the same thing, just better. Emotional. The link instructs. Like or die clicking!</p>
<div style="text-align:center"><img src="http://blockquote.be/wp-content/uploads/2011/05/like.png" alt="" title="like" width="120" height="53" class="aligncenter size-full wp-image-970" /></div>
<p>The facebook like button instructs you to like &#8211; <em>read click</em> &#8211; the button. It doesn&#8217;t say &#8220;I like&#8221;, it doesn&#8217;t say &#8220;click here to like&#8221;, it&#8217;s just &#8220;like&#8221;.</p>
<p>Implicitly I translate it to &#8220;I like&#8221;, as must people do (<a href="#respond">disagree with me ?</a>). But it is nothing more or less than an embedded command: like.</p>
<p>The simplicity of the concept &#8220;telling people what to do&#8221; is definitely the main reason why the &#8220;click here&#8221; link is not fading away. Even though the text fragment is pretty powerful, the reasons not to use it still prevail. <a href="#respond">Click here</a> to <a href="#respond">comment</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2011/05/06/click-here-a-relic-from-the-past/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Content strategy, the same thing in a new jacket?</title>
		<link>http://blockquote.be/2011/04/01/content-strategy-the-same-thing-in-a-new-jacket/</link>
		<comments>http://blockquote.be/2011/04/01/content-strategy-the-same-thing-in-a-new-jacket/#comments</comments>
		<pubDate>Fri, 01 Apr 2011 09:05:10 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[IA]]></category>
		<category><![CDATA[Personas]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blockquote.be/?p=600</guid>
		<description><![CDATA[I was asked if I had any experience with content strategy by an online communication expert and I could not give a clear answer. I didn&#8217;t have a clear-cut idea of what content strategy actually was. The concept is pretty &#8230; <a href="http://blockquote.be/2011/04/01/content-strategy-the-same-thing-in-a-new-jacket/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I was asked if I had any experience with content strategy by an online communication expert and I could not give a clear answer. I didn&#8217;t have a clear-cut idea of what content strategy actually was. The concept is pretty new to me, it was already on my radar, but I just could not get my finger on the pulse. </p>
<p>So <a href="http://www.alistapart.com/articles/thedisciplineofcontentstrategy/">I looked around</a>, found a few <a href="http://knol.google.com/k/content-strategy">articles on the subject</a>, and I bought a book.<br />
The book <a href="http://www.abookapart.com/products/the-elements-of-content-strategy">&#8220;The Elements of Content Strategy&#8221; written by Erin Kissane</a> published by A Book Apart.</p>
<p><span id="more-600"></span></p>
<p>I devoured the book: short and concise writing and it provides a clear picture of the relationship with other functions in the webteam (editors, IAs, designers, etc..). I was happy to discover that the section of useful resources has a list of books that I had read or own:
</p>
<ul>
<li><a href="http://www.amazon.com/gp/product/0596527349/ref=as_li_ss_tl?ie=UTF8&#038;tag=bloabloforweb-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0596527349">Information Architecture for the World Wide Web by Lou Rosenfeld</a>, </li>
<li><a href="http://www.amazon.com/gp/product/0321344758/ref=as_li_ss_tl?ie=UTF8&#038;tag=bloabloforweb-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0321344758">Don&#8217;t make me think by Steve Krug</a>, </li>
<li><a href="http://www.amazon.com/gp/product/0321683684/ref=as_li_ss_tl?ie=UTF8&#038;tag=bloabloforweb-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0321683684">The Elements of User Experience by Jess James Garret</a> and </li>
<li><a href="http://www.amazon.com/gp/product/0735713065/ref=as_li_ss_tl?ie=UTF8&#038;tag=bloabloforweb-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0735713065">Managing Enterprise Content by Ann Rockley</a>.  </li>
</ul>
<p>Seems I should have some idea of what content strategy is, right?</p>
<p>The book explains a few things about Content strategists. Basically a <abbr title="Content Strategist">CS</abbr> thinks about the who, what, where and why of content.
</p>
<p><strong>Who will publish that document?</strong><br />
Editors need to be trained, and the document needs to go through a process, formal or informal, to make sure it is properly published. Document life-cycle is part of what a <abbr title="Content Strategist">CS</abbr> does, but that is also what IA&#8217;s do, right? Designing workflows in a CMS, how to reuse content, which content to reuse, that is also part of the <abbr title="Content Strategist">IA</abbr> tasks.
</p>
<p><strong>What are you going to publish?</strong><br />
Data and content are pretty abundant if you know where to look for. But that doesn&#8217;t mean everything has to go online. Here the tasks of a <abbr title="Content Strategist">CS</abbr> and <abbr title="Content Strategist">IA</abbr> start to differ in that the <abbr title="Content Strategist">IA</abbr> does not always have a grip on the actual content.
</p>
<p><strong>Where are you going to publish it?</strong><br />
Content can be reused and rewritten for different channels. If you are posting it on twitter, Facebook, an RSS feed or a webpage,  the <abbr title="Content Strategist">CS</abbr> considers which parts of the text goes online. Maybe even the tone and voice of the content has to be reviewed.
</p>
<p>I think here the <abbr title="Content Strategist">CS</abbr> tasks start to get borderline with <abbr title="Search Egnine Optimisation">SEO</abbr>  tasks and/or journalism.  One good examples of this overlap can be seen at the BBC and how they produce headlines. Most of the <a href="http://www.useit.com/alertbox/headlines-bbc.html" title="World's Best Headlines: BBC News (Jakob Nielsen's Alertbox)">headlines convey the whole story in 5 words</a>. Is that good copywriting? a content strategists defining standards? or the <abbr title="Search Egnine Optimisation">SEO</abbr>  requiring the most prominent keywords to be available in the titles? I guess journalists have been doing this already for a long long time.
</p>
<p><strong>Why are you going to publish this?</strong><br />
The strategy, the why behind the content should be become clear after stakeholder interviews and audience analyses.<br />
The strategy should bring those 2 mindsets together. Here the idea is the same as in IA: <a href="http://www.boxesandarrows.com/files/banda/where-is-your-mental/indiyoung.mentalmodel.large.png" title="">align the mental model of the business with the mindset of the audience</a>.
</p>
<p>In chapter 3 the author lists a batch of deliverables (<span title="Accessibility guidelines,  Benchmarks ,  Channel strategy ,  CMS requirements,  Communication plans ,  Community and social strategy ,  Community moderation policies ,  Competitive analyses ,  Content production workshops ,  Content sourcing plans ,  Content style guides ,  Content templates ,  Editorial calendars ,  Example content ,  Feature descriptions ,  Gap analyses ,  Metadata recommendations ,  Project proposals ,  Publishing workflow ,  Qualitative content audit and findings ,  Quantitative content audit and findings ,  Resource review (people, tools, time) ,  Search-engine optimization reviews ,  Success metrics ,  Taxonomies ,  Traffic analysis ,  Usability tests">Channel strategy ,  CMS requirements,  Communication plans ,  Usability tests</span>) and I think the majority of those documents need to be shared with the IA.
</p>
<p>Both the the <abbr title="Content Strategist">IA</abbr> and the <abbr title="Content Strategist">CS</abbr> perform user research, create content inventories, write up persona&#8217;s, the shared list of tools goes on and on. But I think the content strategists focuses more on the message behind, the voice and tone of the content and for that matter I think the <abbr title="Content Strategist">CS</abbr> is very close to a graphic designer. Choosing the colors and images can drastically change the messages that a website conveys. The tone and voice of the content can do the same.
</p>
<p>A wireframe is a black and white presentation of what will be published where. But the message can be so dramatically changed by choosing the wrong words or the right ones. The wireframe can act as a reference but the if the design uses pink tones and cartoon images, or corporate blue and stock photography, the message is no longer the same.
</p>

<a href='http://blockquote.be/2011/04/01/content-strategy-the-same-thing-in-a-new-jacket/wireframes-gone-corporate/' title='wireframes-gone-corporate'><img width="150" height="150" src="http://blockquote.be/wp-content/uploads/2011/04/wireframes-gone-corporate-150x150.png" class="attachment-thumbnail" alt="wireframes-gone-corporate" title="wireframes-gone-corporate" /></a>
<a href='http://blockquote.be/2011/04/01/content-strategy-the-same-thing-in-a-new-jacket/wireframes-gone-mad/' title='wireframes-gone-mad'><img width="150" height="150" src="http://blockquote.be/wp-content/uploads/2011/04/wireframes-gone-mad-150x150.png" class="attachment-thumbnail" alt="wireframes-gone-mad" title="wireframes-gone-mad" /></a>

<p>Content strategy is nothing new, it has been done from the moment books were published, radio started to broadcast and television shows were brought into the living room.  Yes, the environment has changed, so the tools and techniques need to change too but basically it is a new name for what was considered part of other professions.</p>
<h3>Update</h3>
<p>An <a href="http://www.alistapart.com/articles/a-checklist-for-content-work/">excerpt of the book The Elements of Content Strategy</a> is now online  at A List Apart</p>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2011/04/01/content-strategy-the-same-thing-in-a-new-jacket/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When the CEO wears the wrong hat</title>
		<link>http://blockquote.be/2011/02/04/when-the-ceo-wears-the-wrong-hat/</link>
		<comments>http://blockquote.be/2011/02/04/when-the-ceo-wears-the-wrong-hat/#comments</comments>
		<pubDate>Fri, 04 Feb 2011 13:33:38 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Quicklink]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blockquote.be/?p=561</guid>
		<description><![CDATA[My bookshelf needed some reorganisation lately and I came across Steve Krugs book &#8220;Don&#8217;t make me think&#8220;. I remembered reading something about a dreaming CEO. At that time it made me laugh. But now, it is more likely to make &#8230; <a href="http://blockquote.be/2011/02/04/when-the-ceo-wears-the-wrong-hat/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>My bookshelf needed some reorganisation lately and I came across Steve Krugs book &#8220;<a href="http://www.amazon.com/gp/product/0321344758?ie=UTF8&#038;tag=bloabloforweb-20&#038;linkCode=as2&#038;camp=1789&#038;creative=390957&#038;creativeASIN=0321344758">Don&#8217;t make me think</a>&#8220;.   I remembered reading something about a dreaming CEO. At that time it made me laugh. But now, it is more likely to make me cry.</p>
<p>I couldn&#8217;t remember exactly how the story went, so I had to look it up. It&#8217;s just a small footnote, but it says everything about the position of the webteam in todays corporate culture. I think it still holds a lot of truth these days.</p>
<blockquote><p>I once saw a particularly puzzling feature on the Home page of a prominent &#8211; and otherwise sensible designed &#8211; site. When I asked about it, I was told, “Oh that. It came to our CEO in a dream, so we had to add it.” True story<br />
<cite style="color: #BFA21A;font-style: italic;"><em>Steve Krug, Don&#8217;t make me think (2006), p.127</em></cite></p></blockquote>
<p><span id="more-561"></span><br />
And Steve Krug is the not the only one expressing these thoughts. You can find comparable comments made by Oliver Reichenstein over at <a href="http://www.informationarchitects.jp/">http://www.informationarchitects.jp/</a></p>
<blockquote><p>The concern about the visual style is the echo of the nineties; the nineties are over. It’s well documented that often top decision makers and silly corporate structures mess with the design process. Let me state this clearly: Just because you drive a car it doesn’t make you a car engineer. In other words–CEOs shouldn’t get involved in web design, but in web business strategy.<br />
<cite style="color: #BFA21A;font-style: italic;"><em><a href="http://www.informationarchitects.jp/en/whats-next-in-web-design/">What’s Next in Web Design?</a> by Oliver Reichenstein</em></cite></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2011/02/04/when-the-ceo-wears-the-wrong-hat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenSource and usability</title>
		<link>http://blockquote.be/2008/02/22/opensource-and-usability/</link>
		<comments>http://blockquote.be/2008/02/22/opensource-and-usability/#comments</comments>
		<pubDate>Fri, 22 Feb 2008 08:54:47 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blockquote.be/2008/02/22/opensource-and-usability/</guid>
		<description><![CDATA[Over time open source software grew in popularity, attracting a diverse population of users beyond developers. When new users who were less technically savvy began using developer-centered software, it became the tipping point at which open source software went from &#8230; <a href="http://blockquote.be/2008/02/22/opensource-and-usability/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<blockquote><p>Over time open source software grew in popularity, attracting a diverse population of users beyond developers. When new users who were less technically savvy began using developer-centered software, it became the tipping point at which open source software went from having an &#8220;advanced user interface&#8221; to a &#8220;bad user interface&#8221;. However, software development continued to focus on functionality and features instead of improving the user interface.<br />
<cite><a href="http://www.upassoc.org/upa_publications/upa_voice/volumes/2008/february/usability-open-source.html" title="UPA Voice - February 2008 - Usability in Open Source Software">Usability in Open Source Software</a></cite></p></blockquote>
<p>I ditched Ubuntu the first time I used it because it wasn&#8217;t user-friendly enough. That was 2 years ago.</p>
<p>Now I tried and installed it on 2 computers and planning to install v6 on my old iMac because they actually made a lot of usability improvements.<br />
The interface looks nice, the installation process went through without any problems, and they have all the software I need (a browser: Firefox, word-processing and spreadsheets: OpenOffice, mediaplayers:VLC, Songbird &#8230; )and I can install them without (too m)any problems.</p>
<p>There is really no reason not to use Linux/Ubuntu for home use.</p>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2008/02/22/opensource-and-usability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Considering the user</title>
		<link>http://blockquote.be/2008/02/19/considering-the-user/</link>
		<comments>http://blockquote.be/2008/02/19/considering-the-user/#comments</comments>
		<pubDate>Tue, 19 Feb 2008 20:19:08 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blockquote.be/2008/02/19/considering-the-user/</guid>
		<description><![CDATA[The usability newsletter at usabilitynews.com came up with a list of items that could improve usability for POS systems: cashier systems at fastfood restaurants, retailer stores and the like. The first thing on the list is FAILING TO CONSIDER THE &#8230; <a href="http://blockquote.be/2008/02/19/considering-the-user/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The usability newsletter at <a href="http://usabilitynews.com">usabilitynews.com</a> came up with a list of items that could improve usability for <abbr title="Point of Sale">POS systems</abbr>:  cashier systems at fastfood restaurants, retailer stores and the like.</p>
<p>The first thing on the list is FAILING TO CONSIDER THE END USER. </p>
<p>This sounds like an obvious one and it is, but still, it&#8217;s the first step to take.<br />
I work at a Corporate HQ far away from the people who actually use the systems I create, and I experience this all the time. If I don&#8217;t take the time to go over and have a look, talk to them and see what they actually want, it always results in a merely functional rather then a usable and functional system.</p>
<blockquote><p>1. FAILING TO CONSIDER THE END USER<br />
When I’m hired to design a Point of Sale system, I always start with Field Studies—visits to actual sites where the cashiering system will be used. I nearly always find that the system doesn’t match employee processes, and that the employees have developed ways to “get around” the system and/or make up for system limitations.</p>
<p>Observing employees and conducting interviews at representative business sites are a critical first step in designing a quick and efficient POS system that reduces both errors and training time. Site visits also help ensure a redesign that considers the employee environment, including physical space constraints, distractions, etc.<br />
<cite><a href="http://www.usabilitynews.com/news/article4544.asp" class="broken_link">How to Design a System that Everybody Hates</a></cite>
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2008/02/19/considering-the-user/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Usability for Valentine</title>
		<link>http://blockquote.be/2008/02/15/usability-for-valentine/</link>
		<comments>http://blockquote.be/2008/02/15/usability-for-valentine/#comments</comments>
		<pubDate>Fri, 15 Feb 2008 15:19:49 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blockquote.be/2008/02/15/usability-for-valentine/</guid>
		<description><![CDATA[From Webcredible: The Ecommerce Usability for Valentine Etailers report evaluates the websites of 20 of the leading Valentine&#8217;s ecommerce websites. Based on our experience of usability testing with over 1000 people on a variety of ecommerce sites, we devised 20 &#8230; <a href="http://blockquote.be/2008/02/15/usability-for-valentine/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://www.webcredible.co.uk/">Webcredible</a>:</p>
<blockquote><p>
The Ecommerce Usability for Valentine Etailers report evaluates the websites of 20 of the leading Valentine&#8217;s ecommerce websites. Based on our experience of usability testing with over 1000 people on a variety of ecommerce sites, we devised 20 essential guidelines that all ecommerce websites should adhere to, evaluating each site against these guidelines.<br />
<cite><a href="http://www.webcredible.co.uk/user-friendly-resources/white-papers/valentines-usability.shtml">Ecommerce Usability for Valentine Etailers</a></cite></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2008/02/15/usability-for-valentine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bad error messages</title>
		<link>http://blockquote.be/2007/12/20/bad-error-messages/</link>
		<comments>http://blockquote.be/2007/12/20/bad-error-messages/#comments</comments>
		<pubDate>Thu, 20 Dec 2007 16:35:40 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[IA]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Quicklink]]></category>

		<guid isPermaLink="false">http://blockquote.be/2007/12/20/bad-error-messages/</guid>
		<description><![CDATA[Writing error messages is very hard if you check the list of error screenshots collected on the iarchitect page from Isys IA Inc. My personal favorites is generated by Lotus notes: Mail engine: no error. Some useful guidelines for printing &#8230; <a href="http://blockquote.be/2007/12/20/bad-error-messages/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Writing error messages is very hard if you check the list of <a href="http://homepage.mac.com/bradster/iarchitect/errormsg.htm">error screenshots</a> collected on the iarchitect page from Isys IA Inc. </p>
<p>My personal favorites is generated by Lotus notes: <q>Mail engine: no error</q>.  </p>
<p>Some useful guidelines for printing error messages can be found on the<a href="http://www.ibm.com/developerworks/web/library/us-cranky14.html"> Cranky Users article: could you repeat that in English</a>, or the <a href="http://www.useit.com/alertbox/20010624.html">guidelines for error messages from Norman Nielsens&#8217; alertbox</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2007/12/20/bad-error-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Video interview met Jacob Nielsen</title>
		<link>http://blockquote.be/2006/04/01/video-interveiw-met-jacob-nielsen/</link>
		<comments>http://blockquote.be/2006/04/01/video-interveiw-met-jacob-nielsen/#comments</comments>
		<pubDate>Sat, 01 Apr 2006 10:00:00 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[Dutch]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web development]]></category>
		<category><![CDATA[artikel]]></category>

		<guid isPermaLink="false">http://blockquote.be/?p=229</guid>
		<description><![CDATA[Op de MS site devsource.com is er een video gepubliceerd waarin Jacob Nielsen geinterviewd wordt. Het beoogde publiek zijn developers, coders, real IT/Dev kerels. Jacob ziet er echt uit als een verstrooide professor: net uit de strip van Jommeke gesprongen. &#8230; <a href="http://blockquote.be/2006/04/01/video-interveiw-met-jacob-nielsen/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Op de MS site devsource.com is er een <a href="http://www.devsource.com/article2/0,1895,1937615,00.asp#">video gepubliceerd waarin Jacob Nielsen geinterviewd wordt</a>. Het beoogde publiek zijn developers, coders, real IT/Dev kerels. </p>
<p>Jacob ziet er echt uit als een verstrooide professor: net uit de strip van Jommeke gesprongen.</p>
<p>Het interview geeft wel een beter inzicht in een aantal publicaties van Jacob en hij herhaalt verschillende elementen die je steeds terug vind in zijn <a href="http://www.useit.com/alertbox/">Alertbox</a>. </p>
<ul>
<li>Developers zijn niet de users. En dat is iets dat je overal terug vind. En ik vrees dat de meeste usability specialisten/webmasters/Ias/&#8230;  dat ook niet zijn. </li>
<li>Dus, voor een test heb je een echte user nodig. Geen fancy lab met eyetracking, gewoon een tafel, papier en pen, een luisterend oor.</li>
<li>De interviewer vraagt om enkele goed en slecht websites aan te halen. De eerst die hij aanhaalt is Yahoo. Groot bedrijf, veel inzicht in users, focus op de users en noden.<br />
De tweede website die hij vermeld is die van Victorias Secret. Volgens Jacob een website waar je schoenen kan kopen. :-)  Wel &#8230;, vreemde schoenen naar mijn mening, maar ik kon effe niet meer van het lachen. </li>
<li>Dan krijgen we een uitleg over PDF. Dit interview verduidelijkt zijn standpunt over PDF als print medium. PDF werkt niet in een online omgeving waar &#8220;paging&#8221; en controle over de lay-out van een document weinig of geen betekenis heeft. PDF is niet slecht, PDF is goed om af te drukken.</li>
<li>De volgende stap is natuurlijk dat search niet werkt wanneer je gigantische pdf documenten online zet. Als je een zoek term invoert ben je op zoek naar iets specifiek en heb je geen zin om te wachten  en die 500 Mb PDf handleiding te downloaden. Search is inderdaad een onderschatte tool voor de meeste website. De meeste gratis search engines kan je dan ook beter verwijderen van je website. Als je de search engine niet kan aanpassen aan de noden van je website en van je gebuikers kan je de search feature beter achterwege laten. </li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2006/04/01/video-interveiw-met-jacob-nielsen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Website bloopers mentioning 37signals</title>
		<link>http://blockquote.be/2006/01/31/website-bloopers-mentioning-37signals/</link>
		<comments>http://blockquote.be/2006/01/31/website-bloopers-mentioning-37signals/#comments</comments>
		<pubDate>Tue, 31 Jan 2006 04:00:31 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Quicklink]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blockquote.be/?p=170</guid>
		<description><![CDATA[The first chapter of Web Bloopers has a screenshot of the first homepage of 37signals and what they did wrong :-) The book is more an intro to IA and usability then actual &#8220;graphical webdesign&#8221;. The author, Jeff Johnson, has &#8230; <a href="http://blockquote.be/2006/01/31/website-bloopers-mentioning-37signals/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://books.elsevier.com/companions/9781558608405/WebBloopersCh1.pdf">first chapter of Web Bloopers</a> has a screenshot of the first homepage of 37signals and what they did wrong :-) The book is more an intro to IA and usability then actual &#8220;graphical webdesign&#8221;.  </p>
<p>The author, Jeff Johnson, has written another blooper book on GUI design and released <a href="http://www.acm.org/ubiquity/book/JohnsonChap4.pdf">chapter 4 for download</a>. This chapter handles text and linking, scent, labeling and using the right words.  </p>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2006/01/31/website-bloopers-mentioning-37signals/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design from the Epicenter</title>
		<link>http://blockquote.be/2006/01/25/interface-design-tip-find-the-epicenter-signal-vs-noise/</link>
		<comments>http://blockquote.be/2006/01/25/interface-design-tip-find-the-epicenter-signal-vs-noise/#comments</comments>
		<pubDate>Wed, 25 Jan 2006 04:00:39 +0000</pubDate>
		<dc:creator>Len</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[IA]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[artikel]]></category>
		<category><![CDATA[Information architecture]]></category>

		<guid isPermaLink="false">http://blockquote.be/?p=161</guid>
		<description><![CDATA[The technique explained in this article is really new to me: start with the most important content block and build the page around that block, navigation, side bars, everything. So, if you were to start designing this page from scratch, &#8230; <a href="http://blockquote.be/2006/01/25/interface-design-tip-find-the-epicenter-signal-vs-noise/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The technique explained in <a href="http://www.37signals.com/svn/archives/000737.php">this article</a> is really new to me: start with the most important content block and build the page around that block, navigation, side bars, everything. </p>
<blockquote><p>So, if you were to start <tag>designing </tag>this page from scratch, you’d start here — with the message unit. The subject, the body, the metadata, the link and file attachment styles, etc. Only when that unit is complete would you begin to think about the second most critical element on the page</p>
<address><a href="http://www.37signals.com/svn/archives/000737.php">Jason Fried</a></address>
</blockquote>
<p>The post was published in 2004 but seems still relevant as they posted a pointer to another blog <a href="http://to-done.com/">&#8220;To-Done&#8221;</a> where Britt Parrot writes about a similar technique to get a web design <tag>project </tag>going: <a href="http://www.to-done.com/2005/11/finding-your-starting-point/#more-87">Starting in the middle</a></p>
<p>And <a href="http://www.flingmedia.com/services/user_epicenter_design.php" class="broken_link">flingmedia uses a similar technique to do <tag>audience research</tag></a>.</p>
<p>The idea of putting the focus on the main goal or most important block of the page is interesting enough to try. It certainly worked for <a href="http://www.37signals.com/svn/archives/000737.php">basecamp</a> and other apps from <a href="http://www.37signals.com">37signals</a> and it is different then other techniques like a <tag>Page Description Diagram</tag> (PDD) that comes together after exensive research and discussion.</p>
]]></content:encoded>
			<wfw:commentRss>http://blockquote.be/2006/01/25/interface-design-tip-find-the-epicenter-signal-vs-noise/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

