<?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>2013-05-21T17:09:18+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>Expanded user journey maps: Combining several UX deliverables into one useful document</title>
<description>The more data the document contains, the stronger the need for proper information design.
&quot;UX deliverables had a rocky year so far. I feel particularly bad for the humble wireframe, which took some serious knocks over the past few months. There&apos;s also a growing skepticism about the value of Personas. The Persona thing made me particularly uneasy because I&apos;ve always been a huge fan, and we still start most of our projects with a workshop to define Personas and User Journeys.&quot;
(Rian van der Merwe ~ Elezea)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/05/#006834</link>
<guid isPermaLink="false">6834@http://www.informationdesign.org/</guid>
 -->

<dc:subject>User experience</dc:subject>

<dc:date>2013-05-21T17:09:18+01:00</dc:date>
</item>

<item>
<title>Love, hate, and empathy: Why we still need personas</title>
<description>Timeline forgets the very first personas for design: Henry Dreyfuss&apos; Joe and Josephine (1955).
&quot;These steps (solid research, creative analysis, and compelling presentation and rollout) can bring teams back around to a tool that they badly need. Feel free to dump the shallow personas that people roll their eyes at. It&apos;s time to reengage with empathetic work by making your users real, and letting their real voices be heard.&quot;
(Kyra Edeker and Jan Moorman ~ UX Magazine)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/02/#006744</link>
<guid isPermaLink="false">6744@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2013-02-22T10:47:29+01:00</dc:date>
</item>

<item>
<title>Are personas still relevant to UX strategy?</title>
<description>They will always be a great starting point for the unknowns of empathy and UCD.
&quot;There have been some who have proclaimed the impending demise of personas as a UX design approach since shortly after their introduction. While the optimal approach to creating and employing personas is still evolving—thanks to more useful data becoming available to design teams and new project-management methods—their usefulness has not yet diminished. If anything, personas have become even more useful because they put a human face on aggregated data and foster a user-centered design approach even within the context of efficiency-driven development processes.&quot;
(Paul Bryan a.k.a. @paulbryan ~ UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/01/#006703</link>
<guid isPermaLink="false">6703@http://www.informationdesign.org/</guid>
 -->

<dc:subject>User experience</dc:subject>

<dc:date>2013-01-21T10:02:35+01:00</dc:date>
</item>

<item>
<title>Creating Socionas: Building creative understanding of people&apos;s experiences in the early stages of new product development</title>
<description>Personas going social. Next up: Mobinas.
&quot;Creating Socionas seeks to address two questions: What do design teams need to understand about the social to develop products and services that delight users? And how can they build this understanding under the constraints of new product development practice?&quot;
(Carolien Postma ~ Delft University of Technology IDStudiolab)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2012/11/#006620</link>
<guid isPermaLink="false">6620@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2012-11-07T17:15:18+01:00</dc:date>
</item>

<item>
<title>Personas: A Critical Investment For Content Strategy</title>
<description>Personas as the silver bullet to guarantee empathy?
&quot;Content strategy isn&apos;t really a discipline but a defined approach to handling an organization&apos;s content consistently across departments and channels. It can only be effective if it becomes ubiquitous to the processes and procedures that already exist within business - communications, public relations, customer service, marketing, graphic design, IT, etc. While the defined strategy may be about content, the tactics by which we achieve our content goals are really about people. Who are we publishing content for? How will they interact with the content we present? How do they define relevancy? What is meaningful and engaging to them? Borrowing a tool that user experience and interaction designers have used for years, personas are a powerful way to not only create and implement a sound content strategy, but to facilitate its adoption by everyone in the organization.&quot;
(Kristina Mausser a.k.a. @krismausser ~ Follow the UX Leader)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2012/04/#006411</link>
<guid isPermaLink="false">6411@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2012-04-10T16:30:38+01:00</dc:date>
</item>

<item>
<title>Why Personas are Critical for Content Strategy</title>
<description>Personas are great for any UX field, content strategy included.
&quot;The most popular content strategy tools borrow from the discipline of information architecture, but there is one invaluable tool that is imperative to the process of strategy and implementation of tactics that we can thank our user experience cousins for: personas.&quot;
(Kristina Mausser a.k.a. @krismausser ~ Johnny Holland Magazine)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2012/02/#006349</link>
<guid isPermaLink="false">6349@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2012-02-16T21:15:16+01:00</dc:date>
</item>

<item>
<title>Pragmatic Personas</title>
<description>&quot;Knowing who will use your software is important to the software development process. Having the end user in mind helps you develop features that fit the user&apos;s needs. And, figuring out your end user, as Jeff Patton reveals, is indeed easy. In this column, Jeff details stereotypes to avoid, questions to ask, and how to implement this pragmatic persona in your development process.&quot; (Jeff Patton ~ StickyMinds)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2011/01/#005884</link>
<guid isPermaLink="false">5884@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2011-01-18T11:38:18+01:00</dc:date>
</item>

<item>
<title>Using Personas During Design and Documentation</title>
<description>&quot;(...) although demographics and task analysis play an important part in persona creation, personas are more than just a collection of user profiles and groups. You should make them as real as you can. They should embody all the human attributes you&apos;d expect to find in your users. For example, they could be moody, very task oriented, work in a specific type of environment, or even hate the idea of referring to documentation unless they are absolutely compelled to do so.&quot; (Niranjan Jahagirdar and Arun Joseph Martin ~ UXmatters.com)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/10/#005760</link>
<guid isPermaLink="false">5760@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2010-10-19T09:21:09+01:00</dc:date>
</item>

<item>
<title>Personas: Explorations in Developing a Deep and Dimensioned Character</title>
<description>&quot;If we are going to begin to address these issues, we need to get at the root of the problem—our empathetic understanding of our users. Having empathy for users and understanding their needs doesn&apos;t come from reading words on a page. It doesn’t come from statistical analysis of demographics either. It comes from truly embodying and experiencing the character of a persona, so it becomes ingrained emotionally and physically in our memories. Actors understand this. From the time Stanislavski began teaching Method Acting - a process of transformation in which actors begin to take on the true nature of a character - actors have referred to this moment when they realize a character&apos;s emotional memory and have truly become the character as the moment of embodiment.&quot; (Traci Lepore ~ UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/08/#005695</link>
<guid isPermaLink="false">5695@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2010-08-23T10:23:21+01:00</dc:date>
</item>

<item>
<title>Storyboards, Scenarios, Design Personas</title>
<description>&quot;Persona design falls far short of its potential without scenario design and walkthroughs. Only putting the personas into action bridges the contexts of use and implementation.&quot; (Design Crux)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/07/#005664</link>
<guid isPermaLink="false">5664@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2010-07-08T11:22:19+01:00</dc:date>
</item>

<item>
<title>Zombie Personas</title>
<description>&quot;This is by far the nerdiest episode we ever did, so fasten your seat belts. In his session at UXcamp, Tom said: &quot;Personas – love &apos;em or hate &apos;em – you can&apos;t not use &apos;em. Either you have zombies, or you have living ones.&quot; In this recording of his session he talks about different kinds of zombies like Mirror Personas, Undead Personas, Unicorn Personas or Stupid User Personas. He gives advice on how to avoid these fellas and how to make good use of living personas during a project. As a bonus, Tom explains why 37signals doesn&apos;t need personas at all.&quot; (UX Café)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/06/#005643</link>
<guid isPermaLink="false">5643@http://www.informationdesign.org/</guid>
 -->

<dc:subject>User experience</dc:subject>

<dc:date>2010-06-22T13:39:54+01:00</dc:date>
</item>

<item>
<title>Using Persona Advocates to develop user-centric intranets and portals</title>
<description>&quot;Grasping complex information needs and uses can indeed be daunting. One powerful design tool, personas, can help make sense of these needs and provide a framework for building Intranets that will satisfy a variety of needs. Effectively developed and used, personas enable Intranet teams to hone in on user needs and build interfaces and user experiences that end-user audiences can and will use.&quot; (McQueen Consulting)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/06/#005618</link>
<guid isPermaLink="false">5618@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2010-06-08T13:07:04+01:00</dc:date>
</item>

<item>
<title>Personas as User Assistance and Navigation Aids</title>
<description>&quot;A lot of work goes into creating personas, and I was delighted to discover this innovative way in which the team carried forward the benefits of that work into the final product, where users could benefit from it as well. The personas also provide a rich form of user experience by portraying typical practices for effectively using the portal. I recommend that other UX designers consider applying personas in this way—initially using these user research artifacts during design, then incorporating them into products as user assistance and navigation aids.&quot; (Mike Hughes ~ UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/06/#005612</link>
<guid isPermaLink="false">5612@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2010-06-07T09:28:30+01:00</dc:date>
</item>

<item>
<title>The Power of Personas</title>
<description>&quot;In this installment, we took somewhat detailed tour of personas. First, we covered how to make them—the processes and techniques involved in developing, validating, and maturing the personas themselves, which has a big benefit to the whole team involved in getting a much better understanding of whom the solution is being developed for. Then we discussed some different uses of personas, how not to use them, as well as how to—chiefly to gain empathy to inform what and how you build so that it makes sense for your target audience as well as a valuable communication tool to keep team members on the same page, speaking the same language, and collaborating in terms of people rather than in terms of technical or hierarchical terms.&quot; (Dr. Charles B. Kreitzberg and Ambrose Little)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/04/#005509</link>
<guid isPermaLink="false">5509@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2010-04-02T14:43:58+01:00</dc:date>
</item>

<item>
<title>The Essence of a Successful Persona Project</title>
<description>&quot;Personas are a flexible and powerful tool for user researchers. They&apos;re also one of the most misunderstood. When done well, they ensure the team focuses on the needs and delights of their users. Like other effective user research techniques, personas deliver confidence and insights to the team. Personas help the team make important design decisions with a thorough understanding of who the users are, what they need, and when they need it.&quot; (Jared Spool)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/02/#005436</link>
<guid isPermaLink="false">5436@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2010-02-18T09:25:18+01:00</dc:date>
</item>


</channel>
</rss>