<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.11.81 (http://www.squarespace.com/) on Sat, 02 Jun 2012 00:24:35 GMT--><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><title>Elegant Interaction</title><subtitle>Elegant Interaction</subtitle><id>http://www.lyndsaymazzola.com/imported-data/</id><link rel="alternate" type="application/xhtml+xml" href="http://www.lyndsaymazzola.com/imported-data/"/><link rel="self" type="application/atom+xml" href="http://www.lyndsaymazzola.com/imported-data/atom.xml"/><updated>2011-08-16T16:15:26Z</updated><generator uri="http://www.squarespace.com/" version="Squarespace Site Server v5.11.81 (http://www.squarespace.com/)">Squarespace</generator><entry><title>Visual Design in Axure RP</title><category term="axure"/><category term="best practices"/><category term="visual design"/><id>http://www.lyndsaymazzola.com/imported-data/2011/8/15/visual-design-in-axure-rp.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2011/8/15/visual-design-in-axure-rp.html"/><author><name>Lyndsay</name></author><published>2011-08-15T19:33:11Z</published><updated>2011-08-15T19:33:11Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>Had a productive week last week as I hooked up an Axure prototype based on my visual design direction. After I checked out Adobe's release of <a href="http://muse.adobe.com/" target="_blank">Muse</a> today, one feature that caught my eye was the paragraph styles. I did not know that Axure also had this (albeit hidden) feature until I came across Fred Beecher's useful presentation on Managing Visual Design in Axure.</p>
<div id="__ss_2508349" style="width: 510px;"><strong style="display: block; margin: 12px 0 4px;"><a title="Managing Visual Design in Axure" href="http://www.slideshare.net/fred_beecher/managing-visual-design-in-axure" target="_blank">Managing Visual Design in Axure</a></strong> <iframe src="http://www.slideshare.net/slideshow/embed_code/2508349?rel=0" width="510" height="426" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
<div style="padding: 5px 0 12px;">View more <a href="http://www.slideshare.net/" target="_blank">presentations</a> from <a href="http://www.slideshare.net/fred_beecher" target="_blank">Fred Beecher</a></div>
</div>]]></content></entry><entry><title>Playing with Adobe Edge</title><id>http://www.lyndsaymazzola.com/imported-data/2011/8/4/playing-with-adobe-edge.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2011/8/4/playing-with-adobe-edge.html"/><author><name>Lyndsay</name></author><published>2011-08-04T19:05:15Z</published><updated>2011-08-04T19:05:15Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>Started to play with Adobe Edge today. Watched <a href="http://tv.adobe.com/watch/adc-presents/edge-getting-started/" target="_blank">this overview</a> and found it pretty easy to follow along while I created <a href="http://www.lyndsaymazzola.com/storage/sample-animation.html" target="_blank">my own version</a>. While I've not created a lot of motion design in my career, I am familiar with Flash, and found Edge to be far more nimble. The HTML file in Edge exported a combination of CSS, jQuery and JavaScript.</p>
<p>While Edge doesn't yet fully support HTML5 (objects exported as divs instead of canvas), Adobe says they are moving in that direction. Too early to judge?</p>]]></content></entry><entry><title>The Who, What and How</title><category term="ux"/><id>http://www.lyndsaymazzola.com/imported-data/2011/8/3/the-who-what-and-how.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2011/8/3/the-who-what-and-how.html"/><author><name>Lyndsay</name></author><published>2011-08-03T18:30:00Z</published><updated>2011-08-03T18:30:00Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>A quick, sketchy diagram of UX tools and artifacts in the context of design process.</p>
<p><span class="full-image-block ssNonEditable"><span><img src="http://www.lyndsaymazzola.com/storage/who-what-how.png?__SQUARESPACE_CACHEVERSION=1312416011150" alt="" /></span></span></p>]]></content></entry><entry><title>Brooks's Law and Babies</title><category term="best practices"/><category term="estimation"/><category term="ux"/><id>http://www.lyndsaymazzola.com/imported-data/2011/8/3/brookss-law-and-babies.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2011/8/3/brookss-law-and-babies.html"/><author><name>Lyndsay</name></author><published>2011-08-03T17:48:05Z</published><updated>2011-08-03T17:48:05Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>During one of our training workshops on UX Estimation, I was introduced to&nbsp;<a href="http://en.wikipedia.org/wiki/Brooks's_law" target="_blank">Brooks's Law</a>. As a best practice, one needs to strike the right balance of scope and people on a project. This needs to be done before the project starts; not during. As Brooks stated,&nbsp;<strong>"Nine women can't make a baby in one month."</strong>&nbsp;When you consider factors such as ramp-up time and communication overhead involved for each person added, it becomes clear why you need to get the estimation right the first time.</p>]]></content></entry><entry><title>On Thinking on Your Feet</title><category term="consulting"/><category term="ux"/><id>http://www.lyndsaymazzola.com/imported-data/2011/7/20/on-thinking-on-your-feet-1.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2011/7/20/on-thinking-on-your-feet-1.html"/><author><name>Lyndsay</name></author><published>2011-07-21T01:12:38Z</published><updated>2011-07-21T01:12:38Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p class="p1">As a consultant, it's important to be able to think on your feet. It's a skill that's not practiced&nbsp;often&nbsp;enough, and one that can strike fear into our hearts. In a group exercise led by our director, today our UX team was challenged to think on our feet when he asked each of us &nbsp;a specific, UX-related question. It really drove home the importance of having natural, rehearsed answers to questions about what we do.&nbsp;</p>
<ul class="ul1">
<li>Make the personal connection when explaining. When asked, "What do you do?" we could respond with, "I improve design so that you don't swear at your computer screen." Effective because people immediately connect with that.&nbsp;</li>
<li class="li1">Sample questions:&nbsp;What is UX?&nbsp;What does &lt;your company&gt; do? Why should we do Personas?&nbsp;What do you do at &lt;your company&gt;?</li>
<li class="li1">How do we respond to objections? E.g., "We don't have time for wireframes. Can't you just jump into the visual design?" Or, "You're able to code the designs as well, right? We don't have the budget for an additional resource."</li>
<li class="li1">Pitfalls:&nbsp;We descend into jargon. E.g., "I'm a Visual Designer, not an Information Architect."&nbsp;Difficult to say "no" to clients.</li>
<li class="li1">Better ways to approach.&nbsp;E.g., "Here's why you don't want me to ____ . I'm maxed out at 40 hours a week. It's possible that our timeline will be blown."</li>
<li class="li1">Objections are opportunities to educate client on&nbsp;process and roles so that we can be preventative. E.g., "We have three roles. Here's why." Shows that it saves time to involve more people than less.&nbsp;</li>
<li class="li1">Put yourself in the client's shoes. Their interest is how they are going to get their product out.&nbsp;</li>
</ul>]]></content></entry><entry><title>Clarifying Brand Strategy</title><id>http://www.lyndsaymazzola.com/imported-data/2011/5/25/clarifying-brand-strategy.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2011/5/25/clarifying-brand-strategy.html"/><author><name>Lyndsay</name></author><published>2011-05-25T17:54:37Z</published><updated>2011-05-25T17:54:37Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>An important part of any user experience project is to define the branding requirements. Sometimes we take the client's existing branding guidelines and extend them to the product we design. In new product development, most often the existing requirements do not exist, and it is on us to clarify the brand strategy. While I've always worked with a sound process that is rooted in clear rationale, this book has become a welcome new addition to my toolkit. What I liked most in Designing Brand Identity was its seemingly fresh take on ways to distill, synthesize, and illustrate this important part in the branding process. <span class="full-image-block ssNonEditable"><span><img src="http://www.lyndsaymazzola.com/storage/blogpost_designingidentity.jpg?__SQUARESPACE_CACHEVERSION=1306346115585" alt="" /></span></span>A great reference for any visual designer. <a href="http://www.amazon.com/Designing-Brand-Identity-Essential-Branding/dp/0470401427/ref=sr_1_fkmr0_1?ie=UTF8&amp;qid=1306346192&amp;sr=8-1-fkmr0" target="_blank">Find it over at Amazon</a>.</p>]]></content></entry><entry><title>Transitions</title><id>http://www.lyndsaymazzola.com/imported-data/2009/10/27/transitions.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2009/10/27/transitions.html"/><author><name>Lyndsay</name></author><published>2009-10-28T01:32:13Z</published><updated>2009-10-28T01:32:13Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>These past few months have seen the growing pains of a Visual Designer in her transition to a User Experience Architect role. I've been head down in an exciting new project that has allowed me to explore human centered design from the ground up. Lots of agonizing over the user's needs, goals, and motivations. Stacks of paper and whiteboards full of sketches. Rapid prototyping with Axure. There's something very satisfying about working so closely with business and user needs; seeing the big picture and then diving deep into details. I know one thing for sure &mdash; the next time I approach the visual design, I'll have gone in with an even broader perspective. The ability to see the big picture and connect all the dots is absolutely key.</p>]]></content></entry><entry><title>Writing Email: Be Succinct</title><category term="best practices"/><category term="email"/><category term="writing"/><id>http://www.lyndsaymazzola.com/imported-data/2009/6/18/writing-email-be-succinct.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2009/6/18/writing-email-be-succinct.html"/><author><name>Lyndsay</name></author><published>2009-06-18T21:05:03Z</published><updated>2009-06-18T21:05:03Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>When it comes to verbose work emails that force me to comb through each tedious paragraph for the main points, I find that my patience wears thin. It's perhaps for this very reason that I strive to be succint in my own email communication. I know that the inboxes of my recipients are flooded on a daily basis, so I don't want to add to the noise and clutter. A well-crafted, succinct message has a far greater chance to cut through the noise and get a response. The advantage is two-fold: not only does my recipient benefit, but I likewise benefit when I'm forced to boil my message down to its essence.</p>
<p>I'm a big fan of short paragraphs and bulleted lists. As a best practice, this is validated by Web content strategists. <a href="http://www.braintraffic.com/" target="_blank">Brain Traffic</a>, one such firm, offers this advice in their post on <a href="http://blog.braintraffic.com/2009/05/web-writing-for-email/" target="_blank">Web Writing for Email</a>:</p>
<ul>
<li>
<p>Don&rsquo;t use ambiguous language.</p>
</li>
<li>
<p>Eliminate unnecessary words.</p>
</li>
<li>
<p>Keep your sentences and paragraphs short.</p>
</li>
<li>
<p>When making lists, use bullets.</p>
</li>
<li>
<p>When giving instruction or steps, use numbered lists.</p>
</li>
<li>
<p>Your last sentence should include a clear call to action.</p>
</li>
</ul>]]></content></entry><entry><title>On Beauty</title><category term="conferences"/><category term="visual design"/><id>http://www.lyndsaymazzola.com/imported-data/2009/5/28/on-beauty.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2009/5/28/on-beauty.html"/><author><name>Lyndsay</name></author><published>2009-05-28T00:46:18Z</published><updated>2009-05-28T00:46:18Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>I've followed the buzz generated by UPA Boston's Mini UPA Conference, twittered via #miniupa. Came across Aye Moah's <a href="http://www.slideshare.net/ayemoah/moah-mini-upa2009" target="_blank">presentation</a>, "What User Interface Designers Can Learn from Architecture." Slide 28 contains a great quote by Matthew Frederick: "Beauty is due more to harmonious relationships among the elements of a composition rather than to the elements themselves."</p>
<p>I couldn't help but think of LukeW's <a href="http://www.uxmatters.com/mt/archives/2008/11/common-visual-design-misconceptions.php" target="_blank">article</a>, "Common Visual Design Misconceptions," where he dispels the myth that it's possible to evaluate visual design in pieces. It's critical that design decisions are made by looking at things holistically, rather than in isolation. As LukeW says, "When a designer adjusts one element, she needs to refactor the overall composition to restore balance. Design decisions made in isolation tend <em>not</em> to add up to a coherent whole."</p>]]></content></entry><entry><title>'Women of UX' Mention via #followfriday</title><id>http://www.lyndsaymazzola.com/imported-data/2009/5/16/women-of-ux-mention-via-followfriday.html</id><link rel="alternate" type="text/html" href="http://www.lyndsaymazzola.com/imported-data/2009/5/16/women-of-ux-mention-via-followfriday.html"/><author><name>Lyndsay</name></author><published>2009-05-16T03:24:25Z</published><updated>2009-05-16T03:24:25Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>Ok, so this totally made my day. <a href="http://whitneyhess.com/" target="_blank">Whitney Hess</a> included me as one of the 'Women of UX' on Twitter. Listened to her IA Summit 09 "Evangelizing Yourself" <a href="http://boxesandarrows.com/view/ia-summit-09-day-3" target="_blank">podcast</a> a couple weeks ago, and as a fellow introvert, have been inspired to reach out more into the UX community ever since. It doesn't always come easy to put myself 'out there', but it's nice to receive a nudge of validation and encouragement! <span class="full-image-block ssNonEditable"><span><img src="http://www.lyndsaymazzola.com/storage/womenofux_followfriday.png?__SQUARESPACE_CACHEVERSION=1242444743341" alt="" /></span><span class="thumbnail-caption" style="width: 316px;">Honorary #followfriday mention on Twitter</span></span></p>]]></content></entry></feed>
