<?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>Intentional Design Inc. &#187; user experience</title>
	<atom:link href="http://intentionaldesign.ca/tag/user-experience/feed/" rel="self" type="application/rss+xml" />
	<link>http://intentionaldesign.ca</link>
	<description>Content strategies for business impact</description>
	<lastBuildDate>Sun, 22 Jan 2012 22:34:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<image>
  <link>http://intentionaldesign.ca</link>
  <url>http://intentionaldesign.ca/www/pmh3472/public_html/wp-content/uploads/2009/09/IDI-favicon.ico</url>
  <title>Intentional Design Inc.</title>
</image>
		<item>
		<title>Getting ROI by Using Lean in Content Production</title>
		<link>http://intentionaldesign.ca/2011/10/26/getting-roi-by-using-lean-in-content-production/</link>
		<comments>http://intentionaldesign.ca/2011/10/26/getting-roi-by-using-lean-in-content-production/#comments</comments>
		<pubDate>Wed, 26 Oct 2011 15:06:20 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Development]]></category>
		<category><![CDATA[Content Strategies]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[content lifecycle]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[processes]]></category>
		<category><![CDATA[ROI]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=1508</guid>
		<description><![CDATA[Rigorous examination of even a small area of content production can yield significant results using Lean principles.]]></description>
			<content:encoded><![CDATA[<p>A couple of weeks ago, I was at UserFocus in Washington, DC, and a poster caught my eye: <a title="Karla Turcios' IxDA page" href="http://ixdadc.ning.com/profile/KarlaTurcios" target="_blank">Karla Turcios</a> discussing a Lean UX Style Guide for a project with the Nature Conservatory.</p>
<p><a href="http://intentionaldesign.ca/2011/10/26/getting-roi-by-using-lean-in-content-production/lean-in-ux/" rel="attachment wp-att-1514"><img class="aligncenter size-medium wp-image-1514" title="Lean in UX" src="http://intentionaldesign.ca/www/pmh3472/public_html/wp-content/uploads/2011/10/Lean-in-UX-300x225.jpg" alt="Lean UX Style Guide" width="300" height="225" /></a></p>
<p>It was interesting to me to see how Lean has made it into this area because at first glance, Lean is all about production line efficiencies, and here it&#8217;s being applied to a discipline that is far from production line, and couldn&#8217;t be effective without a certain amount of creativity. And creativity is hard to streamline in terms of &#8220;reducing waste.&#8221;</p>
<p>The idea of applying Lean principles to a service environment isn&#8217;t new, however. In 2004, Lean was just starting to be adapted to areas beyond manufacturing. I worked on a project where we applied Lean principles to the production of content, where the savings were great and the ROI was stunning (though as <a title="Scott Abel" href="http://thecontentwrangler.com/" target="_blank">Scott Abel</a> always warns: your mileage may vary).</p>
<p>My client and I turned our success story into a presentation. As the question of ROI comes up continuously, I thought I&#8217;d post the presentation to show how a rigorous examination of even a small area of content production can yield significant results.</p>
<p><a href="http://www.slideshare.net/rahelab/how-far-to-lean">How Far to Lean</a> (goes to Slideshare.net) or view below:</p>
<object style="margin:0px" width="425" height="355"><param name="movie" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=id=9890089&amp;doc=howfartolean-111026094604-phpapp01" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><param name="wmode" value="transparent" /><embed src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=id=9890089&amp;doc=howfartolean-111026094604-phpapp01" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355" wmode="transparent"></embed></object>
<p>&nbsp;</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=1508&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2011/10/26/getting-roi-by-using-lean-in-content-production/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Defining Content in the Age of Technology</title>
		<link>http://intentionaldesign.ca/2011/10/18/defining-content-in-the-age-of-technology/</link>
		<comments>http://intentionaldesign.ca/2011/10/18/defining-content-in-the-age-of-technology/#comments</comments>
		<pubDate>Tue, 18 Oct 2011 15:54:52 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Development]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[Content Strategies]]></category>
		<category><![CDATA[user experience]]></category>
		<category><![CDATA[open standards]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[structured content]]></category>
		<category><![CDATA[syndication]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=1478</guid>
		<description><![CDATA[Copy, multiplied by its technopower, makes it into content. Content needs copy; and in a post-paper world, copy definitely needs content.]]></description>
			<content:encoded><![CDATA[<p>If I were to define content through a formula, the technopower would look something like this (and thanks to <a title="Joe Gollner" href="http://www.gollner.ca/" target="_blank">Joe Gollner</a> for his help in articulating this):</p>
<p><a href="http://intentionaldesign.ca/2011/10/18/defining-content-in-the-age-of-technology/content-formula-3/" rel="attachment wp-att-1500"><img class="aligncenter size-medium wp-image-1500" title="Content Formula" src="http://intentionaldesign.ca/www/pmh3472/public_html/wp-content/uploads/2011/10/Content-Formula2-300x199.png" alt="" width="300" height="199" /></a></p>
<p>Why I say that is because of a concept borrowed from the financial industry called asset amplification. In the context of financial markets, asset amplification describes how changes of wealth in financial markets causes amplification because of follow-on consequences. (Thanks to the Journal of Financial Economics article by Wei Xiong explaining how this works.) Similarly, the power of copy can be amplified if it is placed into a robust technology framework. Once copy is placed <em>inside</em> of a framework, it becomes the <em>content</em> of that framework. Like coffee is the &#8220;content&#8221; of a cup, copy is the content within a technology framework. And like a super-hero with the appropriate gear, copy, with the appropriate framework, gets super-powers, too.</p>
<p>The super-power of content is the potential for follow-on consequences of copy because of the underlying technopower is what turns copy into content. Thinking back a few years, communications coordinators who organized events would type out the event details: event name, start and time, place, cost, and so on, and then spend hours copying and pasting the event into sites that would allow them to paste it into a provided text box or, even more time-consuming, complete a set of form fields that the coordinators had to fill out individually. Today, we use content feeds which allow events to be amplified with no manual intervention. This is done through the technopower of the underlying technology framework.</p>
<p>As we get away from brochureware to robust interactivity, the need for rich semantic content grows. Again, copy, multiplied by technopower, makes content which can be processed by other systems. The event example was a simple one, but there are increasing levels of complexity, from &#8220;simple&#8221; publishing to the kind of interactivity and outputs that allow for successive complex transformations of content. We are all familiar with how content gets syndicated, but what may be a surprise is how much content is manipulated and transformed within a system. Each transformation provides the potential for additional amplification, and eventually provides a much richer user experience for the content consumer.</p>
<p>In the end, content may be nothing without copy; however, in a post-paper world, copy is nothing without content.</p>
<p>Previous post: <a title="Turning Copy into Content" href="http://intentionaldesign.ca/2011/10/11/turning-copy-into-content/" target="_blank">Turning Copy into Content</a></p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=1478&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2011/10/18/defining-content-in-the-age-of-technology/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>The Content Strategy Bookshself</title>
		<link>http://intentionaldesign.ca/2011/06/06/the-content-strategy-bookshself/</link>
		<comments>http://intentionaldesign.ca/2011/06/06/the-content-strategy-bookshself/#comments</comments>
		<pubDate>Tue, 07 Jun 2011 06:09:49 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Strategies]]></category>
		<category><![CDATA[ann rockley]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[deliverables]]></category>
		<category><![CDATA[DITA]]></category>
		<category><![CDATA[interaction design]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[professional development]]></category>
		<category><![CDATA[resources]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=1380</guid>
		<description><![CDATA[If you were to look at your library of books related to content strategy - directly or indirectly - what would be on that shelf? Here's what is on mine.]]></description>
			<content:encoded><![CDATA[<p>If you were to look at your library of books related to content strategy &#8211; directly or indirectly &#8211; what would be on that shelf? Here&#8217;s what is on mine. Some have been with me for a longer time; others are brand new. Also, I&#8217;ve excluded a lot of books on web design and user experience that I didn&#8217;t feel  were really right for this list of books. I&#8217;m not saying that this list forms any sort of corpus; they&#8217;re just books from which I have gleaned information, from a little nugget here or there to the books marked with so many post-it notes, the spine is bent out of shape.</p>
<p>This list is organized arbitrarily by broad category. Hey, my blog, my rules. And what you can do, gentle reader, is add your favourite books to the comments section. More reading, more knowledge!</p>
<h2>Planning and Design</h2>
<p>Harnessing Complexity (Robert Axelrod and Michael Cohen)</p>
<p>Managing Enterprise Content (Ann Rockley)</p>
<p>Content Management Bible (Bob Boiko)</p>
<p>Document Engineering (Robert J Glushko, Tim McGrath)</p>
<p>Content and Complexity (Michael J Alberts, Beth Maxur, eds)</p>
<p>Designing e-Learning (Saul Carliner)</p>
<p>Information Design (Robert Jacobson, ed)</p>
<h2>User Experience</h2>
<p>Understanding Your Users (Catherine Courage, Kathy Baxter)</p>
<p>The User is Always Right (Steve Mulder and Ziv Yaar)</p>
<p>Paper Prototyping (Carolyn Snyder)</p>
<p>Why Software Sucks (David Platt)</p>
<p>Handbook of Usability Testing (Jerry Rubin, Dana Chisnell, Jared Spool)</p>
<p>Storytelling for User Experience (Whitney Quesenbery, Kevin Brooks)</p>
<p>Observing the User Experience (Mike Kuniavsky)</p>
<p>Subject to Change (Peter Merholz, Brandon Schauer)</p>
<p>Rocket Science Made Easy (Steve Krug)</p>
<p>Simple and Usable (Giles Colborne)</p>
<p>Do Good Design (David B Berman)</p>
<p>Built for Use (Karen Donoghue)</p>
<p>Mental Models (Indi Young)</p>
<p>The Inmates are Running the Asylum (Alan Cooper)</p>
<h2>Practitioner Guides</h2>
<p>The Web Content Strategist&#8217;s Bible (Richard Sheffield)</p>
<p>Elements of Content Strategy (Erin Kissane)</p>
<p>Letting Go of the Words (Ginny Redish)</p>
<p>Content Strategy for the Web (Kristina Halvorson)</p>
<p>Creating the Perfect Design Brief (Peter L Phillips)</p>
<p>Business Process Mapping (Jacka Keller)</p>
<p>Request for Proposal (Bud Porter-Roth)</p>
<p>Managing Knowledge (Wayne Applehans, Alden Globe, Greg Laugero)</p>
<p>Managing Your Documentation Products (JoAnn Hackos)</p>
<p>Techniques for Technical Communicators (Carol Barnum, Saul Carliner)</p>
<p>Sister Bernadette&#8217;s Barking Dog (Kitty Burns Florey)</p>
<p>The Accidental Taxonomist (Heather Hedden)</p>
<p>The Visual Display of Quantitative Information (Edward Tufte)</p>
<p>Envisioning Information (Edward Tufte)</p>
<h2>Wordsmithing for Effect</h2>
<p>Clout (Colleen Jones)</p>
<p>Neuro Web Design (Susan M Weinschenk, PhD)</p>
<p>Content Rules (CC Chapman and Ann Handley)</p>
<p>Get Content, Get Customers (Joe Pulizzi and Newt Barrett)</p>
<p>Content Nation (John Blossom)</p>
<p>Curation Nation (Steven Rosenbaum)</p>
<p>Predictably Irrational (Dan Ariely)</p>
<p>Delivering Happiness (Tony Hsieh)</p>
<p>Branded Nation (James B Twitchell)</p>
<p>Call to Action (Bryan and Jeffrey Eisenberg)</p>
<p>Intercultural Communication (James W Neuliep)</p>
<p>A Practical Guide to Localization (Bert Esselink)</p>
<p>International Technical Communication (Nancy L Hoft)</p>
<h2>Metadata and Delivery</h2>
<p>Audience, Relevance, and Search (James Mathewson, Frank Donatone, and Synthia Fishel)</p>
<p>Search Engine Visibility (Shari Thurow)</p>
<p>Metadata Solutions (Adrienne Tennenbaum)</p>
<p>Killer Web Content (Gerry McGovern)</p>
<p>Wiki (Alan Porter)</p>
<p>Introduction to DITA (Jennifer Linton, Kylene Bruski)</p>
<h2>User Engagement</h2>
<p>Conversation and Community (Anne Gentle)</p>
<p>Here Comes Everybody (Clay Shirky)</p>
<p>SocialCorp (Joel Postman)</p>
<p>Sway (Ori and Rom Brafman)</p>
<p>The Thank You Economy (Gary Vaynerchuk)</p>
<p>Radically Transparent (Andy Beal, Dr. Judy Strauss)</p>
<p>Crowdsourcing (Jeff Howe)</p>
<p>Participating in Explanatory Dialogues (Johanna D Moore)</p>
<p>&nbsp;</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=1380&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2011/06/06/the-content-strategy-bookshself/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Congility conference features IDI contributions</title>
		<link>http://intentionaldesign.ca/2011/04/08/congility-conference-features-idi-contributions/</link>
		<comments>http://intentionaldesign.ca/2011/04/08/congility-conference-features-idi-contributions/#comments</comments>
		<pubDate>Fri, 08 Apr 2011 16:56:11 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Development]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[open standards]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=1314</guid>
		<description><![CDATA[Rahel Bailie participates in Congility 2011 - Gatwick, UK, May 2011.]]></description>
			<content:encoded><![CDATA[<p>Now that content strategy events are popping up everywhere, or so it seems, there starts to be differentiation between the offerings of the various events. Coming up at the end of May is Congility, a Gatwick-based conference with this year&#8217;s theme of: Content Integration &#8211; Leveraging Content Standards to Improve Customer Experience.</p>
<p>IDI&#8217;s Rahel Bailie will be there, making one of the keynote presentations, <a href="http://www.congility.com/site/program_detail/the_content_strategy_paradox">The Content Strategy Paradox</a>, and running a workshop, <a href="http://www.congility.com/site/program_detail/not_all_strategies_are_created_equal_a_cross-genre_content">Not All Content Strategies are Created Equal</a>, about strategies for cross-genre content.</p>
<p>Read her take on <a href="http://www.congility.com/index.php/site/speaker_detail/bailie/">content agility</a><br />
Revisit her 2010 webinar on <a href="http://www.x-pubs.com/site/news/2008/">content strategy and ROI</a></p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=1314&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2011/04/08/congility-conference-features-idi-contributions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Content Review: A Content Quality Scorecard</title>
		<link>http://intentionaldesign.ca/2011/03/08/the-content-review/</link>
		<comments>http://intentionaldesign.ca/2011/03/08/the-content-review/#comments</comments>
		<pubDate>Tue, 08 Mar 2011 17:02:57 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Strategies]]></category>
		<category><![CDATA[Deliverables]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[deliverables]]></category>
		<category><![CDATA[heuristics]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=1294</guid>
		<description><![CDATA[The content review is a measure of existing content quality against a set of heuristics, from which you can generate a content scorecard.]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re familiar with heuristic reviews of websites, you&#8217;ll be right at home with the content review. It&#8217;s a way to look at a body of content and get a snapshot of the content strengths and weaknesses against the stated objectives. The review draws heavily from user centered design principles, starting with user personas and working through key scenarios.</p>
<p>Content strategist Kathy Hanbury shares her way of going about a content review, and producing a content usability scorecard.</p>
<p><a title="The Content Review and Content Scorecard" href="http://e3contentstrategy.blogspot.com/2011/03/content-strategy-deliverable-expert.html" target="_blank">The Content Review (Heuristic Review, Expert Review) and the Content Review sample report</a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=1294&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2011/03/08/the-content-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pushing customers away with bad user experience</title>
		<link>http://intentionaldesign.ca/2010/10/23/1184/</link>
		<comments>http://intentionaldesign.ca/2010/10/23/1184/#comments</comments>
		<pubDate>Sat, 23 Oct 2010 21:06:39 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=1184</guid>
		<description><![CDATA[When convenience becomes inconvenient: bad customer support experience.]]></description>
			<content:encoded><![CDATA[<p>Dear Imperial Oil,</p>
<p>I&#8217;m sure you have user experience people helping you, but I&#8217;ll bet you don&#8217;t implement half of what they tell you. If you did, I wouldn&#8217;t be writing this blog post explaining how to lose supporters and antagonize customers.</p>
<p>I have received my snail-mail letter explaining that I need to update my credit card to use my Esso Speedpass key tag. You give me some instructions, but they don&#8217;t  cover my situation.</p>
<p>Your website isn&#8217;t helping me because:</p>
<ol>
<li>I exceeded my number of logins &#8211; after all, it&#8217;s probably been years since I last went to your website &#8211; and now am told to call your Customer Service Center.</li>
<li>Self-service is faster, supposedly, but your &#8220;help&#8221; center doesn&#8217;t answer my question and your <a title="FAQs" href="https://www.essoextra.com/programs/SpeedpassFaqHome.page">FAQs </a>are, well, <a title="not particularly helpful" href="http://www.contentmarketinginstitute.com/2010/09/faq-pages/" target="_blank">not particularly helpful</a>.</li>
<li>I fall back on the old telephone, but phoning your customer service center won&#8217;t lead me to a customer service agent. AND, pressing &#8220;0&#8243; just sends me back to the opening menu. (Your support content is definitely not aligned &#8211; where is the consistency?)</li>
</ol>
<p>So, now I&#8217;m kind of stuck. On one hand, you&#8217;ve made it so painful for me to rectify my problem that my next step is likely to toss my key tag into the trash, shred the letter, and put this experience behind me. I know the score; I&#8217;m a single lone customer in a huge pond, and you couldn&#8217;t care less whether I renew my account or not.</p>
<p>On the other hand, I like the convenience of a key tag.If I really, really wanted a new Speedpass tag, I could report mine lost, and you&#8217;ll send me a new one and all the problems will get rectified, in the course of setting up a new account. But thinking into the future, I&#8217;ve already had to replace my credit cards a couple of times this year alone.  Do I want to go through a dead-end voice mail tree each time I need to update my account?</p>
<p>So, Imperial Oil, listen to your user experience folks. I suspect I&#8217;m not alone in considering the barriers you&#8217;ve built into your customer experience, and deciding it&#8217;s easier to bail.</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=1184&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2010/10/23/1184/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Digital interaction and content strategy: a winning combination</title>
		<link>http://intentionaldesign.ca/2010/10/11/digital-interaction-and-content-strategy-a-winning-combination/</link>
		<comments>http://intentionaldesign.ca/2010/10/11/digital-interaction-and-content-strategy-a-winning-combination/#comments</comments>
		<pubDate>Mon, 11 Oct 2010 16:56:55 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Development]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[experience design]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=1175</guid>
		<description><![CDATA[Digital interaction and content strategy is a winning combination, particularly this week on the Johnny Holland site.]]></description>
			<content:encoded><![CDATA[<p>The connection between user experience and content is becoming clearer to many communities of practice, and it&#8217;s great to see that Johnny Holland Magazine is connecting the dots in the space of human-computer interaction. It&#8217;s <a title="Content Strategy Week at Johnny Holland" href="http://johnnyholland.org/2010/10/11/johnny-proudly-presents-content-strategy-week/" target="_blank">Content Strategy Week at Johnny Holland</a>, with five articles on different aspects of content strategy.</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=1175&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2010/10/11/digital-interaction-and-content-strategy-a-winning-combination/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Underestimating the &#8220;yes but&#8221; factor</title>
		<link>http://intentionaldesign.ca/2009/11/29/underestimating-the-yes-but-factor/</link>
		<comments>http://intentionaldesign.ca/2009/11/29/underestimating-the-yes-but-factor/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 02:13:49 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[management]]></category>
		<category><![CDATA[Web development]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[processes]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=962</guid>
		<description><![CDATA[The "yes but" factors can ruin a project if stakeholders dig in their heels to protect their territory.]]></description>
			<content:encoded><![CDATA[<p>Time is fluid, as demonstrated by a research team lead by <a style="color: blue;" title="Carleton University: Biography" href="http://www.carleton.ca/research/chairs/nserc_chairs/lindgaard.html">Dr. Gitte Lindgaard</a> and explained in a <a title="useit.com post on time scales" href="http://www.useit.com/alertbox/timeframes.html" target="_blank">useit.com post</a>; in the &#8221;4th dimension&#8221; of time, user experience phenomena work across many powers of 10. Ever heard a last-year event referred to as &#8220;a decade ago in Internet years&#8221;?</p>
<p>Be sure that visitors subject your website to the same first-impression scrutiny that they exercise in real life, only faster. It takes 0.1 second to decide whether your site is attractive, 10 seconds to decide that your site is &#8220;taking too long&#8221; to respond, and 1 minute to be fed up with a task or a video.</p>
<p>Explaining the importance of getting this right is critical to a development team has its problems, as people &#8220;yes but&#8221; when it comes to their territory. The marketing department may &#8220;yes but&#8221; over the whiz-bang elements that slow down the site. Interaction designers may &#8220;yes but&#8221; when asked to redo problematic area. Developers may &#8220;yes but&#8221; when asked to do over some code. The writers may &#8220;yes but&#8221; when you insist that a content strategy must precede the content development stage.</p>
<p>Actually, it&#8217;s not even the &#8220;yes but&#8221; that is the problem; that may just development stakeholders working through how to fix the situation. The problem is when the &#8220;yes but&#8221; is accompanied by a workaround, a justification, or a reason that serves to solve an internal problem rather than a client-facing problem. It can throw the development timeline off, affect the quality of the final product, and compromise the maintainability of the site. Because all of these factors have an effect on the Total Cost of Ownership, sometimes in serious ways, the &#8220;yes but&#8221; can be the &#8220;gotcha&#8221; that takes a project down; definitely not something I&#8217;d want to underestimate.</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=962&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2009/11/29/underestimating-the-yes-but-factor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Consequences of not having a good content strategy</title>
		<link>http://intentionaldesign.ca/2009/11/09/consequences-of-not-having-a-good-content-strategy/</link>
		<comments>http://intentionaldesign.ca/2009/11/09/consequences-of-not-having-a-good-content-strategy/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 16:40:54 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Development]]></category>
		<category><![CDATA[Content Strategies]]></category>
		<category><![CDATA[content as asset]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[ROI]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=986</guid>
		<description><![CDATA[An unexpected, informal usability test shows the role of content as part of the overall user experience.  ]]></description>
			<content:encoded><![CDATA[<p>Yesterday, I bought a phone from  Staples. I chose the AT&amp;T brand, for no particular reason other than the  physical interface looked like it could be straightforward and it had the features I wanted. When I got the  phone home, I unpacked it, attached the base, then took one cordless headset  upstairs and plugged it in, and another headset to the ground-level home  office and plugged it in. Then I started to configure the phone&#8217;s options.  Things went well &#8211; the schema was generally to press &#8220;Menu/Select&#8221;,  scroll to find an option, then press &#8220;Menu/Select&#8221; again to choose  the option, and press Menu/Select again to confirm the change.</p>
<p>So when it came  time to changing the answering machine greeting message, I followed the  instructions only to discover that there is no option to select. I tried all  the little tricks to see if the option got hidden elsewhere in the menu tree,  but it was definitely missing. Well, that&#8217;s fine; I will tough out the pain of  contacting customer support, through the phone number in the back of the book.  The phone number works in Canada &#8211; always an iffy question &#8211; so that&#8217;s  encouraging, and after listening to all the preambles, I press 1 for English,  enter my product number, and go through the various menus but there is no  option for &#8220;menu items are missing&#8221;. It seems that all the options  end up the same way, leading to an end point of &#8220;visit our website at  …&#8221;.</p>
<p>Now, gigantic corporations all have us trained to despise having to  call in; in other words: Don&#8217;t you think I&#8217;d have checked the website first if  I thought I could find the answer on your website? It would have been so much  easier: go to the site, choose the model number, and  But of course, the user experience was quite  painful. Here is an encapsulation of the frustration points:</p>
<ol>
<li>After doing a Google search for AT&amp;T 84209 (the model number) phone, I kept getting routed to the att.com site, which was obviously US-based, and geared to      telephone service subscribers.</li>
<li>I redialed the      number from the instruction book and was given <a href="http://www.telephones.att.com">www.telephones.att.com</a> as the URL. Typing in 84209 got me to a      shopping area. Do I want to buy a replacement cordless battery? I must say      that if I happened to know the model number of a phone I wanted to buy,      I&#8217;d be in luck because the second shopping option is to buy the very phone      that I&#8217;m getting annoyed over.</li>
<li>There are links      to the manual and Quick Start guide, which I consulted and had the same      incorrect information.</li>
<li>Filling in the      Contact Us form field promises to net a response within &#8211; depending on      which of the messages you believe &#8211; 72 hours (on website), 2 days      (on-screen auto-reply message), or 3 days (auto-reply email) but I doubt      that I&#8217;ll get a meaningful answer. It may be too late anyhow, as I&#8217;ve run      about the house, disconnecting telephone bits and bobs and tossing them      into a bag to return to the store.</li>
</ol>
<p>Now, I admit that  my question is not one of the top ten questions, and it might be embarrassing  to put it on the automated reply options (Press 8 if the interface  doesn&#8217;t work as per instructions.) but  surely someone has asked this question before, and somewhere, a content  developer has tackled this discrepancy. The point is that there needs to be a  strategy around content that goes beyond the basics. Now that I&#8217;ve calmed down  and revisited the situation with an industry insider&#8217;s eye, the support site is lovely &#8211; beautiful colours  and the navigation to the FAQs is quite simple. But when a customer is  searching content, and can&#8217;t find it, then all the other niceties fall away.  The laser beam focus on finding the content, which is needed to complete their  task, overrides all other aspects of the user experience. Task-based analysis  at its best.</p>
<p>So to AT&amp;T, I  would ask: if one of your questions is &#8220;Who is Charlie Johnson and why is  his name displayed on my phone?&#8221; surely the question of missing menu  items could be addressed, as well? This site is a classic example of focusing resources on the usability side of the support site, but not having a content strategy befitting such a site.  In this case, I did receive an email a few days later, referring me to a &#8220;real person&#8221; in another department, but by that time, my answer was, &#8220;Thanks, but too little too late. I&#8217;ve exchanged the phone for another brand.&#8221;</p>
<p>Seeing as how returns of electronic consumer products is a multi-billion dollar problem in North America, companies could definitely benefit from having strong content strategies, not just on their website, but across the product line, from instructions to training to their support site.</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=986&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2009/11/09/consequences-of-not-having-a-good-content-strategy/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Content strategy explained: two perspectives</title>
		<link>http://intentionaldesign.ca/2009/10/25/content-strategy-explained-two-perspectives/</link>
		<comments>http://intentionaldesign.ca/2009/10/25/content-strategy-explained-two-perspectives/#comments</comments>
		<pubDate>Sun, 25 Oct 2009 13:41:21 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Strategies]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[user experience]]></category>
		<category><![CDATA[content strategy]]></category>

		<guid isPermaLink="false">http://intentionaldesign.ca/?p=980</guid>
		<description><![CDATA[nForm rep Matthew Nish-Lapidus interviewed me and Kristina Halvorson, in advance of the CANUX 2009 weekend workshop in beautiful Banff, on the topic of content strategy. The interviews, in podcast form, discuss content strategy from quite different perspectives, yet there is an underlying similarity about this field of practice. In true content strategy form, the [...]]]></description>
			<content:encoded><![CDATA[<p>nForm rep <a title="Matthew Nish-Lapidus" href="http://nform.ca/about-us/matthew-nishlapidus" target="_blank">Matthew Nish-Lapidus</a> interviewed me and Kristina Halvorson, in advance of the <a title="CANUX 2009" href="http://canux.nform.ca/" target="_blank">CANUX 2009</a> weekend workshop in beautiful Banff, on the topic of content strategy. The <a title="content strategy podcasts with Bailie, Halvorson" href="http://nform.ca/blog/2009/10/content-strategy-at-canux-with" target="_blank">interviews, in podcast form</a>, discuss content strategy from quite different perspectives, yet there is an underlying similarity about this field of practice. In true content strategy form, the medium affects the message;  listening to a podcast provides a less formal, yet rich and fluid perspective.</p>
<p>If you&#8217;ve never been to CANUX, you&#8217;re missing out on a fabulous opportunity. Being up in a resort-like mountain setting at the <a title="Banff Centre" href="http://www.banffcentre.ca/" target="_blank">Banff Centre</a> imbues the workshop with some cosmic-force creative atmosphere. There are a few days left to sign up with the advance discount, so don&#8217;t delay if you&#8217;re sitting on the fence.</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=980&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2009/10/25/content-strategy-explained-two-perspectives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

