<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Salvy Cavicchio on Medium]]></title>
        <description><![CDATA[Stories by Salvy Cavicchio on Medium]]></description>
        <link>https://medium.com/@salvycavicchio?source=rss-4e527b34bd08------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*loLzckmMkMG1ifQI.</url>
            <title>Stories by Salvy Cavicchio on Medium</title>
            <link>https://medium.com/@salvycavicchio?source=rss-4e527b34bd08------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:41:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@salvycavicchio/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Make Your Users Happy by Designing for the Extremes]]></title>
            <link>https://medium.com/@salvycavicchio/designing-for-extremes-e0d13f84c61e?source=rss-4e527b34bd08------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0d13f84c61e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[happiness]]></category>
            <dc:creator><![CDATA[Salvy Cavicchio]]></dc:creator>
            <pubDate>Fri, 17 Jun 2016 13:01:02 GMT</pubDate>
            <atom:updated>2018-01-05T03:19:10.113Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Easy Way to Raise your Usability Threshold</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*tFAn1kxQcR8nXJ0-61sJlg.jpeg" /></figure><p>Some of the most valuable tools us designers have at our disposal are the <a href="https://medium.com/@salvycavicchio/https-medium-com-salvycavicchio-personas-and-pain-points-48864883ea19#.p75z4wuno">personas and scenarios</a> that we create as a way to define our user’s goals. They help us to see who our average users are and what they want to be able to do with our product. Stop using them to prototype. <em>The biggest usability mistake that designers make is to design products for the average user.</em></p><h4>The problem with designing for the average user is that they do not exist.</h4><p>The personas and scenarios that are so helpful in determining the goals of our user do not represent any individual person. They are created from a combination of all users (that’s the whole point). Any facet of their personality is completely and utterly artificial. Yes, our personas are created from real data, and yes, they show the characteristics of our users, but<strong> they do not represent any real person</strong>. Therefore, if we design for the average user we are designing a system for someone who simply does not exist. All that ends up happening is we create a product that satisfies nobody. In this sense, the average person is rather unique.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LV__L7YgX8RbQjXAl6zCOA.png" /><figcaption>Notice how in searching for the average of our sample, we have ignored a majority of people.</figcaption></figure><h4>Inclusive design accounts for users in all extremes.</h4><p>Earlier, we thought that by modeling our project after the average user we were making it more usable for a majority of our user base, but in actuality we created limitations on who is able to take full advantage of it. Instead, let us design for the extremes. A good program, website, or tool should let all users accomplish their intended tasks as easily and directly as possible. If your product is usable and intuitive to novice and expert users, it will create an enjoyable user experience for them and every user in between.</p><h4>Work smart, not hard.</h4><p>Designers and engineers want to invent things from scratch when in reality they could be leveraging the tools that people are already familiar with and happy using (you’re right, <a href="https://medium.com/u/52d45a2865c1">David</a>). Let your intuition guide design, but stick to conventions to increase usability. Using unfamiliar methods will cause frustration when a person can’t understand how to interact with the interface. Nobody likes to feel dumb. Usability is all about making sure that a product works well for all users, don’t make them think too hard.</p><p><em>This post is part 5 of a 5 piece series of articles on various aspects of UX/UI design and design-driven thinking. If you enjoyed this article, remember to recommend, comment, and share.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0d13f84c61e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus your MPV to Channel Unique Innovation]]></title>
            <link>https://medium.com/@salvycavicchio/discovering-your-mvp-db06f65faeed?source=rss-4e527b34bd08------2</link>
            <guid isPermaLink="false">https://medium.com/p/db06f65faeed</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Salvy Cavicchio]]></dc:creator>
            <pubDate>Mon, 13 Jun 2016 16:45:23 GMT</pubDate>
            <atom:updated>2016-06-17T13:55:01.534Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Importance of Understanding the Minimum Viable Product</h4><p>The minimum viable product (MVP) is is a powerful concept popularized by lean-startup pioneers Eric Reis and Steve Blank that allows any startup to test their ideas before launching into the costly side of development and production. The MVP is the version of your idea which has just enough features to gather validated learning about the product and its continued development. Results from MVP testing indicate if the product should even be built to begin with, and prove if it makes sense to move forwards with your product or pivot to another sector.</p><h4>The MVP strategy helps to avoid building products that customers do not want</h4><p>The MVP is a risk reduction tool that validates the need or opportunity for a new product. A minimum viable product can be a prototype, complete product, or sub-set of a larger project that helps to define, test, and validate ideas.</p><blockquote>“[The MVP is] selling the vision and delivering the minimum feature set to visionaries, not everyone.” (Steve Blank)</blockquote><p>The minimum viable product is the product with the highest return on investment versus risk. Defining your product through its MVP before starting development can accelerate learning of your user base, reduce wasted engineering hours, get the product to market faster, and reduce overall cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*LvJfQwujmSHQuucq6Br-xg.gif" /><figcaption>The cost of adding features or fixing errors increases exponentially over the course of a project’s development</figcaption></figure><h4>The MVP is a useful tool for determining the key parameters to the success or failure of a startup before it is too late to iterate.</h4><p><em>This post is part 4 of a 10 piece series of articles on various aspects of UX/UI design and design-driven thinking. Part 5 is </em><a href="https://medium.com/@salvycavicchio/designing-for-extremes-e0d13f84c61e?source=linkShare-4e527b34bd08-1466171647"><em>here</em></a><em>. If you enjoyed this article, remember to recommend, comment, and share.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db06f65faeed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Personas and Pain Points]]></title>
            <link>https://medium.com/@salvycavicchio/https-medium-com-salvycavicchio-personas-and-pain-points-48864883ea19?source=rss-4e527b34bd08------2</link>
            <guid isPermaLink="false">https://medium.com/p/48864883ea19</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Salvy Cavicchio]]></dc:creator>
            <pubDate>Wed, 08 Jun 2016 13:01:03 GMT</pubDate>
            <atom:updated>2016-06-13T16:46:48.843Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making Sense of User Data in UX/UI Design</h4><p>Research and testing are vital tasks that occur early in the design process to ensure that designers are on the right path to understanding the users needs and providing for them. We (as a people, business, or otherwise) want to solve <em>real problems</em>, not “band-aid” solutions onto existing standards. User research can alight a team, clarify the identity of the user, and validate the motivating ideas behind a product.</p><p>Yet, if you were interviewing people for an app concerning food allergens, it would not be very useful to observe that 50% of your subjects had no food related allergy. It would however, be useful to know that of the 50% of people with food related allergies, 70% of them feel that they have no good tool with which to track their eating habits and find food to order that is safe for them to eat. With this extra context to our data, we have found an unfulfilled need of our user that we can base our product on.<em> Successful products are successful when they complete an unfulfilled need or opportunity.</em></p><h4>Organizing data helps designers discover what the user wants</h4><p>The easiest way to observe peoples behaviors is through real user experiences. Knowing that a user took 3 clicks to perform an action that should have only taken 1 does not help the designer to discover the root of the usability issue encountered. Therefore, to represent data collected in research and testing, we create personas, scenarios, and user stories to showcase the users needs and actions.</p><h4>Personas, scenarios, and user stories create context for interactions between the user and a product</h4><p>Persona’s are the user archetypes that UX/UI designers use to guide human-centered design. Persona’s are built from user data collected during research and testing; they are used to pick the primary user of a product and remind the designer who they are designing for. As with research and testing, personas and scenarios lead objective driven design by helping designers decide which features or product aspects are most important to their project, and prevent them from relying on assumptions to drive design. Personas and scenarios together help us to create user stories, a shorthand way to describe features within a product.</p><h4>Our persona encountered the following scenarios,… what do they tell us about our user?</h4><blockquote>“ <strong>John Doe</strong> snoozes his alarm multiple times every morning and still wakes up tired”</blockquote><blockquote>“ <strong>John</strong> was late for work again because he slept through his alarm clock”</blockquote><blockquote>“ <strong>John</strong> set his alarm as his favorite song hoping that it would motivate him to wake up, and now he can’t stand it anymore”</blockquote><p>“What have we discovered about <strong><em>John</em></strong>? It seems like John has trouble getting up in the morning. Since he slept through his alarm clock maybe he isn’t getting enough sleep, or can’t hear his alarm. John also snoozes his alarm multiple times, so if would be a fair conjuncture to say that the snooze on John’s alarm is not long enough.</p><h4>Proper data visualization provides stronger insight</h4><p>By observing our raw data through these scenarios, we have discovered unfulfilled needs and pain points within John’s current alarm situation. <em>Our new product can now become successful by solving these unfulfilled needs or opportunities.</em></p><h4>If you know someone like John, you just validated our <em>persona</em>.</h4><p><em>Remember, everything is validated with research and testing.</em></p><p><strong><em>John </em></strong>represents one of our possible user archetypes, and the attributes and behaviors of a multitude of our user base. The scenarios which John finds himself in represent probable scenarios from any one of our many users. Using John as our persona to guide the design process allows our design to become less subjective and more task oriented to fit the users motivations and context. The pain points that John encounters are the trouble spots that we as designers will want to look out for when developing our final product and user flow.</p><p><em>This post is part 3 of a 10 piece series of articles on various aspects of UX/UI design. Part 4 is </em><a href="https://medium.com/@salvycavicchio/discovering-your-mvp-db06f65faeed#.jb5yjb7ud"><em>here</em></a><em>. If you enjoyed this article, remember to recommend, comment, and share.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48864883ea19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Modern Interview]]></title>
            <link>https://medium.com/@salvycavicchio/the-modern-interview-de6ead8fc4f6?source=rss-4e527b34bd08------2</link>
            <guid isPermaLink="false">https://medium.com/p/de6ead8fc4f6</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Salvy Cavicchio]]></dc:creator>
            <pubDate>Wed, 01 Jun 2016 19:29:54 GMT</pubDate>
            <atom:updated>2016-06-08T04:46:49.661Z</atom:updated>
            <content:encoded><![CDATA[<h4>Moving into the era of UX centered innovation</h4><p>The design of products by business has shaped local economies and been the driving force of technological innovation in history. Ford’s Model T, the Apple iPod, and Edison’s lightbulb were each the result of breakthroughs in engineering led by those who would later be known as pioneers and visionaries in their fields, and each immensely changed the way that people live.</p><h4>Innovation is born from the path less traveled</h4><p>A dangerous yet vital lesson to be learned from Steve Jobs is to rely on your intuition.</p><blockquote>“A lot of times, people don’t know what they want until you show it to them.” (Steve Jobs)</blockquote><p>While the domain of many businesses is to improve upon past design, the release of Apple products such as the Mac, iPod, iPhone and iPad created entirely new product categories.</p><p>A product’s success signaled the start of a new technological revolution in an era where competition within industry was performance driven. We had reached the point in history where people wanted more from their tools. More power, more performance, more technology; every object needs to be able to do more for us, better for us.</p><p>This high-technology type of innovation was a race of research and development to see who could most quickly bridge the gap between the current level of technological capability and the average users desire. There, the unfilled need of the user provided a space in which engineers and scientists could take a technology-centered approach to design. This begs the question of what to do once this unfilled need is no more.</p><h4>Technology becomes irrelevant once it works</h4><p>The age has now come where technology has surpassed the needed levels of performance, and we are presented with an excess of quality. At this point technology is “good enough”, and becomes irrelevant to the user, until a new performance is needed. The power of innovation now shifts from the business to the user. User experience dominates product design and performance is no longer measured by the ability of the technology but rather the ability of the user to interact with the device. The modern business model has shifted dramatically to become user-centered .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OfIlEDjHBaIwmmAdX_F0Cg.png" /><figcaption>The user-centered business model</figcaption></figure><p><em>Take a detour to the music industry</em> - an industry which for all of time has enriched and developed cultures throughout the world - and observe the most influential musicians of our time. Stevie Wonder, Louis Armstrong, Elvis Presley, Bob Dylan, and Ray Charles to name a few. The success of these individuals birthed the start of new genres in music, just as the success of businesses has sparked innovation. The music industry, however, is not subject to technology in the same way as a business. Music technology has always been “good enough”, and the music industry as a result has always had success through a user-centered approach, measuring success by the peoples response. <strong><em>This is how we define success in UX centered design.</em></strong></p><h4>Interviews create the new benchmarks of performance</h4><p>Once you become the designer, you can never again be the user. Our conceptual model of the device is now as a designer, we do truly understand the purpose of each feature and function of the device, so it is difficult, if not impossible to understand the difficulties that the user will face.</p><p>Interviews allow us to better understand our users needs and bridge the gap between the designers conceptual model, users conceptual model, and system image. We (as a people, business, or otherwise) want to solve <em>real problems</em>, not band-aid solutions onto existing standards. Interviews are one of the many ways that designers can conduct research and testing, and create connections in data from sales, engineering, and other product aspects to the user.</p><h4>Good interviewers ask about behaviors, not intentions</h4><p>The biggest myth of interviews is that people can tell you what they want. People said they wanted faster horses, yet received a car; a portable CD player, a brighter candle…</p><p>People tend to make confident, yet false assumptions about their future behavior. New Years Resolutions are the perfect example, what is the percentage of people that actually follow through on every resolution they make? I can assure you that the number is significantly low. There is a huge difference between imagining doing something and actually doing it, even more so when concerning a new design or behavior.</p><blockquote>“If I had asked people what they wanted, they would have said faster horses.” (Henry Ford)</blockquote><p>Good interviewers don’t want people to tell them what they think they want, they want to learn about their history, past behaviors, and goals. Once we have data on a large number of users, then we can start to create ways to synthesize and explain their behaviors in order to understand where to focus future design efforts. In this way, <em>design becomes less subjective and more prone to success</em>. This is the purpose of the modern interview.</p><h4>The modern interview guides innovative design</h4><p><em>This post is part 2 of a 10 piece series of articles on various aspects of UX/UI design. Part 3 can be found </em><a href="https://medium.com/@salvycavicchio/personas-and-pain-points"><em>here</em></a><em>. If you enjoyed this article, remember to recommend, comment, and share.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de6ead8fc4f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Research and Testing in Design]]></title>
            <link>https://medium.com/@salvycavicchio/on-research-and-testing-in-design-324a298ac8bd?source=rss-4e527b34bd08------2</link>
            <guid isPermaLink="false">https://medium.com/p/324a298ac8bd</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[human-behavior]]></category>
            <category><![CDATA[research-and-discovery]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Salvy Cavicchio]]></dc:creator>
            <pubDate>Wed, 25 May 2016 19:47:01 GMT</pubDate>
            <atom:updated>2016-06-08T04:47:33.937Z</atom:updated>
            <content:encoded><![CDATA[<h4>How accidental affordances inspire iterative design</h4><p>When working on human-centered design, we must start with an exceptional understanding of people and the needs that a design is hoping to meet. UX/UI designers focus largely on the conception of the look, feel, and operation of a product; these items coming together to build the conceptual model of the design. Yet, as designers of new and innovative technologies, we must make assumptions as to how our users will interact with a product, what they want to achieve by using our device, and how they will do so. Similar to assumptions in scientific research, with each assumption that we make there is a greater chance that one of our assumptions will prove to be incorrect, invalidating any component of the project design that relies on that fact.</p><h4>To embrace human-centered design, we must aim to follow the path which offers the least assumptions of human behavior</h4><p>The most common and frustrating design flaw that will occur in the lifecycle of a product is misuse. Watching a person fumble with their briefcase, struggling to use a computer or open a door, or having difficulty regulating the temperature of their car, are all instances of poor, unintuitive human-centered design caused by false assumptions in the design process. The ultimate goal of the UX designer is to make a device so intuitive that the user hardly even realizes the effects of the design. To do this, a user must be able to gain an accurate conceptual model of a device from the signifiers and affordances allowed by the designer.</p><h4>Good communication is the key to intuitive design</h4><p>Unfortunately for the designer, people hardly ever praise good design, yet never fail to criticize bad design; thus is the life of the artist.</p><p>Miscommunication and misunderstanding of the capabilities and uses of a device are caused by the gaps between the Designers Conceptual Model, User’s Conceptual Model, and System Image.<strong> </strong>Each assumption that a designer makes on human behavior causes uninformed design choices, leading to confusing and frustrating designs. With each additional assumption that we make the chance of poor design increases exponentially.</p><p>Observe the gaps in the conceptual models of the “Featuritis” Curve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*0HYbGTJdk2Hw4_PpOOqmBA.jpeg" /></figure><p>Learning from this chart, the most obvious, yet most disastrous assumption that one can make towards human-centered design is that user happiness depends on the number of features that a product presents. This is a farce. Even so, when a student or designer looks to the “Featuritis” Curve to help them improve their design thinking, the first bad move they can make is to remove extraneous features from their product. This not only fails to solve the issue at hand, which pertains to the intuition of the design, it takes away from the possible uses of the product.</p><p>With each added feature there is more chance for confusing, overwhelming design yet if the only tool that designers had to achieve good design was the removal of features, cars would not have radios, smartphones would not exist, and the computer I am typing on would instead be a typewriter. People appreciate being able to use their devices for a variety of tasks. What people loathe is when the poor design of a device hinders their productivity and confidence.</p><h4>Avoid multivalent design.</h4><p>Instead of removing features, the best solution is to make the implemented features more accessible and intuitive so that the user can easily and happily work as intended. When driving in my car, I am confident that pressing the large button next to the radio will only turn on the radio, and nothing else. Therefore, I trust that I know how to turn on the radio, can do so safely while driving, and then can enjoy listening to music as I drive. Confidence and ease of use in design creates a happy, intuitive user experience. With every added feature, there should be a single, clear path to success as to avoid the confusion and frustration of poor design communication.</p><h4>The “Featuritis” Curve is an example of poor communication.</h4><p>The “Featuritis” Curve does not mean to hinder the quality of our design, so what is its true purpose that we are missing? To understand this we look at the designers conceptual model. If you or I were to design this curve from scratch, what would the purpose be? The goal of the curve is to show the relationship between User Happiness and the Number of Features of a product; the correlation of these factors, but <strong>not</strong> the causation as we had previously assumed.</p><p><strong>Think</strong>, what went wrong in the design that changed the system image from the conceptual model?</p><p>On the spectrum of possibilities from the designers conceptual model to our own where does the system image lie? What can be derived from the physical structure of the device? Does the image trend towards the designers conception, or our own? The truth is that the system image does not perfectly describe either model. Each discrepancy between the system image and conceptual models allows for further misinterpretation and miscommunication, leading to less intuitive design.</p><h4>Iteration Betters Design.</h4><p>Look again at what went wrong in the design of the “Featuritis” Curve. The designer must have made an affordance or signifier that lead us to create our conceptual model. Once we find this issue we can begin to construct a new and improved version of the design. This is design iteration.</p><p>The problem that we encountered was the assumption of causation between User Happiness and the Number of Features, so let us try to iterate a new design that accounts for this problem. First, I will add a signifier to correct the unintended affordance that we have been given.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*k5C1QYSd6T0U16T05Xnx8Q.png" /></figure><p>By adding the word “Correlation” to the title, the user now knows that this graph is showing just the correlation between these two factors, and not the causation. Adding signifiers is a fine way achieve good design communication and we can now consider our task done. Even so, let us try yet another iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*LyNf_Ra5RazuznOAIDMYdA.png" /></figure><p>Instead of adding additional signifiers, I have removed the original affordance that allowed us to draw an inaccurate conceptual model. The graph now focuses on the ease of feature use instead of the number of features given and the reader is no longer lead towards the previous assumption.</p><h4>“When you come to a fork in the road, take it” (Don Norman)</h4><p>Both iterations presented are equally valid design solutions. One removes affordances, the other adds a signifier, yet both allows us to reach our desired goal. Design started as a way to create beauty in everyday object, now designers develop new ways for people to interact with the world. Each iteration of design allows us to understand further how people interact with the objects around them, and the accidental affordances that lead to poor communication and misuse are our greatest tools for observing and learning of the tendencies of human behavior. Design is both a craft and an evidence based discipline.</p><h4>Iterative design is validated with research and testing</h4><p>With each accidental affordance, poor signifier, or other mistakes we make in creating intuitive human-centered design, we are presented with an opportunity to iterate and innovate our design with new-found knowledge. The exceptional understanding of people and the needs of a design that is necessary in the human-centered design process can only be gained by research and testing. Intuitive design is born from feedback and evolution, observing the results and use of our design to iterate a better solution, continuing to loop until we have achieved all goals.</p><h4>Assumptions are the UX designers greatest enemy… and the thing they must use to design. @<a href="https://medium.com/u/4368064e6ea6">Blade Kotelly</a></h4><p><em>This post is part 1 of a 10 piece series of articles on various aspects of UX/UI design. Part 2 can be found </em><a href="https://medium.com/@salvycavicchio/the-modern-interview-de6ead8fc4f6#.wae1lbx98"><em>here</em></a><em>. If you enjoyed this article, remember to recommend, comment, and share.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=324a298ac8bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>