<?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 Mendy Gee on Medium]]></title>
        <description><![CDATA[Stories by Mendy Gee on Medium]]></description>
        <link>https://medium.com/@mendygeedesign?source=rss-2f0f48a577f7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Mendy Gee on Medium</title>
            <link>https://medium.com/@mendygeedesign?source=rss-2f0f48a577f7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:13:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mendygeedesign/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[Are we missing the boat when we synthesize and affinitize our research?]]></title>
            <link>https://medium.com/@mendygeedesign/are-we-missing-the-boat-when-we-synthesize-and-affinitize-our-research-573ee334a8d8?source=rss-2f0f48a577f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/573ee334a8d8</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[average]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Mendy Gee]]></dc:creator>
            <pubDate>Tue, 03 Sep 2019 16:41:48 GMT</pubDate>
            <atom:updated>2019-09-05T00:08:58.933Z</atom:updated>
            <content:encoded><![CDATA[<h4>Would love some feedback from fellow designers, researchers, and anyone who is involved in the product design and development world.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQ9Q90ALFg3szb4NVOGplw.jpeg" /></figure><p>I recently read a pretty extraordinary book about averages and I’m wondering if and how the ideas discussed in the book might apply to how we approach and employ our design research.</p><p>In “<a href="http://www.toddrose.com/books#/endofaverage/">The End of Average</a>” author <a href="https://medium.com/u/abeada3401ac">Todd Rose</a> <em>(director of the Mind, Brain, and Education program at Harvard University)</em> expounds on one basic theme: <strong>A solution for everyone is a solution for no one.</strong></p><p>One of Rose’s first and biggest contentions is against the Belgian statistician and sociologist Lambert Adolphe Jacques Quetelet, who would become most famous for his classification of the “average man”, which would later evolve to become known as the BMI (Body Mass Index, or “Quetelet Index”). Quetelet maintained that not only is the average indicative of the group as a whole, but even more so, the average is the <em>best</em> modal of the entire group, and that this average is the ideal after which all ought to strive to emulate.</p><p>The problem with this way of thinking, contends Rose, is that after averaging out all the subjects which comprise the average, if you were to then compare each <strong><em>individual</em></strong> subject to the new average, they would look <strong><em>nothing</em></strong> like the average whatsoever. <em>The average is an unrealistic, unattainable and fake representation of the real individuals who comprise the average.</em></p><h3><strong>On Research</strong></h3><p>When we gather our research, we tend to begin making our logical groupings, affinitizations and syntheses based on the common threads, denominators, and themes which emerge from these nuggets of information. How can we ensure that when we create these groupings, we are not forming ideas which are in fact misrepresentative of the actual sources of these data points?</p><h3><strong>On Personas</strong></h3><p>There is a ton of debate out there around the efficacy of personas. I think most would agree that as long as personas are being done right, they can be extremely useful tools for designing the right solutions for the right users.</p><p>My question is even if our personas are in fact, well researched and true amalgamations of data points gathered over multiple user interviews, are we fooling ourselves into believing the emergent persona is representative of the individuals’ behaviors and goals? How do we ensure that the persona is not another “Average Man”, an unrealistic misrepresentation of real individuals?</p><h3>3 Principles</h3><p>In the book, Rose outlines 3 principles by which we can think about averages, and how we can more accurately understand the individuals who make up the average.</p><p><strong>The Jaggedness Principle</strong>: Nothing is one-dimensional.</p><p><strong>The Context Principle</strong>: Everyone behaves in different ways depending on the context and environment in which they find themselves. Introverts at work but extroverts at home is just one of many examples.</p><p><strong>The Pathways Principle</strong>: The road to success is not a ladder to be climbed rung by rung. There are webs of paths we can each trod and the linear path imposed on most of society is usually not the one for us.</p><p>Perhaps by further studying and applying these three principles in our design processes, we might begin to design better products suited for the individuals who actually use our products.</p><p>Comments welcome!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=573ee334a8d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The bulk experience: exploring multi-select and bulk actions]]></title>
            <link>https://uxdesign.cc/the-bulk-experience-7fcca8080f82?source=rss-2f0f48a577f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fcca8080f82</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Mendy Gee]]></dc:creator>
            <pubDate>Sun, 02 Jun 2019 22:44:43 GMT</pubDate>
            <atom:updated>2019-06-03T23:51:33.240Z</atom:updated>
            <content:encoded><![CDATA[<p>Designing for enterprise often involves ideating solutions for data-heavy content, and in an industry where expediency and ease-of-use are a driving force behind success, our users are often intent on accessing, manipulating, and taking action on multiple items at once, or, bulk action.</p><p>During a recent design sprint for a consultancy client, our design exploration led us to examine 3 distinct takes on multi-select and bulk action. The following is a brief look at some of the key differences and take aways from each of these examples.</p><h3>1. Checkboxes with Sticky Toolbar (Gmail)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YHY_PO_t-RKbBAzkNITi9Q.jpeg" /><figcaption>The Gmail model has visible checkboxes and a sticky action bar.</figcaption></figure><p>The most direct and accessible option of them all. The Gmail model employs distinct checkboxes and action buttons readily available to the user.</p><h4>Pros:</h4><ul><li>Extremely obvious and readily accessible</li><li>Works well on desktop and mobile when hover is not available</li><li>Includes “Select All” and other options upfront (although this works best and is most apparent when the content is displayed in list format)</li></ul><h4>Cons:</h4><ul><li>From a visual perspective, the repetitive icons can look a bit cluttered</li><li>If space is a concern (and it often is), the extra icons can take up some valuable screen real estate</li></ul><h3>2. Shift/Alt + click; right-click (G Drive)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XxBtKgdVx13EMr0v6qdypA.jpeg" /><figcaption>The G Drive model: Both select and action functions are always hidden.</figcaption></figure><p>Google Drive goes to the other extreme in comparison to its email companion. Arguably the least accessible of the three, bulk action in G Drive relies heavily on interaction conventions (albeit well adopted conventions) in that the user is required to shift-click to select, and then right-click to take action on the selected items.</p><p>In this model both the select function and the action functions are completely hidden. The onus is on the user to know that these functions exist, and how to access these functions. Many software interfaces also rely heavily on this pattern (e.g. layers in sketch or adobe software). While this model does look cleaner and will inevitable save space, it lacks clear affordances. One major drawback in this model is that without clear checkboxes, the shift-click/right-click action is impossible to complete on mobile or tablet unless substituted with a different gesture (e.g. double-tap or 3D touch in iOS).</p><h4>Pros:</h4><ul><li>Minimal design</li><li>Space saving</li><li>Utilizes well-adopted interaction conventions</li><li>Works well for both list or grid items</li></ul><h4>Cons:</h4><ul><li>Select and action functionality is always hidden</li><li>Requires inherent knowledge of action steps</li><li>Does not work on mobile unless executed with a different gesture like double tap or 3D Touch on iOS</li></ul><h3>3. Hover: The 2-Step Solution (Invision)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dMdpXe-XcTqEJENT5v4lQw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5qoE9aWP1VmsnZIJmY5vCg.jpeg" /><figcaption>The Invision model uses hover to indicate that an item can be selected (left) and a “select mode” with checkboxes and action bar once one item has been selected (right).</figcaption></figure><p>In an effort to make the best of both worlds, the InVision example relies on a hover function to save space and signify “selectibility”, and a separate “select mode” once one item has been selected. Both select and action functions are initially hidden thus saving space and creating minimal design, but become readily available once the user enters “select mode” creating clear affordances and accessibility. However, the drawback of a feature based on hover is the limitations on mobile or tablet devices.</p><h4>Pros:</h4><ul><li>A 2 step solution offers clean design and intuitive functionality.</li></ul><h4>Cons:</h4><ul><li>“Select All” and other select options are only available once user selects at least one item.</li><li>Limited to devices where hover is an option.</li></ul><h3>What do use when</h3><p>There is no one correct way. We cannot apply blanket rules across all design, but we <em>can</em> learn as much as possible about what has been done in the past, and what conventions already exist.</p><p>As designers, it is our duty to examine each instance, understand the business constraints, understand our users, their workflows, and the environments they work in, and create intuitive experiences appropriate for each individual scenario.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fcca8080f82" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-bulk-experience-7fcca8080f82">The bulk experience: exploring multi-select and bulk actions</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>