<?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 Tanmay Vatsa on Medium]]></title>
        <description><![CDATA[Stories by Tanmay Vatsa on Medium]]></description>
        <link>https://medium.com/@tanmayvatsa1507?source=rss-3831f8df186e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6kLTg-9yo6VtWpcy83imNg.jpeg</url>
            <title>Stories by Tanmay Vatsa on Medium</title>
            <link>https://medium.com/@tanmayvatsa1507?source=rss-3831f8df186e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:51:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tanmayvatsa1507/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[UX Design Whiteboarding Round:: How to get bonus points]]></title>
            <link>https://medium.com/@tanmayvatsa1507/ux-design-whiteboarding-round-how-to-get-bonus-points-e6f1899b950d?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6f1899b950d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[whiteboarding]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Sun, 04 Oct 2026 03:09:24 GMT</pubDate>
            <atom:updated>2026-10-04T03:29:18.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-XhXC0RjA9cPV37AR0e-eg.png" /></figure><p>There’s a very specific kind of fear only designers understand.</p><p>You’re in an interview, three people watching, with a blank whiteboard staring right back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*di8x3l6FbQ7crQOt.jpg" /></figure><p>Someone says:</p><blockquote><strong><em>“Alright, let’s say we’re building a product for…”</em></strong></blockquote><p>And before they even finish the sentence, your brain has already opened Figma.</p><p><strong>“Okay, maybe a card here. Bottom nav. Maybe AI. Maybe gamification. Maybe a progress bar.”</strong></p><p>I would say, Congratulations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*tsDogYCbDH6G4Clq.gif" /></figure><p><strong>You’ve just started solving a problem you don’t understand.</strong></p><p>In 5 years, I’ve been on both sides of these conversations, talked to my mentors, and I’ve realised something:</p><blockquote><strong>The strongest designers in whiteboarding rounds aren’t necessarily the ones who come up with the coolest solution. They’re the ones who are comfortable sitting in the messy, uncomfortable part of the problem for a little longer. They don’t rush to show that they can design. They show that they can think. And that’s a very different skill.</strong></blockquote><h3>The whiteboard is not asking for your UI</h3><p>This is probably the biggest mental shift you can make. When someone gives you a design problem, your first instinct should NOT be:</p><p><strong>“What should I build?”</strong></p><p>It should be:</p><p><strong>“Who the hell are we building this for, and why the hell should I solve this?”</strong></p><p>Let’s say I tell you:</p><blockquote><em>“Design a better experience for people waiting at airports.”</em></blockquote><p>Cool.</p><p>Your brain might immediately go:</p><p>Airport app, Live flight tracker, Entertainment, Food ordering, Notifications, Lounge booking, and whatnot; maybe gamification, some futuristic AI assistant that somehow knows your emotional state because apparently that’s what every product needs now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/215/0*RPhRbFtQpvgRyT63.gif" /></figure><p>But wait.</p><p><strong>Who is waiting at the airport?</strong></p><p>A business traveller? A family with two kids? Someone flying for the first time? Someone with a six-hour layover? Someone who’s already late? Someone who just wants coffee? Someone whose flight is delayed? Someone travelling internationally? Someone who has mobility issues?</p><p><strong>You see the problem???????</strong></p><p>“Airport passengers” isn’t really a user.</p><p>It’s a massive bucket containing people with completely different behaviours.</p><p>So instead of immediately picking a person and declaring:</p><blockquote><em>“My user is a 27-year-old urban professional…”</em></blockquote><p>Please don’t. You’re not writing a dating profile. Reset your mind and think in <strong>cohorts.</strong></p><p>A cohort could be:</p><blockquote><em>“People with a 2–4 hour layover who don’t want to leave the airport.”</em></blockquote><p>Now we have something, and we can ask:</p><ul><li><strong>What do they currently do?</strong></li><li><strong>How do they spend that time?</strong></li><li><strong>What frustrates them?</strong></li><li><strong>What are they trying to accomplish?</strong></li><li><strong>What do they already use?</strong></li><li><strong>What habits already exist?</strong></li></ul><p>And voilaaa we’re solving an actual problem.</p><h3>A design manager working at Google taught me this: Don’t marry the first idea you have</h3><p>One of the easiest ways to identify an inexperienced designer in a whiteboarding round is how quickly they fall in love with their first idea.</p><p>They get an idea. They draw it. Then they spend the next 20 minutes defending it. Even when the conversation starts telling them it’s probably not the right direction.</p><p>Don’t do that. Let your brain go absolutely nuts in the beginning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*xl76X7HQDIcPX82Y.png" /></figure><p>Think of everything: Physical, digital, human, service, behavioural, environmental, automation, community, whatever.</p><p><strong>Let the horse run.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*bGFlRTXs-9Gc8CdT.gif" /></figure><p>But don’t let it run forever. Once you’ve explored enough possibilities, start pulling it back.</p><p>And one of the best ways I’ve found to do that is ridiculously simple:</p><h3>Ask yourself: What do people already do?</h3><p>Because users don’t wake up every morning hoping a product designer will give them a new behaviour.</p><ul><li>They already have habits.</li><li>They already have shortcuts.</li><li>They already have routines.</li><li>They already have weird little hacks.</li><li>They already use WhatsApp for things WhatsApp was never supposed to do.</li><li>They already take screenshots instead of bookmarking things.</li><li>They already send themselves messages.</li><li>They already put things in carts and forget about them.</li><li>They already check Instagram while waiting for their food.</li><li>They already Google symptoms at 2 AM and convince themselves they have three rare diseases.</li></ul><p><strong>Behaviour is your goldmine.</strong></p><p>Instead of asking:</p><blockquote><strong><em>“What cool feature can I add?”</em></strong></blockquote><p>Ask:</p><blockquote><strong><em>“What is this person already doing that we can make easier?”</em></strong></blockquote><p>That question will save you from inventing a lot of unnecessary shit.</p><h3>Before you solve it, interrogate it</h3><p>The problem statement you’re given isn’t always the complete problem.</p><p>Sometimes it’s deliberately vague; sometimes the interviewer is testing whether you’ll notice.</p><p>So ASKKKKKKKKK as many questions as you can!!!! In design terms, we call it “Understanding the problem”. And don’t ever be scared of asking questions.</p><p>Things like:</p><blockquote><em>“Is this something users are currently struggling with, or is this a hypothetical problem?”</em></blockquote><p>That’s a great question.</p><p>Because the way you solve a validated problem is very different from how you explore a hypothetical one.</p><p>Then:</p><blockquote><em>Are there any constraints I should know about?</em></blockquote><blockquote><em>Is there anything specific that could block a potential solution?</em></blockquote><blockquote><em>Are we restricted to a digital solution?</em></blockquote><blockquote><em>Can I think about this as a physical or service problem too?</em></blockquote><p><strong>These questions aren’t slowing you down. They’re actually giving you the map before you start driving.</strong></p><p>Consider you are going to a new place and these questions are Google Maps for you, they will give you a path to reach that place, so be as specific you can. And trust me, <strong>you’d rather spend three minutes understanding the road than spend twenty minutes designing a beautiful road to the wrong destination.</strong></p><h3>Make the interviewers your users (or atleast try doing it)</h3><p>This is probably one of my favourite things to do.</p><p>If there are three people sitting across from you, don’t treat them like three people waiting to judge your solution.</p><p><strong>Use them. Literally. Say:</strong></p><blockquote><em>“I’m going to make you guys my users for a minute.”</em></blockquote><p>Once they agree, even if one of them agrees, ask them questions, make sure the other two folks get the fear of missing out, and make them interested in your conversation with the one who accepted being your user:</p><blockquote>Ask about this users habit, try to fit them into a type of user cohor</blockquote><p>Suddenly the room changes; you are no longer giving a presentation; instead, you are having a conversation.</p><p>And that’s exactly what good product design should feel like.</p><p><strong>Effective Contribution and Engagement!</strong></p><p>That’s much more interesting than you standing in front of a whiteboard talking at them for 30 minutes.</p><h3>And when they talk, actually listen</h3><p>You ask the interviewer a question, and while they’re answering, your brain is already preparing your next sentence. <strong>Don’t.</strong></p><p>Firsttttttt my friend, Listen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*-RLjvJcWShP9JAhM.gif" /></figure><p>Because sometimes they’ll give you something incredibly valuable.</p><p>Maybe they’ll say:</p><blockquote><em>“Actually, users don’t have access to that information.”</em></blockquote><p>Maybe:</p><blockquote><em>“We tried something similar before.”</em></blockquote><p>Write it down.</p><p>Maybe:</p><blockquote><em>“Our biggest constraint is engineering bandwidth.”</em></blockquote><p>Write it down.</p><p>Write it down on the board. Show them you are actually listening to what they are suggesting, don’t just say, “yeah yeah noted.”</p><p>And now, this tiny thing can give you a huge advantage:</p><h3>Write their points on the board.</h3><p>Don’t just nod.</p><p>Don’t say:</p><blockquote><em>“Yeah, makes sense.”</em></blockquote><p>Physically write it, circle it, put a star next to it.</p><p>Because something changes when they see their own point sitting on the board. It tells them:</p><p><strong>“I heard you.”</strong></p><p>And more importantly:</p><p><strong>“Your input is changing how I’m thinking.”</strong></p><p>People actually love that, as nobody wants to feel like they’re sitting there for 30 minutes just to watch you execute a pre-written TED Talk.</p><p>Bring them into the process.</p><h3>Your whiteboard should look a little chaotic, scribbles, cross marks, and what not!</h3><p>Please don’t try to make your whiteboard look like a Behance case study.</p><p>This isn’t the time for perfect spacing. Your board should show your brain working.</p><p>Write:</p><ul><li><strong>USER COHORT</strong></li><li><strong>WHAT THEY DO TODAY</strong></li><li><strong>PAIN</strong></li><li><strong>CONSTRAINTS</strong></li><li><strong>ASSUMPTIONS</strong></li><li><strong>IDEAS</strong></li></ul><p>Then scribble, cross things out, circle something, maybe draw an arrow, change your mind.</p><p>Actually, that’s good, because the interviewer isn’t only looking at the final answer; instead, they are watching:</p><p><strong>How did you get there?</strong></p><p>If you erase every thought that didn’t work, they only see the final destination. If you leave some of the thinking visible, they can see the journey.</p><p><strong>And that’s the actual interview.</strong></p><h3>Don’t make the panel a validation machine</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*8Bm6MQYxO1MBklOM.jpg" /></figure><p>There’s another trap I’ve seen designers fall into. I mean yes, I was one of those designers.</p><p>Every few minutes, I rewired my brain and seeking an answer from the panel (because someone said, keep the whiteboarding round interactive):</p><ul><li><strong><em>Does this make sense?</em></strong></li><li><strong><em>Do you think this is a good direction?”</em></strong></li><li><strong><em>Should I go with this?</em></strong></li><li><strong><em>Is this what you were expecting? bla bla bla….</em></strong></li></ul><p>NOOOOOO!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8qRR-2pso9JsYsUF.jpg" /></figure><p>Please stop asking the panel to approve every thought you have.❌</p><p>You’re not looking for validation; you’re looking for information. There’s a huge difference.</p><p><strong>Instead of:</strong></p><blockquote><em>“Is this a good solution?”</em></blockquote><p><strong>Say:</strong></p><blockquote><em>“I’m considering two directions here. One optimises for speed, while the other optimises for flexibility. I’m leaning towards the first because of reason X.”</em></blockquote><p>While reading this, did you feel confident? That’s the same thing your interviewer experiences too. You’re not asking them to make the decision for you; instead, you started showing them how <strong>you</strong> make decisions.</p><p>You ROCK here!!!</p><h3>But but but, what if they give you the solution while you are still explaining yours?</h3><p>This happens most of the time. You’re explaining your thinking and one interviewer goes:</p><blockquote><strong><em>“What if we just…?”</em></strong></blockquote><p>And suddenly your ego enters the room before you do.</p><p><strong>“But that’s literally not what I was thinking.”</strong></p><p>Who cares? This isn’t Shark Tank, my friend, and you’re not protecting your intellectual property.</p><p>Listen to what they said. Shut your mouth for a moment, activate your brain, open your ears wide, and LISTENNNNNNN!!!!</p><p>Once you listen to each word they said, pause for 5 seconds, look around the room, and say:</p><blockquote><em>“That’s interesting. I think we could incorporate that into this direction/that actually makes sense, because…”</em></blockquote><p>And then actually do it; find out the bridge that will stitch their solution and yours. If you don’t think it will be a good solution, tell them in a way which takes the panel back to thinking mode.</p><p><strong>For example, That’s an interesting take you just explained, John; let’s analyse both solutions if it is scalable across situations. Banggg! What did it do?? It sent your panel to help you out, proving that the solution they told you actually works!</strong></p><p>In a moment, this tells the panel something really important:</p><p><strong>You can collaborate.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*X54bMt1dyR1D22QR.gif" /></figure><p>You didn’t treat feedback as an attack on your intelligence, instead, you took someone else’s thought, improved it, combined it with your own thinking, and went forward.</p><p><strong>That’s what working on a real product looks like</strong>.</p><h3>Next important thing: Try to cover the whole room</h3><p>If there are two to four people in the interview, don’t spend 30 minutes looking at the one person who asked the question.</p><p>Talk to everyone, make eye contact, ask different people for perspectives.</p><p>If someone hasn’t spoken, ask them:</p><blockquote><em>“I’d love to hear your take on this as well.”</em></blockquote><p>If someone gave you a constraint earlier:</p><blockquote><em>“Coming back to the point you mentioned earlier…”</em></blockquote><p>Now you’re connecting the dots, you’re showing that you’re not just performing, you’re <strong>facilitating a conversation, </strong>and honestly, that’s a pretty strong signal for a designer.</p><blockquote><strong>Because in a real product team, you will constantly be dealing with different opinions: Product wants one thing, engineering says no, business wants another thing, research says users behave differently, marketing has another opinion, and somewhere in the middle, there’s you with a Figma file open at 2 AM.</strong></blockquote><h3>Post figuring out the persona: Do the “habits” test</h3><p>Pulling Double Diamond here and now it’s time to converge your ideas. When you’ve gone wide enough, start getting specific.</p><p>This is where I like to ask:</p><blockquote><strong><em>“What does this person already do in their day?”</em></strong></blockquote><p>Because sometimes the solution is hiding inside an existing habit.</p><p><strong>Imagine you’re asked to design a product that helps people remember important tasks.</strong></p><p>Don’t immediately create:</p><p><strong>Task app → reminders → streaks → badges → leaderboard → AI assistant</strong></p><p>The panel doesn’t need Duolingo for remembering to call the dentist.</p><p>Instead ask yourself:</p><ul><li>What does the person already do?</li><li>Maybe they check their phone when they wake up.</li><li>Maybe they have a morning coffee.</li><li>Maybe they open WhatsApp after work.</li><li>Maybe they check their calendar before leaving home.</li><li>Maybe they have a bedtime routine.</li><li>Could the experience fit naturally into one of those moments?</li></ul><p>Once you ask all these questions, that’s called <strong>good product thinking!</strong></p><h3>The last five minutes are free mentorship. Take it.</h3><p>You’ve reached the end, you explained your solution and have maybe five minutes left.</p><p>The classic candidate response:</p><blockquote><strong><em>“No, I don’t have any questions.”</em></strong></blockquote><p>Why? You literally have experienced people sitting in front of you. Ask them something.</p><p><strong>But don’t ask:</strong></p><blockquote><strong><em>“Was my solution good?” (Again the validation seeker mindset)</em></strong></blockquote><p>Ask:</p><blockquote><strong><em>“If you had five minutes, could you walk me through how you would’ve approached this problem? I’m asking because if I go back and iterate on this later, I’d love to have your perspective in mind.”</em></strong></blockquote><p>Now, that’s a completely different conversation, you’re learning how they think. It shows that you’re curious enough to want to learn even after you’ve finished being evaluated.</p><h3>And lastly, my friend, the real whiteboarding flex</h3><p>The biggest misconception about whiteboarding rounds is that you need to walk in with a giant brain and walk out with a giant solution.</p><p>You don’t.</p><p>The real flex instead is being able to sit with ambiguity without desperately trying to kill it with a UI.</p><h3>So next time someone says “Design this…”</h3><p><strong>Don’t reach for the marker immediately.</strong></p><p>I know the instinct. You hear the problem statement, there’s a blank whiteboard staring at you, and suddenly your brain starts screaming, <em>“I need to show them something.” </em><strong>Resist it.</strong></p><p>Here’s a checklist for you:</p><ul><li><strong>Take a deep breath.</strong></li><li><strong>Read the problem properly.</strong></li><li><strong>Then look at the people sitting across from you and start a conversation.</strong></li><li><strong>Ask questions.</strong></li><li><strong>Understand how they’re interpreting the problem.</strong></li><li><strong>If it makes sense for the exercise, treat them as your users and use their answers to shape the direction.</strong></li><li><strong>Listen carefully, and write down the points they give you. There’s something powerful about putting their thoughts on the board in front of them; it turns the interview from a one-way presentation into a conversation.</strong></li><li><strong>Once you’ve understood the problem, give yourself permission to think wildly for a few minutes.</strong></li><li><strong>Explore the obvious ideas, the ridiculous ones, and everything in between. Then slowly bring yourself back to reality.</strong></li><li><strong>Start looking at human behaviour. What are people doing today? What habits have they already built? What constraints exist? Is this actually a problem worth solving? And, perhaps most importantly, does this problem even need a digital solution?</strong></li><li><strong>Only then start drawing.</strong></li></ul><p>And there’s one question that can give you a surprisingly good bonus point:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*sLhd-kDhccRuD8-S" /></figure><p><strong>“Does this actually need to be an app?”</strong></p><p>Maybe the answer is a physical product, a service, a change in an existing process, or technology isn’t the answer at all. You’re not being asked to prove that you can design an app.</p><p><strong>You’re being asked to prove that you can solve a problem.</strong></p><p>That distinction can completely change the way you approach the round.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*TmbyyMDrk20_6jZG.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6f1899b950d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Abstract Laddering in UX: Uncover the “Why” behind user choices]]></title>
            <link>https://medium.com/@tanmayvatsa1507/abstract-laddering-in-ux-uncover-the-why-behind-user-choices-9cc04fd352f4?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cc04fd352f4</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Thu, 23 Jul 2026 03:04:38 GMT</pubDate>
            <atom:updated>2026-07-23T03:04:38.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCHZ9QLqKAOw_qBZop5vqQ.png" /></figure><blockquote><strong>Imagine you ask someone why they bought a particular pair of running shoes.</strong></blockquote><p>They say, “because they’re lightweight.”</p><p>That answer feels complete. What if I say, It isn’t? 😩</p><p><strong>It’s just the first step on a ladder, and most of us stop climbing right there, satisfied with an answer that barely scratches the surface of what a person actually wants.</strong></p><p>Abstract laddering is the practice of climbing that ladder anyway. It is one of the most underrated tools in a designer’s kit, not because it’s complicated, but because it’s almost embarrassingly simple, and simplicity is often mistaken for unimportance.</p><h3>What laddering actually means</h3><p>At its heart, laddering is a conversation technique. You take a surface level answer someone gives you, and you keep asking a gentle, curious “why does that matter to you” until you stop hearing about features and start hearing about feelings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*C6aE_R0gijYlgBfn.jpeg" /></figure><p>It usually moves through three levels, like rungs on a ladder:</p><p><strong>1. Attributes</strong> (the concrete, physical thing) “These shoes are lightweight.”</p><p><strong>2. Consequences</strong> (what that attribute actually does for the person) “So I don’t get tired quickly, and I can run longer.”</p><p><strong>3. Values</strong> (the deep, emotional reason underneath it all) “Running longer makes me feel like I’m in control of my body, and that matters to me because I want to feel capable as I get older.”</p><blockquote><strong>Notice what happened there. Nobody set out to talk about aging or self-worth. They started by talking about shoe weight. But a few honest “why” questions later, you’ve arrived somewhere far more human, and far more useful for anyone designing a product around that person.</strong></blockquote><p>This method has its roots in something called Means-End Theory, first proposed by the psychologist Jonathan Gutman in the early 1980s, and later refined into a practical research technique by Gutman together with Thomas Reynolds.</p><p>The theory rests on a simple belief: <strong>people don’t buy products for the products themselves; they buy them for what those products let them become or feel. A shoe is never really about the shoe.</strong> The idea itself borrows from an even older piece of psychology, George Kelly’s Personal Construct Theory from the 1950s, which argued that <strong>people understand the world through personal, layered meanings rather than flat facts.</strong></p><h3>Why designers should care about this at all</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*JT_oMxKBW67ARyPg.gif" /></figure><p>Here is the uncomfortable truth about most user research:</p><blockquote>If you only ask people what they want, they will tell you about features. More filters, a faster checkout button, a bigger search bar.</blockquote><p>Taken at face value, these answers lead to endless feature requests and cluttered products that still somehow leave people unsatisfied.</p><p><strong>Laddering exists because features are never the real destination; they’re just the doorway.</strong></p><p>Behind almost every feature request sits a value the person is trying to protect or express, things like safety, belonging, control, freedom, or being seen as capable. <strong>This idea also echoes Maslow’s hierarchy of needs, where the things people say they want (a faster app, a cheaper plan) are usually sitting on top of much older, deeper needs like security, esteem, or connection. 😌</strong></p><p>When a designer understands the value underneath a request, they stop building exactly what was asked for, and start building what was actually needed, which are often two very different things.</p><h3>A gentle everyday example</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/0*XAhvUaDpTtg8maqx.png" /></figure><p>Let’s use something almost everyone has experienced: S<strong>etting a reminder on your phone.</strong></p><p>If you ask someone <strong>why they use reminders</strong>, they might say, “so I don’t forget things.” That’s the attribute level, plain and functional.</p><p>Ask again, gently, <strong>“why does forgetting things bother you so much?”</strong> and you might hear, “because when I forget something important, I feel like I’m letting people down.”</p><p>Ask once more, <strong>“why does that matter to you?”</strong> and you may finally arrive at something like, “because I want to be seen as someone people can rely on.”</p><p>Look at the distance we just traveled. We started at a to-do list feature and ended up at a person’s need to be trusted and dependable.</p><ul><li>A designer who only heard the first answer might just build a louder notification.</li><li>A designer who climbed the whole ladder might design something that quietly celebrates consistency, streaks, gentle encouragement, a sense of being on top of things, because that’s the actual emotional payoff being chased.</li></ul><h3>Real products that were probably built on a ladder like this</h3><p>The best way to trust this method is to see it already working quietly in products you use every day.</p><p><strong>Duolingo’s streak counter</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*sDBpiU4C4gHnOhfo.png" /></figure><p>On the surface, someone might say they like Duolingo because “it reminds me to practice daily.”</p><p>Climb one rung and you get, “so I don’t lose progress I’ve already made.” Climb once more and you often land on something like, “I want proof that I’m becoming a person who follows through on things.” The streak isn’t really about language learning at all, it’s about identity and self-trust, and that’s exactly why losing a long streak feels so disproportionately painful.</p><p><strong>Notion</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dMCji67DZRAfy88B.png" /></figure><p><strong>The attribute is</strong> “it lets me organize everything in one place.”</p><p><strong>The consequence is</strong> “so I’m not scrambling to find things or missing deadlines.”</p><p><strong>The value</strong>, for many people, is “I want to feel like my life is under control, even when everything around me feels chaotic.”</p><p>A cluttered, over featured tool fails not because it lacks functions, but because it fails that deeper need for a sense of calm and order.</p><p><strong>Swiggy</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8Tb6wGY0T-CNBsMW.jpg" /></figure><p><strong>The attribute is</strong> “it gets food to my door quickly.”</p><p><strong>The consequence is</strong> “so I don’t have to cook or step out when I’m exhausted.”</p><p><strong>Climb one more rung and you often land on</strong>, “I want to feel a little taken care of, even on the days I have nobody around to do that for me.”</p><blockquote>Swiggy isn’t really competing on delivery speed alone, it’s quietly competing on that feeling of relief, the sense that one thing in a hard day just got easier.</blockquote><p><strong>Airbnb</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rvNBOQBYJDWcC6w6.jpg" /></figure><p><strong>The attribute is</strong> “it lets me book a home instead of a hotel room.”</p><p><strong>The consequence is</strong> “so I get to actually live in a place for a few days instead of just visiting it.”</p><p><strong>The value underneath</strong>, and Airbnb has built its entire brand around this, is “I want to feel like I belong somewhere, even if it’s only for a weekend.”</p><blockquote>That’s why their long-standing mission line was literally “belong anywhere,” a value statement pulled straight from the top of a ladder like this one.</blockquote><p><strong>District</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*xoCbUZImXCdR8ZHz" /></figure><p><strong>The attribute is</strong> “it shows me events, restaurants, and things happening near me.”</p><p><strong>The consequence is</strong> “so I always have something to look forward to instead of just staying in.”</p><p><strong>The value, for a lot of people, is</strong> “I want to feel like I’m actually living my life fully, not letting it pass by.”</p><blockquote>A discovery app like this succeeds not because its listings are exhaustive, but because it turns a quiet Tuesday into a night worth remembering, and that feeling is the real product being sold.</blockquote><p>In every one of these cases, the feature is just the visible tip.</p><p><strong>Laddering is the method that lets a designer see the much larger shape sitting quietly underneath the water.</strong></p><h3>How to actually do this in a real conversation</h3><p>If AI can help me understand this whole thing, why not use it to explain it to you also? So I created an image which explains this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UvrMnm2-SvDSvy3pxiZOJA.png" /></figure><p>Laddering works best when it feels like a natural, unhurried conversation, not an interrogation. A few honest principles help:</p><p><strong>Ask “why” like you’re genuinely curious, not like you’re testing someone.</strong></p><p>The moment it feels like a quiz, people retreat into safe, surface-level answers. The tone should feel more like a friend leaning in, not a researcher with a clipboard.</p><p><strong>Let silence do some of the work.</strong></p><p>After asking why something matters, resist the urge to fill the pause. People often need a few quiet seconds to find the real answer; the first thing they say is rarely the deepest thing they feel.</p><p><strong>Follow the emotion, not the logic.</strong></p><p>If someone’s voice softens, or they pause, or they say something that sounds slightly more personal than before, that’s usually the ladder starting to reveal something real. Lean into that moment rather than moving past it.</p><p><strong>Know when to stop climbing.</strong></p><p>You don’t need to turn every conversation into a therapy session. Once you reach a value like security, freedom, belonging, pride, or control, you’ve usually arrived somewhere solid enough to design around.</p><h3>Why this beats simply asking “WHAT DO YOU WANT”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*908LHUFpbsR4XRw3" /></figure><p>If you ask someone what they want directly, you get a wishlist.</p><p>Wishlists are honest, but they’re shallow, because people are naturally better at describing symptoms than causes.</p><p>They know a feature would help; they often don’t consciously know why it would help, because the actual reason lives at an emotional level most people don’t examine daily.</p><p><strong>Laddering respects that gap.</strong></p><p>It assumes people are telling the truth at every level: they really do want lightweight shoes, they really do want reminders, but it also assumes that <strong>truth has layers, and that the most useful layer for design decisions is usually the one people didn’t think to mention first.</strong></p><h3>The quiet elegance of this method</h3><p>What makes abstract laddering beautiful, and it genuinely is beautiful in a strange way, is that it doesn’t require expensive tools, complicated software, or clever tricks.</p><p>It requires patience and a willingness to keep asking one more question when it would be easier to stop.</p><p>Good design, at its core, is an act of empathy translated into pixels and interactions.</p><blockquote><strong>Laddering is simply a structured way of practicing that empathy honestly, climbing past the obvious, past the surface, until you reach the part of a person that features alone can never fully speak to.</strong></blockquote><p>Every product we love, the ones that feel like they truly understand us, was probably built by someone who climbed a ladder like this at some point, whether they called it that or not. They asked WHYYYYYYYYYYYYYY, and then they asked WHYYYY again, until an ordinary answer turned into an honest one.</p><p>That, in the end, is the whole craft.</p><p><strong>Not building what people say they want, but understanding, gently and patiently, what they actually mean.☺️</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/0*zOfvIdKOT0kYlkK3.gif" /><figcaption>Thanks, that’s the end of this article!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cc04fd352f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Affordance in Design? Even I learnt it the hard way]]></title>
            <link>https://medium.com/@tanmayvatsa1507/what-is-affordance-in-design-even-i-learnt-it-the-hard-way-cb78cba4d71a?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb78cba4d71a</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Mon, 20 Jul 2026 03:08:16 GMT</pubDate>
            <atom:updated>2026-07-20T03:08:16.349Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*QW1tPiTcWcO07JS2Qm9pWg.png" /><figcaption>The universal problem and a simple solution</figcaption></figure><p>Okay, so picture this. You open an app, you don’t read a manual, nobody explains anything to you, and yet somehow your thumb just <em>knows</em> where to tap. That little bit of magic? That’s <strong>AFFORDANCE</strong>.</p><p>And no, it’s not some fancy design school word meant to confuse you at a job interview. It’s literally the reason your parents can order food on <a href="https://medium.com/u/ef2c5a9dfd53">Zomato</a> without a tutorial.</p><p>Let’s break this down properly:</p><h3>What actually is Affordance?</h3><p>Affordance is a design term that basically means: <strong>an object’s design tells you what you can do with it, without anyone having to explain it.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tOwCE7CKXhEl095R.jpg" /></figure><p>The term was coined by psychologist <strong>James J. Gibson</strong> back in the 1970s and later brought into design/UX by <a href="https://medium.com/u/1808934e1fd3">Don Norman</a> <strong>in his book “The Design of Everyday Things.”</strong> Norman’s whole point was that good design doesn’t need instructions. If you need a sign that says “push” on a door, the door already failed at its job. The handle should’ve told you that itself.</p><p>In UX, affordance is the same idea but on your screen.</p><ul><li>A button should look tappable,</li><li>A slider should look draggable,</li><li>A toggle should look flippable</li></ul><p>If your users are confused about what to click, the platform you just designed has an affordance problem, not a “users are dumb” problem.</p><p>There’s a simple formula to remember:</p><blockquote><strong><em>Good Affordance = the design whispers “tap me here” without saying a single word.</em></strong></blockquote><h3>There are three types of affordance every designer should know</h3><ol><li><strong>Real (Physical) Affordance</strong></li></ol><p>This is the actual, literal thing an object can do. A button can be pressed. A phone screen can be swiped. This exists whether or not you notice it.</p><p><strong>2. Perceived Affordance</strong></p><p>This is what YOU think you can do based on how something looks. This is the real MVP in digital design because in an app, there’s no “real” affordance; it’s all screen and pixels, so everything is perceived. If a button doesn’t look pressable, your brain won’t even try.</p><p><strong>3. False Affordance</strong></p><p>This is when something LOOKS interactive but isn’t (or vice versa), and it lowkey ruins the whole experience. Like a text that’s underlined and blue but isn’t actually a link- I mean, “Straight up rage bait for your users”</p><h3>Let’s talk examples using applications every Indian has on their phone right now:</h3><p>This is where it gets fun because even I didn’t understand it without taking reference from well-built platforms. Let’s break down affordance using apps you probably used in the last hour.</p><h3>Swiggy and Zomato: the “Swipe to Reorder” magic</h3><p>Ever noticed how on Swiggy, a re-order CTA sits at the bottom right corner? As soon as you click it, there’s the whole list of items ordered earlier and an “Add CTA”.</p><p>That subtle interaction and entry point is the app whispering “Hey, I’m interactive; go on, try me out; I will make your life easy.”</p><p>That’s textbook perceived affordance. No tooltip needed, your thumb just does it instinctively because the design cued you.</p><h3>PhonePe and Google Pay: the UPI PIN keypad</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*wDLrhnrY2RyBtDTD" /></figure><p>The number pad that pops up when you’re entering your UPI PIN has raised looking buttons, subtle shadows, and satisfying little press animations (that tiny bounce when you tap a digit).</p><p>This mimics a real physical keypad. Your brain has years of experience pressing physical buttons, so this design borrows that muscle memory.</p><p><strong>That’s affordance working with your past experiences, not against them.</strong></p><h3>CRED: the “Premium yet Mysterious” Affordance Flex</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jy6FKsMxfCtzn9kB.png" /></figure><p>CRED is honestly a case study on its own. Their buttons have this soft, almost 3D, claymorphic look that just screams “tap me, I’m satisfying.”</p><p>Even their scratch cards use a texture that visually says “scratch this,” borrowing directly from real-world lottery tickets.</p><blockquote><strong>That’s affordance transferring from real life objects straight into a digital interface, and it works because your brain already has a mental model for how scratch cards behave.</strong></blockquote><h3>Ola, Rapido, and Uber: The Draggable Bottom Sheet</h3><p>That bottom sheet when you’re booking a cab and of course 40 drivers didn’t accept your cab request? Nobody told you it’s draggable.</p><p>But you just did it while waiting, as it looks like a handle to drag the bottom sheet up and down.</p><p>This tiny grey pill on top of the bottom sheet is doing so much heavy lifting in terms of perceived affordance.</p><p>Imagine these applications remove the scroll the bottom sheet up option, and suddenly people will be stuck, confused why the map isn’t fully visible.</p><h3>Bookmyshow or District: Seat Selection screen</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u1JxUK_RL_oPJWGf" /></figure><p>When you’re picking movie seats, <strong>available seats are a different color, sold-out seats are greyed out and non-clickable, and your selected seats glow in a highlighted color.</strong></p><p>This is a masterclass in affordance layering; colors instantly communicate what’s tappable, what’s not, and what’s already chosen.</p><blockquote><strong>Nobody reads a legend to figure this out, the color coding itself is the instruction manual.</strong></blockquote><h3>Flipkart and Myntra: the “add to cart” vs “buy now” hierarchy</h3><blockquote>Yeah, I haven’t added images here as I want you to go and check these applications out and find out everything I have mentioned in this article.</blockquote><p>Notice how “Add to Bag” is usually bold and solid colored, while “Buy Now” often looks more outlined or secondary?</p><p>You will have a question in mind: why Buy Now is not highlighted, my primary intention is to buy a cloth. The reason: Myntra wants you to add as many clothes as you want to the bag and then order them in bulk!</p><p>That visual weight difference is <strong>intentional affordance design</strong>; it’s nudging you (gently, or not so gently) toward the primary action while still making the secondary action clearly clickable.</p><p>This is affordance combined with visual hierarchy, and it’s basically silent persuasion.</p><h3>WhatsApp: the mic icon that turns into a send arrow</h3><blockquote>Check it yourself while you are reading this section</blockquote><p>This one’s iconic. As soon as you click on the mic, the icon smoothly morphs into a paper plane send icon.</p><p>This transformation itself is an affordance signal; it’s telling you “the action available here has changed; now you can send text instead of recording voice.”</p><h3>Blinkit: The pulsing “ADD” button</h3><blockquote><strong>Are you checking the Blinkit app now?</strong></blockquote><p>That little plus button that sometimes has a subtle pulse or bounce animation when a product’s price drops or it’s trending? That micro animation is affordance on steroids; it’s not just saying “you can tap this”; it’s saying “you should probably tap this right now.”</p><p><strong>Movement draws the eye and signals interactivity even faster than static color does.</strong></p><h3>Why is Affordance basically the backbone of good UX</h3><p>Here’s the tea. Users don’t read your app; they scan it. Nobody’s sitting there analyzing your interface like a school textbook.</p><p>People move fast, thumbs on autopilot, brains running on vibes and pattern recognition.</p><p>If your design doesn’t afford the right actions clearly, users either:</p><ul><li>Freeze up, not knowing what to do next (rage quit incoming)</li><li>Tap the wrong thing entirely (hello, accidental orders and refund requests)</li><li>Straight up, assume the feature doesn’t exist because it wasn’t “visible enough”</li></ul><p>Bad affordance literally costs companies money: drop-offs, uninstalls, one-star reviews saying “confusing app, don’t understand how to use it.” Good affordance means less user frustration, fewer support tickets, and honestly, just a smoother vibe overall.</p><h3>Signals that create a strong affordance (the toolkit)</h3><p>If you’re a designer reading this and thinking “okay, how do I actually DO this,” here’s your cheat sheet:</p><ul><li><strong>Shadows and elevation</strong>: things that pop off the screen feel touchable</li><li><strong>Color contrast</strong>: bright, vibrant colors on buttons say “click me &quot;; greyed-out, muted colors say “not right now”</li><li><strong>Shape consistency</strong>: rounded pill shapes across an app consistently mean “button,” so keep it consistent</li><li><strong>Icons with familiar meaning</strong>: a trash can icon universally means delete, don’t reinvent this wheel</li><li><strong>Motion and microinteractions</strong>: subtle animations on tap or hover confirm “yes, this did something”</li><li><strong>Typography weight</strong>: bold text draws attention as an action, thin text reads as passive information</li><li><strong>Spacing and grouping</strong>: related actions grouped together, unrelated ones kept apart</li></ul><h3>The Golden Rule to remember</h3><p>If a user has to pause, squint, or ask <strong>“wait, can I click this?”</strong> your affordance already failed.</p><p>The best UX doesn’t explain itself; it just makes sense the moment your eyes land on it.</p><p>So next time you’re scrolling Instagram, ordering food on <a href="https://medium.com/u/40d7b7280b39">Swiggy India</a>, or paying rent through <a href="https://medium.com/u/2ec3d856de9a">The PhonePe Team</a>, pause for a second and notice how many tiny visual cues are silently guiding your thumb without you even realizing it.</p><blockquote><strong>That’s affordance, quietly doing the heavy lifting behind every smooth app experience you’ve ever had.</strong></blockquote><blockquote><strong>Design that doesn’t need instructions is design that respects your time. And honestly, that’s the whole point.</strong></blockquote><h3>How designers should actually USE affordance (not just know about it)</h3><h3><strong>Design for thumbs, not eyes</strong></h3><p>Most affordance advice is written like people are staring at a desktop with a mouse.</p><p><strong>Wrong.</strong></p><p>On mobile (which is basically all of the world), affordance needs to work for a thumb moving fast in the bottom two-thirds of the screen. That’s why apps like Airbnb, Grab, Noon, Swiggy, Zomato, etc. keep primary actions low, in thumb-reach zones.</p><p>If your “buy now” CTA is affording perfectly but sitting in the top right, congrats, you built a beautiful button nobody can comfortably tap.</p><h3><strong>Match affordance strength to action importance</strong></h3><p><strong>Not everything should scream “tap me.”</strong></p><p>A destructive action like “delete account” shouldn’t have a loud, exciting affordance; that’s a trap.</p><p>Instead, it should feel a little harder to trigger, less inviting, sometimes even requiring a second confirmation step.</p><p>This is called “<strong>Friction as a Feature”</strong>. Good designers deliberately weaken affordance for risky actions and strengthen it for safe, desired ones.</p><h3><strong>Borrow mental models from real life, ruthlessly</strong></h3><p>The brain already has thousands of mental models baked in from the physical world.</p><ul><li>A shadow means something is raised.</li><li>A dial rotates.</li><li>A card can be flipped.</li></ul><p>Every time you invent a totally new interaction pattern from scratch, you’re fighting decades of muscle memory.</p><blockquote>Steal from real life whenever you can, that’s exactly why CRED’s scratch card feature works instantly with zero explanation.</blockquote><h3><strong>Test affordance without saying anything.</strong></h3><p><strong>The real pro move:</strong> put your design in front of someone and say nothing literally.</p><ul><li>Don’t explain the screen.</li><li>Just watch where their thumb hesitates.</li></ul><p><strong>Hesitation is data.</strong></p><p>If people pause before tapping something, that’s not a UX flaw you fix later; that’s an affordance failing in real time, right in front of you.</p><h3>At last: The Secrets barely anyone talks about</h3><p>Here’s where it gets spicy. These are things senior designers know but rarely tell:</p><p><strong>Secret 1: Affordance decays with familiarity, on purpose</strong></p><p>Once users learn a pattern, you can actually reduce visual affordance without losing usability.</p><p>That’s why power user apps (like CRED, or even WhatsApp Web) get more minimal over time.</p><blockquote><strong>Beginners need loud cues. Experts need less visual noise and more speed.</strong></blockquote><p>This is why redesigns that “simplify” things sometimes confuse new users but delight existing ones.</p><p>It is not a mistake; it’s intentional affordance fading.</p><p><strong>Secret 2: Negative space is an affordance tool, not just aesthetics.</strong></p><p>Empty space around a button doesn’t just look clean; it isolates the element and screams “this is the one thing you should focus on here.”</p><p>Crowded screens kill affordance even if every individual button looks perfectly tappable, because the brain can’t figure out priority.</p><p>This is why Apple’s checkout flows feel so obvious: it’s not the buttons doing the work alone; it’s the emptiness around them.</p><p><strong>Secret 3: Sound and haptics are affordances too.</strong></p><p>Most people think affordance is purely visual. Wrong. That tiny vibration when you swipe to delete a message, or the click sound on a UPI PIN pad, these are affordance signal delivered through touch and sound instead of sight.</p><p>Apps that skip this feel “cheap” even if the visuals are identical to a competitor&#39;s.</p><p>Swiggy or PhonePe’s subtle haptic buzz on adding something to cart or successful payment is doing more psychological trust-building than people realize.</p><p><strong>Secret 4: Consistency beats cleverness, always</strong></p><p>A genuinely well-kept secret.</p><p>Designers love inventing a unique, artsy new interaction because it feels creative. But if your app is the only one where swiping right means delete instead of the industry standard swipe left, you’ve just created a tiny daily tax on every user’s brain.</p><p>The best affordance often isn’t original; it’s <em>predictable</em>. <strong>Boring wins, not you, I am talking about design!</strong></p><p><strong>Secret 5: False affordance is sometimes used deliberately (and it’s a little evil).</strong></p><p>Some apps intentionally design fake affordance to manipulate behavior. Think of a “close ad” X button that’s tiny and grey while the actual ad content looks huge and clickable everywhere. Or a subscription cancel button that’s styled to look disabled when it’s actually active.</p><p>This is called a <strong>dark pattern</strong>, and while it technically “works” short term, it destroys trust the moment users notice. Ethical designers avoid this even when it would boost conversion, because trust is the actual long game.</p><p><strong>Secret 6: Motion previews the outcome before the tap even happens</strong></p><p>Designers who use subtle animation not just to confirm an action happened, but to preview what WILL happen before the user commits get results.</p><p>Think of how a bottom sheet slightly peeks up from the edge of the screen before you even touch it; it’s silently telling you “there’s more content here; drag me up.”</p><blockquote><strong>This pre-affordance, hinting at a possible interaction before contact, is one of the most underused tricks in the game.</strong></blockquote><p>Thanks for reading this till here, even I learned this the hard way! 😅</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb78cba4d71a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should we call it User Experience (UX) or Human Experience (HX)?]]></title>
            <link>https://medium.com/@tanmayvatsa1507/should-we-call-it-user-experience-ux-or-human-experience-hx-15ac9db6ce7f?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/15ac9db6ce7f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 19:32:29 GMT</pubDate>
            <atom:updated>2026-03-31T19:32:29.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gz67uHJFEs-8sThVRCMjHA.png" /></figure><p>Listen up, fellow designers. We need to have a real talk about something that’s been bothering me for a while now.</p><p>We’ve been out here calling it <strong>“User Experience”</strong> for decades, creating these neat little persona cards with stock photos, fictional coffee preferences, and made-up job titles… and honestly? It’s giving “I did the bare minimum and called it research” energy.</p><p>No cap, it’s time we graduate from designing for creatures called “users” to designing for, you know, actual <strong>HUMANS</strong>. Revolutionary concept, I know. LOL!</p><h3>The “User” Label gives a major Ick 😬</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*iFgC_m5OYouai2Xy" /></figure><blockquote><strong>Let’s be real for a second. When you call someone a “USER,” what are you really saying? 👀</strong></blockquote><p>You’re literally defining an entire human being by their relationship with… YOUR PRODUCT. That’s it. That’s the whole vibe.</p><p>The term “USER” carries connotations of addiction to something or let’s say technology or maybe electronic gadgets, ummm Yikes!</p><p>Definitely not exactly the energy we want to be putting out there, right?🤨</p><p>Think about it: You wouldn’t introduce yourself at a party like <strong>“Hi, I’m Shweta, a Netflix user.”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*J2-6gh_rORsIdSQt.gif" /></figure><p>That would be unhinged.</p><p>You’d be like, <strong>“Hi, I’m Shweta, I’m into Marketing, I have a chaotic sleep schedule, and sometimes I crave Sushi while watching cooking shows at 12 AM.”</strong></p><p><strong>See the difference?</strong></p><p>You’re a whole person with feelings, moods, contexts, and complexities.</p><p>But in UX land? Nah. You’re just “Shweta, 28, Marketing Manager, values quality and sustainability.” Period. End of story.</p><blockquote>We’ve basically turned you into a LinkedIn bio when you’re actually a entire novel with plot twists.</blockquote><h3>I think this persona industrial complex needs to be STOPPED! 🛑</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*PxArIyweco8NjshW.png" /></figure><p>Okay, so let me tell you about personas.</p><p>We love them, we’ve been using them since like the ’90s, and they’re… fine?</p><p>But here’s the tea: Personas tell us who our users are/can be, but they often fail to predict how users will actually behave when confronted with real decisions, time pressure, and cognitive overload.</p><p><strong>Remember “Shweta the Marketing Manager”?</strong> Our fictional persona who “values sustainability”? Well, guess what happens when Shweta’s phone is at 2% battery, she’s running late for a meeting, and she needs to book a cab RIGHT NOW?</p><p>She’s clicking the first available option that gets her there <strong>THE</strong> <strong>FASTEST! ⚡️</strong></p><blockquote><strong>When users are under time pressure, they default to familiar options rather than researching sustainable alternatives, and when cognitively overloaded, they abandon complex forms regardless of their environmental values.</strong></blockquote><p>But our cute little persona card didn’t prepare us for</p><p>A. Stressed Shweta,</p><p>B. Hungry Shweta,</p><p>C. Shweta-who-just-got-dumped, or</p><p>D. Shweta-who’s-been-doom-scrolling-at-3 AM.</p><p>We just got regular 9-to-5 S,hweta who apparently never has a bad day or changes her mind based on context.</p><p>Yeah, that’s too many Shwetaaaaaaaaa I wrote above, but thanks for reading my article till now, you ROCK! 🍻 <strong>Now, drink some water and let’s get back to FOCUS MODE my friend:</strong></p><h3>Real Humans Are Glitchy, And That’s Beautiful ✨</h3><p><strong>Here’s what personas DON’T ❌ capture:</strong></p><ul><li><strong>Mood swings</strong> (we’ve all ordered stuff online at midnight that we deeply regretted in the morning)</li><li><strong>Context switching</strong> (professional you vs. weekend you are basically different people)</li><li><strong>Life happens</strong> (stress, joy, exhaustion, hunger — all of these change how we interact with products)</li><li><strong>Cultural nuances</strong> (especially in diverse markets like India — more on this in a sec)</li></ul><p>The research backs this up: context, cognitive load, and situational factors often override personality traits and demographics when it comes to user behavior.</p><p><strong>Layman explanation? Ofcourse 😌</strong></p><p>What I want to say here is: Your fancy well-detailed persona with a name, photo, problem, and favorite KFC order is essentially fan fiction.</p><h3>Let me Welcome you to the Next Billion Users Era 🌏</h3><p>Now, let’s talk about something that really exposes the limitations of traditional UX thinking: <strong>The Next Billion Users!</strong></p><p>Google’s been doing the actual work here, and they’ve figured out something crucial: the next billion users are not becoming more like us. We are becoming more like them!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*LneGxKcYJ7fBubE0.gif" /><figcaption>Yeah! Mic drop moment it is</figcaption></figure><p>There are people in places like USA, France, India, Brazil, Indonesia, Nigeria and many more regions who are coming online for the first time.</p><p>And here’s what’s wild: a first-time internet user living in rural India will have very different needs and wants than a seasoned technophile in Los Angeles.</p><p><strong>But it goes deeper than that. 🤯</strong></p><p>We’re not even talking about <strong>“PERSONAS”</strong> anymore — we’re talking about people who:</p><ul><li>Might not even know what that shopping cart icon means (one person in India thought it was the cart that garbage collectors use 💀)</li><li>Are sharing devices with multiple family members</li><li>Have limited data plans and unreliable connectivity</li><li>Use voice more than typing because they’re more comfortable in their native language</li><li>Haven’t yet been conditioned by years of using similar apps</li></ul><h3>The Humans are built different and we need to think about them as designers!</h3><p>For now, let’s zoom into India specifically. India now has 886 million internet users, with 55% rural penetration. That’s insane growth, and it’s changing everything.</p><p>Here’s what makes Indian digital users different:</p><ul><li><strong>They’re mobile-first, not mobile-second</strong>: Most next billion users have never used a PC and may never use one. They don’t think of the internet as something you access with a mouse and keyboard</li><li><strong>Video is their language</strong>: Short-form video content is huge. Video content is gaining sharply in importance, with short, snackable video clips being the best way to communicate with the next billion users.</li><li><strong>They want localized content</strong>: The generation coming online in India is more comfortable in their native language than in English, and language can be a big blocker to expanding internet access. <strong>(Don’t tell me you never thought why HYPER PERSONALIZATION became so important for people as well as products)</strong></li><li><strong>Context is everything</strong>: Indians spend 2.5–3.2 hours per day on social platforms, primarily via smartphones, with Instagram, Facebook or WhatsApp being ubiquitous, with about 500 million users.</li></ul><p>But here’s the plot twist: These insights don’t just help “new” users.</p><p>Features built for the next billion users, like Google maps, are now used across the world by commuters going through unknown roads, tunnels and tourists visiting new countries.</p><blockquote><strong>In simple terms, when you design for human needs in their full complexity and context, everyone benefits. That’s the whole point of Human Experience design, bestie!!!!!</strong></blockquote><h3>So what even is “Human Experience” design? 💭</h3><p>Okay, so if “User Experience” is giving outdated energy, what’s the alternative?</p><p><strong>Human Experience</strong> <strong>(HX) design</strong></p><p>It’s not just UX with a rebrand — it’s a fundamental shift in how we think about who we’re designing for.</p><ul><li>Human Experience Design serves humans, not technology.</li><li>Users are only one segment of the humans who have relationships with our products and services — we also design for customers who buy, active stakeholders who benefit from and influence the product, and passive stakeholders who are affected by it.</li></ul><p><strong>Think about it with an example:</strong></p><p>When Google Pay launched in India, they had to think beyond just “users.” The team built an entity-based transaction interface because the most natural way for people to recall payments was to remember the person they transacted/interacted with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*8EMrXZbuGnTy-HDJnl2FmA.png" /></figure><p>They also introduced gamification through scratch cards. <strong>This wasn’t about following some persona template — it was about understanding actual human behavior in context.</strong></p><h3>What I have learned in these years of being a UX Designer, there are three levels of being human 🧠</h3><p>Human Experience design recognizes that we all operate on multiple levels:</p><ol><li><strong>Visceral Level</strong>: This is your immediate, gut reaction. The “OMGGGG, pretty” or “Ew David, that’s sketchy” response before you even think about it.</li><li><strong>Behavioral Level</strong>: This is about getting stuff done. Can you actually accomplish what you need to? Is it frustrating or smooth?</li><li><strong>Reflective Level</strong>: This is the deeper meaning. How does using this product make you feel about yourself? Does it align with your values and identity?</li></ol><p>Traditional UX mostly focuses on Level 2 (can users complete tasks efficiently?).</p><p><strong>Human Experience design says:</strong></p><p>Yo Boy! what about the other two levels? What about the whole human?</p><h3>The Reality Check: We’re All Messy Humans 🎭</h3><p>Here’s what designing for humans (not users) actually means in practice:</p><h3>1. Acknowledge That Context Is King 👑</h3><p>The same person behaves completely differently based on:</p><ul><li>Time of day (3 PM you vs. 3 AM you)</li><li>Stress levels (chill Sunday you vs. deadline panic you)</li><li>Environment (home you vs. commute you vs. work you)</li><li>Social context (alone vs. with friends vs. with family)</li></ul><p>We’re no longer just sitting and clicking on a computer. We’re talking to our devices, swiping and gesturing, watching, sometimes even using our eyes or movement to interact. Everyone is constantly moving, switching between phones, laptops, cars, watches, TVs, and whatever comes next.</p><p><strong>Your design needs to flex with all of this, not just work for one perfect scenario.</strong></p><h3>2. Let’s respect Cultural Intelligence 🌍</h3><p>The biggest mistake designers make is to think English-first and then translate for local use. The correct approach is to rethink every element on an interface in the context of the user.</p><p><strong>This means:</strong></p><ul><li>Don’t just slap a translation on your UI and call it “localized.”</li><li>Icons that make sense in Silicon Valley might mean nothing (or something totally different) in England</li><li>Payment methods, trust signals, and social norms vary wildly</li><li>People are gaining a new sense of pride and connection to their native languages, and increasing accessibility to local vernacular content online reflects this</li></ul><h3>3. Most importantly, Design for the unhappy paths too 🛣️</h3><p>Everyone loves designing the “HAPPY PATH” — when everything goes smoothly, and users behave exactly as expected.</p><p><strong>But real life? It’s messy.</strong></p><p>What happens when:</p><ul><li>Your users have unreliable internet/situations? (Literally the reality for millions)</li><li>Are they accessing your app on a shared device with privacy concerns?</li><li>They make a mistake and panic in miliseconds?</li><li>They’re in a crisis and need help NOW, not after reading your cute onboarding tutorials?</li></ul><p>The next billion users face anxiety and fear when using new technology. Icons and buttons that experienced users take for granted may not be immediately apparent to them.</p><p>Your solution and design my friend, should hold space for confusion, frustration, and learning — because that’s being HUMAN!</p><h3>4. And and and, Remember: Humans are not Robots 🤖</h3><p>We’re not looking/expecting for “optimal efficiency” 24/7.</p><p><strong>Sometimes we want:</strong></p><ul><li><strong>To feel cool or smart</strong></li><li><strong>To connect with others</strong></li><li><strong>To express ourselves</strong></li><li><strong>To be entertained</strong></li><li><strong>To feel safe and in control</strong></li><li><strong>Just to vibe</strong></li></ul><p>The fundamental goal of Human Experience Design is to help people experience love, which in this context represents catharsis that results in feelings of connection, safety, mastery, and/or satisfaction.</p><p>Love might sound dramatic, but think about it:</p><ul><li>That feeling when you turn the key and your car starts immediately? That’s love.</li><li>When an app saves your progress right before you were about to lose it? Love.</li><li>When a website remembers your preferences without being creepy about it? Also love.</li></ul><h3>Atleast the way I think is that: The Future Is Human-Shaped 🚀</h3><p>Look, I’m not saying we should completely throw away personas or traditional UX methods. They are most useful as starting points. <strong>But we need to stop pretending they’re the whole story.</strong></p><p>The future likely involves hybrid approaches that combine the empathy-building power of personas with the predictive accuracy of behavioral research.</p><p>This simply means:</p><p><strong>Do This</strong> ✅:</p><ul><li>Use real behavioral data, not assumptions</li><li>Account for different contexts and emotional states</li><li>Design for the full spectrum of human experiences</li><li>Test with actual humans in real situations</li><li>Keep iterating based on how people actually behave</li><li>Respect cultural and linguistic diversity</li><li>Design for both happy and unhappy paths</li></ul><p><strong>Not That</strong> ❌:</p><ul><li>Creating elaborate persona cards and never updating them</li><li>Assuming everyone uses your product the same way</li><li>Designing only for the “ideal” scenario</li><li>Ignoring context, mood, and situational factors</li><li>Treating diverse markets as monoliths</li><li>Forgetting that humans are irrational, emotional, and wonderful</li></ul><h3>I promise this is the last paragraph YAY!</h3><p>So, my friend, after you read what I think, should we call it <strong>“User Experience” or “Human Experience”?</strong></p><p>I mean, call it whatever you want, but <strong>design like you’re creating for whole humans, not simplified characters</strong>. Design for people who:</p><ul><li>Have bad days</li><li>Get hungry</li><li>Switch contexts constantly</li><li>Come from different cultures</li><li>Speak different languages</li><li>Experience stress, joy, confusion, and everything in between</li><li>Are sometimes your “next billion users” who’ve never seen your clever UI patterns before</li></ul><blockquote><strong>Because at the end of the day, we design solutions, software and systems for people to use it, and we should aspire for those visual solutions to be designed by people, for people.</strong></blockquote><p>The users we think we’re designing for? They don’t exist. They’re figments of our whiteboard sessions.</p><p>But the humans using our products? They’re real, they’re complex, they’re beautiful in their messiness, and they deserve better than being reduced to a demographic checkbox and a stock photo.</p><p>Let’s design for them instead. Let’s make it human.</p><p><em>You don’t know but you have become my new friend since you read till last! Now, as a designer friend, openly give your thoughts on what you just read! </em><strong><em>And tell me if you are in team UX or team HX?</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15ac9db6ce7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2026 UX Blueprint: How to Become a Design Baddie in the Age of AI ]]></title>
            <link>https://medium.com/@tanmayvatsa1507/the-2026-ux-blueprint-how-to-become-a-design-baddie-in-the-age-of-ai-e7f80d077a5b?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7f80d077a5b</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[learn]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[blueprint]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Tue, 30 Dec 2025 09:49:55 GMT</pubDate>
            <atom:updated>2025-12-30T09:49:55.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IsbEIv_E_Ng3zvkB58vhJw.png" /></figure><h4>Forget everything you knew about “Pixel-Pushing.” The game has changed, and the bar is higher than ever. 💅✨</h4><p>If you’re looking at the design landscape in 2026 and feeling a little “shook,” you’re not alone.</p><p>The era of spending three weeks on a UI kit is officially in the archives. We are living in the <strong>Post-Interface Era</strong>, where AI does the grunt work and designers have evolved into <strong>Product Architects.</strong></p><blockquote><strong>If I were starting from zero today, I wouldn’t just learn how to use Figma — I’d learn how to command the machine.</strong></blockquote><p>Here are the 20 pillars of the modern UX/UI career.</p><h3>1. Master “Curation over Creation” 🎨</h3><p>In 2026, AI can generate 100 UI layouts in seconds. Your value isn’t in drawing the boxes; it’s in being the <strong>Creative Director</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*bbOlXUxHPs_wt09j.jpg" /><figcaption>Google Stitch</figcaption></figure><p>You need to develop an elite “eye” to filter the AI’s output, identifying which version actually solves the user’s problem and which is just “hallucinated” fluff.</p><h3>2. Become a “Prompt Architect” ⌨️</h3><p>Generic prompts get generic results. To get hired, you need to master <strong>System Prompting</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/0*9QsGAC8E49a1YN3Z.jpg" /><figcaption>A Website design generated using Lovable</figcaption></figure><p>This means learning how to feed AI-specific constraints, user personas, and brand voice guidelines so the generated designs actually align with a real business strategy.</p><h3>3. Hyper-Specialization in Spatial UI (XR) 🥽</h3><p>The “flat” web is still here, but the high-paying roles are in <strong>Spatial Design</strong>. With the mainstreaming of AR glasses, you must understand z-axis depth, lighting, and how a user interacts with digital objects in their physical living room.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*yaOUznZIee8VmSfJ.jpg" /></figure><h3>4. Designing for “Zero-UI” 🗣️</h3><p>We are moving away from screens. You need to learn how to design <strong>Voice User Interfaces (VUI)</strong> and haptic feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*CDsqEOACYI99edUL.jpg" /></figure><p>This involves mapping out conversation flows and “invisible” triggers where the AI anticipates a user’s needs before they even tap a button.</p><h3>5. Ethical AI &amp; “The Trust Gap” 🛡️</h3><blockquote>Users in 2026 are skeptical of AI.</blockquote><p>Your job can be to design for <strong>Transparency</strong>. This means creating <strong>“Confidence Scores” </strong>for AI outputs and designing clear <strong>“Off-Ramps”</strong> so users know exactly when they are talking to a bot versus a human.</p><h3>6. Data Literacy is the New “Grid System” 📊</h3><blockquote><strong>You can’t just say “I think users like this.”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pIiPQUDmcu0z2uz-.jpg" /></figure><p>You need to be able to look at real-time AI analytics dashboards and interpret complex data patterns.</p><p>Companies want designers who can bridge the gap between <strong>“the feels” and “the numbers.”</strong></p><h3>7. Advanced Prototyping in Spline &amp; Bezi 🧊</h3><p>Figma is the baseline, but <strong>Spline</strong> and <strong>Bezi</strong> are the flex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3dwpW1wKLG9VsONp.png" /></figure><p>In 2026, static mockups are “mid.” You need to build interactive, 3D environments that stakeholders can walk through virtually to understand the user journey.</p><h3>8. Accessibility (A11y) as a Legal Requirement ♿</h3><p>Inclusive design isn’t a “nice-to-have” anymore — it’s a global legal standard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/0*0VFGMxg2uWcKnLj4.jpg" /></figure><p>You must be an expert in screen-reader optimization, high-contrast modes for AR, and neuro-inclusive design (making apps usable for people with ADHD or sensory sensitivities).</p><h3>9. Micro-Interaction Mastery ✨</h3><p>Since AI handles the big layouts, you should focus on the <strong>details</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*wVKqZz-5ZrkUF22XHWH0fw.gif" /></figure><p>Master the tiny animations (Use Rive, After Effects, etc.), button-press feedbacks, and loading states that make an app feel “premium” and alive.</p><p><strong>This is where the “human touch” truly shines.</strong></p><h3>10. Multi-Modal UX Strategy 📱⌚</h3><blockquote><strong>Users don’t just use one device. You need to design seamless “Hand-offs.”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A11N63cbvapZkEHaTC83pg.png" /></figure><p>A user might start a task via voice on their smart glasses, continue it on their phone, and finish it on a desktop.</p><p>Designing that fluid transition is a top-tier skill.</p><h3>11. Learn “No-Code” Development 🛠️</h3><p>The line between designer and developer has blurred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*96iXjl9NFJeZUuaa.png" /></figure><p>You should be able to take your designs into tools like <strong>Framer</strong> or <strong>Webflow</strong> and launch a production-ready site yourself.</p><blockquote>Being a <strong>“Designer who can Ship”</strong> is a major salary booster.</blockquote><h3>12. Emotional Intelligence (EQ) over IQ ❤️</h3><p>AI has a high IQ but zero EQ.</p><p>As a designer, your job is to advocate for the <strong>human emotion</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/0*C1VdkLalv1kh-wJE.jpg" /><figcaption>Start with these three baseline thoughts</figcaption></figure><p>You need to conduct deep ethnographic research to understand the <strong>“WHY”</strong> behind user behavior that a data model might miss.</p><h3>13. Systemic Thinking &amp; Design Systems 🏗️</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*14h7YJawdF9YfuHKFJSjBA.png" /></figure><p>Don’t design pages; design <strong>systems</strong>.</p><p>You need to know how to build and maintain AI-driven design systems that automatically update across platforms when a single variable is changed.</p><h3>14. “The Feedback Loop” Management 🔄</h3><blockquote>In 2026, products are constantly evolving based on live AI feedback.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*We89LTApb5DZ65i8.jpg" /></figure><p>You need to be comfortable with <strong>Continuous Discovery</strong> — constantly tweaking the UX based on how users are interacting with the product <em>right now</em>, not six months ago.</p><h3>15. Personal Branding on Social Platforms 🤳</h3><blockquote><strong>Your portfolio is just the start. Recruiters are looking for “Thought Leaders.”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0OrFL2ybzcyShKZywhjwSQ.png" /></figure><p>Document your learning journey on LinkedIn, X, or Instagram. Showing that you understand the 2026 tech “vibes” makes you a much more attractive hire.</p><h3>16. Psychology of Persuasion &amp; Ethics 🧠</h3><p>Understand “Nudge Theory” and how to guide users without being manipulative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YWVJrZTBNT_LcEsT.gif" /></figure><p>In a world of “Dark Patterns,” being the designer who stands for <strong>Ethical UX</strong> is a huge selling point for major tech brands.</p><h3>17. Rapid Iteration via “Wizard of Oz” Testing 🧙‍♂️</h3><p>Learn how to fake complex AI features using low-fi tools to test if a concept even works before a single line of code is written.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pGM0XZNM4oanmFHf.png" /></figure><p>This “Fail Fast” mentality is what 2026 startups crave.</p><h3>18. Copywriting is Part of the Design ✍️</h3><blockquote><strong>With AI-generated text being everywhere, “lorem ipsum” is a crime.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k--k2qVCrpPpwG8F.png" /></figure><p>You need to be able to write (or prompt) <strong>Micro-copy</strong> that sounds human, witty, and perfectly aligned with the brand’s personality.</p><h3>20. The “Long-Game” Mentality 🧘</h3><p>Tech moves fast, but human psychology changes slowly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v704XLe8L7iqfXj_fMP7_g.png" /></figure><p>Don’t get distracted by every new AI tool.</p><p>Focus on the core principles of <strong>usability, utility, and delight.</strong> If you master the fundamentals of human behavior, you’ll be un-fireable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7f80d077a5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2026 UX/UI Design Trends that will be everywhere]]></title>
            <link>https://medium.com/@tanmayvatsa1507/2026-ux-ui-design-trends-that-will-be-everywhere-0cb83b572319?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/0cb83b572319</guid>
            <category><![CDATA[latest-web-design-trend]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[2026]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 07:53:57 GMT</pubDate>
            <atom:updated>2025-12-29T07:53:57.590Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hey there 👋🏻</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*93vlHXjBcPkzsUMTO6RbmQ.png" /></figure><p>This time I’ll be talking real stuff — the “Clean design” aesthetic of the early 2020s is officially in its retirement era. The beige-on-white, soulless minimalism that defined the last decade?</p><p><strong>Skip!!!!!!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*CMTLfhSgptb7dEkc.gif" /></figure><p><strong>In 2026</strong>, digital design has entered its <strong>“Main Character”</strong> era.</p><p>We’re talking about interfaces that feel like a high-octane Instagram Reel, textures that look squishy enough to touch, and AI that actually understands the <em>vibe</em>.</p><p>Whether you’re doom-scrolling on <strong>Zomato</strong> or hunting for a fit on <strong>Myntra FWD</strong>, the digital landscape in India is getting a massive glow-up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rpAL1kavHjc1l931.png" /></figure><h3>Here are “<strong>10 UX/UI Design Trends”</strong> that are making us actually want to stay on any digital product for more than seven seconds:</h3><h3>1. Tactile Maximalism: The “Squishy-uishy” UI</h3><blockquote>We’re over flat pixels. 2026 is all about <strong>Digital Texture</strong>.</blockquote><p>Buttons look like they’re made of jelly, chrome, or clay. When you press them, they don’t just “click” — they deform and bounce back.</p><ul><li><strong>The Vibe:</strong> High-gloss 3D and inflatable icons.</li><li><strong>Reference:</strong> Think of <strong>Blinkit’s</strong> latest festive icons — they look like you could literally pluck a <em>Laddu</em> off the screen.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oxe1Cb8Q7H1G0Kqkwe7DOw.png" /><figcaption>Blinkit Festive UI</figcaption></figure><h3>2. Kinetic Typography: Let the Letters Dance</h3><blockquote>Static text? <strong>Boring.</strong></blockquote><p>In 2026, words are performers. Kinetic typography means headlines that stretch, bounce, or liquify as you scroll.</p><ul><li><strong>The Vibe:</strong> Moving text that reacts to your thumb.</li><li><strong>Reference:</strong> <strong>CRED</strong> has been the OG here, but now even apps like <strong>Zomato</strong> are using “dancing text” to make your order tracking feel like a mini-party.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*racsaJt0nt_bdjgU.gif" /><figcaption>Just an example! 😇</figcaption></figure><h3>3. Bento Grids 2.0: Organized Chaos</h3><blockquote>Apple started it, but 2026 is going to make it perfect.</blockquote><p>The <strong>Bento Grid</strong> organizes content into sleek, rounded rectangular cards. It’s peak satisfying — perfect for our short attention spans.</p><ul><li><strong>The Vibe:</strong> Modular, scannable, and extremely “aesthetic.”</li><li><strong>Reference:</strong> <strong>Myntra FWD</strong> uses this beautifully to show you “Mood Boards” instead of just a boring product list.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EhB21AUkC4cUQPb1cgXOuA.png" /></figure><h3>4. AI-Driven “Main Character” Energy</h3><blockquote>Standard UIs are so old now.</blockquote><p>In 2026, the app’s entire vibe changes based on <strong>you</strong>. If you’re in your <strong>“Productivity Era,”</strong> the app turns minimal. If it’s Friday night and you’re hyped, it shifts to neon gradients.</p><ul><li><strong>The Vibe:</strong> Adaptive layouts that “read” your mood.</li><li><strong>Reference:</strong> <strong>Spotify India</strong> already does this with “Niche Mixes,” but now the <em>entire layout</em> shifts to match your vibe.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*szy_RUGkAkxTKmvA.png" /></figure><h3>5. Sci-Fi “Cyber” Gradients</h3><blockquote>Forget subtle pastels. We’re in our <strong>Cyberpunk Era</strong>.</blockquote><p>Think deep blacks paired with “Electric Neon,” “Sunset Coral,” and “Holographic Silver.”</p><ul><li><strong>The Vibe:</strong> High-contrast, dark-mode-first, and glowing.</li><li><strong>Reference:</strong> <strong>Pocket FM</strong> and <strong>Jar</strong> are leaning hard into these futuristic neon glows to attract the night-owl crowd.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*c-pvuCACzY8dJ-HN.png" /><figcaption>Jar App UI</figcaption></figure><h3>6. Scrollytelling: The Interactive Journey</h3><blockquote>Scrolling isn’t just a move; it’s a story.</blockquote><p>As you scroll, elements fly in, change color, and transform. It’s basically a movie you control with your thumb.</p><ul><li><strong>The Vibe:</strong> Immersive and impossible to put down.</li><li><strong>Reference:</strong> <strong>Tata Neu</strong> uses scrollytelling for their big product launches, making the “unboxing” experience purely digital.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*MAL0NSHUsw05mPIU" /></figure><h3>7. Hyper-Local Vernacular: Desi is Cool</h3><blockquote>English-only is a “skip.”</blockquote><p>2026 is about <strong>Vernacular-First Design</strong>. We’re seeing custom-designed typography in Hindi, Tamil, and Bengali that looks just as “hype” as English streetwear brands.</p><ul><li><strong>The Vibe:</strong> Culturally rooted but globally polished.</li><li><strong>Indian Ref:</strong> <strong>Meesho</strong> and <strong>ShareChat</strong> are the leaders here, making the UI feel like it belongs in <em>Bharat</em>, not just Bangalore.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ku0MyCz_Clupmkno.png" /></figure><h3>8. Doodles &amp; Human Imperfections</h3><blockquote>In a world full of AI-perfect images, we crave the <strong>“Human Touch.”</strong></blockquote><p>Expect to see hand-drawn scribbles, sketchy underlines, and “ugly-cool” stickers everywhere.</p><ul><li><strong>The Vibe:</strong> Authentic, raw, and low-key “unprofessional” in the best way.</li><li><strong>Reference:</strong> <strong>Curo from Cult Fit </strong>makes the brand feel like your quirky best friend.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/1*36DZ1hy2MSMPRKGoCAKyQw.png" /><figcaption>Curo — Cultfit</figcaption></figure><h3>9. Immersive 3D Commerce</h3><blockquote>Why look at a 2D photo when you can walk through a digital store?</blockquote><p>2026 is huge for <strong>3D Product Previews</strong>. You can rotate that sneaker or see the texture of that fabric in real-time.</p><ul><li><strong>The Vibe:</strong> Real-time 3D models you can touch and spin.</li><li><strong>Reference:</strong> Applications like <strong>Pepperfry</strong> let you virtually “walk” through your room.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z7HG6kgFvRjW9aLa.jpg" /></figure><h3>10. Nostalgia x Futurism</h3><blockquote>We’re still obsessed with the early 2000s, but with a 2026 twist.</blockquote><p>Pixel art mixed with high-res 3D. It’s sentimental but sci-fi.</p><ul><li><strong>The Vibe:</strong> Low-poly graphics and old-school textures.</li><li><strong>Reference:</strong> <strong>Nykaa</strong> often runs “Retro-Glams” campaigns that use this Y2K aesthetic to sell Gen Z makeup lines.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KpTTlw8sC8KAk-ba.jpg" /><figcaption>Nykaa Retro Glams</figcaption></figure><p>If you found this insightful, don’t forget to share it across! 🎉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0cb83b572319" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience that sells: How Scarcity hacks your brain & boosts conversions]]></title>
            <link>https://medium.com/@tanmayvatsa1507/ux-that-sells-how-scarcity-hacks-your-brain-boosts-conversions-849243bca4be?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/849243bca4be</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Wed, 19 Mar 2025 13:50:57 GMT</pubDate>
            <atom:updated>2025-03-19T13:59:30.260Z</atom:updated>
            <content:encoded><![CDATA[<h3>Have you ever felt a constant feeling to buy anything from platforms like Amazon, Flipkart, Nykaa, Plix, Giva, etc?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*_G4KPe20s5RUpHR2.gif" /></figure><p>In today’s hyper-competitive e-commerce world, brands are constantly playing mind games to make you hit that <strong>‘Buy Now’</strong> button.</p><p>One of the biggest power moves?</p><p><strong>THE SCARCITY EFFECT</strong>.</p><blockquote>It’s that feeling when you see <strong>“Only 2 left in stock!”</strong> or <strong>“Sale ends in 2 hours!”</strong> and suddenly, you NEED to grab that item. Platforms like Flipkart, Myntra, Blinkit, Zepto and Amazon have mastered this trick, making you act fast before it’s <strong>‘too late.’</strong></blockquote><h3>Let’ decode this:</h3><p>Scarcity Effect is all about making products seem rare, so you want them more. It mainly comes in two flavors:</p><ol><li><strong>Low Stock Alert:</strong> “Only a few left!” messages that make you panic-buy.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*UN7nDvJnVcJDwFhj.jpeg" /></figure><p><strong>2. Time-Limited Deals:</strong> Flash sales, countdown timers, and one-day-only discounts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*1Xn_7VrX0oiKcMSm1-VD5w.png" /></figure><p>These tactics mess with your brain, pushing you to purchase before it’s gone. 🤯🤯</p><h3>How Scarcity Works on Your Brain?</h3><p>The psychology behind it is sneaky but effective:</p><ol><li><strong>Loss Aversion</strong>: We’ve all seen our family lose their minds over a missed deal. Let’s be real. Imagine Flipkart flashing <strong>‘Only 2 left in stock!’</strong> on a fire new iPhone 16. You’re not risking that, right? That little panic makes you smash ‘Buy Now’ faster than you’d planned, because losing out stings way more than saving a few bucks.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6BylcOcLG-iGnjl1GQ0rjA.png" /></figure><p><strong>2. FOMO (Fear of Missing Out)</strong>: When something feels special, you want it more. Amazon/Zepto does this with <strong>“Lightning Deals”</strong> or <strong>“Deal of the Day” </strong>— like a headphone discount for just 2 hours. You think, <strong>“Everyone’s grabbing it, I can’t miss out!”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6vc3MD-pSwkl-Kqw0na-A.png" /></figure><blockquote>It’s like seeing a party you’re not invited to — you <em>have</em> to join.</blockquote><p><strong>3. Herd Mentality</strong>: We follow what others do. Platforms like Bewakoof puts <strong>“Bestseller”</strong> on a funky t-shirt, or Amazon shows <strong>“10,000+ bought this”</strong> on a gadget.</p><p>You think, <strong>“If so many people like it, it must be awesome!” You buy it because you trust the crowd, even if you’re not sure.</strong></p><p><strong>4. Impulse Trigger</strong>: Urgency makes you act without thinking. Flipkart’s <strong>“Big Billion Days”</strong> sale with a countdown timer — <strong>“Ends in 5 hours/Get Early Access” </strong>— pushes you to grab that discounted TV now before anyone else grabs that offer.</p><p>Logic? <strong>You just click “Buy” because it’s now or never.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KfrDh8aodVTh4OPu.jpg" /></figure><p><strong>These tricks work like MAGICCCCC!!!🤯🎉</strong></p><ul><li>Flipkart’s low-stock warnings, or</li><li>Amazon’s flashy timers, or</li><li>Nykaa’s Limited-Edition drops, or</li><li>Zomato’s Hurry-up tactics, Restaurant closing in 2 mins, or</li><li>Bewakoof’s <strong>“everyone’s buying this”</strong> vibes</li></ul><blockquote><strong>They hit your emotions, not your brain.</strong></blockquote><p>Ever bought something from these sites and later <strong>wondered WHYYYYYY?🤯</strong> That’s the psychology doing its sneaky job!</p><h3>How Scarcity Shows Up in Design</h3><p>Scarcity isn’t just about words — it’s also about <strong>how it looks on screen</strong>. Here’s how top e-commerce platforms design for urgency:</p><h4>1. High-Contrast Elements 🔥</h4><ul><li><strong>Bright red/orange colors</strong> for urgency (e.g., countdown timers, low-stock alerts,instant deals,etc.)</li><li><strong>Bold, capitalized text</strong> like “LAST CHANCE” to grab attention</li></ul><h4>2. Countdown Timers &amp; Motion Graphics ⏳</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*tXD-JSe6I-rlJto9.gif" /></figure><ul><li><strong>Ticking timers</strong> on product pages create urgency</li><li><strong>Animated progress bars</strong> (For example, “Selling Fast — 80% claimed”) show demand in real-time</li></ul><h4><strong>3. Subtle Cues &amp; Gentle Prompts 🎯</strong></h4><ul><li><strong>Alerts:</strong> “Hurry! Someone just grabbed this item!”</li><li><strong>Live indicators:</strong> “X users are checking this out now”</li></ul><p><strong>4. Intelligent Personalization 🎯</strong></p><ul><li><strong>Urgency messages:</strong> “Limited stock in your size!” to drive quick action</li><li><strong>Wishlist nudges:</strong> “Your saved item is almost out of stock!”</li></ul><p><strong>5. Engagement &amp; Exclusive Perks 🎮</strong></p><ul><li>Early access for VIPs to enhance exclusivity</li><li>Lucky spin deals with time-sensitive rewards</li></ul><h3><strong>Summary:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*MDVLlpHncJ5ZJ3K-.jpg" /></figure><p>Scarcity is a psychological principle that plays a pivotal role in influencing consumer behavior, and it’s one of the most effective strategies — or “hacks” — employed in e-commerce to boost sales.</p><p>The idea is simple yet powerful: when something appears limited in availability, whether in terms of quantity, time, or exclusivity, it becomes more desirable. This sense of urgency taps into a basic human instinct — fear of missing out (FOMO) — prompting people to act quickly rather than risk losing the opportunity.</p><p>Major e-commerce players like Flipkart, Myntra, Nykaa, Giva, Zomato, and Amazon have mastered this tactic, weaving it seamlessly into their marketing and sales strategies to capture attention, create excitement, and ultimately drive higher conversion rates.</p><blockquote><strong>The brilliance of scarcity lies in its ability to amplify perceived value.</strong></blockquote><p>When an item or offer seems rare, customers don’t just see a product — they see a chance they might lose. This shifts their mindset from casual browsing to decisive action, which is exactly what these e-commerce giants aim for.</p><p>By strategically deploying scarcity — whether through limited-time deals, stock countdowns, or exclusive drops — it not only grabs your attention in a crowded digital marketplace but also converts that attention into tangible sales.</p><blockquote>Overall, this single effect has been proven to boost sales and conversions, enhance user experience, and keep customers coming back for more. I mean, HOW COOOOOLLL! 🌟🚀</blockquote><p>Thanks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=849243bca4be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flick-Moments: The low-key UX glowup you need]]></title>
            <link>https://medium.com/@tanmayvatsa1507/flick-moments-the-low-key-ux-glowup-you-need-5a71fcb43b03?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a71fcb43b03</guid>
            <category><![CDATA[learn]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[microinteractions]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Wed, 26 Feb 2025 18:39:42 GMT</pubDate>
            <atom:updated>2025-02-26T18:39:42.872Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Ever tapped a button and felt an almost invisible yet satisfying animation? Or received a playful nudge from an app that made you smile? 🤯</blockquote><p>Recently, I came across a post on X where someone praised Slack’s cool loaders. Instantly, my curiosity kicked in — I had to know what these little moments were called. So, I named them “<strong>Flick-Moment User Experience”</strong>— those tiny, seamless interactions that enhance usability and spark delight without users even realizing it. The unsung heroes of great UX design, subtly shaping how we feel about a product in just a split second.🥸</p><h3>What Are Flick-Moment UX Experiences?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*zloEmsW66nIHq0vs.jpg" /></figure><p>Flick-moments are those minor, seamless interactions that make digital experiences feel more intuitive, engaging, and human. Unlike major UX elements like page layouts or navigation structures, flick-moments are subtle — often manifesting as micro-interactions, animations, or feedback loops that create a sense of smoothness and connection between users and products.</p><p><strong>A flick-moment could be (as of what I have learnt):</strong></p><ul><li>The gentle bounce of a button when tapped.</li><li>A witty message appearing when you complete a task like <strong>“Yayy! You did it Abhay!”</strong></li><li>A smooth transition when swiping between screens.</li><li>A micro-animation that acknowledges user input, making an action feel natural and responsive.</li></ul><p>These moments may be atomic, but they influence how users perceive and interact with a product, <strong>often making the difference between a mundane experience and a memorable one.</strong></p><h3>Flick-Moment UX: That one little detail you didn’t notice/barely notice but creates a huge impact ( I mean, see I am writing a whole article on it!) 🤓</h3><p>To understand this better, let’s revisit our daily habits and look at the apps and websites we use regularly — how do they incorporate flick moments into their user flows?</p><h3>1. Zomato’s Playful Empty State Messages</h3><p>Ever searched for a restaurant on Zomato and found nothing or stuck due to weak network? Instead of a dull “No Results Found” message, Zomato often displays quirky, humorous messages that keep the experience engaging. It’s a flick-moment that transforms disappointment into a lighthearted interaction, keeping users engaged rather than frustrated. I have added an example below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*4yr9zNHMWrRoc-oC2sM_lw.png" /></figure><h3>2. Slack’s Typing Indicator, Loader &amp; Message Reactions</h3><p>Slack is full of flick-moments that create an effortless, enjoyable communication experience. The subtle typing indicator (“Anamika is typing…”) provides just the right amount of anticipation, while emoji reactions on messages create instant, lightweight engagement without unnecessary clutter.</p><p>Another great flick-moment in Slack is its playful loader. When opening the app, users are greeted with witty loading messages like “<strong>Reticulating splines” or “Making work less work.”</strong> These small, humorous touches turn a mundane waiting period into a delightful experience, reinforcing Slack’s friendly and engaging brand personality.</p><h3>3. Swiggy’s Delightful Micro Interactions</h3><p>Swiggy is packed with flick-moments that enhance the user experience effortlessly. One great example is the <strong>order tracking animation</strong>. Instead of just showing a static progress bar, Swiggy uses playful visuals — like a tiny delivery person moving across the screen — making the waiting time feel less tedious.</p><h3>4. Instagram’s Double-Tap Like Animation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*P-ihz4CF2CMOB1tO.gif" /></figure><p>The simple heart animation that appears when you double-tap an Instagram post is a classic flick-moment. It’s quick, satisfying, and reinforces your action instantly, making engagement feel effortless.</p><h3>5. Duolingo’s Friendly Feedback</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XfTLfamIOuZFZ9Xf" /></figure><p>Duolingo makes learning addictive with small, rewarding flick-moments. The owl mascot celebrates your achievements with cheerful animations, and even when you make a mistake, the response is friendly rather than discouraging. It’s these small interactions that keep users hooked on the app.</p><h3>Tiny UX gathers huge impact: Why flick-moments rule across applications?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*RK0qZ4ELYi72UWCf.jpg" /></figure><p>Flick-moments may seem minor, but they significantly impact user engagement, retention, and overall satisfaction. Here’s why they matter:</p><ol><li><strong>They Make Interfaces Feel Alive</strong> — A static app feels robotic. Flick-moments add a touch of personality and responsiveness, making interactions feel more natural and interesting.</li><li><strong>They Reduce Friction</strong> — Subtle animations and micro-feedback help users understand what’s happening, preventing confusion and hesitation.</li><li><strong>They Build Emotional Connection</strong> — Playful messages, engaging transitions, and small surprises make users feel good about using the product.</li><li><strong>They Encourage Repeat Usage</strong> — When an experience is enjoyable, people come back. A well-crafted flick-moment can make an app feel so seamless and delightful that users naturally prefer it over competitors.</li></ol><h3>Designing Effective Flick-Moments</h3><p>Want to implement flick-moment UX in your product? Here are some key principles to keep in mind:</p><p>👉 <strong>Keep It Light</strong> — Flick-moments should feel natural, not distracting. If an animation feels like it’s slowing the user down, it’s counterproductive and can irritate the user in return.</p><p>👉 <strong>Make It Meaningful</strong> — A flick-moment should enhance the user experience, not just exist for aesthetics. Nowadays, “WOW” experiences have been mistaken as “More colours and fancy elements”.</p><p>👉 <strong>Match the Brand’s Tone</strong> — The flick-moments in a banking app should feel different from those in a food delivery app. Align interactions with the product’s personality and keep it related to the brand just like your colour palette.</p><p>👉 <strong>Test &amp; Iterate</strong> — This is a very important aspect: <strong>what feels satisfying to a designer may not translate the same way for users.</strong> Testing flick-moments in real user scenarios ensures they enhance rather than disrupt the experience.</p><h3>Woah, that was a ride! Let’s wrap it up now:</h3><blockquote>Flick-moment UX is what turns good products into great ones.</blockquote><p>These seemingly minor details may not be at the forefront of design discussions, but they define how a user <em>feels</em> when interacting with an app. Whether it’s Zomato’s witty messages, Slack’s smooth communication elements, playful loader, Swiggy’s Micro-interactions or Google’s thoughtful transitions, flick-moments create effortless, delightful interactions that keep users engaged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*lBdDVmivvmWdio6e.gif" /></figure><p>As designers, paying attention to these small yet powerful moments is what elevates our work so keep exploring and build these flick-moments for your products.</p><blockquote>Because at the end of the day, it’s not just about functionality — it’s about making experiences feel effortless, human, and <em>just right</em>.</blockquote><p>Thanks! ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a71fcb43b03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Assuming People ‘Get It’ — They Don’t!]]></title>
            <link>https://medium.com/@tanmayvatsa1507/stop-assuming-people-get-it-they-don-t-feaf780aed9c?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/feaf780aed9c</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[knowledge-bias]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Sun, 09 Feb 2025 07:30:06 GMT</pubDate>
            <atom:updated>2025-02-09T07:30:06.380Z</atom:updated>
            <content:encoded><![CDATA[<h3>Stop Assuming People ‘Get It’ — They Don’t!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*P36FmKzQiSe0ya_Y.jpg" /></figure><h3>Have you ever Felt Lost?</h3><p><strong>Imagine this:</strong> You open the IRCTC app to book a train ticket. You’re excited for your trip, but within minutes, frustration kicks in. The buttons seem oddly placed, the instructions are unclear, and suddenly, you’re locked out of your account for reasons unknown. Sound familiar?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*p-KktevDeczsAb-O.jpg" /></figure><blockquote><strong>This is <em>knowledge bias</em> at play — the assumption that what’s obvious to one person is obvious to everyone.</strong></blockquote><p>From government portals like DigiLocker that require multiple steps just to retrieve a document, to any food delivery app’s UI updates that leave your parents wondering where the “COD” option went — knowledge bias affects us daily.</p><p>It’s why first-time users struggle with UPI payments on PhonePe, Paytm, Google Pay,etc. why new employees feel overwhelmed with HR software, and why brands lose customers simply because they assume users already “get it.”</p><h3>What actually is Knowledge Bias?</h3><p>Knowledge bias occurs when we assume that others know what we know, leading to miscommunication and confusion. It happens because once we understand something well, we often forget what it was like not to know it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zMeWkhOiOz0PBW6X.jpg" /></figure><p>This bias affects daily interactions in many ways:</p><ul><li>A doctor might use complex medical terms without realizing a patient doesn’t understand them.</li><li>A teacher may rush through a tough concept, assuming students can keep up.</li><li>A mobile app might expect first-time users to navigate its features without clear guidance,etc.</li></ul><p>In short, knowledge bias creates gaps in understanding. “<strong>Overcoming it requires clear communication, empathy, and designing experiences that guide rather than assume.”</strong></p><h3>How Knowledge Bias Wrecks Research and UX Design</h3><h4>1. Forgetting First-Time Users Exist</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mZaApux6wJ1n64cp.jpg" /></figure><p>Ever seen your parents struggle with UPI payments? They tap around, unsure which button to press next, often stopping to ask, <em>“Is this the right way?”</em> It’s not because they don’t understand technology — it’s because the app assumes they already know how it works.</p><p>Imagine a student attending their first coding class. The teacher rushes through topics, thinking everyone understands. Or a job seeker filling out an online form, confused by words like <em>“curriculum vitae”</em> instead of just <em>“resume.”</em></p><blockquote>Knowledge bias makes simple things feel difficult.</blockquote><h3>2. Overcomplicating Everything</h3><p>Tried filling a government form online? Felt like you needed a PhD to understand it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*SkZADXpzGBtq4-dQ.jpg" /></figure><p>That’s <em>knowledge bias</em> — making simple things feel unnecessarily difficult. It’s why fresh graduates often struggle with job portals that assume they already know how to format a resume the “right” way. Without clear guidance, they might feel lost, leading to frustration and missed opportunities.</p><h3>3. Fake Politeness = Fake Insights</h3><p>Asked someone for feedback and got a <em>“Haan theek hai”</em> instead of actual critique?</p><blockquote>In reality, people hate giving negative feedback.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/0*oyEbWYc7U0Ud6uDj.jpg" /></figure><p>If you don’t dig deeper, you’ll think everything’s fine — when it’s actually not. This is why businesses launch apps, assume they’re great, and later wonder why users are dropping off.</p><h3>4. Assuming Everyone Thinks the Same</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mFJBlT8Fka36SXNx.jpg" /></figure><p>A fintech app designed might work great for coders but totally confuse a farmer in Rajasthan. Different backgrounds = different mental models.</p><p>A food delivery app might assume users know how to apply a promo code, but someone new to digital payments might not even realize where to find or enter it.</p><h3>5. Ignoring Context-Specific Behavior</h3><p>Ever noticed how people in metros and small towns use the same apps differently?</p><p>A Swiggy user like you in Mumbai might check ratings before ordering, while someone in a small town might rely more on word-of-mouth recommendations.</p><blockquote>If designers only test with one audience, they’ll miss out on making their product truly user-friendly.</blockquote><h3>How to Fix It Like a Pro</h3><h3>👉 Test with Real, Diverse Users</h3><p>If you’re building an app for <em>kirana</em> store owners, don’t assume — visit actual stores. Watch how they manage sales, track inventory, and handle payments. If your app is slow, complex, or requires too many steps, they won’t use it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*tbbTZBCohZRymSKn.jpg" /></figure><p>See what tools they already rely on — WhatsApp for orders, voice search over typing, or quick manual calculations.</p><p>Design with these habits in mind. A great product should not be just functional; it should fit seamlessly into your users’ daily routine.</p><h3>🥸 Talk Like a Human</h3><p>If your parents wouldn’t get it, rewrite it. Simple language wins, jargon doesn’t. Use everyday words, not tech-speak.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9bQ5lI_VVgw0m4PZ.png" /></figure><blockquote><strong>Note: </strong>If people can’t understand it in under 5–7 seconds, they’ll move on.</blockquote><h3>😶‍🌫️ Ask Questions That Get Real Answers</h3><p>Instead of “Do you like this?” ask “Show me how you’d use this.”</p><p><strong>For Example: </strong>I make a video call to my mother on WhatsApp and ask her to show me how she places a return order for a defective product, and she explains the whole process to me very clearly.</p><blockquote>People reveal more when they <em>do</em> instead of just <em>saying</em> something. When you see them struggle, you know where the real issues are. OBSERVE my friend! OBSERVE!🌟</blockquote><h3>👑 Think Like a Beginner</h3><p>Pretend you’ve never seen your product before. Where do you get stuck?</p><p><strong>Try this: </strong>Out of nowhere, immediately view what you just made on screen, like a fast corousal, and you will end up noticing elements you missed seeing. That’s the point.</p><p>That’s where users will miss too. Next? Get someone completely new to try it out and watch their reactions.</p><h3>💯 Let Data Call the Shots</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*izGu0Ebn4aYQqMkW.gif" /></figure><p>Test your assumptions with actual user behavior. We often discuss these terms with our stakeholders: A/B tests, analytics, and real-world observations. Don’t rely on what <em>you</em> think is intuitive — watch what users actually do.</p><blockquote><strong>Remember: Data &gt; gut feelings. 🚀</strong></blockquote><h3>Don’t be that person!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*qkNuCmxZFST7ZVZH.gif" /></figure><p>Woah! 🤯 This entire thing you just read is something I learned while studying biases. Here’s a summarized version of it:</p><p><strong>Knowledge bias is everywhere</strong> — teachers rushing through topics, customer support agents using jargon, apps assuming you just <em>know</em> where to tap.</p><p>It’s like handing your grandma a smartphone and saying, <em>“Just update the software,”</em> without realizing she doesn’t even know where the settings are.</p><blockquote><strong>The good news?</strong> Once you <em>see</em> knowledge bias, you can <em>fix</em> it.</blockquote><p>Break things down, test with real people, and design for the <em>clueless, not the experts.</em></p><p><strong>Because the best experiences aren’t just smart — they actually <em>make sense</em> to everyone.</strong></p><p>Thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=feaf780aed9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Chaos to Clarity: Why Listing Elements First is the Ultimate Design Hack??]]></title>
            <link>https://medium.com/@tanmayvatsa1507/from-chaos-to-clarity-why-listing-elements-first-is-the-ultimate-design-hack-a252af06a746?source=rss-3831f8df186e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a252af06a746</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[components]]></category>
            <dc:creator><![CDATA[Tanmay Vatsa]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 21:33:40 GMT</pubDate>
            <atom:updated>2025-01-28T21:37:37.006Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>From Chaos to Clarity: Why listing down elements first is the ultimate design hack??</strong>🎨🚀</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x0bS9P7YOwTAzPAb.png" /></figure><p>Let’s admit it — most of us can’t resist opening up <strong>Figma or Sketch 😎</strong>, ready to throw elements on the canvas and let creativity take over. While that energy is great, this <strong>“let’s wing it”</strong> approach often leads to endless iterations, misplaced elements, and frustrated teams.</p><h3><strong>Here’s the game-changing mantra I learned sometime back:</strong></h3><blockquote><strong>Start by listing down your elements before jumping into component design</strong>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*65wxoD2DrRwrdoEJ" /></figure><p>It’s not just about planning — it’s about working <strong>smarter, faster, and with clarity🥳</strong>. That was a little definition. Now what?</p><p>Now, we will dive deeper into why &amp; how this simple step can save you hours (and headaches) while making your designs shine.🎉🎉🎉</p><h3>I found listing elements a total Game-Changer. How?</h3><h4>1. It sets the right priorities</h4><p>When you list elements beforehand, you’re essentially answering this question:</p><blockquote><strong><em>What’s most important for the user here?</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*MJDIXOnJsMgbucEy.gif" /></figure><p>For instance, if you’re designing a payment screen, the user’s main concern is <strong>completing the payment process quickly and accurately</strong>. By listing the elements <em>(Keep Zomato’s/Swiggy/Zepto, etc. applications handy)</em>:</p><ul><li><strong>Total price:</strong> should grab immediate attention.</li><li><strong>Payment method options: </strong>need to be visible upfront and accessible.</li><li><strong>Confirm button:</strong> should stand out, making the next step obvious.</li></ul><p>When you map these out, you can establish a hierarchy that aligns with the user’s journey.</p><p><strong>The result?</strong> A design that feels intuitive rather than confusing or cluttered.</p><h4>2. No More Awkward Placements</h4><p>We’ve all encountered interfaces where key buttons are hard to find, information is buried, or actions are unintuitive. <strong>These issues aren’t just bad design — they’re a failure to organize the elements properly.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*rhuaDnZBIHwXMSuw" /></figure><p><strong>Imagine this: </strong>You’re designing a food delivery app, and the <strong>“Track Order”</strong> button is tucked away in some obscure corner. The user struggles to find it, leading to frustration.</p><p>By listing and visualizing your elements early on, you can prevent such placement blunders. Every button, card, and icon ends up exactly where it should be, creating a smooth experience for the user.🚀</p><h4>3. Reduces Rework &amp; Saves Time</h4><p>We all know that nothing eats up your productivity like constant rework <strong>(See, we both have experienced this, give me a high-five 🙌🏻 )</strong></p><p>Starting with a clear list of elements solves a huge chunk of your design problems before they even arise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ZuwxR5qDFXKhSaIibF6zA.png" /></figure><p><strong>Think of it as building a puzzle.</strong> If you already know the pieces (elements) and how they fit together, you won’t waste time rearranging them mid-way. Yayy!! 🥳</p><blockquote>Instead of going back and forth with your team about missing or misplaced elements, you can focus on polishing the design to perfection.</blockquote><h4>4. You will be able to create consistency everywhere!</h4><p>Guess what:</p><blockquote><strong>Listing your elements doesn’t just help with one component — it sets a standard for your entire design system.</strong></blockquote><p>Think of it like organizing your phone’s home screen before using it. If all your favorite apps are neatly arranged and always in the same place, you’ll find them instantly, right? The same goes for design.</p><p>Planning elements upfront ensures buttons, cards, and popups are consistently placed, making the experience smooth and natural for users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CVrrKT4oINAUNI7xiMYshg.png" /></figure><h3>Now after all this, let me explain you: How to List Elements like a Master 👑</h3><p>Here’s a simple framework to help you list and organize your design elements effectively:</p><ol><li><strong>Define the purpose</strong>:<br> Start by identifying the main goal of the component or screen. <strong>What action is the user trying to accomplish (This is the most important question to ask — Make a note my friend)</strong> This will guide what elements need to be prioritized.</li><li><strong>List every detail</strong>:<br>Write down every element the component needs — <strong>primary actions, secondary actions, visual cues, feedback states, etc. </strong>Don’t leave anything out, no matter how small.</li><li><strong>Prioritize the elements</strong>:<br><strong>Rank the elements in order of importance. </strong>What needs to be most visible? What can be secondary? This will help you define the visual hierarchy.</li><li><strong>Sketch it out</strong>:<br>Once you have the list, sketch a <strong>low-fidelity wireframe to visualize the placement.</strong> It doesn’t need to be fancy — pen and paper work just fine.</li><li><strong>Get feedback from your stakeholders</strong>:<br>Share your list and sketch with your team before moving to high-fidelity design. This way, you can address any concerns or suggestions before things get too far along.</li></ol><h3>Every concept becomes easy if explained with an example: Login Screens</h3><p>Let’s consider a login screen, for example. Here’s how a properly organized element list might look:</p><p><strong>Starting with Primary Elements</strong>:</p><ul><li>Email/phone input field.</li><li>Password input field.</li><li>Login button (CTA).</li></ul><p><strong>then comes Secondary Elements</strong>:</p><ul><li>Forgot password link.</li><li>Sign-up option for new users.</li></ul><p><strong>and lastly, Optional Add-ons</strong>:</p><ul><li>Social login buttons (Google, Apple, etc).</li><li>A “Show Password” toggle.</li></ul><p>With this list, you can easily prioritize what needs the user’s immediate attention and what can be secondary.</p><p>For instance, the <strong>“Login”</strong> button should be bold and prominent, while the <strong>“Forgot Password”</strong> link can have a smaller, less intrusive placement.</p><h3>Why designers should care about this method at the first place?😶‍🌫️</h3><p>We all have seen the quick commerce revolution and know that the digital landscape today has become fast-paced, competitive, and diverse across domains and regions. In this case, what happens is:</p><blockquote>Whether you’re designing for a power user in a metro city or a first-time app user in a rural area, your design needs to work seamlessly.</blockquote><p>By taking the time to list and organize your elements before jumping into design, you are:</p><ul><li><strong>Reducing friction for the user.</strong></li><li><strong>Building trust through intuitive interfaces.</strong></li><li><strong>Saving yourself from endless revisions and feedback loops.</strong></li></ul><blockquote><a href="https://medium.com/design-bootcamp/rapid-ux-cracking-the-code-for-lightning-fast-optimized-app-experiences-b779b222b515"><strong>Rapid UX </strong></a>isn’t about rushing — it’s about thinking ahead, planning smartly, and delivering experiences that users love.</blockquote><p>I hope I was able to explain you a better method of designing components and each elements importance. 🚀</p><p><strong>Thanks!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a252af06a746" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>