<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<channel>
<title>InfoDesign: Understanding by Design</title>
<link>http://www.informationdesign.org/</link>
<description>Dedicated to the growth and improvement of the information experience industries.</description>
<dc:language>en-us</dc:language>
<dc:creator>plato@xs4all.nl</dc:creator>
<dc:date>2012-02-03T10:19:01+01:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.21-en" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>


<item>
<title>The User Experience Integration Matrix: Integrating UX into the Product Backlog</title>
<description>As long as we see UX projects as software engineering projects and not the other way around, the plus and minus sides of the magnet will not connect.
&quot;Teams moving to agile often struggle to integrate agile with best practices in user-centered design and user experience in general. Fortunately, using a UX Integration Matrix helps integrate UX and agile by including UX information and requirements right in the product backlog. While both agile and UX methods share some best practices-like iteration and defining requirements based on stories about users-agile and UX methods evolved for different purposes, supporting different values. Agile methods were developed without consideration for UX best practices. Early agile pioneers were working on in-house IT projects (custom software) or enterprise software.&quot;
(Jon Innes ~ Boxes and Arrows) courtesy of janjursa</description>
<link>http://www.boxesandarrows.com/view/integrating-ux-into</link>
<dc:subject>User experience</dc:subject>
<dc:date>2012-02-03T10:19:01+01:00</dc:date>
</item>

<item>
<title>Lost Stories Information Design History</title>
<description>Information design, one of the many giant fields on which shoulders we stand.
&quot;In a competitive business marketplace, not everyone wants to acknowledge that each generation tends to learn from, build on or divert from the previous generations ideas and output. We see this phenomenon clearly evident in the various streams of Information Design history.&quot;
(GK VanPatter ~ Humantific)</description>
<link>http://www.humantific.com/lost-stories-information-design-history/</link>
<dc:subject>Information design</dc:subject>
<dc:date>2012-02-03T09:13:15+01:00</dc:date>
</item>

<item>
<title>Why External Links Should Open in New Tabs</title>
<description>Unfortunately, many users don&apos;t even notice a tab has been initiated. Back, back, back...
&quot;When most designers design websites, they don&apos;t pay much attention to links. As long as the link works and takes users to the right page, everything is fine. However, a great user experience goes further than that. There are certain links that should open in new browser tabs, and ones that should open in the same browser tab. It&apos;s important for designers to know the difference.&quot;
(UX Movement) courtesy of rolandnagtegaal</description>
<link>http://uxmovement.com/navigation/why-external-links-should-open-in-new-tabs/</link>
<dc:subject>HCI</dc:subject>
<dc:date>2012-02-02T14:58:36+01:00</dc:date>
</item>

<item>
<title>The top mistakes UX designers make: the writeup</title>
<description>As long as UX designers learn from their mistakes.
&quot;Rather than talk about tactical mistakes, such as in prototyping and running studies, I focused on the ones we overlook the most, about attitude and culture.&quot;
(Scott Berkun a.k.a. @berkun)</description>
<link>http://www.scottberkun.com/blog/2012/the-top-mistakes-ux-designers-make-the-writeup/</link>
<dc:subject>User experience</dc:subject>
<dc:date>2012-02-01T11:39:07+01:00</dc:date>
</item>

<item>
<title>How Chief Customer Officers Are Driving Change</title>
<description>CX is getting a lot of traction due to Forrester these days. I wonder why.
&quot;An increasing number of companies are appointing a single executive to lead customer experience efforts for a business unit or the entire company.&quot;
(Paul Hagen a.k.a. @PaulHagen ~ UX magazine)
</description>
<link>http://uxmag.com/articles/how-chief-customer-officers-are-driving-change</link>
<dc:subject>Customer experience</dc:subject>
<dc:date>2012-01-31T20:45:29+01:00</dc:date>
</item>

<item>
<title>Mental Modeling For Content Work: Information Gathering</title>
<description>Mental modeling, the black swan of webdesign.
&quot;If you don&apos;t have much of a background in philosophy, the social or psychological sciences, you may not be familiar with the concept of intersubjectivity. Most would agree that it refers to a cognitive state somewhere between subjectivity (judgment based on individual personal impressions and feelings and opinions rather than external facts) and objectivity (judgment based on observable phenomena and uninfluenced by emotions or personal prejudices), which refers to a shared understanding of meaning or concept by more than one person.&quot;
(Daniel Eizans a.k.a. @danieleizans)
</description>
<link>http://danieleizans.com/2012/01/mental-modeling-for-content-work-information-gathering/</link>
<dc:subject>Content strategy</dc:subject>
<dc:date>2012-01-31T12:48:55+01:00</dc:date>
</item>

<item>
<title>How the Knowledge Navigator video came about</title>
<description>Great read about the making of the iconic vision video by AAPL.
&quot;Sparked by the introduction of Siri, as well as products such as iPad and Skype, there have been many recent posts and articles tracing the technologies back to a 1987 Apple video called Knowledge Navigator. The video simulated an intelligent personal agent, video chat, linked databases and shared simulations, a digital network of university libraries, networked collaboration, and integrated multimedia and hypertext, in most case decades before they were commercially available. Having been involved in making Knowledge Navigator with some enormously talented Apple colleagues, I thought I would correct the record once and for all about what really happened.&quot;
(Bud Colligan a.k.a. @collbud ~ Dubberly Design Office)</description>
<link>http://www.dubberly.com/articles/how-the-knowledge-navigator-video-came-about.html</link>
<dc:subject>Classics</dc:subject>
<dc:date>2012-01-31T10:29:58+01:00</dc:date>
</item>

<item>
<title>The System of Information Architecture</title>
<description>Systems lead to models, and modelling is what we do.
&quot;Information architects are inveterate systems thinkers. In the Web&apos;s early days, we were the folks who focused less on pages than on the relationships between pages. Today, we continue to design organization, navigation, and search systems as integral parts of the whole. Of course, the context of our practice has shifted. Increasingly, we must design for experiences across channels. Mobile and social are just the beginning. Our future-friendly, cross-channel information architectures need to address the full spectrum of platforms, devices, and media.&quot;
(Peter Morville ~ Journal of Information Architecture Volume 3 Issue 2)</description>
<link>http://journalofia.org/volume3/issue2/01-morville/</link>
<dc:subject>Information architecture</dc:subject>
<dc:date>2012-01-30T16:13:33+01:00</dc:date>
</item>

<item>
<title>A Brief History of Information Architecture</title>
<description>Great write-up of the founding mothers and fathers of our beloved field.
&quot;Information architecture is a professional practice and field of studies focused on solving the basic problems of accessing, and using, the vast amounts of information available today. You commonly hear of information architecture in connection with the design of web sites both large and small, and when wireframes, labels, and taxonomies are discussed. As it is today, it is mainly a production activity, a craft, and it relies on an inductive process and a set, or many sets, of guidelines, best practices, and personal and professional expertise. In other words, information architecture is arguably not a science but, very much like say industrial design, an applied art.&quot;
(Andrea Resmini &amp; Luca Rosati ~ Journal of Information Architecture Volume 3 Issue 2)
</description>
<link>http://journalofia.org/volume3/issue2/03-resmini/</link>
<dc:subject>Information architecture</dc:subject>
<dc:date>2012-01-30T16:10:21+01:00</dc:date>
</item>

<item>
<title>Browser and GUI Chrome</title>
<description>I&apos;m wondering if traditional media also have this chrome thing.
&quot;Chrome is the user interface overhead that surrounds user data and web page content. Although chrome obesity can eat half of the available pixels, a reasonable amount enhances usability.&quot;
(Jakob Nielsen ~ Alertbox)</description>
<link>http://www.useit.com/alertbox/ui-chrome.html</link>
<dc:subject>Usability</dc:subject>
<dc:date>2012-01-30T09:48:47+01:00</dc:date>
</item>


</channel>
</rss>
