<?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 Ren Chang, SOO on Medium]]></title>
        <description><![CDATA[Stories by Ren Chang, SOO on Medium]]></description>
        <link>https://medium.com/@renchangsoo?source=rss-fecee46e039a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JtQBqBQ1mPqFlnNDeI8KIQ.jpeg</url>
            <title>Stories by Ren Chang, SOO on Medium</title>
            <link>https://medium.com/@renchangsoo?source=rss-fecee46e039a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:58:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@renchangsoo/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[Kristoff Could Have Been the Hero, But He Chose to Be the Guide]]></title>
            <link>https://renchangsoo.medium.com/kristoff-could-have-been-the-hero-but-he-chose-to-be-the-guide-db145a3dbe6a?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/db145a3dbe6a</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[disney-design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 00:01:03 GMT</pubDate>
            <atom:updated>2026-08-14T00:01:03.089Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H3GmeOfSjzWZU4WFap2J0w.png" /></figure><p>Anna needed someone to save her.</p><p>She got an ice harvester with a reindeer.</p><p>Kristoff wasn’t polished. He wasn’t royal. He questioned her judgment within minutes of meeting her.</p><p>“You got engaged to someone you just met?”</p><p>He didn’t promise to fix anything. He negotiated supplies. He told her she was making bad decisions. He talked to his reindeer.</p><p>Not exactly prince material.</p><p>And yet — he was the only one who actually helped.</p><blockquote>What if the best collaborator isn’t the one who rescues you — but the one who walks beside you?</blockquote><h3>🧊 The Expert Who Didn’t Look Like One</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/0*ubuzeZ6T-UL5rEMf" /></figure><p>Kristoff knew the North Mountain better than anyone in Arendelle.</p><p>But he didn’t look the part. He was covered in ice, lived with trolls, and had a reindeer as his best friend.</p><p>We dismiss domain experts because they don’t fit our mental model of “expert.”</p><ul><li>The person who knows your users best might not have the right title.</li><li>The one who sees the system clearly might not present well in meetings.</li><li>The colleague who’s been doing the unglamorous work for years might have more insight than the consultant who arrived last week.</li></ul><p>Kristoff’s expertise wasn’t polished. It was earned — through years of ice harvesting that no one saw and no one celebrated.</p><h3>🪞 The Mirror, Not the Cheerleader</h3><p>Anna wanted validation. Kristoff gave her honesty.</p><p>“You got engaged to someone you just met?”</p><p>He wasn’t being difficult. He was naming what everyone else was too polite to say.</p><blockquote>Good research means questioning what users say they want.<br>Good collaboration means having someone willing to poke holes before it’s too late.</blockquote><p>Kristoff wasn’t a cheerleader. He was a mirror.</p><p>That honesty cost him nothing. It earned him everything.</p><h3>🤝 Trust Earned, Not Declared</h3><p>Anna didn’t trust Kristoff immediately. Why would she?</p><p>He earned it through action.</p><ul><li>He showed up when the wolves attacked.</li><li>He carried her through the storm.</li><li>He came back for her when he didn’t have to — when walking away would have been easier.</li></ul><p>He didn’t promise outcomes. He delivered presence.</p><blockquote>Trust isn’t declared. It’s demonstrated.</blockquote><p>One risk at a time.</p><h3>⚡ The Moment He Stepped Back</h3><p>At the castle gates, Kristoff could have stayed.</p><ul><li>He could have insisted on being there.</li><li>He could have made sure she was safe.</li><li>Every instinct told him not to leave.</li></ul><p>Instead, he walked away.</p><p>He trusted her choice — even when it was the wrong one. He let her go back to Hans, the man she believed would save her.</p><ul><li>It would have been easier to stay.</li><li>It would have felt better.</li><li>He would have been there when things went wrong.</li></ul><p>But he knew something most of us forget: sometimes the best thing you can do is let go.</p><p>The moment he stepped back was the moment he proved he was never trying to be the hero.</p><p>That’s restraint. That’s what guides do.</p><h3>✨ The Design Thinking Principle</h3><p>The best collaborators aren’t heroes. They’re guides.</p><p>They don’t take over the journey. They enable it.</p><ul><li>Not rescuing. Accompanying.</li><li>Not solving. Creating conditions.</li><li>Not taking credit. Holding space.</li></ul><blockquote>Heroes take the spotlight. Guides hold the space.</blockquote><p>The question isn’t “How do I save them?”</p><p>It’s “How do I create conditions where they can save themselves?”</p><h3>🔍 Your Guide Audit</h3><p>Before your next collaboration:</p><ul><li>Are you showing up to rescue — or to accompany?</li><li>Are you earning trust through action — or expecting it upfront?</li><li>When was the last time you stepped back so someone else could step up?</li><li>Who on your team has expertise you’ve been dismissing because they don’t “look the part”?</li></ul><p>Kristoff could have been the hero.</p><p>But he chose to be the guide.</p><p>That’s why Anna succeeded.</p><p>Who’s been a Kristoff for you — someone who walked beside you instead of taking over?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db145a3dbe6a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prince Eric Fell for the Voice, Not the Person]]></title>
            <link>https://renchangsoo.medium.com/prince-eric-fell-for-the-voice-not-the-person-8df3fdfaeb92?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8df3fdfaeb92</guid>
            <category><![CDATA[disney-design-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Thu, 13 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-13T00:01:02.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vJtA8hozP5iAL2t3y6HE3w.png" /></figure><p>Ariel saved Eric’s life.</p><p>She pulled him from the wreckage, sang to him on the shore. He woke just long enough to hear her voice — then passed out.</p><p>From that moment, Eric was obsessed with finding “the girl with the voice.”</p><p>Then Ariel showed up at his castle. Same face. Same eyes. Same person who saved him. But she couldn’t speak.</p><p>Eric spent days with her. They toured the kingdom. They laughed. They almost kissed in a rowboat while Sebastian conducted an entire lagoon.</p><p>He felt something. He knew something. And he talked himself out of it.</p><p>She didn’t have the voice. So she couldn’t be the one.</p><blockquote>What if the right answer doesn’t match your spec?</blockquote><h3>🎧 The Mental Model Trap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*sfOqerkyvKcUbM1w" /></figure><p>Eric heard a voice on the beach. He built his entire search around it.</p><p>“Find the girl with the voice.” That became his spec. His filter. His criteria for “the one.”</p><p>But the voice wasn’t her. It was one attribute — an output of the moment, not the person herself. He reduced a complex human to a single signal.</p><p>We do this constantly. We hear one piece of feedback, see one data point, latch onto one feature request — and we build our search around it.</p><p>Eric’s spec was clear.</p><p>It was also wrong.</p><h3>🔍 The Filter That Excluded Her</h3><p>Ariel was an edge case. The right person in an unexpected form. She matched everything that mattered — except the one criterion Eric was listening for.</p><ul><li><strong>What Eric measured:</strong> Does she have the voice?</li><li><strong>What Eric ignored:</strong> Everything else.</li></ul><p>He had a checklist. The checklist didn’t include intuition.</p><h3>💔 The Almost-Kiss Problem</h3><p>In the rowboat, surrounded by music and mood lighting, Eric leaned in. He almost kissed Ariel. Something in him knew.</p><p>Then he pulled back. Not because it was wrong. Because she didn’t fit the spec.</p><p>We do this in discovery. We feel something in an interview — a pause, a contradiction, a moment that doesn’t fit the data. And we override it. Because we can’t put intuition in a slide deck.</p><p>The almost-kiss was right. The spec was wrong.</p><h3>🎭 Confirmation Bias in Disguise</h3><p>Then Ursula showed up — disguised as Vanessa, wearing Ariel’s voice.</p><p>Eric heard the voice. Instant match. He didn’t question it. He didn’t notice that nothing else about her felt right. He validated the signal and stopped looking.</p><p>Ursula had the voice. She must be the one.</p><p>Eric nearly married her.</p><h3>⚡ The Shift</h3><p>Eric only recognised Ariel when her voice returned — seconds before the sunset deadline.</p><p>He didn’t discover the truth. He got lucky.</p><p>Eric was one sunset away from marrying a stranger.</p><p>This is the danger of over-indexing on one attribute. When you’re wrong, you don’t even know you’re wrong.</p><h3>✨ The Design Thinking Principle</h3><p>The solution doesn’t always match the spec.</p><p>The voice was a proxy. It was never the person.</p><blockquote>If you’re only listening for what you expect, you’ll miss what’s actually there.</blockquote><p>The question isn’t “Does this match my spec?”</p><p>It’s “Am I willing to see what doesn’t?”</p><h3>🪞 Your Criteria Audit</h3><p>Before your next discovery phase:</p><p>• What’s your “voice” — the single attribute you’re filtering for?</p><p>• Have you met an edge case that didn’t fit but felt right?</p><p>Eric spent days with the answer. He almost kissed her. He still didn’t see her — because he was listening for something else.</p><p>What’s your “almost-kiss” — the moment you felt the truth but overrode it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8df3fdfaeb92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prince Charming Had One Data Point. He Built a Kingdom-Wide Search on It]]></title>
            <link>https://renchangsoo.medium.com/prince-charming-had-one-data-point-he-built-a-kingdom-wide-search-on-it-7a8deb4a5539?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a8deb4a5539</guid>
            <category><![CDATA[disney-design-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Wed, 12 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-12T00:01:02.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgBf9JLICJjaaXMm1yd8Sw.png" /></figure><p>Prince Charming danced with Cinderella all night.</p><p>They talked. They laughed. They waltzed under chandeliers while the entire kingdom watched. He had hours with her.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*sJfGam4LGSUHJ8_W" /></figure><p>Then she ran. And he was left holding a shoe.</p><p>He had hours with her. He remembered a shoe.</p><p>His next move? Send the Duke door-to-door across the kingdom with one instruction: find the foot that fits.</p><p>Not “find the woman I danced with.” Not “find someone who matches this description.” Just: find the foot.</p><blockquote>What if the wrong person had fit the shoe?</blockquote><h3>👠 The Single Data Point Problem</h3><p>Prince Charming had one artefact: a glass slipper. He treated it like the answer.</p><p>But the slipper wasn’t her. It was something she left behind. A proxy. An output of the evening — not the person herself.</p><p>He built an entire research operation on a single metric: fit.</p><p>No triangulation. No follow-up questions. No attempt to understand context. Just: does the shoe fit? Yes or no?</p><p>We do this constantly. We find one signal — a survey response, a usage metric, a piece of feedback — and we scale our search around it. We mistake the artefact for the user.</p><p>The slipper fit Cinderella. But it could have fit someone else.</p><h3>🔍 Scale Without Insight</h3><p>Here’s what makes it worse: Prince Charming didn’t even do the search himself.</p><p>He sent the Duke. He outsourced the discovery phase.</p><p>The Duke went door to door, slipper in hand, asking women to try it on. He wasn’t looking for understanding. He was looking for a match.</p><p>What the Duke never asked:</p><ul><li>Were you at the ball?</li><li>What did you talk about?</li><li>Why did you leave?</li></ul><p>We do this too. We send surveys instead of having conversations. We check dashboards instead of watching users. We measure NPS instead of asking why.</p><p>The entire kingdom was searched. Zero insights were gathered.</p><h3>🎯 Confirmation Bias Dressed as Romance</h3><p>Prince Charming wasn’t looking for <em>her</em>. He was looking for <em>a match</em>.</p><p>There’s a difference.</p><p>Looking for her would mean curiosity.</p><ul><li>Questions.</li><li>Context.</li><li>Trying to understand who she was, why she came, why she left.</li></ul><p>Looking for a match means confirmation.</p><ul><li>Find the foot that fits.</li><li>Check the box.</li><li>Move on.</li></ul><p>Confirmation bias feels like progress. You’re gathering data. You’re validating. But you’re not learning. You’re just looking for evidence that supports what you’ve already decided.</p><h3>⚡ The Shift</h3><p>The slipper fit Cinderella. The story ended happily.</p><p>But that’s luck, not method.</p><p>Prince Charming was one shoe size away from marrying a stranger.</p><p>What if Anastasia or Drizella had slightly smaller feet? What if someone else in the kingdom happened to share Cinderella’s shoe size? The Duke would have declared victory. Prince Charming would have married the wrong person.</p><p>And he’d never have known.</p><p>This is the danger of single data point decision-making. When it works, you think you had a system. When it fails, you don’t even realise it failed.</p><h3>✨ The Design Thinking Principle</h3><p>A glass slipper is not a user interview.</p><blockquote>Artefacts are outputs, not understanding.<br>Metrics are signals, not people.</blockquote><p><strong>Fit is not the same as right.</strong></p><p>You can’t delegate discovery. The Duke measured fit. He never measured understanding.</p><p>Before you scale your search, ask:</p><ul><li>Am I looking for understanding, or confirmation?</li><li>Am I studying the user, or just the artefact they left behind?</li></ul><p><strong>The question isn’t “Does it fit?”</strong></p><p><strong>It’s “Do I understand who I’m looking for?”</strong></p><h3>🪞 Your Slipper Audit</h3><p>Before your next discovery phase:</p><ul><li>What’s your “glass slipper” — the single data point you’re over-relying on?</li><li>Are you searching for insight, or just looking for a match?</li><li>If you found a “fit,” would you know if it was the right one?</li></ul><p>Prince Charming got lucky. The shoe fit the right person.</p><p>But luck isn’t a research method.</p><p>Have you ever seen a “glass slipper search” at work? What was the slipper?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a8deb4a5539" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Princess Playbook for Human-Centered Design]]></title>
            <link>https://renchangsoo.medium.com/the-princess-playbook-for-human-centered-design-5b0f970d905d?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b0f970d905d</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[disney-design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Tue, 11 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-14T00:55:14.395Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vlq06HXUgRP-WaDOndJ5Xg.png" /></figure><p>Business books taught me frameworks. Disney princesses taught me how change actually happens.</p><p>These aren’t fairy tales. They’re case studies in empathy, iteration, trust, and the courage to design differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*d0gHMzuhVkCyG4jWlZaFyA.png" /></figure><p>Here’s what 16 princesses taught me about creating conditions where people say yes to change.</p><h3>🙊 The Cost of Not Asking</h3><p><a href="https://renchangsoo.medium.com/snow-white-and-the-uninvited-redesign-36feda6f6805"><strong>Snow White</strong></a> redesigned someone’s home without asking. Observation without conversation is surveillance. 🍎</p><p><a href="https://renchangsoo.medium.com/cinderella-designed-for-everyone-but-herself-67d56233f476"><strong>Cinderella</strong></a> designed for everyone but herself. The people best at serving others are often the worst at serving themselves. 👠</p><p><a href="https://renchangsoo.medium.com/what-aurora-was-never-designed-to-say-3ed2dbb604a0"><strong>Aurora</strong></a> has 18 lines in her own film. When you remove all risk, you also remove voice. 💤</p><blockquote>Permission is just the beginning. What happens when you start listening?</blockquote><h3>👂 What Empathy Actually Requires</h3><p><a href="https://renchangsoo.medium.com/why-ariels-fork-collection-beats-your-user-research-eaa034ab902c"><strong>Ariel</strong></a> understood humans better through their shipwrecks than most researchers do through surveys. Stop asking what users want. Start asking what they’re discarding. 🧜</p><p><a href="https://renchangsoo.medium.com/what-belle-knew-about-change-without-knowing-it-60f8b0e83338"><strong>Belle</strong></a> never told the Beast to change. She changed the conditions around him. 📚</p><p><a href="https://renchangsoo.medium.com/the-jasmine-principle-why-empathy-fails-when-we-skip-the-asking-bc77a882b354"><strong>Jasmine</strong></a> had everything — except someone who asked what she actually wanted. 👑</p><p><a href="https://renchangsoo.medium.com/the-pocahontas-principle-stop-painting-users-with-your-colours-511eb32459e6"><strong>Pocahontas</strong></a> called it four centuries ago: we’re still colonising with pixels instead of flags. 🍂</p><blockquote>Understanding isn’t enough. Eventually, you have to act.</blockquote><h3>⚔️ When Plans Meet Reality</h3><p><a href="https://renchangsoo.medium.com/the-sword-as-design-mulans-2-second-prototype-that-changed-everything-4594213b4bb8"><strong>Mulan</strong></a> prototyped her identity in 2 seconds with a sword. Your prototype doesn’t need to be perfect. It needs to exist. 🗡️</p><p><a href="https://renchangsoo.medium.com/the-tower-advantage-what-rapunzel-teaches-us-about-creative-constraints-295f18b22659"><strong>Rapunzel</strong></a> painted the same room for 18 years and created masterpieces. Constraints concentrate creativity. 🎨</p><p><a href="https://renchangsoo.medium.com/how-moana-navigates-without-a-map-and-why-you-should-too-5394a383b6e2"><strong>Moana</strong></a> doesn’t use a GPS. She reads conditions. Stop asking “What’s the plan?” Start asking “What are the conditions?” 🌊</p><p><a href="https://renchangsoo.medium.com/tiana-had-a-10-year-plan-the-swamp-had-other-ideas-c16090925d78"><strong>Tiana</strong></a> had a 10-year plan. The swamp had other ideas. You can’t plan your way to purpose. You prototype it. 🐸</p><blockquote>Then comes the hardest part — what happens when the only thing left to do is trust?</blockquote><h3>🔥 The Hardest Lessons</h3><p><a href="https://renchangsoo.medium.com/elsas-journey-from-fear-to-innovation-1d9b41d5ef44"><strong>Elsa</strong></a> built an ice palace alone on a mountain. Beautiful. Disconnected. Her powers were never the problem. Fear of the powers was. ❄️</p><p><a href="https://renchangsoo.medium.com/anna-knocked-for-thirteen-years-but-the-door-never-opened-c34a4db7d18a"><strong>Anna</strong></a> knocked on the same door for thirteen years. We call it persistence. Design thinking calls it repetition without learning. ⛄</p><p><a href="https://renchangsoo.medium.com/what-merida-heard-when-the-words-were-gone-ace75ed1efe8"><strong>Merida</strong></a> and Elinor talked constantly but never heard each other. Empathy isn’t hearing what someone says — it’s understanding what they can’t say. 🐻</p><p><a href="https://renchangsoo.medium.com/the-raya-principle-trust-as-prototype-28de4848b2e9"><strong>Raya</strong></a> handed Namaari the gem piece with no guarantee it would work. We treat trust as a prerequisite. She created conditions where trust could emerge. 🐉</p><p><a href="https://renchangsoo.medium.com/vanellope-wasnt-a-glitch-she-was-a-feature-f7e9a8072e22"><strong>Vanellope</strong></a> was called a glitch by everyone. But her “defect” made her unstoppable. She didn’t need fixing. She needed seeing. 🎮</p><blockquote>And sometimes, the hardest lesson is recognising yourself in the story.</blockquote><h3>🪞 What They All Knew</h3><p>These stories aren’t fairy tales. They’re mirrors.</p><p>Human-centred design isn’t about fixing people. It’s about creating conditions where they can say yes to change.</p><p>That’s what every princess needed. That’s what your people need too.</p><h3>TL;DR: The Cheat Sheet</h3><p>🍎 <a href="https://renchangsoo.medium.com/snow-white-and-the-uninvited-redesign-36feda6f6805">Snow White</a>: Earn the right to intervene</p><p>👠 <a href="https://renchangsoo.medium.com/cinderella-designed-for-everyone-but-herself-67d56233f476">Cinderella</a>: Design for yourself too</p><p>💤 <a href="https://renchangsoo.medium.com/what-aurora-was-never-designed-to-say-3ed2dbb604a0">Aurora</a>: Design for voice, not just safety</p><p>🧜 <a href="https://renchangsoo.medium.com/why-ariels-fork-collection-beats-your-user-research-eaa034ab902c">Ariel</a>: Collect artefacts, not opinions</p><p>📚 <a href="https://renchangsoo.medium.com/what-belle-knew-about-change-without-knowing-it-60f8b0e83338">Belle</a>: Change the conditions, not the person</p><p>👑 <a href="https://renchangsoo.medium.com/the-jasmine-principle-why-empathy-fails-when-we-skip-the-asking-bc77a882b354">Jasmine</a>: Ask before you solve</p><p>🍂 <a href="https://renchangsoo.medium.com/the-pocahontas-principle-stop-painting-users-with-your-colours-511eb32459e6">Pocahontas</a>: Paint with all the colours</p><p>🗡️ <a href="https://renchangsoo.medium.com/the-sword-as-design-mulans-2-second-prototype-that-changed-everything-4594213b4bb8">Mulan</a>: Ship before you’re ready</p><p>🎨 <a href="https://renchangsoo.medium.com/the-tower-advantage-what-rapunzel-teaches-us-about-creative-constraints-295f18b22659">Rapunzel</a>: Constraints concentrate creativity</p><p>🌊 <a href="https://renchangsoo.medium.com/how-moana-navigates-without-a-map-and-why-you-should-too-5394a383b6e2">Moana</a>: Read conditions, not roadmaps</p><p>🐸 <a href="https://renchangsoo.medium.com/tiana-had-a-10-year-plan-the-swamp-had-other-ideas-c16090925d78">Tiana</a>: Prototype your way to purpose</p><p>❄️ <a href="https://renchangsoo.medium.com/elsas-journey-from-fear-to-innovation-1d9b41d5ef44">Elsa</a>: Fear is the real blocker</p><p>⛄ <a href="https://renchangsoo.medium.com/anna-knocked-for-thirteen-years-but-the-door-never-opened-c34a4db7d18a">Anna</a>: Learn between attempts</p><p>🐻 <a href="https://renchangsoo.medium.com/what-merida-heard-when-the-words-were-gone-ace75ed1efe8">Merida</a>: Hear what isn’t said</p><p>🐉 <a href="https://renchangsoo.medium.com/the-raya-principle-trust-as-prototype-28de4848b2e9">Raya</a>: Create conditions for trust</p><p>🎮 <a href="https://renchangsoo.medium.com/vanellope-wasnt-a-glitch-she-was-a-feature-f7e9a8072e22">Vanellope</a>: The “defect” might be the feature</p><p>Which princess are you still learning from?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b0f970d905d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hercules Won Every Battle. Except the One That Mattered]]></title>
            <link>https://renchangsoo.medium.com/hercules-won-every-battle-except-the-one-that-mattered-a88d8dc2c6e8?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a88d8dc2c6e8</guid>
            <category><![CDATA[disney-design-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-10T00:01:02.286Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cu-6xXECQOzVEP4iXWAO6A.png" /></figure><p>Hercules had the numbers.</p><p>Monsters slain. Arenas sold out. His face on vases, sandals, action figures. Phil declared him a hero. The crowds agreed. The Muses sang his praises. Thebes built statues in his honour.</p><p>By every visible measure, Hercules was the most successful hero in Greece.</p><p>Then he went to Mount Olympus. Zeus looked at him and said no.</p><p>“Being famous isn’t the same as being a true hero.”</p><p>All those metrics. All that validation. And the one judge who actually mattered wasn’t impressed.</p><blockquote>What if you’re optimising for the wrong metric?</blockquote><h3>🎯 The Vanity Metrics Trap</h3><p>Hercules let others define success for him — Phil, the crowds, the merchandise sales. He measured what was visible: applause, fame, body count.</p><ul><li>Phil trained him to win battles.</li><li>The crowds rewarded him for spectacle.</li><li>The merchants paid him for his image.</li></ul><p>Every signal in his environment told him he was succeeding.</p><p>But none of them knew what Zeus was actually looking for.</p><p>Hercules never paused to ask: “What would actually make me a hero?”</p><p>He assumed the metrics he could see were the metrics that mattered. He optimised for applause when the gods were measuring something else entirely.</p><p>Sound familiar?</p><h3>📊 The Metrics We Chase vs. The Outcomes That Matter</h3><p>In design thinking, we talk about validation constantly. Test early. Measure often. Let the data guide you.</p><p>But validation against the wrong criteria is worse than no validation at all. It gives you confidence in the wrong direction.</p><p><strong>What we measure:</strong></p><ul><li>Features shipped</li><li>Engagement numbers</li><li>Meetings attended</li><li>Slides produced</li><li>Deadlines hit</li><li>Tasks completed</li></ul><p><strong>What actually matters:</strong></p><ul><li>Problems solved</li><li>Lives improved</li><li>Value created</li><li>Meaning delivered</li><li>Behaviour changed</li><li>Trust built</li></ul><p>The first list is easy to track. The second list is what we’re actually here for.</p><p>Hercules had a dashboard full of green metrics.</p><ul><li>Monster kills: up.</li><li>Fan engagement: through the roof.</li><li>Brand awareness: universal.</li></ul><p>None of it moved the needle on what Zeus cared about.</p><h3>⚡ The Shift</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*oXUt2B9lScPzpyKI" /></figure><p>Hercules only became a true hero when he dove into the River Styx to save Meg.</p><p>Think about that moment. No arena. No audience. No Phil shouting encouragement from the sidelines. No crowd to cheer. No merchant to license the moment for a commemorative plate.</p><p>Just Hercules, alone, choosing to sacrifice himself for someone he loved.</p><p>No audience. No applause. No metric.</p><p>Just meaning.</p><p>The act that made him immortal was the one nobody was tracking.</p><p>This is the paradox of meaningful work. The moments that matter most often happen when no one is watching. The impact that lasts is rarely the impact that gets measured.</p><p>Hercules spent the entire film chasing metrics that didn’t count. His heroism emerged in the one moment he stopped measuring altogether.</p><h3>✨ The Design Thinking Principle</h3><p>Before you optimise, define what success actually means — not what’s easy to measure.</p><p>This is harder than it sounds. We default to measuring what’s visible because visible things are easy to count. Downloads. Sign-ups. Clicks. Completions.</p><p>But the question isn’t whether you can measure something. The question is whether that something actually matters.</p><blockquote>Validation without clarity is just performance.</blockquote><p>You can validate constantly and still be wrong. You can hit every target and still miss the point. You can ship features, grow numbers, and fill dashboards with green — and still have Zeus look at you and say no.</p><p>The question isn’t “Am I winning?”</p><p>It’s “What game am I actually playing?”</p><h3>🔍 Your Metrics Audit</h3><p>Before your next sprint, your next quarter, your next big initiative — pause.</p><p>Ask yourself:</p><ul><li>What are you measuring — and why that? Are these metrics because they matter, or because they’re easy to track?</li><li>If you hit all your targets, would it actually matter? Imagine perfect execution. Green across the board. Would that success translate to real impact?</li><li>Whose definition of success are you chasing? Phil’s? The crowd’s? Or the one that actually determines whether you’ve made a difference?</li><li>What would meaningful success look like — beyond the dashboard? If you couldn’t measure anything, how would you know you’d succeeded?</li></ul><h3>🎯 The crowd vs. The gods</h3><p>Hercules had the scoreboard. The gods wanted something else entirely.</p><ul><li>The crowds cheered.</li><li>The gods shrugged.</li></ul><p>This is the gap between vanity metrics and meaningful outcomes. The crowd rewards what’s visible. The gods — whatever “gods” means in your context: real impact, lasting change, genuine value — measure something deeper.</p><p>Hercules discovered that heroism wasn’t about the battles you win. It was about the sacrifice you make when no one’s counting.</p><p>The same is true for the work we do.</p><p>Ship features, hit targets, fill the dashboard with green. But never forget to ask: are these the metrics (and moments) that actually matter? Or are we just performing heroism for a crowd that can’t tell the difference?</p><p><strong>What metric are you chasing that might not count?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a88d8dc2c6e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vanellope Wasn’t a Glitch. She Was a Feature]]></title>
            <link>https://renchangsoo.medium.com/vanellope-wasnt-a-glitch-she-was-a-feature-f7e9a8072e22?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7e9a8072e22</guid>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 00:01:03 GMT</pubDate>
            <atom:updated>2026-08-07T00:01:03.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hkH4n4ocnhYtwYvnCoR9RQ.png" /></figure><p>Everyone in Sugar Rush knew one thing about Vanellope: she was broken.</p><p>Her pixels flickered. Her code glitched mid-sentence. The other racers called her a mistake. King Candy banned her from the track — for her own safety, he said. For the survival of the game.</p><p>She lived in the unfinished spaces. Built a kart from scraps. Dreamed of a starting line she was told she’d never reach.</p><p>The game had a place for everyone. Except her.</p><blockquote>What if the thing you’re trying to fix is the thing that sets you apart?</blockquote><h3>🎮 The Defect</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*FGWbLYSQmUq11RyL" /></figure><p>Vanellope’s glitching wasn’t subtle. She’d pixelate without warning. Teleport when she didn’t mean to. Flicker in and out like a dying screen.</p><p>To everyone around her, this was proof. She didn’t belong. A bug. A liability. Something to contain before it spread.</p><p>The other racers wouldn’t stand near her. They feared the glitch was contagious — that her brokenness might infect their code too.</p><p>King Candy made the case clearly: if players saw her glitch, they’d think the game was broken. They’d unplug Sugar Rush. Everyone would die. Her very existence threatened the survival of the world.</p><p>It was persuasive. It was unanimous. It was a lie.</p><p>But Vanellope believed it. That’s the cruellest part. She’d been told she was a mistake so many times that she started to see herself that way. She wanted to race not to prove them wrong — but to prove to herself that she could be something other than broken.</p><p>No one had tried to understand her experience. They’d only diagnosed her from the outside.</p><p>Diagnosis without empathy is just assumption with authority.</p><h3>⚡ The Feature</h3><p>Here’s what the system couldn’t see.</p><p>Vanellope’s glitch let her teleport through walls. Phase through opponents. Flicker past barriers at the exact moment they tried to stop her.</p><p>The thing that made her “broken” made her unstoppable — once she learned to use it.</p><p>Watch the final race. Every glitch gains her ground. The defect becomes her edge. The bug becomes her signature move. The other racers can’t touch her — not because she’s fixed, but because she’s finally free.</p><p>She didn’t need fixing. She needed someone willing to see possibility where everyone else saw error.</p><p>Ralph gave her that. Not by analysing her code. Not by debugging her. By letting her race — by prototyping what she could do instead of theorising about what she couldn’t.</p><p>He started with empathy. He ended with discovery.</p><h3>🔍 The Real Bug</h3><p>Here’s the twist that reframes everything.</p><p>King Candy wasn’t protecting the game. He was Turbo — a virus who had invaded Sugar Rush, rewritten its code, and erased Vanellope from the system. He made her a glitch on purpose. Then convinced everyone she’d always been one.</p><p>He didn’t just corrupt her code. He corrupted the story about her code.</p><p>His power depended on a single assumption: that Vanellope was broken. That she was dangerous. That excluding her was protection, not oppression.</p><p>The moment someone questioned that assumption, his entire system collapsed.</p><p>The defect was never in Vanellope. The defect was in a system designed to make her look like the problem.</p><h3>🏢 The Organisational Mirror</h3><p>This pattern repeats everywhere:</p><ul><li>The team member who asks hard questions — labelled negative, managed out</li><li>The prototype that doesn’t fit the roadmap — killed before it’s understood</li><li>The process that breaks convention — dismissed as impractical</li><li>The idea that challenges assumptions — diluted into consensus</li><li>The person who sees differently — isolated until they conform or leave</li></ul><p>We call them bugs. We design them out. We tell ourselves we’re protecting the system.</p><p>And sometimes, we eliminate the very thing that would have changed everything.</p><p>Worth asking: who decided this was a defect? What were they protecting when they made that call? What story have we inherited about this “problem” — and who benefits from that story staying true?</p><p>Not every anomaly is a bug. Some anomalies are signals — early indicators of something the system hasn’t learned to recognise yet.</p><p>The question isn’t whether the anomaly fits the system. The question is whether the system is worth fitting.</p><h3>✨ The Shift</h3><p>From: “How do we fix this anomaly?” To: “What is this anomaly trying to show us?”</p><p>From: “This doesn’t fit our model.” To: “Maybe our model is incomplete.”</p><blockquote>That’s the core of human-centered design — curiosity before correction.</blockquote><p>Vanellope’s glitch wasn’t noise. It was signal the system couldn’t read. The game had been designed to reject her — and that design was the actual flaw.</p><p>Ralph didn’t fix her. He reframed her. He gave her space to discover that the thing everyone called her weakness was her greatest strength.</p><p>That’s what good design does. It doesn’t smooth away difference. It asks what that difference is trying to tell us.</p><h3>🔎 Your Audit</h3><p>Before you fix the next “bug”:</p><ul><li>What if this isn’t a defect — but a feature you haven’t recognised?</li><li>Who labelled it broken, and what were they protecting?</li><li>What would change if you prototyped with it instead of against it?</li><li>What story have you inherited about this “problem” — and is it true?</li></ul><p>Vanellope didn’t need the game to fix her.</p><p>She needed the game to see her.</p><p><strong>What “glitch” in your team have you been trying to fix instead of explore?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7e9a8072e22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Merida Heard When the Words Were Gone]]></title>
            <link>https://renchangsoo.medium.com/what-merida-heard-when-the-words-were-gone-ace75ed1efe8?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ace75ed1efe8</guid>
            <category><![CDATA[disney-design-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Thu, 06 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-06T00:01:02.750Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SuNYzrVvQG1MpbSLoHctBg.png" /></figure><p>Merida and Elinor talked all the time.</p><p>About duty. About tradition. About what a princess should be.</p><p>They just never heard each other.</p><p>Then Elinor became a bear — and couldn’t speak at all.</p><blockquote>What if the most important things are never said out loud?</blockquote><h3>🗣️ The Conversations That Weren’t</h3><p>Watch Merida and Elinor before the curse.</p><p>They spoke constantly. But every conversation was a collision.</p><p>Elinor said “duty” — Merida heard “cage.” Merida said “freedom” — Elinor heard “reckless.”</p><p>Same words. Completely different meanings.</p><p>Neither was listening. Both were waiting for their turn to speak.</p><p>The problem wasn’t silence. The problem was noise — so much talking that neither could hear what the other actually meant.</p><p>Elinor wasn’t trying to trap Merida. She was trying to protect her — from a kingdom held together by fragile alliances, from clan leaders ready to go to war, from a future she couldn’t control.</p><p>But she never said that. She said “a princess does not…” and “you must…”</p><p>The fear stayed hidden. The love stayed hidden. Only the rules were spoken.</p><h3>🐻 The Bear as Constraint</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*rCDw_UgOA2PPQl_3" /></figure><p>Then the curse took Elinor’s words away.</p><p>No lectures. No corrections. No “a princess must…”</p><p>Just a bear — vulnerable, confused, dependent on the daughter she’d been fighting with.</p><p>And something shifted.</p><p>For the first time, Merida had to pay attention to what her mother did, not what she said.</p><p>She watched Elinor struggle with her new body but still try to maintain dignity. She saw Elinor catch fish — clumsily, reluctantly — to feed them both. She noticed Elinor step between her and danger without hesitation.</p><p>Protection. Sacrifice. Love.</p><p>It was always there. Merida just couldn’t hear it through the words.</p><p>The constraint didn’t create new information. It removed the noise that was hiding what mattered.</p><h3>💡 What Silence Revealed</h3><p>With words gone, Merida finally understood:</p><p>Her mother wasn’t the enemy of her freedom. Her mother was terrified of losing her.</p><p>Every rule, every lecture, every “you must” — it was fear dressed as duty.</p><p>Elinor couldn’t say “I’m scared for you.” She could only say “this is what a princess does.”</p><p>Merida had been fighting the words. She’d missed the meaning underneath.</p><p>That’s what empathy actually is — not hearing what someone says, but understanding what they can’t say.</p><h3>🏢 The Organisational Mirror</h3><p>I see Merida and Elinor in every organisation.</p><ul><li>The stakeholder who says “we need more features” when they actually mean “I’m afraid this won’t be enough.”</li><li>The executive who says “move faster” when they actually mean “I don’t feel in control.”</li><li>The team member who says “I’m fine” when they actually mean “I don’t feel safe enough to tell you.”</li></ul><p>We hear the words. We miss the meaning.</p><p>Then crisis hits — a resignation, a breakdown, a project failure — and suddenly we pay attention. Suddenly we ask the questions we should have asked months ago.</p><p>It took a curse for Merida to listen. What’s it going to take for us?</p><h3>✨ The Shift</h3><p>Empathy isn’t a crisis response. It’s a practice.</p><ul><li>From: Listening to respond. To: Listening to understand.</li><li>From: Hearing what’s said. To: Noticing what isn’t.</li><li>From: Waiting for the bear. To: Paying attention before the curse.</li></ul><p>The most important things are rarely spoken out loud. They’re hidden in behaviour, in hesitation, in what people do when they think no one’s watching.</p><p>Merida didn’t need her mother to change. She needed to hear what her mother couldn’t say.</p><p><strong>Where are you hearing words but missing meaning? ✨</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ace75ed1efe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tiana Had a 10-Year Plan. The Swamp Had Other Ideas]]></title>
            <link>https://renchangsoo.medium.com/tiana-had-a-10-year-plan-the-swamp-had-other-ideas-c16090925d78?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c16090925d78</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[disney-design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Wed, 05 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-05T00:01:02.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*of15qsRlVluph3AaeFn46w.png" /></figure><p>Tiana had it all mapped out.</p><ul><li>Work double shifts.</li><li>Save every penny.</li><li>Buy the old sugar mill.</li><li>Open her father’s dream restaurant.</li></ul><p>Ten years of sacrifice. One clear goal. No room for deviation.</p><p>Then she kissed a frog and lost everything.</p><blockquote>What if the plan you’re protecting is the thing keeping you from what you actually need?</blockquote><h3>🗺️ The Plan That Couldn’t Flex</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*oDFDbp-WUSjy-EbE" /></figure><p>Tiana’s 10-year plan was a masterpiece of control.</p><ul><li>Every dollar accounted for.</li><li>Every shift scheduled.</li><li>Every sacrifice justified by the destination.</li></ul><p>But somewhere along the way, the destination had replaced the reason for going.</p><p>Watch what the plan actually did:</p><ul><li>It isolated her from friends (“I don’t have time for dancing”)</li><li>It collapsed her identity into a single outcome (“I need to get my restaurant”)</li><li>It left no room for learning — only executing</li></ul><p>Tiana didn’t have a strategy. She had a script. And scripts don’t adapt when reality changes.</p><p>The moment the Fenner Brothers rejected her offer, the entire architecture crumbled. Not because the goal was wrong — but because the plan had no capacity for uncertainty.</p><p>Over-planning feels like preparation. Often, it’s protection — from the discomfort of not knowing, from the vulnerability of testing, from the risk of being wrong.</p><p>Then the swamp took the plan away.</p><h3>🐸 The Swamp as Prototype</h3><p>Suddenly, Tiana is a frog. No money. No kitchen. No plan.</p><p>Just a swamp, a talking alligator, and a jazz-obsessed firefly.</p><p>Everything she controlled was gone. She was lost, out of her depth, completely unprepared.</p><p>And something unexpected happened: she started learning.</p><p>The swamp forced her into rapid prototyping:</p><ul><li>Trust Louis? Small bet. He’s loud and unreliable — but genuine.</li><li>Follow Ray? Small bet. He believes in something she can’t see yet.</li><li>Listen to Mama Odie? Small bet. “You got to dig a little deeper” isn’t a business plan — but it’s the question she’d been avoiding.</li></ul><p>Each experiment taught her something her 10-year plan never could.</p><ul><li>The plan demanded control. The swamp taught adaptation.</li><li>The plan meant grinding alone. The swamp brought unexpected allies.</li><li>The plan was fixated on the goal. The swamp revealed the purpose.</li></ul><p>Tiana couldn’t prototype her way to the restaurant. But she could prototype her way to understanding why the restaurant mattered in the first place.</p><h3>🎯 The Goal That Hid the Purpose</h3><p>Tiana’s goal was clear: own a restaurant.</p><p>But she’d confused the how for the why.</p><p>Her father didn’t dream of a building.</p><p>He dreamed of what would happen inside it — neighbours becoming friends, strangers sharing tables, a community held together by gumbo and laughter. The restaurant was how he’d fulfil that purpose. Not the purpose itself.</p><p>Tiana inherited the goal. Somewhere along the way, she lost the purpose.</p><p>The swamp stripped away the goal. And in its absence, the purpose became visible again.</p><p>That’s what prototyping in uncertainty does. It doesn’t give you answers — it shows you which questions actually matter.</p><h3>🏢 The Organisational Mirror</h3><p>I see Tiana’s 10-year plan everywhere.</p><p>The strategy deck that’s perfect on paper. Every milestone mapped. Every dependency charted. Then it meets reality — a market shift, a key resignation, a pandemic — and shatters. The plan had no learning loops. Only execution steps.</p><p>The leaders who won’t move until they have “enough data.” They’re waiting for certainty in a world that doesn’t offer it. The fog won’t clear before you step. It clears because you stepped.</p><p>The teams paralysed by ambiguity. They keep refining the plan, adding contingencies, scheduling alignment meetings. Motion that feels like progress but avoids the only thing that creates progress: testing something real.</p><p>The transformation programmes with 18-month roadmaps and no prototypes until month 12. By then, the assumptions are calcified. The learning comes too late.</p><p>Over-planning is a form of hiding. It lets us feel productive while avoiding the vulnerability of being wrong.</p><h3>💡 The Shift</h3><p>Tiana’s breakthrough didn’t come from a better plan.</p><p>It came when the plan was gone — and she had to learn her way forward.</p><p>From: “I’ll start when I have the full picture.”</p><p>To: “I’ll learn by starting.”</p><p>From: “This goal is my purpose.”</p><p>To: “What is this goal in service of?”</p><p>Real progress in uncertainty isn’t about planning harder.</p><p>It’s about testing sooner.</p><ul><li>Smaller bets.</li><li>Faster learning.</li><li>Holding goals loosely enough that purpose can emerge.</li></ul><p>You can’t plan your way to purpose. You prototype it.</p><p><strong>Where are you planning when you should be prototyping? ✨</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c16090925d78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anna Knocked for Thirteen Years But The Door Never Opened]]></title>
            <link>https://renchangsoo.medium.com/anna-knocked-for-thirteen-years-but-the-door-never-opened-c34a4db7d18a?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c34a4db7d18a</guid>
            <category><![CDATA[disney-design-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-04T00:01:02.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TAa7ITiCF39kW8v8zZivA.png" /></figure><p>Anna knocked on Elsa’s door for thirteen years.</p><p>Same door. Same knock. Same words: “Do you want to build a snowman?”</p><p>Same silence.</p><blockquote>What if the thing we call persistence is actually the thing keeping us stuck?</blockquote><h3>🚪 The Door That Never Opened</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*e6ciuEspSshfmJzE" /></figure><p>Anna was persistent. No one can deny that.</p><p>But watch what she actually did:</p><ul><li>Age 5: Knocked. Asked to build a snowman. Silence.</li><li>Age 9: Knocked. Asked to build a snowman. Silence.</li><li>Age 15: Knocked. Asked to build a snowman. Silence.</li><li>Age 18: Knocked. Asked to build a snowman. Silence.</li></ul><p>Thirteen years. The same approach. The same result.</p><p>We’d call this dedication. Loyalty. Grit.</p><p>Design thinking calls it something else: repetition without learning.</p><p>Iteration requires change between cycles. You try something, observe what happens, learn from it, and adjust your next attempt based on that learning.</p><p>Anna put in the effort. Thirteen years of it. But effort without reflection is just motion.</p><p>She never paused to ask: <em>What did the silence teach me? What should I try differently?</em></p><p>She changed nothing. She just kept knocking.</p><h3>🔍 The Question She Never Asked</h3><p>Anna focused on the door. She never asked about what was behind it.</p><p>She iterated on her approach — how to knock, when to knock, what words to use.</p><p>She never iterated on her understanding — why is this door closed? What is Elsa actually experiencing? What would make this door feel safe to open?</p><p>Anna assumed the problem was access. Get to Elsa, and everything would be fine.</p><p>The real problem was safety.</p><p>Elsa wasn’t ignoring Anna. She was protecting her. The door wasn’t rejection — it was a containment strategy for powers Elsa couldn’t control. Every time Anna knocked, Elsa felt the danger of what might happen if she answered.</p><p>Anna spent thirteen years solving the wrong problem.</p><p>True iteration doesn’t start with refining your solution. It starts with questioning your problem.</p><h3>🎪 The Coronation Prototype</h3><p>When the door finally opened, Anna went big.</p><p>The coronation ball. Hundreds of guests. Maximum visibility. Maximum stakes. She saw her chance to reconnect with Elsa and pushed for everything at once — an engagement to Hans, approval from Elsa, a future unlocked in a single evening.</p><p>It exploded. Spectacularly.</p><p>Elsa’s powers revealed. The kingdom frozen. Anna’s engagement exposed as a manipulation.</p><p>This wasn’t a prototype. It was a production launch.</p><blockquote>First prototypes should be low-fidelity, low-risk, low-cost to fail. You test small so you can learn fast. You create space for things to go wrong without catastrophic consequences.</blockquote><p>Anna tested her most important relationship in the highest-stakes environment possible. No room for learning. No space for recovery. No permission to fail small.</p><p>She didn’t prototype reconnection. She bet everything on a single attempt — and lost.</p><h3>🏢 The Organisational Mirror</h3><p>I see Anna everywhere in organisations.</p><p>The quarterly business reviews where the same initiatives appear, quarter after quarter. “We’re still working on it.” Same approach. Same blockers. Same results. Leadership nods. Nothing changes. We call it persistence. It’s actually avoidance of the harder question: is this the right problem?</p><p>The transformation programmes that keep adding resources when pilots fail. Didn’t work with one team? Try five teams. Didn’t work with five teams? Roll it out to the whole organisation. Resistance isn’t treated as feedback — it’s an obstacle to overcome with more force. Escalation disguised as iteration.</p><p>The product teams who keep refining features users don’t want. Each sprint polishes the solution. No one revisits whether the problem was real. “We’re iterating” becomes a shield against admitting “we’re wrong.”</p><p>The leaders who keep sending the same message, wondering why no one’s listening. Different channels, same content. Different slides, same story. If they’re not hearing you, maybe the message isn’t the problem. Maybe you haven’t understood what’s keeping them from listening.</p><p>Same door. Same knock. Same silence.</p><p>And we celebrate the persistence.</p><h3>💡 The Shift</h3><p>Real iteration asks:</p><ul><li>What did I learn from the last attempt?</li><li>What assumption was I wrong about?</li><li>What’s a smaller, safer way to test this?</li><li>Am I solving the right problem — or just refining the wrong solution?</li></ul><p>Effort feels like progress. It isn’t.</p><p>Learning is progress. And learning requires changing something between attempts.</p><p>Anna’s breakthrough didn’t come from a better knock.</p><p>It came when she stopped trying to open the door and started trying to understand what was behind it. When she shifted from demanding access to offering safety. When she stopped asking Elsa to come out and started showing Elsa she would stay — no matter what.</p><p>The shift isn’t from giving up to trying harder.</p><p>It’s from repeating to learning.</p><p><strong>Where has your persistence become repetition? ✨</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c34a4db7d18a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Megara Knew About Empathy (That Organisations Still Exploit)]]></title>
            <link>https://renchangsoo.medium.com/what-megara-knew-about-empathy-that-organisations-still-exploit-ac4fd4e6effb?source=rss-fecee46e039a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac4fd4e6effb</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[disney-design-thinking]]></category>
            <dc:creator><![CDATA[Ren Chang, SOO]]></dc:creator>
            <pubDate>Mon, 03 Aug 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-08-03T00:01:02.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FFY7vfe4f9hWy3-z2D5vsg.png" /></figure><p>Megara was the best user researcher in the Underworld.</p><p>She listened. She observed. She asked the questions no one else thought to ask. And she handed every insight to the wrong client.</p><blockquote>What if the most dangerous thing about empathy isn’t lacking it — but using it for the wrong purpose?</blockquote><h3>🔥 Megara’s Method</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*gwTLZhAbTO8_OUR6QX-Oug.gif" /></figure><p>Hades didn’t send a warrior to defeat Hercules. He sent a researcher.</p><p>Megara walked alongside Hercules. Not interrogating — just present. She asked about his dreams, his frustrations, his desperate need to prove himself. She watched how he behaved when he thought no one was evaluating him.</p><p>Contextual inquiry. Empathetic listening. Behavioural observation. Textbook user research methods.</p><p>She didn’t extract information. She created conditions for Hercules to reveal himself. And she was brilliant at it.</p><p>The best research doesn’t feel like research. It feels like connection.</p><h3>💔 The Insight She Found</h3><p>Surface-level analysis would have focused on Hercules’ strength. His speed. His combat record. The metrics that everyone could see.</p><p>Megara went deeper. She understood the say-do-feel gap.</p><p>Hercules said he wanted to be a hero. He did heroic things. But what he felt was something else entirely — loneliness, rejection, a desperate need to belong somewhere.</p><p>His real weakness wasn’t physical at all. It was love. Connection. The thing that surface data would have missed entirely.</p><p>The real insight is never in what people say or do. It’s in what they feel.</p><h3>⚡ Research Weaponised</h3><p>Megara gathered the insight. Hades weaponised it.</p><p>She did the empathy work. He used it to destroy.</p><p>Remember the deal? Hades used exactly what Megara discovered — Hercules’ love for her — to make him surrender his strength. The nuanced insight she gathered became the precise lever for his destruction.</p><p>The moment she handed over her findings, she lost control of how they would be used. Her careful understanding of Hercules became a blunt instrument in someone else’s hands.</p><p>This is the researcher’s dilemma: you gather vulnerable, honest data from people who trusted you. What happens to it next is often beyond your control.</p><p>Research without ethical stewardship becomes surveillance.</p><h3>🔄 The Switch</h3><p>Here’s what makes Megara’s story remarkable: she didn’t change her methods.</p><p>She changed her client.</p><p>Same empathetic listening. Same ability to see what others missed. Same skills that made her valuable to Hades.</p><p>But now deployed in service of Hercules, not against him. Her research became protection instead of exploitation.</p><p>The method is the same. Loyalty is what changed everything.</p><h3>🏢 The Organisational Mirror</h3><p>Megara’s story ended with redemption. Most organisational versions don’t.</p><p>I see Megara everywhere in organisations.</p><p>The research conducted after decisions are already made. Leadership has already chosen the direction — they just need evidence to justify it. Insights get cherry-picked. Contradictory findings get buried. “We did the research” becomes a defence, not a discovery process. This research served the decision-maker’s need to feel validated, never the users.</p><p>The transformation consultants who gather frontline insights, then soften the findings for the executive sponsor. They know what the teams actually said. They know what would make the sponsor uncomfortable. So they sand down the edges, reframe the criticism, present a version that won’t threaten anyone’s position. The researcher knows the truth. The client never hears it.</p><p>The employee engagement workshops that extract ideas, creativity, discretionary effort from employees — then implement nothing. Six months later, the same problems exist. The same suggestions sit in a forgotten deck. People feel harvested rather than heard. “We co-designed this” when really, it was just extraction.</p><p>The researchers in these stories? They know. They feel it. They just don’t know how to stop it.</p><p>Same methods. Same empathy. Same skills.</p><p>But who is the research actually serving?</p><h3>💡 The Shift</h3><p>The shift is from asking: “How do we get users to do what we want?”</p><p>To asking: “How do we help users get what they need?”</p><p>Human-centered design isn’t a method. It’s loyalty.</p><p>Empathy skills can either extract or serve. The difference isn’t technique; it’s who you’re actually serving.</p><p>Megara didn’t become a better researcher when she switched sides.</p><p>She became an ethical one.</p><p>Who is your research really serving? ✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac4fd4e6effb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>