<?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>UXmatters</title>
<link>http://www.uxmatters.com</link>
<description>Insights and inspiration for the user experience community</description>
<dc:language>en-us</dc:language>
<dc:creator>pabini@uxmatters.com</dc:creator>
<dc:date>2008-07-22T07:59:25+00:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.2" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
	<item>
		<title>Excel Hacks for Help Writers</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2007/01/mike_hughes.php">Mike Hughes</a></p>
<p class="date">Published: July 21, 2008</p>
<p>One of my earlier careers was in manufacturing management,
and it grounded me in the principles of project planning and management. When I
moved into technical communication, I brought my project management disciplines
with me, and I embraced the prevailing tools of my new profession. I dutifully
produced documentation plans in Microsoft Word and supported them with detailed
project plans in Microsoft Project. However, the problem is that&#8212;like bad
relationships&#8212;these artifacts never gave back results that were sufficient to
reward the effort I put into creating them.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000310.php</link>
		<dc:subject>Columns</dc:subject>
		<dc:date>2008-07-22T07:59:25+00:00</dc:date>
	</item>
	<item>
		<title>Designing a Different Kind of Intranet: An Intranet for a UX Team</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2008/06/anirban_basu-ma.php">Anirban Basu Mallik</a></p>
<p class="date">Published: July 21, 2008</p>
<p>Most of us who are working as part of a design team in a services company, a product company, or even a design boutique have to live with a generic intranet. In this article, I&#8217;ll
  describe how to leverage your company&#8217;s intranet and how to build a community
  around an intranet for a UX team.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000309.php</link>
		<dc:subject>Features</dc:subject>
		<dc:date>2008-07-22T07:56:21+00:00</dc:date>
	</item>
	<item>
		<title>How to Succeed As a First-Time UX Manager</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2007/07/jim_nieters.php">Jim Nieters</a></p>
<p class="date">Published: July 7, 2008</p>
<p>In my last column, I suggested that being a manager of UX is
    no better&#8212;and no worse&#8212;than being a great designer or user researcher, but the
    roles are very different. In fact, as the book <em>The First 90 Days</em> [1] points out, the skills that make you successful as an individual contributor are <i>not</i> the same skills you need as a leader.</p>
  <p class="sub-p">Still, I was glad to see that a couple of people who talked
    with me after reading my column are being offered the opportunity to move into
    management roles and have decided to take the plunge. They asked me how they
    could make this transition a positive experience for them, their teams, and
    their companies. They were asking the right questions. This column discusses
    what attributes can help someone become a successful first-time UX
    manager&#8212;though these attributes are foundational elements for <em>all</em> managers.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000308.php</link>
		<dc:subject>Columns</dc:subject>
		<dc:date>2008-07-07T07:57:00+00:00</dc:date>
	</item>
	<item>
		<title>Preparing for User Research Interviews: Seven Things to Remember</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2007/12/michael_hawley.php">Michael Hawley</a></p>
<p class="date">Published: July 7, 2008</p>
<p>Interviewing is an artful skill that is at the core of a
  wide variety of research methods in user-centered design, including stakeholder
  interviews, contextual inquiry, usability testing, and focus groups.
  Consequently, a researcher&#8217;s skill in conducting interviews has a direct impact
  on the quality and accuracy of research findings and subsequent decisions about
  design. Skilled interviewers can conduct interviews that uncover the most
  important elements of a participant&#8217;s perspective on a task or a product in a
  manner that does <em>not</em> introduce interviewer bias. Companies hire user
  researchers and user-centered designers because they possess this very ability.</p>
<p class="sub-p">There is a wide variety of literature regarding best
  practices for user research interviews. For example, in their book <em>User and Task Analysis for Interface Design</em>, Hackos and Redish devote an entire section to the formulation of unbiased questions. They advise interviewers to avoid asking leading questions, to ask questions that are based
  on a participant&#8217;s experience, and to avoid overly complex, lengthy questions.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000307.php</link>
		<dc:subject>Columns</dc:subject>
		<dc:date>2008-07-07T07:39:24+00:00</dc:date>
	</item>
	<item>
		<title>Convergence and Emergence: 2008 IA Summit</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2008/06/james_kelway.php">James Kelway</a></p>
<p class="date">Published: July 7, 2008</p>
<p>The 2008 IA Summit was held April 10&#8211;14, at the Hyatt Regency in downtown Miami, Florida, shown in Figure 1. It had the highest attendance in the conference&#8217;s nine-year history: Over 600 people signed up for the conference run by ASIS&amp;T (American Society for Information Science and Technology). All the signs are that information architecture (IA) is a community and a practice that is growing, and that its sister disciplines&#8212;interaction design (IxD) and experience design&#8212;are well-represented at the conference&#8212;<em>not</em> just in terms of attendees, but also speakers.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000306.php</link>
		<dc:subject>Reviews</dc:subject>
		<dc:date>2008-07-07T07:00:49+00:00</dc:date>
	</item>
	<item>
		<title>The State of the UX Community</title>
		<description><![CDATA[<p class="author">By <a href="http://www.uxmatters.com/authors/archives/2006/08/jonathan_follet.php">Jonathan Follett</a></p>
<p class="date">Published: June 23, 2008</p>
<p class="quotation">&#8220;An organization&#8217;s reason for being, like that of any organism, is to help the parts that are in relationship to each other, to be  able to deal with change in the environment.&#8221;&#8212;Kevin Kelly</p>
<p>Over the past three decades of computer/human interaction,  we&#8217;ve seen digital technology evolve from a curiosity to a convenience to an  integral part of our everyday lives. For UX professionals, the demand for our  skill sets and the opportunities to practice seem only to grow, whether we be designers or developers, usability specialists or information architects,  working in fields as diverse as Web, mobile, desktop, and embedded software  systems. The UX professions are at a stage that could very well be a tipping point&#8212;where the rapid rise of digital devices, services, and connectivity  converge to create a massive need for UX professionals. The mobile space alone  could generate demand that we can only begin to imagine.</p>
<p class="sub-p">As the need for UX professionals grows and our fields  evolve, so too does the nature of our professional community. With an increased demand for our services comes a pressing need to advocate for our profession&#8217;s business value and secure a strategic role for UX, train and mentor new  practitioners, exchange knowledge among peers, and find ways to positively affect our society.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000305.php</link>
		<dc:subject>Columns</dc:subject>
		<dc:date>2008-06-23T09:32:57+00:00</dc:date>
	</item>
	<item>
		<title>Designing Ethical Experiences: Understanding Juicy Rationalizations</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2008/02/joe_lamantia.php">Joe Lamantia</a></p>
<p class="date">Published: June 23, 2008</p>
<p class="quotation1">From &#8220;The Big Chill&#8221;: [1]</p>
<p><span class="run-in-head">Michael:</span> &#8220;I don&#8217;t know anyone who could get through the day without two or three juicy  rationalizations. They&#8217;re more important than sex.&#8221;</p>
<p><span class="run-in-head">Sam Weber:</span> &#8220;Ah, come on. Nothing&#8217;s more important than sex.&#8221;</em></p>
<p class="quotation2"><span class="run-in-head">Michael:</span> &#8220;Oh yeah? Ever gone a week without a rationalization?&#8221;</em></p>
<p>Designers rationalize their choices just as much as everyone  else. But we also play a unique role in shaping the human world by creating the expressive and functional tools many people use in their daily lives. Our decisions about what <em>is</em> and is <em>not</em> ethical directly impact the lives of a tremendous number of people we will never know. Better understanding of the  choices we make as designers can help us create more ethical user experiences  for ourselves and for everyone.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000304.php</link>
		<dc:subject>Features</dc:subject>
		<dc:date>2008-06-23T09:27:52+00:00</dc:date>
	</item>
	<item>
		<title>Constructing a User  Experience: The Cost-Benefits Compass</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2008/06/ben_werner.php">Ben Werner</a></p>
<p class="date">Published: June 23, 2008</p>
<p>A common frustration among UX professionals who are employed  in the software development industry is the perception that executive-level  management gives lip service to user experience rather than supporting specific  UX activities by allocating sufficient resources for them.</p>
<p class="sub-p">This perception is seldom a reality. Competent management <em>does</em> realize that the user experience is  critical to the long-term health of their company. Unfortunately, when developing software, the temptation to steal from the feature-list cookie jar  and try to squeeze just one more feature into the current development cycle by  skipping UX work is simply too great for most Product Managers. This strategy, however nearsighted, can and often does make money in the short term by  achieving a temporary increase in sales. The only way to win resources in this  situation is to bring the discussion back to dollars.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000300.php</link>
		<dc:subject>Features</dc:subject>
		<dc:date>2008-06-23T08:40:23+00:00</dc:date>
	</item>
	<item>
		<title>International Address Fields in Web Forms</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2005/11/luke_wroblewski.php">Luke Wroblewski</a></p>
<p class="date">Published: June 9, 2008</p>
<p>As enablers of online conversations between businesses and customers, Web forms are often responsible for gathering critical information&#8212;email addresses for continued communications, mailing addresses for product shipments, and billing information for payment processing to name just a few. So it shouldn&#8217;t come as much of a surprise that one of the most common questions I get asked about Web form design is: &#8220;How do I deal with international addresses?&#8221;</p>
<p class="sub-p">But before we get into the nuances of address variations, it&#8217;s worth pointing out that addresses have a commonly understood structure. Through years of experience with mailing and postal systems, people have a pretty concrete idea of what constitutes an address block. This common understanding is so definitive that eyetracking data suggests, once people begin filling in a set of input fields that make up an address, they often cease looking at their labels. The basic structure of an address is so familiar, people don&#8217;t need the guidance labels provide.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000295.php</link>
		<dc:subject>Columns</dc:subject>
		<dc:date>2008-06-09T01:13:02+00:00</dc:date>
	</item>
	<item>
		<title>Better Bills</title>
		<description><![CDATA[<p class="author">By <a href="/authors/archives/2007/05/colleen_jones.php">Colleen Jones</a></p>
<p class="date">Published: June 9, 2008</p>
<p>The bill is a cornerstone communication in the customer experience, especially when it comes to billing for services. Customers want to easily understand and pay their bills, and businesses want to get paid on time. One would think a business would value the bill enough to invest in a thoughtful design. Yet many bills are poorly designed, causing needless confusion and frustration for customers and businesses alike&#8212;not to mention expensive customer service and customer churn. To encourage forward progress in the design of bills, this column profiles three common types of bill readers, discusses nine tips for improving bills, and notes some common implementation challenges.]]></description>
		<link>http://www.uxmatters.com/MT/archives/000293.php</link>
		<dc:subject>Columns</dc:subject>
		<dc:date>2008-06-09T01:08:03+00:00</dc:date>
	</item>


</channel>
</rss>