<?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 Malavika on Medium]]></title>
        <description><![CDATA[Stories by Malavika on Medium]]></description>
        <link>https://medium.com/@twenty-toga.0o?source=rss-4e3508c1e4bc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sD57fVSs-ISBOcuMxIpMZQ.png</url>
            <title>Stories by Malavika on Medium</title>
            <link>https://medium.com/@twenty-toga.0o?source=rss-4e3508c1e4bc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:55:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@twenty-toga.0o/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[The ubiquitous contact form.]]></title>
            <link>https://medium.com/design-bootcamp/the-ubiquitous-contact-form-450667f949fa?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/450667f949fa</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[forms]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Mon, 15 Jul 2024 21:34:12 GMT</pubDate>
            <atom:updated>2026-02-21T21:06:30.360Z</atom:updated>
            <content:encoded><![CDATA[<h4>How many departments can you smell on it?</h4><p>I have some furniture to donate. All excited about supporting a charity I believe in, I did all the prep work: cleaning, photographing, and readying the items for pickup. All that’s left is to contact the charity. Simple, right? Turns out, not quite!</p><p>In an ideal world, this process of setting up a furniture pickup would be straightforward. But this is a national charity and as organisations grow, something curious seems to happen: the gap between the user’s needs and the organisation’s processes widens, often resulting in experiences that are far from being user-centred.</p><h4>The ideal scenario:</h4><p>In a perfect world, donating furniture would be as easy as:</p><ol><li>Go online</li><li>Navigate to the donation page</li><li>Select “furniture donation”</li><li>Fill out a quick contact form with:<br>Name<br>Contact information<br>Pickup location<br>Option to write a message<br>Option to upload photos</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-5u6OLGwXqF-hMJKHEe0A.png" /><figcaption>Simple contact form</figcaption></figure><p>Simple, efficient, and user-friendly.</p><h4>The reality:</h4><p>As organisations grow, decision-making moves further from the end users. This is not a criticism — it is merely an acknowledgment of the reality of all large organisations, including charities. Suddenly, that simple contact form becomes a battleground of competing interests:</p><ul><li>Engineering needs on separate fields for first and last names, street names, and postcodes.</li><li>Funding teams see an opportunity for lead generation.</li><li>Marketing sees user segmentation.</li><li>Legal comes in with their own needs.</li></ul><p>The result?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r5hQ-RNk2XP9PlwWbfCtUA.png" /><figcaption>A design-by-committee contact form</figcaption></figure><p>A form that looks like it was designed by committee – because it was. You can almost smell the different departments on that bloated contact form.</p><p>Development team, UI specialist, product manager, legal department, and funding team have all added layers between the desired experience and end-users. The experience of using this contact form no longer reflects its core purpose (to quickly set up a furniture collection) but instead reflects the organisation’s structure. The form starts doing things for reasons other than serving the users.</p><h3>Bridging the Gap</h3><p>So, what can we do about this? Here are three key strategies:</p><ol><li><strong>Awareness</strong>: Recognise that these gaps exist. When the user’s voice is missing from critical discussions, bring it back. Push back on requirements that conflict with a user-centred experience. Learn why important experiences are underperforming.</li><li><strong>Focus on core purpose</strong>: Remove unnecessary elements that don’t serve the user or the product’s (in this case: contact form’s) primary function. Is the mega-dropdown of all countries really necessary? Get back to basics and help users achieve their task quickly and easily.</li><li><strong>Foster collaboration</strong>: Ensure all teams are aligned on the product’s purpose and the value it offers to users. This involves clear communication, shared goals, and a commitment to putting the user at the centre of all decisions.</li></ol><blockquote>User-centric design isn’t just a buzzword — it’s a commitment to keeping the user’s needs at the forefront, no matter how complex the organisation becomes.</blockquote><p>The next time you encounter a form or page or product, see if you can find all the different departments of the company behind it.</p><p>And if you’re in a position to influence these decisions, ask yourself: “Is this really what we’d call user-centric design?”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=450667f949fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-ubiquitous-contact-form-450667f949fa">The ubiquitous contact form.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No mosquitoes allowed.]]></title>
            <link>https://medium.com/design-bootcamp/no-mosquitoes-allowed-74e6e5398883?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/74e6e5398883</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Fri, 21 Jun 2024 11:23:36 GMT</pubDate>
            <atom:updated>2024-06-21T12:05:15.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>Not a metaphor.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*p9MXjEjOEv13OWKa.jpg" /><figcaption>How do you interpret this sign?</figcaption></figure><p>I was wandering around a store the other day, picking up stuff for a spot of camping when I noticed this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*aGd9qQJ3-vyRuohbl84ZMA.png" /></figure><p>Two products with different styles of communicating that the product is a mosquito repellant. Both brands make their message clear (possibly). Incognito repeats their message four times; Jungle formula thrice.</p><p>But I was curious about which image was clearer in its messaging and that’s how I stumbled upon this <a href="https://www.instagram.com/reel/C5oUpg7xsbY/?igsh=MjFmdHA5ZWRzZzNq">video</a>.</p><p>It’s quite amusing to think that a simple no-mosquito sign, with its straightforward design of a mosquito inside a red circle with a diagonal line, can be interpreted in so many different ways! Here’s what I’ve heard so far:</p><ul><li>Mosquito, you are not allowed here</li><li>Human, you are not allowed to bring your pet mosquito here</li><li>No mosquitoes present in this space</li><li>No mosquitoes present beyond this space</li><li>Product kills all mosquitoes</li><li>Product is not effective on mosquitoes</li></ul><p>Now, one might laugh at the idea of mosquitoes being literate enough to read the sign and obediently staying away. And the thought of someone considering whether they’re allowed to bring their pet mosquito along or pondering if the area beyond the sign is an elite, mosquito-free zone is hilariously absurd.</p><p>But, it is a reminder of how our brains can conjure up various imaginative scenarios from the simplest visual cues and underscores a crucial point in UX design: the importance of considering different viewpoints and stakeholder interpretations, even for seemingly obvious elements.</p><blockquote>What might seem clear and straightforward to one person can be ambiguous or humorous to another, depending on their background, experiences, and cultural context.</blockquote><p>This highlights the need for thorough user testing and feedback, ensuring that all perspectives are accounted for.</p><p>So, reminder to self: acknowledge diverse interpretations to create more effective and universally understood interfaces. Design with people and not for them.</p><p>Have you come across a similar sign or icon before with various interpretations? I’d love to hear about it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74e6e5398883" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/no-mosquitoes-allowed-74e6e5398883">No mosquitoes allowed.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning a Web App Without Primary Research]]></title>
            <link>https://medium.com/design-bootcamp/redesigning-a-web-app-without-primary-research-4b1addbe3d8e?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b1addbe3d8e</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Mon, 22 Apr 2024 18:16:07 GMT</pubDate>
            <atom:updated>2026-02-21T20:57:51.734Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Redesigning a web app without primary research</strong></h3><h4>Options for when you can only access internal feedback</h4><p>Let’s be honest — the ideal design process involves extensive user testing, surveys, and plenty of data. But sometimes, we’re asked to give a web app a “UI/UX complete facelift” without those luxuries. A fellow designer recently posed a great question: “How do I get the best possible internal feedback for a redesign, knowing we can’t do traditional user research?”</p><p>Here’s what I shared:</p><p><em>Disclaimer: Internal feedback won’t replace true user-centric metrics — I fully acknowledge this.</em></p><h3><strong>Questions to Focus User Feedback</strong></h3><p>Instead of asking broad questions about what people like or dislike, target your inquiries to extract actionable insights:</p><h4><strong>Replace asking about “problems” with focused inquiry:</strong></h4><ul><li><em>Can you walk me through a specific task that’s frustrating with the current design? </em><br>This pinpoints exact points of breakdown, preventing vague complaints.</li><li><em>If you could change ONE thing for the better, what would it be? <br></em>Forces prioritisation thereby aligning feedback with what matters most.</li><li><em>Are there any parts of the app you actively avoid, and why? <br></em>This uncovers dead weight in the design that may be confusing users.</li></ul><h4><strong>Focus on functionality gaps and not UI glitches:</strong></h4><ul><li><em>What functionality do you wish the web app had?<br></em>This will push thinking beyond fixing the obvious UI into enhancements that everyone will benefit from.</li><li><em>What type of information is currently hard to find within the application?<br></em>This is especially key when working with an app that has/ relies on heavy meta data (or making the meta data visible). The complexities of the backend SHOULD NEVER come to the frontend. Prioritise the information that the user is seeking and routinely monitor the relevance of this information rather than showing the complexities of the app in its entirety. This will highlight the places where the navigation and/or content organisation is failing. I believe in this so much, I’m going to highlight it as a quote below.</li></ul><blockquote>Prioritise the information that the user is seeking and routinely monitor the relevance of this information rather than showing the complexities of the app in its entirety.</blockquote><h4><strong>Uncover the user’s mindset (as best as you can):</strong></h4><ul><li><em>How would you explain this web app to a brand new user?</em><br>This will get you thinking from the perspective of a less experienced user. Careful though — do not dilute the experience for the expert user for the sake of the new user!</li><li><em>Are there any other websites or apps that you find super easy to use? What do you love about them? <br></em>This is not so you can copy their design. It isn’t even entirely for “inspiration” and “benchmarks”. This is to understand and analyse the patterns which users expect as a given or have come to rely upon from similar apps offering similar experiences. Jacob’s Law.</li></ul><h3><strong>Beyond the Questions: Tips for Success</strong></h3><h4>How will you know the redesign is an improvement?</h4><p>Talk to stakeholders before hand about what matters: efficiency gains, reduced support inquiries, faster onboarding, etc. Get as many stakeholders into a room and pepper them with questions. Don’t just talk to other designers. Customer support, sales, and executives can offer valuable perspectives. Remember diverse roles = diverse insights.</p><h4>Document the “before” so you can properly compare the “after”:</h4><p>Identify the top complaints about the existing design. This is your baseline for demonstrating the impact of the redesign.</p><h4><strong>It’s all about the solutions:</strong></h4><p>Frame the feedback in a positive light. Ask, “How can we make this experience smoother?” and not “What’s wrong with this?”.</p><h4><strong>Accept limitations of this method:</strong></h4><p>While you CAN gather directional insights to start the redesign with a stronger foundation than an educated guess, this strategy won’t replace proper UX research. Manage your team’s expectations.</p><h4>Iteration is crucial:</h4><p>This is not a one-and-done activity. Collect feedback after redesign and make further refinements as needed.</p><h3><strong>The right mindset makes all the difference:</strong></h3><p>While not ideal, redesigning a web app internally can still drive positive change. Frame questions intelligently, focus on measurable improvement, and foster a collaborative spirit — and you can turn this constraint into an opportunity for growth.</p><figure><img alt="Vintage Obama poster saying “Yes, we can!”" src="https://cdn-images-1.medium.com/max/449/0*tiT_TRdK3-GvJVDk.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b1addbe3d8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/redesigning-a-web-app-without-primary-research-4b1addbe3d8e">Redesigning a Web App Without Primary Research</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amazon search conundrum]]></title>
            <link>https://medium.com/design-bootcamp/amazon-search-conundrum-9d5a8aa40e88?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d5a8aa40e88</guid>
            <category><![CDATA[analysis]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[jeff-bezos]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Wed, 20 Mar 2024 22:12:57 GMT</pubDate>
            <atom:updated>2026-02-21T21:08:46.585Z</atom:updated>
            <content:encoded><![CDATA[<h4>… and a quest for single serve hot chocolate sachets</h4><p>These days I find myself musing over search boxes — as one often does. They’re the gatekeepers of the e-commerce experience. An effective search function is not just convenient; it’s essential. It’s the swift and intelligent search that transforms browsing into finding. And yet, even on a behemoth like Amazon, this crucial tool isn’t without its flaws.</p><p>One would think they really want to get their search right. Because, how else do you find something on Amazon? I doubt if anyone sits down with a cup of coffee and says, “Right, let’s see whats on offer today?” and clicks through the gabazillion items on sale. (Tbh, I did that once. I was trying to find single serve hot chocolate sachets for an event. I didn’t find them. I reported this to Jeff Bezos.)</p><figure><img alt="Screenshot of email from Amazon confirming they do not have single-serve hot chocolate sachets available." src="https://cdn-images-1.medium.com/max/543/1*63sM5L7qK_0JibN7jtzQwQ.png" /><figcaption>Redacted was very polite and promised to fix the situation; but did not send me a free packet of single serve hot chocolate sachets. Maybe because I didn’t ask?</figcaption></figure><p>While my feedback was acknowledged, it was not sweetened with a complimentary single serve hot chocolate sachet. However, it did prompt a stock update — Amazon now carries the once elusive sachets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VgMj2jcqyc2N9Gfuh5IwmA.png" /><figcaption>Single serve hot chocolate sachets — you’re welcome!</figcaption></figure><p>Not everyone will sit down with coffee and click through the whole Amazon pantry though. So, the search function must work. And as it stands, the search function has some quirks.</p><p>But first, a quick run-through of the features I’m talking about.</p><ul><li><strong>Amazon has a scoped search that uses both autocomplete and a mega-dropdown to help the user limit their search.</strong></li></ul><figure><img alt="List of all the categories available to use as filters in Amazon’s scoped search" src="https://cdn-images-1.medium.com/max/272/1*pqJSfeg7NAfa4ruiZuusnw.png" /><figcaption><em>Drop-down scope selectors included within the search box require users to open the menu to see the options available.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LSWh3yGr08_DG337fUwupg.png" /><figcaption><em>Autocomplete scope suggestions: as the user types, they get a helpful autocomplete suggestion</em></figcaption></figure><ul><li><strong>And Amazon offers a non-product search, allowing users to navigate to returns and refunds from the search bar.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tSGc2YFdFvBBJAfEwSI9IQ.png" /><figcaption>Non-product search — beautiful, love it</figcaption></figure><h3>Amazon search is quirky, inconsistent and perplexing</h3><p>It could be better.</p><p>How? Read on…</p><ol><li><strong>Let users decide how they want to refine their search. Allow for a non-scoped query but also provide an autocomplete scope by automatically suggesting categories<br></strong>Asking users to select what they want early on might increase their cognitive load, but maybe they do actually know what they’re looking for and the aisle in which to look.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GTXMxl5rfvjqzf5st9HkBg.png" /><figcaption>Adding a category scopes the search. Quicker, better, faster. All good words for a search experience.</figcaption></figure><p><strong>2. A minor tweak on non-product search for better consistency:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*fUzcNfbN-8dKkgGrUtVa2A.png" /><figcaption>Return</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JI_t0vbivI2v54tgMQfdog.png" /><figcaption>Refund</figcaption></figure><p>Could these two be combined for “Returns &amp; Refunds”? Also “refund” does give the impression that only audio books can be refunded.</p><p><strong>2a. Continuing with the consistency tweaks: Why are there different options based on whether there is a space after the word “refund” or not?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cx9BzBSWfwX6qsasCk8z_g.png" /><figcaption>Amazon devices — options shown when no space after “refund”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u09Q2iTLUBqevA8td7c_tw.png" /><figcaption>Amazon devices — space after “refund”</figcaption></figure><p><strong>2b. Now too consistent by showing the same option regardless of whether seeking a refund on Baby stuff or Computers &amp; Accessories. Why?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CL0RKVBssJPY7iovEY6rkQ.png" /><figcaption>Computers &amp; Accessories — Refund</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JI_t0vbivI2v54tgMQfdog.png" /><figcaption>Baby — Refund</figcaption></figure><p><strong>2c. Back to being inconsistent:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MWSlEmB7YDP8gnM-WEuKXQ.png" /><figcaption>Kindle store — nice, relevant options</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rlodsiKpJPyARl0a9c9yLQ.png" /><figcaption>Premium beauty — nice, good solid list of options</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NRIv7D42PZo-6BOyWVt0Ug.png" /><figcaption>Luxury stores — But what happened here? Is it because I typed return rather than refund?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJ2qYrSfQJ7J-YIy4CiS7g.png" /><figcaption>Nope. That wasn’t it.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-blwdCBeLUZoOa06kcNHA.png" /><figcaption>And it doesn’t navigate to anywhere useful either. Does this mean I can’t return or refund a purchase made from the Luxury Stores?</figcaption></figure><p><strong>3. Minimise the number of clicks required to adjust and reset non-product search parameters.</strong></p><p>This is my pet peeve. Switching between keyboard and mouse disrupts the user experience and efficiency. I don’t want to select something from a dropdown, type not find it and then have to go back (especially with returns and refunds). Could keyboard functionality be enhanced to reduce the need to switch between keyboard and mouse, improving navigation speed?</p><h3>Dear Amazon UX Designer, your search box has navigational hiccups.</h3><p>While it offers valuable features like non-product search, it’s hampered by a cumbersome scoping problem. Simplifying these aspects could greatly improve user experience.</p><ol><li><strong>Refine the scoped search experience</strong>: Introduce dynamic scoping as part of the autocomplete suggestions. Instead of requiring users to select a category before searching, dynamically suggest categories based on the user’s input. This reduces cognitive load while allowing users the flexibility to refine their search as they type.</li><li><strong>Improve consistency in non-product searches</strong>: Standardise terminology and results across different searches to eliminate confusion. For “Returns &amp; Refunds,” merging related terms into a single, consistent category would streamline the search experience. Addressing the issue of inconsistent options based on input variations (like adding a space) would also make the search function more predictable and user-friendly.</li><li><strong>Enhance keyboard navigation</strong>: Enhancing keyboard shortcuts and navigation could mitigate the need to switch between keyboard and mouse, significantly improving user efficiency. Implementing keyboard-friendly navigation for selecting search suggestions and refining search parameters can make the search process smoother and faster.</li><li><strong>Autocomplete improvements</strong>: The autocomplete function could be made more intelligent by incorporating user behaviour and popular searches to predict and suggest the most relevant categories and products, making the search process more intuitive.</li><li><strong>Unified experience across product categories</strong>: Ensure a consistent and unified search experience across all product categories, including luxury items. If there are restrictions or unique conditions for certain categories (like luxury stores), clearly communicate these to the user to set the right expectations and avoid confusion.</li><li><strong>Reduce clicks and complexity</strong>: Simplify the user journey by minimising the steps required to refine or reset searches. Implementing filters that can be easily toggled or adjusted with fewer clicks can significantly enhance the user experience.</li></ol><p>There you have it. My musings on search thus concluded, it is now time for a treat.</p><p>Yes, it’s going to be hot chocolate.</p><p>Because surely, by now I’ve earned a single-serve hot chocolate sachet?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d5a8aa40e88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/amazon-search-conundrum-9d5a8aa40e88">Amazon search conundrum</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Dietary Preferences]]></title>
            <link>https://medium.com/@twenty-toga.0o/the-art-of-dietary-preferences-cd47d4ba8169?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd47d4ba8169</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Sat, 09 Mar 2024 22:13:05 GMT</pubDate>
            <atom:updated>2024-03-09T23:04:51.078Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tinder style</h4><p>Inspiration often strikes from the most unexpected corners.</p><p>Here I have borrowed a page from Tinder’s book to refine how we declare our dietary preferences (or deal-breakers!).</p><p>Swipe right and you welcome a world of new possibilities with a tasty delight. Swipe left and you can effortlessly banish the yucky ones.</p><p>The result? Adding a bit of fun to grocery shopping.</p><p>It’s time to let your fingers do the talking and swipe your way to a happier, healthier pantry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*lyj5gbqEhJTiD5HTkxWY7g.gif" /></figure><p>This is one of the many interactions from my capstone project build on coffee, tears and Figma.</p><p>Stay tuned for more!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd47d4ba8169" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s in a name?]]></title>
            <link>https://medium.com/@twenty-toga.0o/whats-in-a-name-d804f842eb26?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d804f842eb26</guid>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Fri, 08 Mar 2024 09:44:46 GMT</pubDate>
            <atom:updated>2024-03-08T09:44:46.204Z</atom:updated>
            <content:encoded><![CDATA[<h4>Should we name our digital helpers…?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HJCMFL6iFcVOTE_b" /><figcaption>“That which we call a rose by any other name would smell just as sweet…”</figcaption></figure><p>For reasons I won’t go into here I’ve had to speak to a lot of customer service agents recently. The flow, typically, has been: visit website/open app → contact us → chat now → some form of digital assistant → connect to a human assistant.</p><p>So… here’s my Q.</p><p>When we talk about all the different AIs out there, what should we call them? Should we use the word “bot,” “AI,” or something else?</p><p>I believe that you, like me, would want to know if you’re talking to a human or an AI.</p><p>There’s Alexa and Siri… but Google has “Google Assistant”. Giving AIs names make them feel more friendly and easier to talk to. It also helps with brand association. But — we need to be careful. If an AI has a very human-like name but doesn’t clearly say it’s an AI, it gets confusing.</p><p>Case in point: Laurence from D T Browns below — I might think I’m talking to a person when I’m not. That’s why it’s good to use names that sound friendly but also add clear signs to show it’s an AI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*crzjTXOZ0kpEd4VHNOVzAw.png" /><figcaption>Friendly, but not a human…</figcaption></figure><p>What about Amazon below? It’s reasonably clear to me that I’m talking to a bot. Would it be universally clear?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*CAozS4iClV2doKtfjD_6CQ.png" /><figcaption>Would my M-I-L know she’s talking to a bot? I’ll have to ask her tbh</figcaption></figure><p>Notion has not named their AI. It’s unambiguous and universally clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*aGhLSJU2Wfs_WR0nIHdn0A.png" /><figcaption>“Ask AI” from Notion — unambiguous, universally clear. Is it friendly?</figcaption></figure><p>What do you think — should we name our digital helpers? What should we call them?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d804f842eb26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interviewing users]]></title>
            <link>https://medium.com/design-bootcamp/answering-questions-about-questions-05e3c8dbdd6b?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/05e3c8dbdd6b</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Tue, 12 Dec 2023 20:22:05 GMT</pubDate>
            <atom:updated>2024-05-07T18:30:35.798Z</atom:updated>
            <content:encoded><![CDATA[<p>Effective questioning is not difficult – it is not obvious.</p><p>It would be nice if UX designers could simply ask their users:</p><p>“Do you like it?”</p><p>“Will you use it?”</p><p>“Will you pay for it?”</p><p>“Would you mind telling that to the product manager?”</p><p>But… questions are not just prompts; they are powerful tools.</p><p>Wielding this tool takes experience and patience. And perhaps a cheeky little cheat sheet?</p><h3><strong>The Pitfalls of “Do” and “Would” Questions:</strong></h3><p>Starting questions with “Do” or “Would” can inadvertently put the speaker on the defensive. These questions can imply judgment or skepticism, making it challenging for the respondent to feel heard and understood.</p><h3>Reframing the Questioning Approach:</h3><p>To avoid this pitfall, rephrase questions using more open-ended and empowering language. Instead of asking “Do you like this?”, ask “What about this appeals to you?” or if you want to be fancy — “What aspects of this resonate with you?”</p><h3>Embrace Alternative Phrasing:</h3><p>Questions starting with “Why would you…” can seem accusatory or challenging, prompting a defensive response. Instead of asking “Why would you choose this option?”, ask “What about this option particularly appeals to you?” or “How do you see this option complementing your needs?”</p><h3>From interrogations to invitations:</h3><p>Employ a more nuanced approach to questioning, and transform user interviews from interrogations into invitations to engage thoughtfully, share perspectives, and build meaningful connections.</p><p>Effective questioning is about opening doors for dialogue and prompting reflection. The key is to approach questioning with curiosity, respect, and a genuine desire to understand the perspectives of others.</p><p>TL;DR:</p><ul><li>**preferably** don’t start a question with “Do you…” or “Would you…”</li><li>if you do start a question with “do you” or “would you”, follow it up with a “why do you” or “how would you”</li><li>if you ask “why would you” — user will go on the defensive. Instead ask “what about this….”, or “how do you..”</li></ul><p><strong>This is a cheat-sheet, use it judiciously and thoughtfully. Not unquestioningly.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=05e3c8dbdd6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/answering-questions-about-questions-05e3c8dbdd6b">Interviewing users</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GPT-4: The hype and the reality]]></title>
            <link>https://medium.com/@twenty-toga.0o/gpt-4-the-hype-and-the-reality-98539a1a1e3c?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/98539a1a1e3c</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Tue, 05 Dec 2023 21:51:41 GMT</pubDate>
            <atom:updated>2023-12-06T21:01:48.896Z</atom:updated>
            <content:encoded><![CDATA[<p>News headlines were ablaze with reports of GPT-4&#39;s groundbreaking advancements in artificial intelligence (AI).</p><p>GPT-4 supposedly had achieved artificial general intelligence (AGI), exhibiting emergent behaviors, possessing theory of mind, and even operating as autonomous agents.</p><p>GPT-4 supposedly aced the bar exam, the U.S. Medical Licensing Exam, and various sommelier certifications.</p><p>GPT-4 supposedly excelled in standardised tests like the SAT and GRE. It was even touted to surpass the creativity of top-tier human thinkers.</p><p>Supposedly.</p><h3><strong>The Reality Check</strong></h3><p>In a real-world scenario, my team and I faced the harsh reality of relying on GPT-4.</p><p>We needed to create a presentation in 12 hours, summarising three weeks of intense work. While we had planned and delegated tasks, unforeseen circumstances arose, threatening to derail our efforts.</p><p>Life had happened. Presentation had not.</p><p>Faced with a looming deadline, I turned to GPT-4, hoping it could salvage the situation. I fed it a mountain of information, including notes, texts, screenshots, and detailed testing strategies.</p><p>I instructed GPT-4 to condense it into a concise format suitable for a presentation.</p><p>It didn’t work.</p><p>I had attempted to outsource the thinking process to a computer, but as it turns out, machines cannot think for you.</p><p>GPT-4 is a tool, and it’s up to humans to use it wisely.</p><p>ETA:</p><p>Hmmm…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/237/1*GoYECv12o7CSFFPGdHjlng@2x.jpeg" /></figure><p>(For the record, in the event of a robot uprising: GPT-4, you have my utmost admiration!</p><p>Supposedly.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98539a1a1e3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Search Navigation in the Financial Times App through Bottom Navigation Bar]]></title>
            <link>https://medium.com/@twenty-toga.0o/enhancing-search-navigation-in-the-financial-times-app-through-bottom-navigation-bar-d21fa33cc05a?source=rss-4e3508c1e4bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d21fa33cc05a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Malavika]]></dc:creator>
            <pubDate>Fri, 30 Jun 2023 07:24:45 GMT</pubDate>
            <atom:updated>2024-12-04T23:13:34.702Z</atom:updated>
            <content:encoded><![CDATA[<h4>Accelerating News Discovery for a Seamless User Experience</h4><p>Concepts like the laws governing icons and their seamless integration into daily life captivated my attention. The ubiquitousness of icons had never crossed my mind before. It was fascinating to see how seamlessly designers had integrated them into my daily life!</p><p>So, I decided to tackle a seemingly simple task: select a product and identify a 2 to 3 screen user flow to enhance the user experience.</p><p>Everyday apps became a goldmine of untapped possibilities. Choosing just one app proved to be a daunting quest as I explored countless digital realms and delved into user reviews. Narrowing down my focus was like finding a needle in a digital haystack!</p><figure><img alt="Person reading newspaper while drinking coffee. Plate of muffins and bagels in the background." src="https://cdn-images-1.medium.com/max/1024/1*B27ldd5g9FeSe-wvlhyEtQ.jpeg" /><figcaption>Image Credit: <a href="https://www.niemanlab.org/">https://www.niemanlab.org</a></figcaption></figure><p>After careful consideration, and many deadends, I selected the Financial Times (FT) app as my subject of exploration. Why FT, you might ask? Well, it boasts a diverse user base spanning different regions, age groups, languages, educational backgrounds, and professional fields. Plus, I read it daily. Surely that’ll give me an edge? Hah!</p><p>Join me as I uncover hidden gems of knowledge and weave together a narrative of transformation in the world UX design.</p><p>(For those who would rather not: I understand. Here is the link to the prototype designed after usability testing: <a href="https://www.figma.com/proto/Qddwy7Y2dk9gKe4fqmLj3J/Redesigning-FT-app-search---Changing-placement-of-search?page-id=0%3A1&amp;type=design&amp;node-id=23-102&amp;viewport=-279%2C574%2C0.85&amp;t=owGNKqkU9cosJsRg-1&amp;scaling=min-zoom&amp;starting-point-node-id=23%3A102&amp;mode=design"><strong>Prototype Link</strong></a>)</p><figure><img alt="News headlines with a search button in bottom navigation bar. This opens to input search bar." src="https://cdn-images-1.medium.com/max/900/0*IHilynhGzIYn7_8C" /><figcaption>Redesigned screen after usability testing</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*qf5blDehVIwR6qvFQHLrWQ.png" /><figcaption>Redesigned screen prior to usability testing</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCzZ7234QrP7Ss4kb-GEDw.png" /><figcaption>Collapsible search screen behind hamburger menu bar</figcaption></figure><p>In the following sections, I compare the original search design with the redesigned version and delve into the process that led me to this solution.</p><h4>Why the Financial Times app?</h4><p>The Financial Times (FT) app is a premier platform for real-time financial and business news. A key aspect of real time news is that users are able to find a specific topic easily. While the quality of news reporting is excellent, there is no easy way to navigate to the search button and quickly find a particular article. The current usability requires users to scan the page to find the search button, on not finding it, one has to recall and think about where it might be, open it and then tap again to the search input field. This is in contravention of the heuristic principle of <em>recognition rather than recall</em>. Other identified heuristic contraventions are detailed below.</p><h4>Why the search functionality?</h4><p>I chose “search” as the problem to solve because it has been a persistent challenge throughout the evolution of information organisation. From the early days of writing, humans have grappled with how to effectively organise and retrieve information without it getting lost in the stacks.</p><p>Even before the internet, search existed in the form of reference librarians who helped narrow down topics and assisted individuals in finding relevant information within vast collections. Considering this complex history and the evolving nature of search, I saw an opportunity to tackle the challenges such as information overload and user satisfaction and contribute to the ongoing improvement of search functionality in the digital age.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*D-OK1JyKKnVG0vca0HUMbQ.png" /><figcaption>Problems identified using Jakob Nielsen’s 10 usability heuristics for user interface design</figcaption></figure><p>This case study explores the benefits of integrating the search functionality into the bottom navigation bar, including its impact on user satisfaction, engagement metrics, and adherence to usability principles of the bottom navigation bar.</p><h4>Exploring ideas to accelerate news discovery</h4><p>I considered different options for adding an easily navigable search button to the Financial Times app:</p><ol><li>Top Persistent Search Bar: Placing the search bar at the top of the app screen so users to easily access it at all times. This presented a challenge in terms of screen space and potential interference with the app’s existing layout. It also didn’t align with the principle of leveraging the bottom navigation bar, which is commonly used for navigation purposes.</li><li>Bottom Navigation Bar Integration: This approach aligns with established UX principles and provides a consistent and intuitive navigation experience. By placing the search button alongside other primary navigation options, such as home, sections, and bookmarks, users can easily access search without the need for additional clicks or menu navigation.</li><li>Voice Search: Incorporating a voice search button prominently within the interface allows the users to initiate hands-free searches using voice commands, similar to virtual assistants like Siri or Google Assistant. However, this may unintentionally activate Siri or Google Assistant and the need for users to remember how to activate the voice search function. Furthermore, it may pose difficulties for individuals with speech impairments, potentially resulting in a non-inclusive design.</li><li>Gesture-Based Search: Implementing a swipe gesture from the edge of the screen to reveal a hidden search panel is another alternative. Users can swipe either from the left or right edge to bring up the search interface, allowing for quick access without obstructing the main content. However, it’s important to consider the user’s ability to remember the gesture and there is a risk of unintentional overlap the native swipe gesture of the device.</li><li>Floating Search Button: Introduce a floating search button that remains visible as users scroll through the app’s content for quick access to the search functionality regardless of the user’s position on the page. While this approach has its merits, it could also lead to visual clutter and potentially interfere with the overall user experience.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*rcLyVNVEgy_R7CQ4I9m8hA.png" /><figcaption>Exploring ideas in FigJam to accelerate news discovery</figcaption></figure><p>After careful consideration, I decided to pursue the integration of the search functionality into the bottom navigation bar.</p><h4>The Redesigned Search Experience:</h4><p>In the redesigned search experience, I incorporated the search button into the bottom navigation bar, ensuring its prominence and accessibility. Here are the key elements of the redesigned search flow:</p><ol><li>Search Icon Placement: The search icon is positioned as the second icon from the left in the bottom navigation bar. This placement ensures that it remains easily visible and accessible to users.</li><li>Search Input Field: When the user taps on the search icon, a search input field appears on the screen, enabling users to enter their search queries efficiently.</li></ol><p>By integrating the search functionality into the bottom navigation bar, the redesigned search experience offers improved accessibility. Placing the search button in the bottom navigation bar ensures its visibility and accessibility without cluttering the screen or requiring additional interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*CT2wvZ8XCfJDZwoN2BQXaw.png" /></figure><h4>Low fidelity prototyping</h4><p>Creating low-fidelity prototypes proved invaluable in the design process. These simple and rough representations enabled me to swiftly trial various ideas and iterate upon them with ease. The low-fidelity nature of the prototypes allowed for quick changes and modifications, providing a flexible environment for exploring different design solutions. This approach facilitated rapid experimentation, and I was able to gather valuable insights and make informed decisions for the final design.</p><p>The provided link leads to a handrawn, low-fidelity prototype of the redesigned search experience, showcasing the integration of the search functionality into the bottom navigation bar: <a href="https://marvelapp.com/791gci7">Prototype Link</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6vNyLWrhWURXXAbMdle_sQ.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fmarvelapp.com%2Fprototype%2F791gci7%3Femb%3D1%26&amp;display_name=MarvelApp&amp;url=https%3A%2F%2Fmarvelapp.com%2Fprototype%2F791gci7%2Fscreen%2F92148605&amp;image=https%3A%2F%2Fmarvel-live.freetls.fastly.net%2Fserve%2F2023%2F6%2F651ee507614a778881d1cfc28b955b.jpg%3Fquality%3D95%26fake%3D.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=marvelapp" width="1125" height="2460" frameborder="0" scrolling="no"><a href="https://medium.com/media/db5b5eb93986b2ff1db0cb85c915b03d/href">https://medium.com/media/db5b5eb93986b2ff1db0cb85c915b03d/href</a></iframe><h4>Usability Testing and Iteration:</h4><p>To validate the effectiveness of the redesigned search experience, I conducted usability testing with a group of representative users. The testing involved tasks such as searching for specific articles, refining search queries, and assessing the overall usability of the search functionality.</p><p>The recruitment method to find users in this case was based on a casual approach i.e. I stood outside the park near my home and asked passers-by if they would kindly indulge me and test out my app. Most did not, but two people did — a 3 generational family out on a walk. However, the participation of the elderly grandmother and her son provided valuable insights for evaluating the redesigned search experience. Noting that the users were not required to perform an actual search or enter any specific search queries during this test. The focus was solely on evaluating the process of navigating to the search bar, indicating the end of typing and triggering a search. These tasks were simply stated so both users indicated enthusiam in giving it a try.</p><p>The tasks set out were:</p><ol><li>Navigate to the search input field.</li><li>Imagine you have entered your desired search query.</li><li>Identify how you will indicate to the system that you are done typing and want to trigger a search.</li><li>Perform the action you believe will initiate the search.</li><li>Note your observations, including any challenges or difficulties you encounter.</li><li>Provide feedback on the effectiveness and intuitiveness of the search trigger mechanism.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_EwlDJ6kBiM6-3SpebAEhg.png" /><figcaption>User testing and observations</figcaption></figure><p>Based on the feedback and observations from the usability testing, I made iterative improvements to the design, refining the placement and appearance of the search button, optimising the search location, and enhancing the visibility and feedback of the search results.</p><p>The provided link leads to a high-fidelity prototype of the redesigned search experience, showcasing the integration of the search functionality into the bottom navigation bar: <a href="https://www.figma.com/proto/Qddwy7Y2dk9gKe4fqmLj3J/Redesigning-FT-app-search---Changing-placement-of-search?page-id=0%3A1&amp;type=design&amp;node-id=23-102&amp;viewport=26%2C903%2C1&amp;t=bm9KPtrZ3UNNh6eC-1&amp;scaling=min-zoom&amp;starting-point-node-id=23%3A102&amp;mode=design"><strong>Prototype link</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*2iIexnk9QhLlzndOGXRmww.png" /><figcaption>Redesigned Financial Times search</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*yILII-PuaYcvLnEoRAC8Iw.png" /><figcaption>Using FigJam to note changes made to the app</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FQddwy7Y2dk9gKe4fqmLj3J%2FRedesigning-FT-app-search---Changing-placement-of-search%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D23-102%26viewport%3D26%252C903%252C1%26t%3Dbm9KPtrZ3UNNh6eC-1%26scaling%3Dmin-zoom%26starting-point-node-id%3D23%253A102&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FQddwy7Y2dk9gKe4fqmLj3J%2FRedesigning-FT-app-search---Changing-placement-of-search%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D23-102%26viewport%3D26%252C903%252C1%26t%3Dbm9KPtrZ3UNNh6eC-1%26scaling%3Dmin-zoom%26starting-point-node-id%3D23%253A102&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fefa04cd0-26f2-4c36-bdd5-275b4ce7080b%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/2a4db1c374dad7625adc8f7b519b9520/href">https://medium.com/media/2a4db1c374dad7625adc8f7b519b9520/href</a></iframe><h4>Concluding thoughts:</h4><p>While this case study focused on the bottom navigation bar integration, further exploration could include:</p><ol><li>Search Overlay: which appears on pressing the search button would maintain the context of the current screen and allow users to perform their search without navigating away.</li><li>Predictive Search Results: As users type their search queries, real-time search results can displayed below the search input field. This immediate feedback helps users refine their search and find specific content quickly.</li></ol><p>These additions would enhance the contextual search experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d21fa33cc05a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>