<?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>2010-03-03T10:26:04+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 Future of Wireframes</title>
<description>&quot;As we move into the next decade of web design, it&apos;s time for us to reevaluate our understanding of wireframes—a tried and tested user experience staple.&quot; (Nishant Kothary - MIX Online) - courtesy of rasmusdegruil</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/03/#005458</link>
<guid isPermaLink="false">5458@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2010-03-03T10:26:04+01:00</dc:date>
</item>

<item>
<title>Preso: Wireframes for the Wicked</title>
<description>&quot;Wireframes beyond the basics, not for the weak at heart. In this panel, three experienced designers will share their tried and true tips for making wireframes really work. We&apos;ll talk about how to sketch a wireframe on the fly to demonstrate an idea and how to create a standalone wireframe deliverable; when to show a concept and when to describe nitty-gritty detail; how to make a narrative wireframe and how to make a specification wireframe. And best of all, we&apos;ll show you plenty of examples.&quot; (Michael Angeles, Nick Finck and Donna Spencer - March 6, 2009)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/01/#005399</link>
<guid isPermaLink="false">5399@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2010-01-19T13:05:54+01:00</dc:date>
</item>

<item>
<title>Where Wireframes Are Concerned</title>
<description>&quot;Wireframes can be useful, valuable artifacts for informing the designer&apos;s process. But they often fail miserably as a first-step deliverable for clients.&quot; (Andy Rutledge - UX Magazine)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/12/#005332</link>
<guid isPermaLink="false">5332@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2009-12-11T09:40:55+01:00</dc:date>
</item>

<item>
<title>Sketchy Wireframes: When you can&apos;t (or shouldn&apos;t) draw a straight line</title>
<description>&quot;When it comes to user interface documentation, wireframes have long been the tool of choice. However, using traditional diagramming tools like Visio, OmniGraffle, and InDesign, most wireframes today look the same as their ancestors did from a decade ago – assembled with rigid, computer-drawn boxes, lines and text. While these artifacts have served us well, they can also be slow to produce, burdened with unnecessary detail and give a false impression of &apos;completion&apos;. To compensate for the drawbacks of traditional wireframes, many practitioners put aside the computer in favor of simple pencil sketches or whiteboard drawings. This speeds up the ideation process, but doesn’t always produce presentable or maintainable documentation.&quot; (Aaron Travis - Boxes and Arrows)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/12/#005323</link>
<guid isPermaLink="false">5323@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2009-12-07T11:31:30+01:00</dc:date>
</item>

<item>
<title>Preso: Sketching the Mobile User Experience</title>
<description>&quot;If you&apos;re a web or interactive designer, chances are sometime very soon you will be asked to design something for a mobile phone. This presentation will introduce rapid and flexible design and prototyping techniques to help you test early, test often and create great mobile experiences.&quot; (Bryan Rieger - Yiibu)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/06/#005071</link>
<guid isPermaLink="false">5071@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Mobile design</dc:subject>

<dc:date>2009-06-09T10:38:37+01:00</dc:date>
</item>

<item>
<title>The Life Cycle of a Wireframe</title>
<description>&quot;For those who are looking for my slides from the Puget Sound SIGCHI lecture and for those who missed it but are curious, here is my presentation.  It focuses specifically on my personal process for creating wireframes.  There are 4 parts to my process, each has a series of deliverables that feed into it and principals I try to keep in mind, the outcome is either a single or a series of IA deliverables. My overall strategy for IA is three step process; understanding the problem (note: not merely identifying the problem but really understanding it), find a solution (there may be more than one solution, but there is often only one right solution), and present the solution (a large part of your job as a IA is presenting your work so the client can understand the results).  Hope you enjoy the slides, these are admittedly pretty rough.  I plan to refine and show better pairing between the principals and the specific outcome of applying them to the wireframes in the future.&quot; - (Nick Finck)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/06/#005063</link>
<guid isPermaLink="false">5063@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2009-06-03T14:54:17+01:00</dc:date>
</item>

<item>
<title>Wireframes Magazine</title>
<description>&quot;Oh come on don&apos;t be shy. Do you have something to show off while documenting rich interaction, dynamic content, user flows, and web 2.0 wireframes? Please send me a sample and I will put it up. Also tell me who to credit and if you would like an optional link back.&quot; (Jakub Linowski)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/01/#004849</link>
<guid isPermaLink="false">4849@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2009-01-13T15:43:44+01:00</dc:date>
</item>

<item>
<title>Wireframeworks Manifesto</title>
<description>&quot;Over the last ten years, the Internet has gone from being the product of technology to the media channel of choice for much of the general public. Designers and developers have forged together innovative, entertaining and essential landmarks that can be accessed by computer, mobile and TV. As the importance of access, effectiveness and ergonomics of the web has become self evident, the role of the user experience professional has become the missing link between technology and people. We aim to make the web more usable, accessible, findable and practical.&quot; (Hammad Khan - Wireframeworks)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2008/11/#004778</link>
<guid isPermaLink="false">4778@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Information architecture</dc:subject>

<dc:date>2008-11-24T15:00:43+01:00</dc:date>
</item>

<item>
<title>Real Wireframes Get Real Results</title>
<description>&quot;Wireframes are in fact the first design iteration, and this overlap of visual design can be uncomfortable for teams. However, denial is not the way to fix this issue. Good collaborative relationships should make this overlap an opportunity to reduce work, not fight over ownership. Concern that wireframe might be mistaken for a visual design, or worse, be criticized for lacking design, may be holding the entire project back. It is much easier to communicate within the project team than the outside audience. Consider ways to make the transition as smooth as possible, for example having the wireframe be designed to import into the designer tool without retyping all the text.&quot; (Stephen Turbek - Boxes and Arrows)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2006/09/#003938</link>
<guid isPermaLink="false">3938@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2006-09-20T19:23:28+01:00</dc:date>
</item>

<item>
<title>Graffletopia</title>
<description>&quot;As a web designer, I&apos;ve been using OmniGraffle for years. It&apos;s fantastic for designing interfaces — miles better than Adobe Illustrator for most tasks. Stencils are a big part of why Graffle is great. So, hopefully, this website will make it easier to find cool stencils. Let the sharing begin!&quot; (About Graffletopia)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2006/07/#003846</link>
<guid isPermaLink="false">3846@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2006-07-18T11:42:22+01:00</dc:date>
</item>

<item>
<title>Wireframe Annotations in Visio : Special Deliverable #11</title>
<description>&quot;This article introduces several techniques in the context of wireframe annotations. At the conclusion, you will have learned to create an annotation widget, and you will also have learned several facets of Visio you may not have been aware of.&quot; (Dan Brown - Boxes and Arrows)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2004/10/#002801</link>
<guid isPermaLink="false">2801@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2004-10-29T07:21:24+01:00</dc:date>
</item>

<item>
<title>Representing Content and Data in Wireframes</title>
<description>&quot;Sample data can make or break a wireframe, whose purpose is typically to illustrate architecture and interaction. Poorly selected sample data can end up clouding the wireframe or distracting stakeholders from its purpose. By codifying the types of sample content they employ in their deliverables, information architects can create a coherent narrative to illustrate a website&apos;s functionality.&quot; (Dan Brown - Boxes and Arrows)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2004/08/#002652</link>
<guid isPermaLink="false">2652@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2004-08-17T09:52:41+01:00</dc:date>
</item>

<item>
<title>Where the Wireframes Are: Special Deliverable #3</title>
<description>&quot;A wireframe (...) describes the contents of a web page by illustrating a mock layout.&quot; (Dan Brown - Boxes and Arrows)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2002/07/#001191</link>
<guid isPermaLink="false">1191@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2002-07-03T16:24:11+01:00</dc:date>
</item>

<item>
<title>Using Wireframes</title>
<description>&quot;A wireframe is a visualization tool for presenting the layout of a web page element inventory.&quot; (Strange Systems)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2002/05/#001048</link>
<guid isPermaLink="false">1048@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2002-05-28T10:53:20+01:00</dc:date>
</item>

<item>
<title>WireFrames</title>
<description>&quot;(...) wireframes should look like frames made of wire.&quot; (Victor Lombardi - IAWiki)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2001/11/#001564</link>
<guid isPermaLink="false">1564@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Wireframes</dc:subject>

<dc:date>2001-11-30T14:42:42+01:00</dc:date>
</item>


</channel>
</rss>