<?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 Ria George on Medium]]></title>
        <description><![CDATA[Stories by Ria George on Medium]]></description>
        <link>https://medium.com/@riageorge1124?source=rss-52fc212712d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*qQ_cRZ7-srJlWW23</url>
            <title>Stories by Ria George on Medium</title>
            <link>https://medium.com/@riageorge1124?source=rss-52fc212712d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:24:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@riageorge1124/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[Nobody designed the consent flow.]]></title>
            <link>https://medium.com/@riageorge1124/nobody-designed-the-consent-flow-5cd446245d28?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cd446245d28</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Tue, 12 May 2026 05:25:12 GMT</pubDate>
            <atom:updated>2026-05-12T05:25:12.474Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S3T9IttXdOnS6OwAeZv3AQ.png" /></figure><p>Think about the last time you clicked “I accept.” Not skimmed. Not dismissed the banner before it finished loading. Actually read what you were agreeing to. You probably can’t remember. That’s by design.</p><p>Every time technology does something new to a human — tracks their location, reads their messages, activates their brain nodes — the consent moment gets handled the same way. It gets handed to legal. Legal writes a policy. The policy becomes a banner. The banner becomes something you close before finishing the first sentence. Somewhere in that chain, the actual problem gets dropped entirely. Does this person understand what they’re agreeing to?</p><p>That’s not a design solution. That’s a legal solution to a design problem. That’s exactly why it doesn’t work.</p><p>Consent has three jobs. Inform. Be understood. Be a real choice. Right now it does none of them well. Cookie banners don’t inform you of anything useful. Privacy policies are written to protect the company, not educate you. The choice — accept or leave — isn’t really a choice when the product is woven into your daily life.</p><p>We didn’t design consent. We designed the appearance of consent. There’s a significant difference.</p><p>Rapido shows you how many drivers rejected your request. Sounds like transparency. But look at what comes immediately after — a tip nudge. The information architecture isn’t there to help you understand what’s happening. It’s there to make you feel the weight of rejection so you reach for your wallet. You’re being nudged without knowing it. That’s consent in reverse.</p><p>Nike built 22 foam nodes into a shoe that activates specific brain activity. Just by wearing it. No disclosure on the box. No explanation of which brain state they’re optimising for. No mechanism to opt out except not buying it. You consented to the purchase. Did you consent to what happens to your brain after?</p><p>Sakhi is an AI health companion I built myself. It asks personal questions about your body. Building it forced me to make active decisions about what it stores, what it forgets, when it asks versus when it just listens. Those decisions exist in every AI product. Most teams never make them consciously. They default to collect everything, ask permission later.</p><p>The problem isn’t that companies are evil. The problem is that consent was never given to a designer to solve. Nobody ever sat down and asked: what does it feel like to genuinely understand what you’re agreeing to? What does that moment look like? How do you design it so a person walks away actually informed — not just legally covered? That question has never been on a product brief.</p><p>Now we have AI. Every AI product makes decisions about your data, your behaviour, your attention, your body. The surface area of consent is exploding. The stakes are higher than they’ve ever been. Our design language for consent hasn’t moved since the cookie banner. That gap is already a problem.</p><p>Designers need to own this. Not because it’ll be assigned to us — it won’t. The incentives are wrong and the business case is weak. Nobody gets promoted for making consent clearer.</p><p>But we’re the only ones who understand that a wall of text is not the same as comprehension. A checkbox is not the same as a choice. Compliance is not the same as trust. We understand information hierarchy. We understand cognitive load. We understand that the moment someone is asked to make a decision is a designed moment — and it can be designed well or very badly. Right now it’s being designed badly. By people who aren’t designers.</p><p>The design process didn’t die. It moved upstream. Past the feature. Past the flow. Past the brief. Into the question of what we actually owe the people who use what we build.</p><p>Nobody designed the consent flow. Maybe that’s the next thing worth building.</p><p>humans over products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cd446245d28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Confident Teams Still Ship the Wrong Things]]></title>
            <link>https://medium.com/@riageorge1124/why-confident-teams-still-ship-the-wrong-things-923ee358334a?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/923ee358334a</guid>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[human-psychology]]></category>
            <category><![CDATA[thinking-fast-and-slow]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Fri, 05 Dec 2025 03:46:44 GMT</pubDate>
            <atom:updated>2025-12-05T03:46:44.370Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Part 3 of the Thinking, Fast &amp; Slow series — for designers, PMs, and teams who want to build with clarity in a noisy world.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0CxoxwGv_BtYC7kGcxcKww.png" /></figure><p>If Article 1 was the lens — <br>and Article 2 was the diagnosis — <br>then this one is the punchline:</p><p><strong>Why do smart, talented, experienced teams<br>still ship things that flop?</strong></p><p>Not because they’re careless.<br>Not because they lack data.<br>Not because they don’t “care about users.”</p><p>But because the human mind — yours, mine, your CEO’s — <br>has a few final blindspots that hit hardest <em>exactly when</em> you feel most sure.</p><p>Let’s break them down — clean, sharp, and painfully real.</p><h3>1. Overconfidence — The Blindspot That Feels Like Talent</h3><p>Overconfidence isn’t arrogance.<br>It’s the mind’s default mode.</p><p>The moment a team sees a clean narrative, a promising metric, or a shiny prototype, System 1 whispers:</p><blockquote><em>“Obviously this will work.”</em></blockquote><p>It feels like product sense.<br>It’s actually prediction theatre.</p><p>Why this destroys teams:</p><ul><li>timelines shrink artificially</li><li>The effort is underestimated</li><li>complexity is ignored</li><li>success feels “inevitable”</li><li>dissent gets quieter</li><li>validation gets postponed</li></ul><p>This is why teams say “two weeks max” knowing very well it’s a quarter.</p><p>This isn’t incompetence.<br>It’s human cognition over-trusting its own storytelling.</p><h3>2. The Planning Fallacy — Everything Takes Longer (Even When You Know It Will)</h3><p>The planning fallacy is brutal because knowing it exists doesn’t help.<br>Even Kahneman himself admitted:</p><blockquote><em>“We fell for the planning fallacy while writing about the planning fallacy.”</em></blockquote><p>It hits every team:</p><ul><li>design seems simple</li><li>dev seems straightforward</li><li>dependencies “feel small”</li><li>scope creep feels unlikely</li></ul><p>This is why roadmaps slip even in companies with thousands of people and cutting-edge tooling.</p><p>The mind sees the best-case scenario.<br>It quietly deletes the rest.</p><h3>3. Loss Aversion — Why Teams Fear Backtracking More Than Being Wrong</h3><p>People hate losses twice as much as they like wins.</p><p>How this shows up in product:</p><ul><li>teams keep weak features alive</li><li>nobody kills bad ideas early</li><li>sunk costs become “justifications”</li><li>shipping becomes “we’ve come too far to stop now”</li><li>experiments get biased toward confirming what already exists</li></ul><p>A dying idea often gets more resources than a promising one.</p><p>Not because the idea deserves it — <br>But because killing it <em>feels</em> like losing.</p><p>Loss aversion keeps teams stuck.</p><h3>4. Framing — The Same Truth, Two Completely Different Decisions</h3><p>Change the frame, change the reaction.</p><p>“90% success”<br>vs<br>“10% failure.”</p><p>Same fact.<br>Different behaviour.</p><p>This affects:</p><ul><li>roadmap prioritisation</li><li>risk calls</li><li>design direction</li><li>A/B interpretations</li><li>hiring decisions</li><li>metrics storytelling</li></ul><p>Great teams choose the frame intentionally.<br>Average teams get manipulated by it.</p><h3>5. The Remembering vs Experiencing Mind — The Silent Product Killer</h3><p>Your users have two selves:</p><ul><li>the one living the experience</li><li>the one remembering the experience</li></ul><p>The remembering self decides:</p><ul><li>whether they return</li><li>whether they trust your product</li><li>whether they recommend it</li><li>whether the session “felt good”</li></ul><p>And that remembering self cares about:</p><ul><li>peaks</li><li>endings</li><li>the story it can retell later</li></ul><p>Not the duration.<br>Not the accuracy.<br>Not the logical flow.</p><p>This is why:</p><ul><li>one bad moment ruins a perfect journey</li><li>one great moment can redeem a boring one</li><li>onboarding matters more than complexity</li><li>support experiences define loyalty</li></ul><p>Once you get this, whole product strategies shift.</p><h3>So Why Did I Write About This Book — For Designers and PMs?</h3><p>Not because it’s psychology.<br> Not because it’s famous.<br> Not for the quotes.</p><p>But because <strong>this book explains the real reason doing product work right is so damn important:</strong></p><blockquote><em>You’re not fighting competitors.<br> You’re fighting your own mind.</em></blockquote><p>Every critique.<br>Every estimate.<br>Every “quick change.”<br>Every confident prediction.<br>Every roadmap conversation.</p><p>All of it is a cognitive battlefield — <br>and most teams don’t even know they’re in a fight.</p><p>Thinking, Fast &amp; Slow gave me the vocabulary for the quiet things I was already watching happen in the room:</p><ul><li>why confidence never equals correctness</li><li>why simple flows can fail</li><li>why spikes mislead teams</li><li>why predictions age poorly</li><li>why teams repeat the same mistakes</li><li>why research gets misread</li><li>why meetings spiral into “gut feelings” disguised as strategy</li></ul><p>This series exists for one reason:</p><p><strong>Because once you see these patterns, you can’t unsee them.<br>And once you can’t unsee them, you become dangerous — in the best possible way.</strong></p><h3>Your Takeaway</h3><p>If Articles 1 and 2 taught you to notice the mind<br> and notice the traps,</p><p>then Article 3 teaches you the skill that separates mid-level from truly senior:</p><p><strong>Build systems that protect the work<br>from the confidence of the people doing the work.</strong></p><p>The job isn’t:</p><ul><li>to be right</li><li>to predict perfectly</li><li>to “have amazing intuition”</li></ul><p>The job is:</p><ul><li>to design guardrails</li><li>to validate aggressively</li><li>to catch the wrong brain speaking</li><li>to separate stories from signals</li><li>to choose the frame, not be controlled by it</li><li>to optimize for what the <em>remembering user</em> will walk away with</li></ul><p>Teams that do this don’t magically avoid mistakes.<br>They just avoid the expensive ones.</p><p>And the leaders who do this — <br> designers or PMs — <br> become the calmest, clearest thinkers in the room.</p><p>Not because they know more.<br>But because they <strong>notice more</strong>.</p><p>That’s the real superpower.</p><p>That’s the point of this series.</p><p>And if you adopt this lens — <br>you won’t just build better products.<br>You’ll build better teams, better decisions, and better judgment.</p><p>The kind you only get once you understand how people think<br>before you try to design for them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=923ee358334a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Biases That Quietly Ruin Product Decisions]]></title>
            <link>https://medium.com/@riageorge1124/biases-that-quietly-ruin-product-decisions-38bd808d7715?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/38bd808d7715</guid>
            <category><![CDATA[thinking-fast-and-slow]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[human-psychology]]></category>
            <category><![CDATA[behavioral-economics]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Wed, 03 Dec 2025 03:46:28 GMT</pubDate>
            <atom:updated>2025-12-03T03:46:28.524Z</atom:updated>
            <content:encoded><![CDATA[<p><em>(Part 2 of the 3-part series on Thinking, Fast &amp; Slow for Product Teams)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8SrZk_oiPEoaxec7h7miQ.png" /></figure><p>If Article 1 was about <em>how</em> the mind works…<br>Article 2 is about <em>how that mind quietly blindsides your roadmap.</em></p><p>Because once you understand the two systems inside your head, the next uncomfortable truth becomes obvious:</p><p><strong>It’s not bad intentions that ruin product decisions.<br>It’s cognitive shortcuts.<br>And they happen fast.</strong></p><p>Every team — from Meta to Zomato to Uber — falls for these traps.<br>The teams that survive learn to recognise them early.<br>This article is your map for that.</p><p>Let’s break down the three big biases that silently shape what teams build.</p><h3>1. Anchoring — The First Number Wins</h3><p>Anchoring is simple:</p><p><strong>The first number you hear becomes the reference point for everything that follows.</strong></p><p>Even if that number is wrong.<br>Even if it’s random.<br>Even if everyone knows it’s ridiculous.</p><p>Your brain can’t help it.</p><h4>A real example: Uber’s surge pricing redesign</h4><p>When Uber redesigned the surge pricing screen, early tests showed riders hated seeing:</p><blockquote><em>“2.0x surge”</em></blockquote><p>Even if the price was fair.</p><p>That “2.0x” became the anchor.<br>It <em>felt</em> like a loss.<br>It triggered System 1: <strong>“I’m being cheated.”</strong></p><p>So Uber redesigned the UI to show <strong>actual upfront cost</strong>, not the multiplier.</p><p>The anchor changed — and so did user behaviour.</p><p><a href="https://www.uber.com/blog/research/the-effects-of-ubers-surge-pricing-a-case-study/"><em>(Source: Uber Design Blog, “Designing Upfront Pricing,” 2017)</em></a></p><h3>2. Availability — “Whatever I Remember Must Be True”</h3><p>Your brain assumes something is important<br> → if it’s easy to recall<br> → if it’s vivid<br> → if it recently happened<br> → if it emotionally popped.</p><p>But memory ≠ truth.</p><h4>A real example: WhatsApp’s panic over the ‘forwarded’ label</h4><p>After misinformation incidents went viral, WhatsApp faced enormous pressure.<br>Not because the overall volume of misinformation suddenly spiked…</p><p>…but because a <em>small number</em> of high-profile incidents became extremely memorable.</p><p>The availability bias shaped public perception.</p><p>So WhatsApp added:</p><ul><li>“Forwarded” labels</li><li>Limits on bulk forwarding</li><li>Friction on virality</li></ul><p>Not because the <em>average</em> user was spreading fake news — they weren’t — <br>But because the <em>vividness</em> of a few incidents dominated global memory.</p><p>Product teams fall for availability when they overreact to:</p><ul><li>One noisy customer</li><li>One dramatic bug</li><li>One viral tweet</li><li>One crazy user interview</li></ul><p>What’s vivid feels true.<br>But what’s common matters more.</p><h3>3. Representativeness — The Pattern That Was Never Real</h3><p>Representativeness bias is when your brain jumps to:</p><p><strong>“This looks like that… so it must be the same.”</strong></p><p>It swaps logic for vibes.<br>Probability for personality.</p><h3>A real example: Airbnb overestimating “professional hosts”</h3><p>For years, Airbnb assumed:</p><blockquote><em>“Multiple listings = more professional = higher quality.”</em></blockquote><p>A perfect-sounding pattern.</p><p>Except… not true.</p><p>Internal quality data eventually revealed:</p><ul><li>Single-home hosts → often more caring</li><li>Multi-property managers → sometimes less invested</li></ul><p>Airbnb had to rework ranking algorithms to stop overvaluing “professional-looking” hosts.</p><p><em>(Source: Airbnb Engineering, “Building a Pricing &amp; Quality Model,” 2018)</em></p><h4>Representativeness tricks you into assuming:</h4><ul><li>“This user <em>looks</em> like a power user.”</li><li>“This request <em>sounds</em> like a feature gap.”</li><li>“This problem <em>feels</em> similar to last quarter’s issue.”</li></ul><p>But vibes ≠ patterns.<br>Patterns ≠ truth.</p><h3>4. Substitution — Answering the Wrong Question</h3><p>This is the sneakiest bias.</p><p>When you face a hard question your brain can’t answer quickly — <br>System 1 silently replaces it with an easier one.</p><p>And you don’t even notice.</p><p><strong>Hard question:</strong></p><blockquote><em>“Is this new homepage variation better for long-term retention?”</em></blockquote><p><strong>Easy substituted question:</strong></p><blockquote><em>“Do I personally like this more?”</em></blockquote><h4>YouTube’s 2011 homepage redesign — where teams substituted criticism for quality</h4><p>When YouTube tested a simplified homepage in 2011, critics said:</p><blockquote><em>“It looks too empty.”<br>“It feels less informative.”<br>“Why remove so much content?”</em></blockquote><p>They were answering the easy question:</p><p><strong>“Does this look familiar to me?”</strong></p><p>But the real question was:<br><strong>“Does this reduce cognitive overload and increase watch time?”</strong></p><p>When rolled out, YouTube’s metrics shot up:</p><ul><li>Watch time increased</li><li>Bounce rates dropped</li><li>Homepage clarity improved</li></ul><p>Teams had been evaluating aesthetics, not outcomes.</p><p>That’s substitution.</p><h3>5. The Law of Small Numbers — Overreacting to Tiny Samples</h3><p>Your brain loves patterns so much<br> it sees them even where they don’t exist.</p><h4>A real example: Spotify’s early personalisation issues</h4><p>In Spotify’s early days, PMs repeatedly overreacted to tiny pockets of users:</p><ul><li>A micro-group bingeing a random playlist</li><li>A niche genre suddenly trending in one city</li><li>A burst of activity by a small cluster of superfans</li></ul><p>They would assume “trend” where there was actually <strong>noise</strong>.</p><p>This led to:</p><ul><li>irrelevant homepage recommendations</li><li>mislabelled “trends”</li><li>inaccurate algos</li></ul><p>Spotify later built larger-baseline models to avoid small-number illusions.</p><p>Small sample ≠ truth.<br> It’s just loud.</p><h3>6. Regression to the Mean — The Bounce-Back Nobody Expects</h3><p>When something is unusually high or low, it naturally moves back toward normal.</p><p>But teams mistake this for “impact.”</p><h4>A real example: Zomato’s 10-minute delivery spike</h4><p>In early 2022, Zomato saw:</p><ul><li>insane order spikes from PR buzz</li><li>unusually high day-one engagement</li><li>huge curiosity clicks</li></ul><p>Internal reactions were loud:</p><blockquote><em>“The future is 10-minute delivery!”</em></blockquote><p>Then…<br>everything regressed to the mean.</p><p>Order patterns stabilised.<br>Curiosity dropped.<br>Behaviours normalised.</p><p>The spike wasn’t the new normal — <br>it was a PR event.</p><p><a href="https://economictimes.indiatimes.com/tech/technology/startups-recalibrate-approach-to-ten-minute-deliveries-amid-operational-challenges/articleshow/92045165.cms"><em>(Sources: MoneyControl, Economics Times reports 2022)</em></a></p><p>Yet teams almost built entire roadmaps off the extreme day-one numbers.</p><p>That’s the trap.</p><h3>So what do designers &amp; PMs actually do with all this?</h3><p>The answer isn’t<br>“think harder”<br> or<br> “have better product sense.”</p><p>It’s way simpler — and way more powerful:</p><p><strong>Know which mind is talking.<br>Know which bias is shaping the room.<br>And design guardrails around the traps.</strong></p><p>Because your fast brain <em>will</em> take shortcuts.<br>Your team’s fast brain <em>will</em> jump to conclusions.<br>And your org’s fast brain <em>will</em> overreact to noise.</p><p>Guardrails stop that from derailing the work.</p><p>The easiest way to build those guardrails?<br>Use questions as checkpoints:</p><ul><li><strong>“Is this an anchor?”</strong></li><li><strong>“Are we reacting to a vivid story or an actual pattern?”</strong></li><li><strong>“Are we mistaking a vibe for truth?”</strong></li><li><strong>“Did we replace a hard question with an easy one?”</strong></li><li><strong>“Is this a spike or a trend?”</strong></li></ul><p>Great product people don’t eliminate biases — <br> <strong>they see them early, name them openly,<br> and design around them.</strong></p><p>They anchor on data, not opinions.<br>They check availability against real frequency.<br>They challenge “looks like” stories with base rates.<br>They catch substitution the moment intuition gets lazy.</p><p>Because here’s the truth big companies already know:</p><p><strong>Products don’t fail because teams are stupid.<br>Products fail because teams trust the wrong brain.</strong></p><p>And if you’re a designer or PM building for the real world…<br>these guardrails might be the difference between shipping something genuinely brilliant — <br>or something <strong>beautifully wrong</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38bd808d7715" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Two Minds Behind Every Product Decision]]></title>
            <link>https://medium.com/@riageorge1124/the-two-minds-behind-every-product-decision-ceb1967c604a?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ceb1967c604a</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ideation]]></category>
            <category><![CDATA[thinking-fast-and-slow]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Sat, 22 Nov 2025 11:37:13 GMT</pubDate>
            <atom:updated>2025-11-22T11:37:13.782Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How System 1 &amp; System 2 secretly run your design, your roadmap, your meetings, and your “intuition.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPjodvpgMzlqN1Mc0uXOzQ.png" /></figure><p>If you’ve ever sat in a product meeting wondering:</p><p><strong>“Why are smart people choosing the wrong thing… again?”</strong></p><p>Welcome to reality.</p><p>And I don’t mean “bad ideas.”<br> I mean the decisions that <em>feel</em> right in the moment — <br> everyone nods, confidence is sky-high — <br> and six months later you’re quietly asking:</p><p><strong>“…how did we miss something this obvious?”</strong></p><p>We blame deadlines. Pressure. Stakeholders.<br> But honestly?</p><p>Most bad product calls happen because of something much simpler:</p><p><strong>The brain we’re using to make them.</strong></p><p>And that brain has two modes.<br> Only one of them is actually doing the thinking.</p><p>Reading Daniel Kahneman’s <em>Thinking, Fast and Slow</em> made this painfully obvious — <br> Here’s the breakdown from a product and design lens.</p><h3>We all have two minds — only one feels like “you.”</h3><p>Psychologists call them <em>System 1</em> and <em>System 2</em>.<br> Forget the textbook labels. Think of them like this:</p><h3>System 1 — The Fast Brain</h3><p>The part of you that:</p><ul><li>reacts instantly</li><li>forms an opinion in half a second</li><li>jumps to conclusions</li><li>loves patterns</li><li>hates uncertainty</li><li>feels <em>absolutely sure</em> even when it’s <em>absolutely wrong</em></li></ul><p>This is the voice that glances at a design and goes:<br> <strong>“Hmm… something’s off.”</strong></p><p>It can’t explain why.<br> But it feels very confident anyway.</p><h3>System 2 — The Slow Brain</h3><p>The part of you that:</p><ul><li>thinks deliberately</li><li>analyses and questions</li><li>uses logic and data</li><li>burns actual energy</li><li>works slower but more accurately</li></ul><p>This is the version of you that thinks it’s in charge.</p><p>But here’s the truth most people never admit in a PRD:</p><p><strong>System 1 makes the decision.<br> System 2 writes the explanation.</strong></p><p>System 1 is the impulsive CEO.<br> System 2 is the exhausted PR team running behind it trying to justify everything.</p><h3>A scene every designer or PM has lived through</h3><p>You show two concepts.<br> Both well-designed. Both solid.</p><p>A stakeholder looks at them for <strong>1.5 seconds</strong> and says:</p><blockquote><em>“I like the first one more.”</em></blockquote><p>You ask why.</p><p>They go:<br> “Feels cleaner.”<br> “Feels more modern.”<br> “Users will get this.”</p><p>None of this is data.<br> None of this is insight.</p><p>It’s pure System 1 — <br> wearing a suit and pretending to be logic.</p><p>Then System 2 wakes up and politely backfills the reasoning:</p><p>“Yes, the symmetry aligns with best practices… also let’s A/B test to be safe.”</p><p>This isn’t ego.<br> <strong>This is biology.</strong></p><p>Your brain makes a snap judgment,<br> then invents reasons afterwards to sound reasonable.</p><p>The moment you understand this, the product finally begins to make sense.</p><h3>Product mistakes aren’t random — they’re predictable</h3><p>Go back and look at any product failure you’ve seen.</p><p>Almost all of them began as a System 1 decision:</p><ul><li>“This feature seems cool — users will love it.”</li><li>“This flow looks simpler.”</li><li>“It’s just a small change, two days max.”</li><li>“This feels like the right direction.”</li></ul><p>Feelings dressed up as facts.</p><p>This is why teams:</p><ul><li>overbuild features nobody asked for</li><li>underestimate timelines</li><li>overreact to loud but rare feedback</li><li>ignore boring data</li><li>copy other apps without context</li></ul><p>System 1 is steering.<br> System 2 is asleep in the backseat.</p><p>Why are our brains wired to fail like this? It comes down to efficiency.</p><h3>Why this happens: thinking is expensive</h3><p>Here’s the part most designers and PMs never consider:</p><p><strong>System 2 burns real energy.</strong><br> Your brain literally avoids using it unless forced.</p><p>System 1 is cheap and instant.<br> So your mind defaults to it.</p><p>That default quietly shapes everything:</p><ul><li>how roadmaps are prioritized</li><li>how estimates are made</li><li>how research is interpreted</li><li>how user behaviour is explained</li><li>how strategy is debated</li><li>how meetings spiral</li></ul><p>We think we’re thinking.<br> Most of the time, we’re just reacting.</p><h3>Why this matters for product and design teams</h3><p>Understanding these two systems immediately explains:</p><ul><li>why stakeholders react the way they do</li><li>why users behave “irrationally”</li><li>why meetings escalate</li><li>why your intuition sometimes lies to you</li><li>why some decisions “felt right” but weren’t</li></ul><p>Products are not built logically.<br> <strong>They’re built psychologically.</strong></p><p>Once you grasp this, you stop designing <em>only</em> wireframes — <br> and start designing your <strong>workflow, mindset, and decision environment</strong> too.</p><h3>A real example: redesigning a checkout flow</h3><p>System 1 reactions in a meeting:</p><ul><li>“This one <em>feels</em> smoother.”</li><li>“This layout <em>feels</em> more trustworthy.”</li><li>“This CTA <em>seems</em> more clickable.”</li></ul><p>These are blind guesses, not insights.</p><p>System 2 questions — the ones great teams ask:</p><ul><li>“What friction are we removing?”</li><li>“What metric will this change move?”</li><li>“What evidence supports this?”</li><li>“What trade-offs are we introducing?”</li><li>“How will we know early if this fails?”</li></ul><p>When teams don’t separate instinct from analysis,<br> <strong>intuition gets mistaken for wisdom.</strong></p><p>Then conversion drops, and nobody knows why.</p><h3>The real job of a product person?</h3><p>Getting both brains to work together.**</p><p>System 1 gives you:</p><ul><li>speed</li><li>creativity</li><li>pattern recognition</li></ul><p>System 2 gives you:</p><ul><li>discipline</li><li>clarity</li><li>structure</li><li>validation</li></ul><p>Teams that depend only on System 1<br> → make bold but reckless decisions.</p><p>Teams that depend only on System 2<br> → move slowly and stagnate.</p><p>The best teams know when to switch modes.</p><p>They say:</p><p><strong>“This is an intuition.<br> Let’s validate it as if we’re wrong.”</strong></p><p>That humility — that awareness — <br> is the quiet superpower behind great products.</p><h3>Think of this article as the lens</h3><p>Without this foundation, the next part — the biases — <br> will feel random and academic.</p><p>With this lens?</p><p>Anchoring, availability, representativeness, loss aversion…<br> all become <strong>predictable traps you’ll spot instantly.</strong></p><p>The next article will be where we break those down — <br> how they quietly ruin product decisions silently, confidently, and repeatedly.</p><p>But for now, just remember this:</p><p><strong>Most product decisions feel rational.<br> They’re actually fast-brain guesses.</strong></p><p>Your job isn’t to kill System 1.<br> <strong>It’s to train it.</strong><br> And once you do, the way you design, negotiate, estimate, build, and lead<br> will never be the same.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ceb1967c604a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Indian Apps Are Becoming “Busier” — And Why It Actually Works Here]]></title>
            <link>https://medium.com/@riageorge1124/why-indian-apps-are-becoming-busier-and-why-it-actually-works-here-bb4bc4e7272a?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb4bc4e7272a</guid>
            <category><![CDATA[india]]></category>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Thu, 20 Nov 2025 15:29:31 GMT</pubDate>
            <atom:updated>2025-11-20T15:29:31.134Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Indian Apps Are Becoming “Busier” — And Why It Actually Works Here</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KNRsD65slaZRUM9kuFKvFQ.png" /></figure><p>Open PhonePe, Zomato, Paytm, Blinkit, Meesho — really any India-first app — and one thing hits you immediately:</p><p><strong>A lot is happening on the screen.</strong></p><p>Tiles.<br> Labels.<br> Offers.<br> Quick actions.<br> Live statuses.<br> Features surfaced upfront.<br> Hardly any empty space.</p><p>And surprisingly… it works.<br> Not despite the density — but because of it.</p><p>This isn’t “bad UI.”<br> This is <strong>intentional density</strong>.<br> And in India, that density is a <em>product advantage</em>.</p><p>Let’s talk about why.</p><h3>1. Busy ≠ Bad — It’s Local Optimization</h3><p>Minimalism looks great on Dribbble.<br> But in the real world — especially India’s world — minimal often reads as:</p><ul><li>“Did it load?”</li><li>“Is something missing?”</li><li>“What do I tap?”</li></ul><p>Think about where Indian users are actually using apps:</p><ul><li>In shops</li><li>On the road</li><li>In crowded markets</li><li>Amid noise</li><li>With interruptions</li><li>With a low network</li><li>On mid-range devices</li></ul><p>A 2023 IIMA study on digital behaviour shows that Indian users rely more on <strong>visible cues</strong> because their environments are chaotic.</p><p>So a screen that looks “clean” to a designer… often feels “uncertain” to the user.</p><p>That’s why density isn’t a mistake — it’s context-aware optimization.</p><h3>2. Density = Trust (More Than Aesthetics)</h3><p>India is a low-trust environment for digital tasks:</p><ul><li>UPI failures</li><li>Network drops</li><li>OTP delays</li><li>Fraud concerns</li><li>App crashes during payments</li></ul><p>So apps compensate with <strong>visual reassurance</strong>.</p><p>Look at PhonePe’s home screen:<br> UPI, recharge, electricity, insurance, FASTag, bookings — all up front.<br> No digging.</p><p>Zomato shows categories, offers, trending dishes, safety badges, ETA, and order state all at once.</p><p>Blinkit instantly displays delivery time, categories, and deals.</p><p>To a Western designer, it looks “crowded.”<br> To an Indian user, it looks <strong>safe</strong>.</p><p>You see more.<br> You trust more.<br> You use more.</p><h3>3. The Sweet Spot: Dense, Yet Never Overwhelming</h3><p>This is the part most people misunderstand.</p><blockquote><strong><em>Good India-first design is dense — not chaotic.<br> Rich, not messy.<br> Explicit, not noisy.</em></strong></blockquote><p>The density is <em>structured</em>:</p><ul><li>Clear grouping</li><li>Predictable patterns</li><li>Obvious CTAs</li><li>Labels on everything</li><li>Strong visual hierarchy</li><li>Colour used meaningfully</li></ul><p>It’s density with intention.<br> Not density with abandon.</p><p>That’s the UI recipe that works here.</p><h3>4. Screenshots Are the Real UX in India</h3><p>One behaviour drives a LOT of Indian UX:</p><p><strong>People screenshot everything.</strong></p><p>UPI confirmations.<br> Bills.<br> Order status.<br> Maps.<br> Chats.<br> Offers.</p><p>And then they forward it on WhatsApp.</p><p>If your UI is too minimal, the screenshot loses context.<br> If it’s explicit, the screenshot becomes a clear communication artifact.</p><p>This single behaviour pushes Indian apps toward:</p><ul><li>More labels</li><li>More visible information</li><li>Clearer states</li><li>More context on screen</li></ul><p>Screenshots are not an edge case.<br> They’re part of the product.</p><h3>5. Minimalism Often Performs Worse Here</h3><p>While companies don’t publish internal A/B results, behavioural data supports what we see:</p><p>A UPI study found that <strong>~75% of Indian users increased digital spending</strong> because the interface felt:</p><ul><li>guided</li><li>certain</li><li>easy to follow</li><li>visually explicit</li></ul><p>Minimal screens remove those cues.<br> Dense screens <strong>reduce cognitive load</strong> in this specific context.</p><p>So the real rule is:</p><blockquote><strong><em>Simple = good</em></strong><em><br> </em><strong><em>Sparse = not necessarily good</em></strong><em><br> </em><strong><em>Clear = always good</em></strong><em><br> And in India, clarity lives inside visual richness.</em></blockquote><h3>6. A Crowded Market Forces Visibility</h3><p>Every major category in India has multiple strong players.<br> If you don’t show value instantly, users switch without hesitation.</p><p>So the UI becomes your <strong>storefront</strong>:</p><ul><li>What can this app do?</li><li>Why should I stay?</li><li>What’s new?</li><li>What’s useful right now?</li><li>What’s urgent?</li><li>What’s on offer?</li></ul><p>Minimalism hides value.<br> Indian apps <em>surface</em> value.</p><p>It’s not clutter — it’s differentiation.</p><h3>7. Ambiguity = Risk. And Users Avoid Risk.</h3><p>Indian users multitask constantly — managing customers, deliveries, calls, payments, orders, logistics, staff, and family, all on the same device.</p><p>Ambiguity is expensive.</p><p>So Indian apps use:</p><ul><li>clear labels</li><li>success confirmations</li><li>status updates</li><li>twice-visible CTAs</li><li>repetitive reassurances</li><li>predictable layouts</li></ul><p>Users don’t want “less.”<br> They want <strong>less confusion</strong>.</p><h3>8. What Designers Should Actually Take Away</h3><p>Here’s the real learning:</p><blockquote><strong><em>In India, good UX doesn’t mean fewer elements.<br> It means fewer doubts.</em></strong></blockquote><p>When building India-first:</p><ul><li>Don’t hide features behind hamburger menus.</li><li>Don’t remove labels just because it looks cleaner.</li><li>Design for screenshot-readability.</li><li>Surface the top actions immediately.</li><li>Make everything obvious.</li><li>Prioritize certainty over aesthetics.</li></ul><p>Minimalism is a visual trend.<br> Clarity is a human need.</p><p>And in India, clarity often needs more visibility, not less.</p><h3>Final Thought</h3><p>If there’s one thing designing for Indian users taught me, it’s this:</p><p><strong>People don’t resist visual density.<br> They resist uncertainty.</strong></p><p>And once you design for certainty — not minimalism, not aesthetics, not trends — everything else falls into place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb4bc4e7272a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Instagram Broke a 10-Year Pattern (And Why It Makes Perfect Sense)]]></title>
            <link>https://medium.com/@riageorge1124/why-instagram-broke-a-10-year-pattern-and-why-it-makes-perfect-sense-4329b898b638?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4329b898b638</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[instagram]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Wed, 19 Nov 2025 12:21:27 GMT</pubDate>
            <atom:updated>2025-11-19T12:21:27.122Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oqtu0QS8ZIbG-TgF58_vIg.png" /></figure><p><strong>A small navigation tweak that reveals how products shape — and are shaped by — user behaviour.</strong></p><p>If you want to understand how product decisions are really made at scale… watch what Instagram does quietly.<br> Not the flashy AI announcements.<br> Not the new filters.<br> The tiny navigation tweaks that billions of people suddenly have to re-learn.</p><p>Recently, Instagram pushed one such change:<br> Messages and Search moved into a <strong>swipeable </strong>bottom bar.</p><p>Small? Yes.<br> Accidental? Never.<br> And the reasoning behind it is something product teams often <em>overlook completely</em>.</p><p>If you’re a designer, PM, or someone who likes to understand the psychology behind product choices… this change is a masterclass.</p><h3>So… why move something that already works?</h3><p>For almost a decade, DMs sat neatly in the top-right corner.<br> The placement was universal across apps, familiar to everyone.</p><p>Then overnight: boom.<br> They’re in thebottom nav that swipes like a mini operating system.</p><p>It feels odd at first, because the industry has taught us that</p><p>“familiar = good.”</p><p>But here’s the uncomfortable truth most teams learn too late:</p><p><strong>Users don’t use interfaces.<br> Users use habits.</strong></p><p>And habits change.</p><h3>DMs aren’t an accessory anymore — they’re the main event</h3><p>For Gen Z, Instagram isn’t just a content app.<br> It’s a messaging app disguised as a content app.</p><p>The loop is:</p><p><strong>Watch → react → share in DM → talk → repeat.</strong></p><p>Keeping DMs in the corner meant that Instagram was making its most valuable loop… harder to reach.</p><p>And Instagram doesn’t do “harder to reach.”</p><h3>What looks like UI is actually behaviour engineering</h3><p>Here’s what this bottom navigation really does:</p><ul><li><strong>Shortens time-to-action</strong> (faster access to DMs = more messages sent)</li><li><strong>Increases one-hand reachability</strong> (thumb-friendly = higher frequency)</li><li><strong>Boosts cross-navigation</strong> (search ↔ DMs ↔ Reels ↔ feed)</li><li><strong>Strengthens habit loops</strong> (the swipe becomes muscle memory)</li></ul><p>None of this is about aesthetics.</p><p>It’s about engagement.<br> Retention.<br> And the billion-user game of “how do we reduce friction by 0.1 seconds?”</p><h3>But won’t people complain?</h3><p>Of course they will.<br> People complained about:</p><ul><li>Stories</li><li>Reels</li><li>The heart tab moving</li><li>The Explore tab moving</li><li>Timeline changes</li></ul><p>Everything, basically</p><p>Meta knows the pattern:</p><p><strong>Week 1:</strong> “What is this?”<br> <strong>Week 2:</strong> “I hate this.”<br> <strong>Week 3:</strong> <em>Uses it 100 times a day without thinking.</em></p><blockquote>Short-term outrage is cheap.<br> Long-term stagnation is expensive.</blockquote><p>That’s the bet.</p><h3>Why Instagram can change things Google never will</h3><p>Compare Instagram and Google Search.</p><p>Google’s UI barely changes because:</p><ul><li>Stability = trust</li><li>The interface <em>is</em> the brand</li><li>People come to Google for certainty</li></ul><p>Instagram’s interface, on the other hand:</p><ul><li>Is always evolving</li><li>Is driven by engagement metrics</li><li>Is competing in the attention economy</li></ul><p>One treats its UI as sacred.<br> The other treats it as an experimental lab.</p><p>Both are right — for their context.</p><h3>If you take one thing from this, let it be this question:</h3><p>Don’t ask<br> <strong>“Why did they redesign this?”</strong></p><p>Ask<br> <strong>“What behaviour were they trying to unlock?”</strong></p><p>Every meaningful product shift can be traced back to:</p><ul><li>A metric</li><li>A habit loop</li><li>A friction point</li><li>A future bet</li></ul><p>The navigation change isn’t about icons.<br> It’s about steering billions of micro-behaviours in a new direction.</p><h3>So What Do We Take Away From This?</h3><p>Watching Instagram break a 10-year pattern reminded me of something simple but easy to miss:</p><p>People don’t mind change.<br> They think more slowly.</p><p>Shift behaviour, reduce friction, shorten the path — users adapt faster than we expect.<br> Instagram leans into that. They measure it, tweak it, and ship when the numbers prove the behaviour is ready to move.</p><p>And for anyone building products, big or small, that’s the real lesson here:</p><p>If a change makes the core action easier, the habit will follow.<br> If it doesn’t… no amount of UI cleverness can save it.</p><p>That’s all this navigation update really is — not a design experiment, but a behaviour bet.</p><p>And honestly? It’s a bet worth studying.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4329b898b638" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why MSMEs Trust WhatsApp More Than Your App]]></title>
            <link>https://medium.com/@riageorge1124/why-msmes-trust-whatsapp-more-than-your-app-aefcf26a6e81?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/aefcf26a6e81</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[msmes]]></category>
            <category><![CDATA[user-psychology]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Sun, 13 Jul 2025 18:19:03 GMT</pubDate>
            <atom:updated>2025-07-13T18:19:03.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jSvaGvYF1JmyvzoePtu7_Q.jpeg" /></figure><p>While designing for a digital product aimed at MSME business owners in India, we had a clear goal:</p><p>Help users network, close business deals, and communicate — all in one place.</p><p>We built the usual suspects:<br> → A content <strong>feed</strong><br> → A <strong>networking</strong> tool<br> → A <strong>chat</strong> system that worked inside the product</p><p>We expected users to discover leads, share content, and message each other seamlessly within the ecosystem.</p><p>But that’s not what happened.</p><p>Despite the features, nearly every meaningful interaction shifted <strong>immediately</strong> to WhatsApp.</p><h3>👀 What the Field Told Us (Loud and Unmistakably)</h3><h4>📎 Content Sharing</h4><p>We shared videos, articles, and relevant business insights inside the app.<br> Users consumed the content — and said:<br> <strong>“Can you send it on WhatsApp? I want to share it with my staff.”</strong></p><h4>🤝 Networking</h4><p>Users are connected with relevant business owners inside our tool.<br> The first message? Always the same:<br> <strong>“Let’s talk on WhatsApp.”</strong></p><h4>🧵 Business Listing</h4><p>Some users even added their WhatsApp number directly in their profile description:<br> <strong>“Reach out to us here: [Phone number]”</strong><br> — bypassing the app’s messaging flow entirely.</p><h3>🧭 Why It Happens</h3><p>At first, this looked like low feature adoption.<br> But the truth was sharper:</p><blockquote><strong><em>Users weren’t rejecting the product.<br> They were sticking to what already worked.</em></strong></blockquote><p>For MSMEs, WhatsApp isn’t a fallback — it’s the <em>default</em>.</p><h3>✅ Why WhatsApp Wins (Every Time)</h3><p>WhatsApp Works Because…For MSMEs, That Means…</p><p>✔️ Text, voice, image-friendly • Speakthe way they want — no “correct” format✔️ Always availableThey don’t have to remember which app had what✔️ Low data, low riskWorks even in bad networks, doesn’t break✔️ Familiar interfaceNo onboarding, no cognitive jump✔️ Already a habitOne less change in a day full of work</p><p>It’s not just about convenience.<br> It’s about <strong>control, safety, and speed.</strong></p><h3>🛑 The Hard Truth: We Couldn’t Act on It</h3><p>The biggest challenge?</p><p>We have not been able to implement the solutions we knew might help due to multiple reasons.<br> Building WhatsApp integrations? Not on the table.</p><p>So we sat with the insight, and had to ask a harder question:</p><blockquote><em>“If we can’t fix it now, how do we make sense of it as designers?”</em></blockquote><h3>🧠 Here’s What We Wished We Could Do</h3><p>We couldn’t ship these yet, but here’s what we believed would have made a difference:</p><h4>🔁 Build Bridges, Not Silos</h4><ul><li>Add <strong>“Send to WhatsApp”</strong> for content, profiles, and updates</li><li>Let users share their business card with one tap, formatted for WhatsApp</li></ul><h4>🤝 Design for Handoff, Not Lock-In</h4><ul><li>Build flows that expect users to leave the app and come back</li><li>Make content easy to screenshot, share, and forward — even if it’s not “tracked”</li></ul><h4>🧠 Use Real Language</h4><ul><li>“Send an intro” → instead of “Connect with this business”</li><li>“Talk to someone like you” → instead of “Start conversation”</li></ul><p>We didn’t build these. But the behavior told us: <strong>this is where the product should have gone.</strong></p><h3>🔍 What Others Are Doing (Right)</h3><p>We’re not the only ones seeing this shift.<br> Several India-first MSME apps are already <em>working with</em> WhatsApp, not against it:</p><p>They don’t compete with WhatsApp.<br> They <strong>integrate into it.</strong><br> They make it part of the system — not something users have to “switch out” of.</p><h3>✨ Final Reflection</h3><p>Designing for MSMEs taught me this:</p><blockquote><em>If you want to serve real businesses,<br> </em><strong><em>You don’t build against behavior.<br> You build inside it.</em></strong></blockquote><p>Sometimes you don’t get to ship what you believe in.<br> But observing what <em>is</em> — and holding space for <em>what could be</em> — is design work, too.</p><p>And if this reflection helps even one more team question why their in-app messaging isn’t sticking — it’s already done its job.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aefcf26a6e81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Designing for MSMEs: What I Learned, Why They Matter, and Why We Keep Getting It Wrong]]></title>
            <link>https://medium.com/@riageorge1124/designing-for-msmes-what-i-learned-why-they-matter-and-why-we-keep-getting-it-wrong-1f05e4683272?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f05e4683272</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[msmes]]></category>
            <category><![CDATA[design-for-india]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Sun, 06 Jul 2025 19:18:17 GMT</pubDate>
            <atom:updated>2025-07-13T14:55:45.274Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*340yvyNA_OXYYUEbaz0qvQ.png" /></figure><p>When I started designing for a flagship app serving the MSME (Micro, Small &amp; Medium Enterprise) sector, I assumed I’d be designing for “smaller businesses.” I expected the usual: simpler dashboards, cleaner forms, a mobile-first layout.</p><p>I was wrong. What I encountered instead was a user group that <strong>thinks completely differently</strong> — and taught me far more than any product spec or stakeholder brief ever could.</p><p>This article is a reflection on that journey. It’s for designers, researchers, and product thinkers trying to solve for the real India — beyond personas and polished pitch decks.</p><h4><strong>🧭 MSMEs Aren’t Just Smaller Enterprises — They’re a Whole Different World</strong></h4><p>Let’s get this straight: MSMEs are not “startups with less money.”</p><p>They are <strong>risk-aware</strong>, context-bound, deeply personal businesses — often <strong>run by one person managing cash, customers, logistics, and tech support all at once.</strong></p><p>And yet, <strong>they’re expected to adopt software</strong> designed by teams who’ve never once stepped into their world.</p><p><strong>Here’s what I learned:</strong></p><ul><li>They operate in cluttered contexts — shops, storerooms, homes, roadside stalls.</li><li>They don’t fear technology — they fear breaking trust with a customer.</li><li>They don’t want dashboards — they want confidence that the job’s done.</li><li>They don’t read manuals — they ask their nephew or a WhatsApp group.</li></ul><p>These users are smart. Not digitally fluent, maybe — but <strong>frugal, adaptable, and brutally efficient</strong> with what works.</p><h4>📉 What We Often Get Wrong as Designers</h4><ol><li>Designing for Features, Not Outcomes:</li></ol><p>We keep adding features, assuming they will “solve” for adoption. But if a user can’t even trust the login screen or gets stuck resetting passwords, <strong>nothing else matters</strong>.</p><p>2. Ignoring Emotional Friction:</p><p>For many MSMEs, adopting a new tool isn’t a cool trial — it’s a <strong>social risk</strong>. If they fail in front of staff, friends, or customers, <strong>it damages reputation</strong>.</p><p>3. Assuming Digital Confidence:</p><p>We design tooltips, filters, and multi-step flows assuming “basic literacy.” But for a user toggling between calls, deliveries, and billing, that friction <strong>isn’t cognitive — it’s contextua</strong>l.</p><p>4. Treating WhatsApp as a Competitor</p><p>WhatsApp isn’t their fallback. It’s their <strong>default system</strong>. Because it works. Because it’s trusted. Because it doesn’t ask them to change who they are.</p><p><strong>WhatsApp wins not because it’s better tech — but because it respects their mental model.</strong></p><h4>🔄 Lessons From the Field</h4><p>Here are the takeaways that truly changed how I design:</p><ul><li>Design <strong>certainty</strong>, not just clarity. (E.g., feedback when something is saved)</li><li>Reduce<strong> decision load</strong> at every step. (E.g., don’t ask what can be auto-configured)</li><li>Optimize for <strong>low-data, one-handed usage</strong>. Always test in a busy room with a 3G connection.</li><li>Build <strong>trust</strong> <strong>slowly</strong>. First solve one problem well. Then layer on the rest.</li></ul><h4><strong>💬 Why This Study Matters (for Designers &amp; Researchers)</strong></h4><p>MSMEs form <strong>30%+ of India’s GDP</strong> and are deeply embedded in rural, semi-urban, and local economies.</p><p>If we don’t design for them, we design for exclusion.</p><p>This article is for:</p><ul><li>🎯 Designers building beyond the English-first, startup bubble</li><li>🔍 Researchers wondering why their testing doesn’t translate into real-world adoption</li><li>🚀 Teams that want to design tools that are <strong>used</strong>, not just launched.</li></ul><h4><strong>✨ Final Reflection</strong></h4><p>Designing for MSMEs taught me that UX is not about flow — it’s about <strong>empathy at context speed</strong>.</p><p>It’s made me a better listener. A slower thinker. A sharper simplifier.</p><p>And if this post sparks even one more product team to sit with a kirana shop owner, a delivery partner, or a printing press operator — it’s done its job.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f05e4683272" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reimagining Zoom for Education: A Strategic UX Case Study on Transforming Remote Learning…]]></title>
            <link>https://medium.com/@riageorge1124/reimagining-zoom-for-education-a-strategic-ux-case-study-on-transforming-remote-learning-7fe01f3269c9?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fe01f3269c9</guid>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Fri, 13 Jun 2025 19:24:56 GMT</pubDate>
            <atom:updated>2026-05-14T16:08:56.144Z</atom:updated>
            <content:encoded><![CDATA[<h3>Reimagining <strong>Zoom</strong> for Education: A Strategic UX Case Study on Transforming Remote Learning Experiences</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w9owyzDF1ggW3uXyrGHoZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fljKUIieGPketVNk1rM76w.png" /><figcaption><a href="https://www.devlinpeck.com/content/online-learning-statistics">Citation Link 1</a>; <a href="https://www.devlinpeck.com/content/online-learning-statistics">Link 2</a>;<a href="https://www.magnetaba.com/blog/e-learning-online-learning-statistics"> Link 3</a></figcaption></figure><h4><strong>Business Problem:</strong></h4><blockquote><em>Zoom is widely used in education, but it wasn’t built for learning. Its business-focused interface lacks critical tools for engagement, classroom management, and accessibility. As education becomes increasingly hybrid and digital-first, Zoom must evolve beyond video calls to support real teaching.</em></blockquote><blockquote><em>Why does it matter?</em></blockquote><blockquote>With the global shift to online learning, there is a significant opportunity for Zoom to become the go-to education platform by addressing these gaps.</blockquote><h4><strong>Business Opportunity:</strong></h4><p>There is a clear opportunity for Zoom to reposition itself as the go-to platform for remote learning by addressing the unmet needs. By evolving its product to support integrated classroom workflows better, enhance engagement, and improve accessibility, Zoom can redefine online education and capture long-term market leadership in the education sector.</p><p>📌<em>According to </em><a href="https://www.holoniq.com/notes/global-education-technology-market-to-reach-404b-by-2025?_hsenc=p2ANqtz-9MZtQbIAOnW_HGJGJgtYS2w94lKoJgMN8jiiCVh8EMrcstRhbpRLRpRhPTFeGWI6emVUQXpLbfCbiy0HCNnHzZHNijZQ"><em>Holon&#39;s </em></a><em>2024 Global Education Report, the global EdTech market is projected to reach </em><strong><em>$404B by 2025</em></strong><em>, with </em><strong><em>online collaboration tools making up 22%</em></strong><em> of classroom technology budgets.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lWHnAL9zRX5-KJQ8zHRSMA.png" /></figure><h3>Zoom is everywhere in education. It was never built for it.</h3><p>I started noticing this when I kept hearing the same frustration from teachers around me. Not “Zoom is bad.” Just — “it doesn’t really work for teaching.” And the more I listened, the more I realised that nobody had actually designed Zoom <em>for a classroom</em>. They’d designed it for a conference room and handed it to educators.</p><p>That bothered me enough to do something about it.</p><p><strong>My role:</strong> UX Research, Product Strategy, Concept Design <strong>Timeline:</strong> June 2025 <strong>Methods:</strong> Secondary research, competitive analysis, 15 user interviews, surveys, usability testing</p><p>So I started where every good design problem starts. With the people living inside it.</p><p>I spoke to 15 educators — K–12 teachers, university professors, special education teachers. I asked them to walk me through a normal class day on Zoom. Not what they wished it could do. Just what actually happens.</p><p>The stories were almost identical.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*zrRNPUc7ZKq9Syku1wN7bg.png" /></figure><p>Four different people. Four versions of the same problem.</p><p>I also ran a survey with the same group. The numbers confirmed what the stories suggested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5yUdcJcpNfloYd3EyXEwxA.png" /><figcaption>PRIMARY RESEARCH</figcaption></figure><p>80% said student engagement was their biggest challenge. 53% were dissatisfied with Zoom’s current education features. 73% were still tracking attendance manually. Every. Single. Session.</p><p>Before proceeding, I wanted to understand the competitive landscape. Who else was trying to solve this? What were they getting right that Zoom wasn’t?</p><p>I looked at Google Classroom, Microsoft Teams for Education, and BigBlueButton. These are platforms with real adoption in Indian classrooms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3PshULidAci42lc_8eExeg.png" /></figure><p>The gap was clear. Zoom had the video. Everyone else had built around it — scheduling, attendance, analytics, LMS integration. BigBlueButton stood out for one specific reason: they used actual learning science to design their features. Auto-generated quizzes from slide content. Activity scores. Engagement tracking tied to pedagogy. They built for how teaching actually works.</p><p>Zoom built their product for how meetings work. That’s the problem.</p><blockquote>“To understand the gap more precisely, I mapped out how feature effectiveness could actually be measured in a classroom context.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fodyv7t60Eg2xlGVEMmA_Q.png" /><figcaption>Feature Audit</figcaption></figure><p>After all the research, five things became impossible to ignore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2jpUw5YPxEjLbI8uzXVtgg.png" /><figcaption>KEY INSIGHTS</figcaption></figure><p>Teachers are losing the first 10 minutes of every class to manual attendance. Students with cameras off are invisible — no way to know who’s lost, who’s bored, who’s gone. Breakout rooms get avoided entirely because the setup delay kills momentum. Files shared in chat disappear the moment the session ends. And only 27% of teachers feel Zoom supports special needs students well.</p><p>These aren’t feature requests. They’re workflow failures happening every single day.</p><p>I needed to understand who, specifically, I was designing for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZB5J1buufS9bZrV6fXrMPg.png" /><figcaption>User personas</figcaption></figure><p>I focused on educators as the primary target — not students, not IT admins. Because here’s the thing: fix the teacher’s experience and everything downstream improves. Student engagement, learning outcomes, tool adoption. The educator is the leverage point.</p><p>Here’s what a typical class session looks like for a teacher right now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KW8ZBOvvU5n8e4SWX-0F9g.png" /><figcaption>CURRENT USER JOURNEY</figcaption></figure><p>Six stages. Every stage has friction. The pattern is consistent — teachers are spending their cognitive energy on logistics instead of teaching. That’s not a Zoom problem. That’s a design problem.</p><p>The core insight I kept coming back to: <strong>Zoom gives you a video call. It doesn’t give you a classroom.</strong></p><p>So I started exploring what a classroom could look like.</p><p>I came up with 8 directions across three areas — engagement, automation, and accessibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWXDNaQNjjc11I_W6BagAQ.png" /><figcaption>IDEATION BOARD</figcaption></figure><p>Smart Poll Generator. Focus Mode. Hand-Raise Queue. Task Timer. Auto Attendance. Post-Class Summary. Adaptive Video Quality. Live Captioning.</p><p>I put each one through three filters: Is it realistic to build without infrastructure changes? Does it solve more than one pain point? Does it live inside Zoom’s existing ecosystem?</p><p>Two failed immediately. Smart Poll Generator involved complex AI backend. Adaptive Video Quality is infrastructure-level — not a UX problem to solve.</p><p>Four were good but too narrow. Each solved one thing. Good features, not solutions.</p><p>Two were strong: Auto Attendance and Hand-Raise Queue. High-frequency pain points. Could work together.</p><p>And then I realised the strongest answer wasn’t a single feature. It was bringing everything together into a single interface built around how educators actually teach. So I went ahead and digitised teaching</p><p>That became <strong>Zoom Classboard.</strong></p><p>Why did Classboard win over everything else?</p><p>It solves five pain points in one place. It doesn’t require Zoom to rebuild their infrastructure. It lives inside the existing app. And every single feature was something an educator asked for directly in the interviews.</p><p>It’s not a new app. It’s a new way to run a classroom inside the one teachers are already using.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U78-2BzohNkuYdvextgTfw.png" /><figcaption>PROPOSED JOURNEY</figcaption></figure><p>The design is split into three phases that mirror how teaching actually works.</p><p><strong>Before class:</strong> A session builder, not just a calendar invite. You set a lesson title, a learning goal, a subject and grade level. You can attach pre-read materials and an optional quiz that students complete before joining. Students arrive prepared. The class starts with context, not cold.</p><p><strong>During class:</strong> A persistent control hub. Auto-attendance that logs joins and sends parent alerts if a student is 15 minutes late. An engagement tracker showing focus %, poll responses, and participation. A tool dock that includes : polls, whiteboard, breakout and timer that is always visible, one tap away. A hand-raise queue that prioritises who needs attention. All of this in one place, without breaking teaching rhythm.</p><p><strong>After class:</strong> An auto-generated report. Attendance timestamps. Tool usage data. Average talk time. An engagement score teachers can track over time. A follow-up flag for students who disengaged. Export to PDF or sync to LMS.</p><p>The shift: from “join a meeting” to running a structured, data-backed classroom.</p><p>I tested early-stage screens with one school teacher and two college students. Scenario-based walkthrough in Figma.</p><p>Some things worked straight away. The layout felt intuitive. The auto-attendance and parent alert made immediate sense. Teachers liked seeing live engagement data.</p><p>Some things broke. Pre-class materials disappeared once the session started — teachers couldn’t refer back to them mid-class. The engagement tracker needed clearer visual cues. The post-class report didn’t tell teachers what to <em>do</em> next.</p><p>So I fixed them. Pre-class materials now persist in a tab during the live session. The hand-raise queue uses colour and icon priority to guide attention. The post-class report has a “Send Follow-Up” button for flagged students.</p><p>That’s what testing is for.</p><p>If I could do this again, I’d narrow the research focus earlier. I interviewed across three user segments — teachers, students, admins. Useful context, but it diluted the synthesis phase. I should have gone deeper on educators from day one.</p><p>What I’d build next: high-fidelity screens, a second round of testing with active K–12 teachers in low-bandwidth environments, and eventually — LMS integration. That’s the real unlock. Zoom connecting natively with Canvas, Moodle, Google Classroom. That turns it from a video add-on to a core part of how schools run.</p><p>The thing that stayed with me through all of this: teachers are always on. They’re managing thirty students, a lesson plan, technical issues, and accessibility needs at the same time. Every extra tap costs them. Every buried menu costs them.</p><p>The best thing a product can do for an educator is get out of the way.</p><p>That’s what I tried to build.</p><p><em>Ria George · Product Designer · </em><a href="http://riageorge.designfolio.me/"><em>riageorge.designfolio.me</em></a><em> · @humansoverproducts</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fe01f3269c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designers: The Unofficial Behavioral Economists]]></title>
            <link>https://medium.com/@riageorge1124/why-arent-users-hooked-on-your-design-b27c44a7c4bb?source=rss-52fc212712d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b27c44a7c4bb</guid>
            <dc:creator><![CDATA[Ria George]]></dc:creator>
            <pubDate>Tue, 26 Mar 2024 18:32:24 GMT</pubDate>
            <atom:updated>2024-04-09T14:03:30.926Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TILfbrHH4tmtiqVU.jpg" /></figure><p>Think designing is just about aesthetics? Far from it. It’s not merely about choosing the perfect shade of blue; it’s about influencing choices and shaping desires with the precision of a behavioral economist. You’re not just making things look pretty; you’re the mastermind crafting the narrative of desire itself, often without people realizing they’re being led down this meticulously designed path.</p><p><strong>Digging Into Behavioral Economics</strong></p><p>Why do we end up binge-watching shows that are just “meh” or impulsively buying things we don’t need? It’s all about the emotional tugs and biases that steer us — far from the logical beings we fancy ourselves to be. Behavioral economics delves into this chaos, uncovering the why behind our “one more episode” at 2 AM or that irresistible sale that wasn’t even on our radar.</p><p><strong>Why This Matters to Designers</strong></p><p>Imagine predicting user behavior before even they can. That’s the edge behavioral economics gives you. It’s about designing experiences that resonate so deeply, that they tap into the primal part of our being.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F9915210&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fmichael-scott-why-are-you-the-way-you-are-theoffice-steve-carell-why-gif-9915210&amp;image=https%3A%2F%2Fmedia.tenor.com%2FUtC62ENB49YAAAAF%2Fmichael-scott-why-are-you-the-way-you-are.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/09fbd8d857d068afcc7517857caa9d27/href">https://medium.com/media/09fbd8d857d068afcc7517857caa9d27/href</a></iframe><p><strong>A Designer’s Guide to the Mind</strong></p><p>Let’s take a stroll through the human psyche and see behavioral economics at work in design:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B74Rrz7l1WqCQ9oeVD1-Gw.jpeg" /><figcaption>Loss Aversion seen in Spotify</figcaption></figure><ol><li>Loss Aversion: Like holding onto a gift you never liked because ditching it feels wasteful? That’s our aversion to loss in action. When Spotify offers free premium trials, letting go becomes as tough as returning a borrowed puppy. It’s not just a trial; it’s an experience users can’t bear to lose.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5graIGexCMag3DvvngELA.png" /><figcaption>Anchoring Effect seen in Amazon</figcaption></figure><p>2. Anchoring Effect: Ever felt like you scored a deal on a “discounted” item? The initial price sets your expectations. Amazon’s “list price” next to the “sale price” makes you feel like you’re getting a bargain, even if you never intended to spend that much.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ua6KEGDR8oE5Zoo1CNoLVg.png" /><figcaption>IKEA effect seen in Canva</figcaption></figure><p>3. The IKEA Effect: Remember that slightly off-kilter table you assembled? Your affection for it is rooted in the effort you invested. When a platform like Canva allows users to customize their designs, it becomes more than a tool; it becomes a canvas for personal expression.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*P7c-oCRQJ9OsU376J6kCSw.png" /><figcaption>Decoy effect seen in Figma</figcaption></figure><p>4. The Decoy Effect: Decision paralysis kicks in with too many choices, but a worse third option can clarify your decision. This is like when a menu offers an overpriced option, making the moderately expensive dish suddenly seem reasonable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zS2d8EiY1-gT3Spr9ANqWA.png" /><figcaption>Endowment Effect seen in Instagram</figcaption></figure><p>5. Endowment Effect: Digital or not, owning something makes us value it more. People place a higher value on things they own or intend to buy. On Instagram, users tailor their feeds and stories, transforming the app into their personalized showcase. It becomes more than an app; it’s a reflection of their world.</p><p><strong>Keeping It Real and Ethical</strong></p><p>Here’s the deal: wielding this kind of influence means you’ve got to play by the rules. No underhanded tactics. Think of it as using your powers for good, guiding users like a trustworthy sidekick, not leading them astray.</p><p><strong>Dive Deeper Into Design</strong></p><p>With this understanding, you’re not just designing; you’re uncovering what truly engages people. Each tap and swipe is a clue in decoding what makes an experience genuinely captivating. Remember, you’re not just ticking off tasks; you’re embarking on a quest to discover the essence of memorable design.</p><p>Now, take these insights for a spin. Watch how they play out in real life and in your designs. The goal? Guide, don’t manipulate; enhance, don’t deceive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b27c44a7c4bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>