<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>UNIPAWS</title>
        <link>https://paragraph.com/@unipaws</link>
        <description>undefined</description>
        <lastBuildDate>Sun, 05 Jul 2026 06:51:09 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>UNIPAWS</title>
            <url>https://storage.googleapis.com/papyrus_images/349bc8801ef77a8403b6c4b6ee871d5c.png</url>
            <link>https://paragraph.com/@unipaws</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Your users don't always know what they want ☝️]]></title>
            <link>https://paragraph.com/@unipaws/yoyour-users-dont-always-know-what-they-want-☝️</link>
            <guid>gaApjqXxQISi0hnFGdbT</guid>
            <pubDate>Sun, 31 Mar 2024 18:51:59 GMT</pubDate>
            <description><![CDATA[Despite the fact that they are beneficial, these traditional methods have limits. Here's why:1. Not mind readers: Picture yourself conversing with pe...]]></description>
            <content:encoded><![CDATA[<p>Despite the fact that they are beneficial, these traditional methods have limits. Here's why:<br><br><strong>1. Not mind readers:</strong> Picture yourself conversing with people in the 90s if you asked them if they would want "immediate access to global information in their pocket" (smartphone). They could say "no" not exactly knowing the opportunities.<br><br><strong>2. The "Shiny object" trap.</strong> The appeal of the latest technology trends can be so strong, but it is important to solve the user problem. Remember when 3D TVs were all the rage? While original, they were generally not good enough for most people to pay a lot of money or spend much time and effort on them.<br><br>Hence, the question arises how we can close the gap between what users state and they actually need.<br><br><strong>Here are some tips:</strong><br><br><span data-name="gem" class="emoji" data-type="emoji">💎</span> User session recordings. Imagine that you release a new fitness app with a fancy workout builder. User interviews praise the feature highly, but downloads of workout plans are still low. The recording might reveal the users getting stuck in the builder’s complexity, being irritated by unclear directions, or even being overloaded with customization options. This brings out a usability problem that the interview might have missed. <br><br><span data-name="gem" class="emoji" data-type="emoji">💎</span> Heatmaps. Visualize user behavior by detecting areas that get the most (and the least) exposure.<br><br><span data-name="gem" class="emoji" data-type="emoji">💎</span> Behavior-based questions. Inquire about particular actions that you've witnessed. Instead of generic questions, ask users who abandoned checkout: "We noticed you didn't finish your order, can you please tell us about your experience?"<br><br><span data-name="gem" class="emoji" data-type="emoji">💎</span> The five WHYs. Try asking "why" five times in a row until you reach the heart of a customer's problem. Consider the example of users from a food delivery app who claim that the "reorder" option is sluggish. Asking "why" five times could reveal: "Why is it so slow? As the loading of my previous orders takes too much time. Why? Because there are too many orders at the same time. Why? Because the app doesn't have any filtering options for past orders."<br><br><span data-name="gem" class="emoji" data-type="emoji">💎</span> Prototype sketching. Ask users to draw what their perfect solution would look like (just don't worry about it being perfect!). Let's say you are designing a new music streaming app. Users' initial sketches may show a user flow that would be more biased towards curated playlists than individual song selection, or reveal a preference for a more visual browsing experience based on album art or artist photos.<br><br>Ready to build a product that users will <span data-name="heart" class="emoji" data-type="emoji">❤</span>? Get in touch today:<br><br><span data-name="link" class="emoji" data-type="emoji">🔗</span> Telegram: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://t.me/sannheten">https://t.me/sannheten</a> <br><span data-name="link" class="emoji" data-type="emoji">🔗</span> WhatsApp: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://lnkd.in/dM9py5t8">https://lnkd.in/dM9py5t8</a> <br><span data-name="link" class="emoji" data-type="emoji">🔗</span> Dribbble: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://lnkd.in/diwgRu2q">https://lnkd.in/diwgRu2q</a><br><span data-name="link" class="emoji" data-type="emoji">🔗</span> LinkedIn: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.linkedin.com/company/unipaws-space/">https://www.linkedin.com/company/unipaws-space/</a></p>]]></content:encoded>
            <author>unipaws@newsletter.paragraph.com (UNIPAWS)</author>
            <category>user research</category>
            <category>uxui</category>
            <category>design</category>
            <category>product design</category>
            <category>design strategy</category>
            <enclosure url="https://storage.googleapis.com/papyrus_images/f2e0186418db4ff224aa4a17d9e7d158.jpg" length="0" type="image/jpg"/>
        </item>
    </channel>
</rss>