<?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 Romario Verbran on Medium]]></title>
        <description><![CDATA[Stories by Romario Verbran on Medium]]></description>
        <link>https://medium.com/@romarioverbran?source=rss-53ee4ac7f11f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3UZirJjkKu5ljBceIrJ6iw.jpeg</url>
            <title>Stories by Romario Verbran on Medium</title>
            <link>https://medium.com/@romarioverbran?source=rss-53ee4ac7f11f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 03:54:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@romarioverbran/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[[Game UX Case] How I raised an MMO’s player base by 70%]]></title>
            <link>https://romarioverbran.medium.com/game-ux-case-how-i-raised-an-mmos-player-base-by-70-f2f414fdf9f?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2f414fdf9f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[games]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Mon, 03 Oct 2022 00:05:58 GMT</pubDate>
            <atom:updated>2022-10-15T05:10:52.351Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using UX and behavioural psychology to take Priston Tale back to its former glory</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EUwyHtnWagYcDRKd_m0gGQ.jpeg" /></figure><p><strong>Awarded Game of the Year twice,</strong> Priston Tale is a classic MMORPG with 20 years of history and thousands of players worldwide. A game once so popular that you’d have to pay a monthly fee and wait in login queues!</p><p>But time hasn’t done PT wellnine New RPGs like World of Warcraft brought more balanced gameplays and innovative features, making most Priston servers shut down. Most players are nostalgic adults trying to relive their childhood memories, with only a tiny fraction of new players.</p><p>We are starting to change that, though. Applying behavioural psychology, UX design, and modern game deatures, I helped PTEU (European Union) raise its player base by 70% along with a 140% revenue increase over the last 9hs — and the data shows we are far from the peak!</p><h3>The challenge</h3><p>Priston Tale is mostly played by 30 to 40yo people that grew up with the game, BUT the game didn’t care to grow up with them. The result is a 20yo experience for gamers that now play the biggest titles in the market, causing many to quit and seek better games.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*imPWHCc232ylngO5vKTvjw.jpeg" /></figure><p>Another problem is PT’s code: programmed with a deprecated 50yo language, only a few devs can handle the dreadful backend of the game — and they sure charge well for those skills.</p><p>All of this combined, we not only had to learn what players needed but also ensure our creativity was within the code’s boundaries, mostly limiting us to tweaking and fixing existing features instead of creating new ones.</p><h3>Methodology</h3><h3>Undercover Contextual Inquiries</h3><p>Why undercover? Because PT is a passion-driven community where players want to prove they are the most hardcore gamers in the world — and that only gets worse in the presence of developers, which could modify their beloved “classic experience”.</p><p>Being undercover for two months allowed me to disguise my interviews as conversations and get unbiased opinions from them. It also enabled me to face the entire player journey like a regular player, which gave me a unique perspective on the game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ub3Ql8HS9eP-aDzy" /></figure><p>The affinity map above shows a few of the discoveries I made, the most important issues being..:</p><ul><li><strong>Boring grind:</strong> you have to kill monsters to level up in Priston Tale, but the process gets extremely repetitive (what we call “grinding”), <em>leading many players to say the game felt like work.</em></li></ul><p>Other servers “solve” this by multiplying EXP points (required to level up), but that’s a huge mistake since level requirements multiply equally. Not only the faster levelling is illusory, but also detrimental because players skip the early and mid-game phases, killing their sense of <a href="https://yukaichou.com/gamification-study/8-core-drives-gamification-2-development-accomplishment/">Accomplishment and Development</a>.</p><ul><li><strong>Unbalanced maps:</strong> hard work never paid off in PT because monsters had bad drops, causing players to always be underequipped. (Which in turn leaves them weak to access stronger maps, forcing them to play extra hours in places they should have already left.)</li></ul><p>Also, many maps’ EXP rewards were unbalanced, e.g., a Lv 90 region being less rewarding than a Lv 75 one, leading players to spend even more hours on maps they are already sick of.</p><blockquote>Players expected to feel like heroes but felt like menial workers in a factory line.</blockquote><ul><li><strong>Excluding meta:</strong> only 3 out of 10 classes (characters) were good at grinding, while the other 7 only lured* for them most of the time. (*Running back and forth to bring monsters for others to kill.)</li></ul><p>Making matters worse, <em>all</em> classes’ performance plummeted as players levelled up, reaching a point where the game was so hard that players felt weaker than when they started. It’s like going to the gym to lose muscles!</p><ul><li><strong>“Lack of time”:</strong> all these difficulties together, achieving anything in the game simply took too long for a regular adult player. Something as simple as a quest would take 45 minutes to complete, but players need at least 7 of them daily — which means 5 hours per day!</li></ul><p>You can see Priston didn’t lack features, but reward loops instead. We didn’t need to reinvent the wheel, but make it turn in the first place!</p><h3>Research Repository</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z561kFup3b8HcbH8" /><figcaption>I consolidated all our knowledge in a private database</figcaption></figure><p>You never forget how to ride a bicycle, but what if bicycles suddenly changed overnight?</p><p>I figure that our discoveries would lead to dramatic changes to mechanics that were already ingrained in devs’ minds with a passion, so failing to get everybody on the same page could kill the project.</p><p>To prevent conflicts and enable all devs to update the game independently, I created an Airtable repository explaining our findings and changes, <strong>enabling any dev to understand and update the game by themselves.</strong></p><ul><li>Need to create a new monster? Get the formulae in the repos.</li><li>Building a new map? Learn how to plan its geography and distribute monsters in minutes.</li><li>Lost a developer? No problem: all UX and dev knowledge is stored so even an intern could initiate the hardest tasks.</li></ul><p>Actually, PTEU’s latest top map was fully set up by a dev* with zero map-building experience and top players are pretty satisfied with it. It’s like having an engineering student building a perfect skyscraper all by himself! (*That appropriate professional was unavailable back then.)</p><h3>Design Solutions</h3><p>Maaany things were done, but you can see the biggest changes below:</p><h4>Monster roles</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifN3tzpjjDsGVbTclH166A.jpeg" /></figure><p>Although Priston Tale is an <strong>action</strong> RPG, I noticed the gameplay was surprisingly idle: players went to a spawn (a location where monsters are born) and simply spammed a given spell endlessly without any strategy. (Many even used auto-click software and alt+tabbed the game!)</p><p>One of the reasons was that all monsters on a map were similar in power, <strong>so I solved that by giving monsters specific roles like..:</strong></p><ul><li><strong>Minion</strong>: dies in seconds just so you feel powerful when crushing them. (Players also get to see their EXP rising non-stop, curbing boredom.)</li><li><strong>Demi-boss:</strong> less frequent, but strong enough to kill a whole party in seconds. You’d better rally the party to take him down ASAP!</li><li><strong>Shooter:</strong> always out of your spells’ range and forms an army of his own if left unattended. At least one player has to hunt them down.</li><li><strong>Tank:</strong> takes a while to die and prevents more monsters from spawning, so the quicker you kill them, the more EXP your party gets.</li></ul><p>We are just scratching the surface here, but you can see those mob roles add a layer of complexity to the game that forces players to strategise. Instead of simply gathering 6 players to spam spells randomly, players now assign roles to each other, looking for new ways to speed up their kill rate. <em>(Please, don’t share this article with them :P)</em></p><h3>Character rebalancing &amp; new playing styles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F5UccVtquILYloMhXa3ymw.jpeg" /></figure><p>Remember this is a 20yo with a low population? This is tragic when only 3 out of 10 chars are good at AoE (mass killing), which is the main way to level up quickly.</p><p>Although it’s important that each class has a given advantage over others, I concluded that all classes had to be similarly efficient AoE-wise to ensure no one would quit because they felt powerless.</p><p>Removing the privilege of those 3 classes seriously annoyed some players, but the player base increased because now everyone can play any day, any time, under any condition. Fighting skills over class choice! (I.e., efficiency variation dropped from 100%+ to ~20%)</p><p>Another important change was how chars were built: I noticed everybody picked AoE builds since mass killing is so important in PT, but that was disappointing because it killed players’ <a href="https://yukaichou.com/gamification-study/8-core-drives-gamification-3-empowerment-creativity-feedback/">Empowerment of Creativity</a>.</p><p>That’s why I reviewed all 10 classes and rebalanced each of their skills, ensuring that every class could be played in 2–3 ways. Players can now forgo their AoE skills and become a 1v1 killer, for instance, annihilating individual enemies. <em>(And as you can see, this contributes to the monster roles system since you could customise your hero to hunt a given monster type.)</em></p><h3>New progression / EXP table</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GZvBg4v60W8QDNd_92KdLg.jpeg" /></figure><p><strong>What people say is not what people do, right?</strong> Priston Tale proved that very clearly.</p><p>Many of our quitting players said they were leaving because PvP (player versus player battles) wasn’t good, but I noticed an odd pattern: the worse a map was, the more they complained about PvP — although it’s a completely unrelated part of the game.</p><p>They didn’t quit because PvP was bad but because monsters became so difficult that they wanted to PvP instead, which also disappointed them, causing a <a href="https://en.wikipedia.org/wiki/Cognitive_appraisal#:~:text=Cognitive%20appraisal%20(also%20called%20simply,health%2C%20coping%2C%20and%20emotion.">Cognitive Appraisal Error</a>. (When one projects their feelings of a situation onto something else, e.g.: hitting your toe against furniture and saying the world is actively against you today.)</p><p>To address that, I played every map with every single class to note down where things broke (e.g., a Lv 80 map being less fun and rewarding than a Lv 70 one), eventually coming up with my own spreadsheet of how an ideal progression would be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pizgdxv-KRLlzR6q" /></figure><p>This enabled players to advance in the world at a steady pace that kept them constantly excited to unlock the next map, removing the feeling of being stuck in a given region.</p><p><strong>Actually, the new progression was so effective that players had an </strong><a href="https://nudges.wordpress.com/the-illusion-of-progress/"><strong>Illusion of Progress</strong></a><strong>:</strong> players felt they were advancing faster even though I designed many regions to be actually slower than before. The only difference is that they were now sure that their efforts would be rewarded at a reasonable, predictable pace.</p><p>The best part is that we had a major uninstall rate around Lv 90 and that has plummeted since then, dramatically raising the number of endgame players on the server. (Where the money is!)</p><h3>Random events</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmH6e7f1LBGuahBOYl1IwQ.jpeg" /></figure><p>Who doesn’t like a surprise gift?! Especially when tired and bored!</p><p>Even with all the changes to improve gameplay, we learned that players are always looking for a way to “break the game” and make it too easy, even boring to play.</p><p>This inspired me to create an <a href="https://yukaichou.com/gamification-study/the-8-core-drives-of-gamification-7-unpredictability/">Unpredictability</a> system called Mimic: a special monster with rare drops that show up somewhere in the world every X minutes, <strong>changing player’s mood from deadly boredom to absolute excitement.</strong></p><p>Mimics became so popular that many play extra hours in hopes of getting a legendary item from them, turning what was supposed to be a distraction into an active goal.</p><h3>Quest system and lore</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b4QJCygf47iugHN-oQvUEg.jpeg" /><figcaption>Bloody Prince, one of the many monster/lore innovations</figcaption></figure><p>Priston Tale was purposely designed to be a grinding game: kill monsters over and over again to gain EXP and level up. No quests; no daily goals; no micro rewards. Just pure grinding.</p><p>PTEU addressed this by adding hundreds of quests to the game, but they could be very unstable since <em>quests could range from minutes to hours without any particular reason.</em> Many players would start a quest excited and leave right after finishing it because they felt boringly exhausted.</p><p>The solution? Calculating average playing time to devise a constant reward loop, giving players many motivation shots based on daily quests that they feel compelled to complete every day.</p><p>You can see all these systems feed each other: rebalanced monsters make battles more exciting ⮞ odds are some cool items will be dropped ⮞ while I wait for that, I finish a daily quest ⮞ the longer I take to finish it, the higher the chances of spotting an awesome Mimic!</p><p>The system is not perfect yet, but the sentence <em>“I’ve been playing for 5 minutes and I’m already bored”</em> has never been uttered again. Players know for a fact that quests fit in their schedule and they enjoy finishing them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/0*weaR2nHCqH7RzB-K" /><figcaption>Player feedback</figcaption></figure><p><strong>Last, can you imagine someone playing a game for 20 years and knowing nothing about its story?!</strong></p><p>Since PT originally had no quests, its story is completely unknown to most players. That’s why I embarked on a long research to learn everything about Priston’s story, allowing me to write dozens of quests that follow players from Lv 1 to 90 — fostering an <a href="https://yukaichou.com/gamification-study/8-core-drives-gamification-1-epic-meaning-calling/#:~:text=What%20is%20Epic%20Meaning%20%26%20Calling,much%20bigger%20than%20just%20yourself.">Epic Meaning and Calling</a> onto them.</p><p>The best part is that researching the game’s story gave the team a new perspective on feature development, motivating all to collaborate on the game’s story with update suggestions that expand Priston’s lore in a cohesive manner. Players now feel it’s a real world instead of a series of random regions stitched together.</p><p><strong>Along with these, I also designed a new travelling system, monsters, and skins</strong> to bring more life to the game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PmKWmQLzGc8G0oPaCxT6iA.jpeg" /><figcaption>This is the Astral Boat: a lore-based travelling system that helps players waste less time walking. Before that, the dev team wouldn’t even consider a new system, but adding lore changed their minds.</figcaption></figure><p><strong>Before we discuss metrics,</strong> here’s an actual trailer of all recent changes:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMbv6TeTpk7Q%3Fstart%3D5%26feature%3Doembed%26start%3D5&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMbv6TeTpk7Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMbv6TeTpk7Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9314271483eac304c7a60653d826e3ca/href">https://medium.com/media/9314271483eac304c7a60653d826e3ca/href</a></iframe><h3>Failures and Sucess</h3><p>Before talking about the good, I must say many things rest unfixed, be it due to coding limitations, failed executions, or simply not knowing how to tackle a problem.</p><ul><li>We still have low-level brackets where many players quit.</li><li>Level 90 specifically still makes many players lose motivation.</li><li>Getting players fully equipped is still hard, making some players feel they aren’t progressing.</li><li>Some monster roles are overpowered because I accidentally made them cruel to fair players while trying to punish cheaters.</li><li>Although decently balanced in test results, many players perceive some classes as overpowered due to numeric illusions. (E.g. Class 1 deals 200+800 {=1000} damage while Class 2 deals 500+500 {=1000}, making the former seem stronger because the number 800 is bigger than 500.)</li></ul><p>These and other problems were logged and will be addressed in the upcoming season, but we unfortunately can’t say much due to NDA.</p><h4>Business Results</h4><ul><li>Player count raised by 70%.</li><li>Revenue rose by 140%.</li><li>Character price rose from $1xx to over 4xx euros.</li><li><strong>Seasons no longer die off in 2 weeks, our greatest achievement.***</strong></li><li>Low-level maps are no longer empty, enabling more players to start a journey.</li><li>The average player level (=playing time) raised by 40%.</li></ul><p>***This is the most important result since PTEU is season-based: every X months, a new server starts where all players start <strong>a new journey for the next two months.</strong></p><p>Seasons always generate hyped, but problems were so many that most players would quit within the first 2 weeks, ruining PTEU’s profits and also making the game boring and lonely for those who started later.</p><p><strong>My greatest pride as a Priston developer is to say seasons now live up to their very last day and many even ask us to extend them.</strong> Even veterans, known haters of the seasonal system, are giving it a try due to its success!</p><p>As a member of PTEU’s dev team, I’ll keep working on the game for many seasons to come. If you happen to be a fan or simply want to learn more about UX and game design, just <a href="https://www.linkedin.com/in/romarioverbran/">follow me on LinkedIn</a>. (And if you are a game design pro, please, come enlighten me with your knowledge!)</p><p>Thanks for reading this article!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2f414fdf9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Case Study: How we saved $180 thousand using truly BAD ideas]]></title>
            <link>https://medium.com/design-bootcamp/case-study-how-we-saved-180-thousand-using-truly-bad-ideas-e14b6c7cc52?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e14b6c7cc52</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Wed, 03 Mar 2021 07:24:13 GMT</pubDate>
            <atom:updated>2021-10-05T12:14:12.414Z</atom:updated>
            <content:encoded><![CDATA[<h4>Facilitation techniques to make a fortune with the least creative people at your company</h4><figure><img alt="Woman browsing clothes on a human-sized smartphone screen" src="https://cdn-images-1.medium.com/max/1024/1*cf1x8r9Yf6rLfM4HSokg5A.jpeg" /></figure><p><strong>Working on a multimillion fashion marketplace,</strong> you can imagine that Black Friday is a day we all anticipate. Even the slightest tweaks can yield a fortune, so you can’t waste any opportunities.</p><p>That’s when your Marketing Manager shows up and say:</p><blockquote><em>“I always make the greatest BFs every place I work, so I must also do it here. </em>Designer (me), I need you to design a landing page so we can get some leads!”</blockquote><p>But if there’s one thing I’ve learned as a designer, is that <a href="https://uxdesign.cc/user-stories-are-poison-for-designers-creativity-486b128c0052">the first idea that comes to your mind is always the first idea worth forgetting</a>. The App Store is packed with failed apps born out of “strokes of genius”.</p><p>This is a story of how <strong>we broke records and saved $180.000 </strong>by questioning things we take for granted with disgracefully bad ideas. I hope you enjoy it :)</p><h3>The Challenge</h3><figure><img alt="Girl being asked if she either wants $100 or $120 in a week, to what she readily responds “I want $100 today!”" src="https://cdn-images-1.medium.com/max/1024/1*YDB1FFPG1Nz0XlI93NpUhA.png" /><figcaption>Art by Lakshmi Mani</figcaption></figure><p>The big problem is that <strong>most BF email landings neglect the notion of </strong><a href="https://www.wikiwand.com/en/Hyperbolic_discounting"><strong>Hyperbolic Discounting</strong></a><strong> </strong>and our urge for instant gratification.</p><p>In the image above, Lakshmi would have a 20% raise in 7 days —twice as much as the <a href="https://www.nerdwallet.com/article/investing/average-stock-market-return">average return on stocks</a> over a whole year—which is a HUGE return on time investment.</p><p>But just like her, you’d rather get $100 today, wouldn’t you?</p><p><em>So why do we assume people want to subscribe to email lists and wait? </em>As a former marketing manager, I felt we could do better.</p><blockquote><strong><em>My goal was to rethink how landing pages were made and show managers the importance of giving the team creative room to work.</em></strong></blockquote><h3>Ideation &amp; Facilitation Techniques</h3><figure><img alt="Designers at a table doing a brainstorming session" src="https://cdn-images-1.medium.com/max/1024/0*XGRSAei30uDPSM-2" /><figcaption>Photo by <a href="https://unsplash.com/@youxventures?utm_source=medium&amp;utm_medium=referral">You X Ventures</a></figcaption></figure><p>A small project such as this (2 weeks) is a great opportunity to run a design sprint and innovate quickly, proving the value of investing in good design.</p><p>I decided to run a creative workshop to explore the buyer’s journey towards a coveted Black Friday deal. Here are my creative tools:</p><ol><li>User Journey Map</li><li><strong>Challenging Assumptions</strong> (The Superstar here)</li><li>How Might We questions</li><li><strong>Worst Possible Idea </strong>(This works like magic)</li><li>Brainwalking</li><li>Four Categories Method</li></ol><h3>The User Journey Map</h3><p>To prevent us from building another boring landing with a lonely email form, my goal was to challenge assumptions on how a regular BF purchase occurs and find out how to make subscription forms more tempting / engaging.</p><p>I decided to dissect each step of the buying process and draw a UJM to help my colleagues —<em> the real stars of this project</em> —experience such a journey.</p><figure><img alt="User Journey Map showing the path from awareness to purchase" src="https://cdn-images-1.medium.com/max/1024/1*OX1DbIgLy-ZO3B4ymcj20A.png" /></figure><blockquote>“You have to ask a few dumb questions before you reach the insightful ones,“ Don Norman</blockquote><p><strong>Assumptions are everything you take for granted</strong> — the obvious stuff that simply exists without questioning — but since we don’t question them, we also don’t come up with creative replacements.</p><p>Example: Anne thinks of how much SHE will save this BF. That’s cool, but why Anne’s friends and relatives are out of the process? Why subscription forms are so self-centred when we have a new social network every year?</p><p>By picking up these (and other) obvious points, I could gear my colleagues’ creativity towards finding new ways of capturing leads.</p><figure><img alt="5 Post-its with assumptions about the product, like “the buying process is self-centered”; “people only buy if discounts are huge…”" src="https://cdn-images-1.medium.com/max/1017/1*rqjYFOasVrUCapuMYAFCZQ.jpeg" /></figure><p>These and many other assumptions were turned into <a href="https://www.designkit.org/methods/3">How Might We questions</a> the team answered with the TERRIBLE ideas right here. ↓</p><h3>Boosting Creativity with the Worst Possible Ideas</h3><p><strong>Have you ever went blank when requested to come up with a new idea? </strong>Maybe it was something as trivial as labelling a page, but it felt sooo difficult!</p><p>Working in a group makes it all worse as you fear your fellow designers are more creative than you. (If you aren’t a creative professional, you know the creative guys will crush you.) It’s an awful situation for everyone.</p><p>But what if we simply made people say the worst things they possibly can?</p><p>By telling people to come up with trashy ideas, we shift the pressure from <em>“prove you are the best”</em> to <em>“show us how nuts you can go”</em>, turning judgement into bursting-laughter.</p><p>Even the most square minded people will bring you new ideas, for instance:</p><figure><img alt="A row of posts-its with really bad ideas, like “let’s buy an illegal email list…”" src="https://cdn-images-1.medium.com/max/1024/1*NwArFIzBCaARgE-9yEUubA.jpeg" /><figcaption>The second one was jaw-breaking, hahaha…</figcaption></figure><p>Aren’t these ridiculous? But those awful ideas conceal countless valuable insights that we simply forget or worse: things we don’t want to play with.</p><p>To ridicule the idea of giving away leather clothes is also to say they are worth a lot and that customers would freak out if we did it. To say we should distribute defective clothes reminds us of the many unsold products on shelf.</p><p>These and many other insights never crossed our minds during the whole BF warm-up, but thanks to the <a href="https://www.interaction-design.org/literature/topics/worst-possible-idea#:~:text=Worst%20Possible%20Idea%20is%20an,gain%20insights%20towards%20great%20ideas.">Worst Possible Idea technique</a>, we uncovered a whole new array of design and marketing possibilities.</p><h3>Brainwalking: Turning Bad Ideas Into Features</h3><p>Bad ideas won’t bring innovation by themselves, right? Brainwalking is a great way to catalyse collective creativity, seizing the best of everyone’s expertise.</p><p>To brainwalk is to simply leave your post-its behind and walk up to your colleague’s post-it. You read it then pull out a new one, writing how that idea could be better / how to turn an awful idea into a useful one. (Since we were working remotely, we used InVision Freehand for that.)</p><figure><img alt="Brainwriting board showing original ideas and many improvements" src="https://cdn-images-1.medium.com/max/657/1*N11QUb7L0jcIlf_J4G0bRw.jpeg" /><figcaption>Unfortunately, these are confidential data</figcaption></figure><p>An interesting benefit about this process is that <em>you end up with so many ideas that people forget what belongs to them,</em> so you rarely see people attached or jealous of anything they did. Group creativity pulverises authorship!</p><p><strong>Disclaimer: my role was to enable the best of my colleagues,</strong> hence I didn’t bring any good ideas at any moment. My colleagues were the genius here :D</p><h3>Last Step: The Four Categories Method</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*mb7r_fATRb5jwxEWsditKA.jpeg" /></figure><p>Remember I said we had two weeks to ideate and develop? The problem is that we came up with so many ideas we could never build that quickly.</p><p>The Four Categories Method is a prioritisation matrix that helps you label what are your <em>Most Rational, Delightful, Daring and Long Shot ideas,</em> making consensus easier for everyone.</p><p>I made slight changes to it considering our marketplace and language.</p><figure><img alt="Matrix showing how each idea is categorised" src="https://cdn-images-1.medium.com/max/767/1*dnL0jHWj-tRY0QBszS22Fw.jpeg" /></figure><blockquote>“But wait, you said you had so many ideas and I only see 12 here!”</blockquote><p>You are right! I forgot to tell you that we <a href="https://www.wikiwand.com/en/Dot-voting">dot-voted</a> our favourite ideas to finish with the ones above, which were then sent to our marketing manager to categorise and prioritise.</p><p>I decided to let the manager categorise them alone because it’s important he also feels he really owns the project. He’s the one whose job is on the line, burdened with business objectives we barely know, so having him finish the creative process was great to ensure we were on the right path.</p><h3>Wireframing &amp; Reasoning</h3><figure><img alt="Wireframing showing the proposed user flow, subscribing with one datum at a time" src="https://cdn-images-1.medium.com/max/1024/1*nDTnRFQwkNZOfoX8aWyhZA.jpeg" /></figure><p><strong>I decided to bring a bit of Gamification to the new form by fostering anticipation and devising a quick loop of dopamine spikes,</strong> conforming to the Hyperbolic Discount I mentioned earlier.</p><p>That was achieved by combining <em>Progressive Disclosure</em> with a series of <em>Instant Gratifications</em>, getting users hooked from start to finish:</p><ol><li>The first screen offers a coupon that can be used anytime, PLUS access to a collection of premium apparel with special discounts. (The blurry section.)</li><li>We wanted more than users’ emails (name, phone, brand preferences), but we know people hate long forms, so I split the data into four sub-forms.</li><li>Each sub-form rewards the user with a discount percentage, promising a discount increase if (s)he moves to the next step.</li><li>When you have enough, you receive the coupon and move to a secret page where you find exclusive deals, including those blurry offers.</li></ol><h3>UX ROI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_AuCynBTA4TvoX7Hy58-bw.png" /></figure><p><strong>Subscription raised from ~5.000 to ~30.000, achieving a 500% increase. </strong>(<em>All estimates were disclosed by the manager himself </em>[I left the company.)</p><p>Thanks to a more streamlined user flow, this UX reduced Cost per Lead seven-fold,<strong> saving $180 thousand in customer acquisition.</strong> This was staggering!</p><p>But what about sales? Well, this is a delicate matter: we rely on what other brands sent us since it’s discount retail — but they’ve been keeping items to themselves due to Covid, so our inventory was <em>severely</em> compromised.</p><p>Even so, <strong>we managed to sell as much as the best BF pre-covid,</strong> so I say that’s something worth celebrating too! :D</p><p><em>Countless ideas we uncovered were rather marketing oriented (not designable) or too hard to develop, so they were stashed to 2021’s BF, when the team will have more time to prepare.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e14b6c7cc52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-how-we-saved-180-thousand-using-truly-bad-ideas-e14b6c7cc52">UX Case Study: How we saved $180 thousand using truly BAD ideas</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How user stories destroy designers’ creativity and how you can fix them]]></title>
            <link>https://uxdesign.cc/user-stories-are-poison-for-designers-creativity-486b128c0052?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/486b128c0052</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Tue, 16 Feb 2021 12:40:38 GMT</pubDate>
            <atom:updated>2021-03-15T01:20:37.342Z</atom:updated>
            <content:encoded><![CDATA[<h4>If you want to design disruptive products, you must abandon standard stories</h4><figure><img alt="Woman inserts cards into a smartphone with the phrases “As a user, I want to, so that”" src="https://cdn-images-1.medium.com/max/1024/1*t9UJfWGxa37U-fWgQMixBQ.jpeg" /></figure><p>As a UX Tutor, I review hundreds of user stories from aspiring designers striving to address their personas’ needs — <em>but they end up doing exactly the opposite.</em></p><p>That’s because <a href="https://www.aha.io/roadmapping/guide/requirements-management/what-is-a-good-feature-or-user-story-template">user stories focus on features rather than needs,</a> so most students (and dev teams) struggle to develop innovative products since this framework suppresses their creative efforts.</p><p>Here’s a recurring example of how user stories impair my students:</p><blockquote>“As a learner, I want to receive notifications so that I can stick to my study schedule.”</blockquote><p>Pretty reasonable, but when was the last time you thought: <em>“you know what, I definitely need more notifications!”?</em></p><p>Back in school, you had the most reliable alarm system (a furious, yelling mother), but that didn’t prevent you from slacking off and cramming the night before a major exam. Yes, notifications can certainly help, but<strong> if student engagement is the problem, then notifications are certainly NOT the answer.</strong></p><p>Actually, I bet that an app that starts a call with your mother when you skip studying would engage you much more, wouldn’t it?</p><p>This joke shows that a given problem has many solutions (that’s what designers live for!), but if you have a tool that makes you rush for answers, you’ll probably end up with the worst one. The first idea that comes is a shitty one 99% of the times.</p><p><strong>My point is that <em>user stories are a </em></strong><a href="https://herbig.co/product-discovery/"><strong>Product Discovery tool</strong></a><strong> – <em>a conversation starter for you to dive into the user’s life –</em></strong><em> </em>but if those stories bring you features, then you cannot discover what is already “discovered”. Conversations are awful when someone claims to have all the answers.</p><p>That’s why we need a new story structure that leaves features aside to concentrate on our users’ pains and needs — and needs can be fixed in infinite ways, just like UXers’ famous Design Thinking can generate infinite solutions!</p><blockquote>“As a product owner, I want to write features in a story format so that I don’t save time by simply writing the requirements.”</blockquote><h3>How to Write Better User Stories</h3><h4>Solution #1: invert it and start with the Why</h4><figure><img alt="Golden circle showing Why (what users really want), How (they’ll get it), and What (they are getting)." src="https://cdn-images-1.medium.com/max/585/1*MxoxdpQC2anmi9ay1wh4sw.jpeg" /></figure><p>Here’s a funny user story some product beginner would write when starting a fashion business:</p><blockquote>As a naked person, I need to buy clothes so that I can hide my shame.</blockquote><p>But do people buy clothes only to hide their parts? Or do they buy it to feel better — to impress colleagues, lovers, and friends?</p><p>That’s why I love <a href="https://medium.com/u/2d95ad0e562b">David Pereira</a>’s advice on <a href="https://www.youtube.com/watch?v=vchYZnTg9oQ">starting with the Why</a>:</p><blockquote>#1: <strong>To</strong> feel empowered in my routine, <strong>as [a user] I want to</strong> acquire clothes <strong>that</strong> make me look elegant.</blockquote><ul><li>Here the focus is on <strong>Why</strong> the user really craves something (a need that comes from within, unrelated to features);</li><li>Followed by <strong>Who</strong> wants it (so your team knows a bit about <a href="https://www.mypronouns.org/ze-hir">zir</a> history);</li><li>Wrapping up with the <strong>What</strong> represented by some intention or even limitation supporting the Why. (Need to learn about the Why? <a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action/up-next?language=en">Click here</a>.)</li></ul><p>“Nice, but my user doesn’t care about fashion. This one doesn’t count!”</p><p>Well, people who really don’t care would save money by buying ripped clothes, but okay, let’s suppose our brand targets the traditional dad:</p><blockquote>#2: <strong>To</strong> save money for what matters most, <strong>as [persona] I want to</strong> get my outfits <strong>for</strong> a low price.</blockquote><p>Now you know why he buys clothes at Walmart; whom he’d rather save his hard-earned money for; and what he expects from your brand.</p><figure><img alt="Infographic of how ideas first diverge (spread towards meaning directions) before converging to some objective solution." src="https://cdn-images-1.medium.com/max/1000/1*eF8uNeml0EOFOi5hgVebfw.jpeg" /><figcaption>Stories are for you to go wild. You can converge towards features later. (Source: IDF)</figcaption></figure><p>Notice you’d still offer the obvious (cheap clothes [or notifications]), but you’d also be able to deliver stuff no other brand ever did for him, like..:</p><ol><li>Giving access to restaurants and local clubs;</li><li>Providing credits for streaming services;</li><li>Organising / fostering family events;</li><li>Or even donating part of your profits to some charity he cares about.</li></ol><p>And how do you learn those needs? Doing UX Research, of course.</p><p>If you can’t craft these stories due to lack of data, then stories are the least of your problems. Get out in the wild and interview some users! :)</p><h4><strong>“But my stakeholders force me to use the traditional format!”</strong></h4><figure><img alt="Frozen Yogurt 20% Fat vs Frozen Yogurte 80% Fat-Free" src="https://cdn-images-1.medium.com/max/1024/1*4p88ra_vLqGoodf7rSRAKw.jpeg" /><figcaption>Same content; opposing feelings. Pick your words carefully. (Source: thedecisionlab)</figcaption></figure><p>I honestly don’t think you should, but I understand some stakeholders can be a bee, so here we go.</p><blockquote>#3: <strong>As</strong> someone who doesn’t bother about fashion, <strong>I want</strong> clothes for a fair price <strong>so that</strong> I can spend on what matters most in life.</blockquote><p>If you’ve ever studied the <a href="https://thedecisionlab.com/biases/framing-effect/">Framing Effect</a>, you probably worthless fashion became the priority here. This is awful, but if you manage to make a joint effort to focus on the “so that…”, you’ll probably be fine. ;)</p><h4>Brief time-out: how to come up with creative ideas quickly?</h4><p>User stories are just a framework so they obviously won’t give you any ideas. (Although it helped me think of those four above in a matter of seconds.)</p><p>The good news is that you can <a href="https://blog.prototypr.io/how-to-generate-diverse-ideas-in-30-minutes-7a4196e7d6ce"><strong>come up with innovative ideas in no more than 30 minutes</strong></a> by checking these creative techniques from Prototypr.</p><p>I promise that combining those with your new stories will amaze you!</p><h4>Solution #2: switch to Job Stories</h4><figure><img alt="What the customer buys (a skate) vs what the user wants (air tricks)" src="https://cdn-images-1.medium.com/max/1024/1*gbJ162vRtTYf9rTGd0V1vA.png" /><figcaption>Customers don’t want skates; they want air manoeuvres. (Source: JBTD.info)</figcaption></figure><p>The Jobs-to-be-Done Theory states that people buy products and services to get some job done — so by really understanding what that job is, chances are your designs will have an easier time dominating its marketplace.</p><p><strong>And what would that job be? Some ultimate goal of acquiring a product</strong> — or an inner need— instead of the purchase itself. In sum, a job is the “Why” behind a product choice.</p><p>Here’s what <a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27">the very creator of Job Stories</a>, Alan Klement, says about it:</p><blockquote><em>We frame every design problem in a Job, focusing on the triggering event or situation, the motivation and goal, and the intended outcome:</em></blockquote><blockquote>When _____ , I want to _____ , so I can _____ .</blockquote><blockquote><em>For example: When an important new customer signs up, I want to be notified*, so I can start a conversation with them.</em></blockquote><p>*Since “notified” is so closely linked to app notifications, I’d recommend you use some other word that doesn’t bring such an obvious association to mind.</p><p><strong>Once again, notifications are NOT the problem!</strong> It’s just that this seller may receive so many alerts that he could missthe relevant ones. Maybe an automatic call from his CRM system, for instance, would notify him better.</p><figure><img alt="When (situation), I want to (motivation), so I can (expectation)." src="https://cdn-images-1.medium.com/max/1024/1*Y0Ns91ASkeOxMmAH3SGTdg.png" /><figcaption>Source: MountainGoatSoftware</figcaption></figure><p><strong>But I have one major disagreement with job stories:</strong> they ditch personas to hyper-focus on their needs.</p><p>That can be problematic since <em>different users facing the same “job” could benefit from different solutions to it</em> (men and women have far different beauty needs, for instance), so using JS could make you neglect crucial info about users.</p><p>Personas solve that with their shared list of personal data (devices, routine, etc.) that you’d skip when writing your JS – or if didn’t, that would result in a huge story. (Probabbly a dull and/or dangerously biased one.)</p><p><strong>So how can we solve this? </strong>JBTD specialists might hate it, but I’d recommend favouring job stories only when dealing with rather procedural tasks. (Ex: users need to tackle a specific problem.)</p><p>If going wild is what you seek (ex: early discovery phases when creating a new product), I’d recommend trying user stories or even daring to add a persona to it. <strong>(Highly discouraged by JBTD pros.)</strong></p><blockquote>When an important new customer from [persona] signs up, he wants to be notified*, so he can start a conversation with them.</blockquote><p>This is against JBTD precepts! Do not try that unless you have enough experience to counteract unexpected biases that may occur.</p><blockquote><strong>Whichever framework you pick, just keep in mind that the Why</strong> should be the focus of your design.</blockquote><h3>Final Recommendations</h3><p>An interesting thing about the Why is that it’s often associated with some driving-force such as a latent emotion.</p><p>That’s because <a href="https://www.annualreviews.org/doi/full/10.1146/annurev-psych-010213-115043#:~:text=The%20research%20reveals%20that%20emotions,emotions%20influence%20judgments%20and%20choices.">emotions are largely responsible for decision-making,</a> so bringing the users’ feelings to your user/job stories will impact how well your design team answers them.</p><figure><img alt="Spoiled child screaming “feelings”." src="https://cdn-images-1.medium.com/max/245/1*3GHgqUfd29F-kAOObYnH9w.gif" /></figure><p>Here’s an example we used earlier:</p><blockquote><strong>To feel empowered in my routine,</strong> as [a user] I want to acquire clothes that make me look elegant.</blockquote><p>Isn’t it better than..:</p><blockquote><strong>To look better in my routine,</strong> as [a user] I want to acquire clothes that make me look elegant.</blockquote><p>All it takes is thinking of <a href="https://wildsimplejoy.com/the-most-empowering-words/">power words</a>, emotions, and any strong verbs that could help your users’ needs shine and make your team empathise with it.</p><p>But you obviously won’t make those up — UX Research should be the grounds of everything you do — so tread carefully if you don’t have enough data.</p><p>And, please, keep in mind what I told you earlier about Product Discovery:</p><blockquote>“You cannot discover what is already discovered.”</blockquote><p>Make sure you are sparking conversations, not an awkward silence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*ZfnEF0yAttZeoq9y" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=486b128c0052" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/user-stories-are-poison-for-designers-creativity-486b128c0052">How user stories destroy designers’ creativity and how you can fix them</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: How I designed an $83K revenue MVP in just 4 days]]></title>
            <link>https://medium.com/design-bootcamp/how-i-designed-an-83k-revenue-mvp-in-just-4-days-b13ef25d7f84?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b13ef25d7f84</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Tue, 26 Jan 2021 19:55:46 GMT</pubDate>
            <atom:updated>2021-10-14T14:31:46.228Z</atom:updated>
            <content:encoded><![CDATA[<h4>The perfect solution is not always the best solution</h4><figure><img alt="Man leaning over piled boxes inside a smartphone" src="https://cdn-images-1.medium.com/max/1024/1*jzhlua6gQjjrzlVaPj1XfA.jpeg" /></figure><p>Logistics are one hell of a hurdle when the entire European Union could fit inside your country’s border twice over.</p><p>This is OFF Premium’s ordeal: a multi-million fashion marketplace working with hundreds of stores spread throughout Brazil’s 8.5 million² kilometres, resulting in shipping costs of up to $400 for a single shirt!</p><p>Customers were furious on social media, claiming they were abandoning packed carts and visiting competitors — and I honestly believe they should. 😅</p><h3>The Problem</h3><figure><img alt="“I want to buy cool stuff online, but shipping is more expensive than the products.”" src="https://cdn-images-1.medium.com/max/512/1*iuCLyXCnFnoZAfdhkDK7WA.jpeg" /><figcaption>“You guys are profiting from this shipping!,” some said. (Spoiler: unfortunately not.)</figcaption></figure><ul><li><strong>Shipping used to be free but commercial policies suddenly changed,</strong> making prices go from $0 to $XXX out of nowhere. (Clients went mad!)</li><li>Built on <a href="https://vtex.com/us-en/">VTEX</a>, OFF’s checkout process is severely “code-locked”, affording minimal CSS tweaks. (The best solutions take months to develop!)</li><li>A consistent buying process that hadn’t changed for years, so any changes would heavily impact the hundreds of thousands of users.</li><li>If that wasn’t enough, we needed to fix it before Black Friday, otherwise it could be a disaster — and we had no more than 4 days to do so!</li></ul><p>No room for failure: only guerrilla UX Research and development remain. (<a href="https://medium.com/serious-scrum/how-i-made-my-team-deliver-value-after-failing-for-6-months-3c96ea1bc2b3">Seriously, talk about Agility!</a>)</p><h3>The Design Process</h3><p><a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">Nielsen proposes you test with 6 users</a> (per user flow) before making any design decisions so you avoid biased results.</p><p>Ain’t nobody had time for that. Once again, <em>4 days,</em> so we had to go extreme!</p><p>What I call <em>“guerilla research and development”</em> is a quick round of test &gt; redesign &gt; test &gt; redesign &gt; <strong><em>while development occurs,</em></strong><em> regardless if you have statistical significance.</em></p><figure><img alt="Design process showing rounds of design, test, and development" src="https://cdn-images-1.medium.com/max/840/1*BhmjXga86eyXOHwJn0XuKg.jpeg" /></figure><p>This sounds pretty insane(risk of technical debt + design bias), but there’s an argument for that: all humans are affected by the same <a href="https://uxdesign.cc/ux-psychology-2-increasing-conversions-with-the-decoy-effect-272500321df7">cognitive biases</a>, so if a user has a given problem, it’s likely that many others also do!</p><p>Also, remember I researched the subject before? I had enough data to say this MVP would work better than the original design, so I defined some basic UI parameters the developer could work on regardless of test results.</p><h3>Original Design &amp; Task Flow</h3><figure><img alt="Four screens showing how the UI originally was" src="https://cdn-images-1.medium.com/max/1024/1*b3HanUmpp3k1RjUJz4PyXg.jpeg" /><figcaption>Here you see shipping cost almost twice as much as the products.</figcaption></figure><h3>Hypothesis Statement</h3><p>Dropdown carts should 1) only provide a summary of your clothes, and 2) clients must know how each item affects shipping price and its estimates.</p><p>Since VTEX’ dropcart is unable to provide detailed shipping, customers would have to test how each item affects pricing (by adding and removing stuff repeatedly), but that probably never happens.</p><p>A solution would be to remove the ZIP field, reducing the burden of seeing added items as a prelude to a purchase. <strong>The less customers see it as a buying process, the more likely they are to add more items </strong>— and the less likely they will be to remove them. <em>We call this the </em><a href="https://www.wikiwand.com/en/Sunk_cost"><em>Sunk Cost Effect</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehkzJ6GgFHM7wvUMQJKLUw.png" /></figure><p>The Sunk Cost Effect is a cognitive bias that makes people stick to choices they invested time or money in, for instance: if you pay $400 for a concert, a dangerous frozen road is not enough to make you stay at home.</p><p>And if you spend an hour adding items to your shopping cart, you also be less willing to remove stuff since you have already grown attached to it.</p><p><strong>Final Assumption: less cart abandonment and more items purchased.</strong></p><h3>New Dropdown Cart UI</h3><p>As I told you in <em>“</em><a href="https://uxdesign.cc/ux-psychology-3-how-to-make-foolproof-designs-with-teslers-law-ab63a05706f1"><em>how Tesler’s Law makes your designs fail</em></a><em>”,</em> every system has a given amount of complexity you must respect — <em>so no matter how good your new design is, it will fail if you don’t account for Tesler.</em></p><p>That’s why we simply couldn’t remove the ZIP field from the dropdown cart. Users would feel lost and potentially mad (<em>“Not only the price is abusive, now you are hiding charges from me?!”</em>), so I had to try a different strategy:</p><figure><img alt="New design showing a warning instead of a ZIP code field" src="https://cdn-images-1.medium.com/max/943/1*2MX55lZu9tQFrc_BMPwLqQ.jpeg" /><figcaption>Before / After</figcaption></figure><p>Replacing the ZIP field with a temporary friendly warning telling users all shipping info can still be found on the next page (cart), as they always did.</p><p>The warning is pretty bold (heavy black) but it’s intentional as it couldn’t be missed and, fortunately, all testees noticed it and proceeded to “checkout”!</p><p><strong>Development instruction:</strong> I requested our developer to implement it right on the first day as “hiding” those bizarre prices would be enough to get people moving beyond the product page.</p><h3>New Cart UI: before testing</h3><p>Relying on <a href="https://uxdesign.cc/5-ux-research-insights-from-the-greatest-fashion-ecommerce-in-brazil-7c7d709a44b1?source=user_profile---------10----------------------------">previous research I had done</a> and lots of conversations with devs, we came up with a new design that I was “sure” would work. Here you go:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PRHX9AVbntfznpIg4NQJUg.jpeg" /><figcaption>New design showing shipping info inside floating cards</figcaption></figure><p>Although the “Best price” box remains (we couldn&#39;t remove it), we now have a set of cards explaining it. Each card represents a package (yes, that’s what <em>“many estimates”</em> meant) so users can see why packages won’t arrive at the same time and how prices vary.</p><p>I bring another bold warning to ensure people notice the changes. This one explains how orders are divided, but even if you don’t click on it, it draws your attention to the set of cards that makes shipping info much clearer than before.</p><p>As I told you, <em>this is not the best solution (the final one says items’ location, shipping company, etc.)</em> but that’s what VTEX’ code let us play with.</p><p><strong>Development instruction:</strong> “Start working on this set of cards with pricing and estimates. Oh, and we might need a ‘remove’ button, so prepare the code. Regardless of test results, I’ll find a way to make these cards work.”</p><h4>New UI after testing: 1st &amp; 2nd user</h4><p>Remember we only had 4 days to develop this? That’s why I designed in-between tests, saving all the time that would be wasted recruiting users.</p><blockquote>Task: “Please, tell me the shipping cost of [given item].”<em> (Placed in the last card, so users must swipe to see it.)</em></blockquote><figure><img alt="New version without floating cards, having borders around it" src="https://cdn-images-1.medium.com/max/943/1*qQ4ACqtqn0gbuGo7oT3aDQ.jpeg" /></figure><p>The first testee (an eComm heavy user) simply didn’t notice she couldn’t swipe right to see more — and as I told you a hundred times, we only had 4 days, so if a user’s problem is all users’ problem!</p><p><strong>That’s when I remembered 93% of human vision is dedicated to border detection to mitigate </strong><a href="https://www.wikiwand.com/en/Ensemble_coding"><strong>Ensemble Coding</strong></a><strong>.</strong> By switching from dropshadows to black borders, I hoped our users’ eyes would never ignore the hidden cards— and fortunately they didn’t!</p><p>Last, you see a new shipping text on the centre. Having “1/3” on the left and “shipping” on the right required a bi-directional eye movement (top-down, then left-right), thus compromising scannability.</p><p><strong>Development instruction:</strong> “add a border to it and make our dropdown cart’s warning work as ‘proceed to cart’ .” (Yes, I user tried it repeatedly.)</p><h4>Last testees: Task: “How could you make it more affordable?”</h4><figure><img alt="Final layout with different diagrammation" src="https://cdn-images-1.medium.com/max/943/1*eJmTZFuwEIhwAetcyIjLww.jpeg" /></figure><p>Here’s a puzzle: if I add a big “remove” button to every package, I’m <a href="https://www.wikiwand.com/en/Nudge_theory">nudging users</a> towards emptying their cards. If I don’t, then I’m providing a bad experience as people will have to find their way around it.</p><p>I only made up my mind after noticing users didn’t realise they could remove an expensive package, saying <em>“I’d abandon the cart altogether.” (</em>That’s exactly what we are fighting against!)</p><p>That’s why I added that discrete “remove” button on the upper-right corner. Yes, we have the bi-directional gaze once again, but having the most relevant info on the left ensures users won’t miss it — while the light-grey “remove” is only noticed by those looking for it. Now we have it!</p><p><strong>(Tests continued successfully after the 3rd testee, so let’s skip those.)</strong></p><h3>A/B Test Results: +$83K after a month</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2Q5d1ZI5gzN-2mTNJT6NQ.jpeg" /><figcaption>Mobile test results</figcaption></figure><p>Mobile resulted in a <strong>$54 thousand increase, led by an additional 5% conversion rate. </strong>Just as I predicted, <em>average purchases rose by $30 </em>as people didn’t need to remove each item to find out why shipping was so expensive.</p><p><em>An unexpected result is that more carts were abandoned and yet OFF sold more.</em></p><p>I’m not sure, but it probably has to do with VTEX having two shipping pages: the one you just saw (cart) and a second one right before the payment page. This second one has more info than the former, but it’s also so intricate that many users simply quit when they reach it.</p><p>So although disclosing shipping info on the cart made more people quit it, those who continued felt so safe that they ignored the confusing pre-payment page, dropping its bounce rate from 17% to 6%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1GwWRjU44EE6m17JPuWBw.jpeg" /><figcaption>Desktop test results</figcaption></figure><p>The desktop version could only run for 2 weeks but it was enough to generate <strong>$29K revenue and a +15% conversion rate. </strong>It seems it would beat the mobile version if it ran for a month, and that’s awesome!</p><p><em>The secret here is that OFF’s desktop site had no cart </em>(you’d go from dropdown cart to payment) because some stakeholders didn’t want it. That was the perfect recipe for disaster as customers relied on that misleading dropdown to estimate their shipping.</p><p>As you’ve noticed, I had to cut corners to get this working in four days but that was certainly worth it. (This required huge alignment between myself, POs and development, <strong>so I seriously discourage you from doing the same unless you reaaally need it.</strong>)</p><p>I’d like to thank my colleagues for this amazing run and also you, for reading this story until the end! ♥</p><p>If you have any doubts, please, share it in the comments and I’ll be glad to lend you a hand! =)</p><p><strong>Oh, feel free to connect: </strong><a href="https://www.linkedin.com/in/romarioverbran/"><strong>https://www.linkedin.com/in/romarioverbran/</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b13ef25d7f84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-designed-an-83k-revenue-mvp-in-just-4-days-b13ef25d7f84">Case study: How I designed an $83K revenue MVP in just 4 days</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Psychology #3: how Tesler’s Law makes your designs fail]]></title>
            <link>https://uxdesign.cc/ux-psychology-3-how-to-make-foolproof-designs-with-teslers-law-ab63a05706f1?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab63a05706f1</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Thu, 14 Jan 2021 17:32:32 GMT</pubDate>
            <atom:updated>2021-01-17T15:37:00.753Z</atom:updated>
            <content:encoded><![CDATA[<h4>Every UX has an amount of complexity you cannot play with</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eFItAhpKSfRFrHc4eB1Pjg.jpeg" /></figure><p><a href="https://www.nngroup.com/articles/fresh-vs-familiar-aggressive-redesign/"><strong>People hate redesigns.</strong></a> Unless the original work is terribad, chances are the new version will be stomped even if it’s remarkably better.</p><p>Snapchat learned it the hard way back in 2018 after a major redesign that <em>burned 35% of their revenue.</em> Although it had a better Information Architecture than the original, it changed the app’s complexity so much that 5 million users simply jumped out of the boat.</p><p><strong>But how can a system be both easy and complex at the same time?</strong></p><p>Let’s explain that with something you’re certainly familiar with: a front door.</p><figure><img alt="A traditional blue door against a yellow background" src="https://cdn-images-1.medium.com/max/1024/1*ZlKaeBrMPQ5gmQWZFL7BSg.jpeg" /></figure><p>Equipped with a lock and handle, doors are pretty straightforward to use anywhere in the world. You just insert a key, turn and push it — no magic here!</p><p>But you need to get a new door as soon as possible. It seems like yours has been eaten away by termites and is now screeching like a demon every time it’s opened. Every f.ing morning by 6 am, it wakes you up as its sound cuts through your ears when your spouse goes remove the snow from the porch.</p><p>Sweating in anger, you jump out of bed, change earlier for work and make a sharp demand: <em>“change this crap before I’m back from work!”</em></p><p>He does exactly as you wish. Here’s what you find when you get back home:</p><figure><img alt="A door without lock and handle, having a rectangular white shape on its upper-part" src="https://cdn-images-1.medium.com/max/1024/1*5neTwL7Shw8lLmVFYBFTOw.jpeg" /></figure><p>No lock, no handle. You push it, punch it, and even throw yourself at it like an NFL player but nothing happens. Mad and freezing in the cold wind, your spouse suddenly opens it and says: <em>“why didn’t you just stare at the sensor?!”</em></p><p>The new door is controlled by eye recognition. It’s much easier than finding your keys inside your chaotic bag, picking the right key in the keychain, inserting it, turning the handle, and pushing the door. Yet you couldn’t do it.</p><blockquote>Isn’t it ironic that it got much harder as it got much easier?</blockquote><p><strong>Tesler’s Law, or The Law of Conservation of Complexity,</strong> asserts that <em>every system has an inherent amount of complexity that cannot be removed or hidden without throwing the burden of managing it at someone.</em></p><figure><img alt="A balance-scale in perfect balance, having a brain on the left and a computer on the right" src="https://cdn-images-1.medium.com/max/1024/1*oYFHxDBTFiJgQR7gwChA7w.jpeg" /></figure><p>By “complexity” I don’t mean difficulty, but the series of actions and resultant feedback a given system requires to perform a given ask — e.g., your <a href="https://www.nngroup.com/articles/mental-models/">Mental Model</a> of how a door should work.</p><p>It’s unquestionable that opening your door is now much easier (from 30+ secs to a quick stare), but achieving that easiness required such a drastic reduction of the base-level complexity that you now must relearn how to use something so simple such as a door.</p><p><strong>New designs are like a balance scale: to make your system’s complexity lighter, weights must be placed on your users’ cognition et vice-versa.</strong></p><p>Oh, I really mean that “vice-versa”: had you (the user) demanded a sliding door instead, your spouse (the developer) would be left to figure how to install it in the house (the application).</p><p>But does this house afford a sliding door? Maybe the walls simply wouldn’t handle such construction, i.e., a technical limitation. It’s also possible that your spouse simply doesn’t know how to install a sliding door, so Tesler’s scale would be against him here.</p><p>Whenever you have an established system or a mental model running, someone will have to manage the irreducible complexity in the works.</p><h3>How to Manage Tesler’s Law in UX Design</h3><h4>#1: Progressive Redesign</h4><figure><img alt="Apple Music’s UI design evolution from 2008 to 2018" src="https://cdn-images-1.medium.com/max/1024/1*Rf9K2Q-zyDwavVI9yDpY8A.jpeg" /><figcaption>Apple Music Player since 2008</figcaption></figure><p>As I told you at the beginning, you don’t fully redesign an app (or introduce a new navigation style) unless it’s rated 1/10. If it’s 5 or even a bit less, people will be mad no matter how better it gets.</p><p>This example from Apple shows how one of the most used music streaming services evolved over 10 years — changing one UI feature at a time, making sure, people wouldn’t rage-quit as they did with Snapchat.</p><p>In our door example, maybe the spouse should have introduced the eye sensor and also kept the handle until the user got used to the new system.</p><h4>#2: Design an Onboarding Flow</h4><figure><img alt="Several UI screens showing a random onboarding process" src="https://cdn-images-1.medium.com/max/800/1*V4GY3p_6OqqH0GJ5KjwY6g.jpeg" /></figure><p>Almost every time I open an Adobe product there will be a quick onboarding session telling what’s changed since the last update. It’s quick and easy, so users always know how to expect from the new experience.</p><p>There’s also a second technique I forgot the name, but you know you open an app and your screen goes dark, with small text bubbles telling you what to do? That’s also great when you are introducing changes to an existing experience.</p><p>Getting back to the door, instructions would help: maybe the sensor could emit some message after noting you had been standing there for 5 minutes. (Which would also be great for those inside the house, after all, you don’t want people standing at your house’s door for so long.)</p><h4>#3: Forgiving Formats &amp; Redundant UI</h4><figure><img alt="Several Snapchat’s new screens" src="https://cdn-images-1.medium.com/max/1024/1*YaCzYWUBDT5BvHHeAvcuIQ.png" /></figure><p>Back to the late and long-gone Snapchat, a great deal of their demise was caused by radically changing the user flow. It’s a whole new experience to a well-established app! How could they have avoided that?</p><p><strong>You must show your users a way around the problems.</strong> That’s why Instagram made profile pictures automatically run stories, but they also included a link to your friends’ profile — otherwise, millions of people who clicked the profile picture to visit the profile would be completely lost.</p><h3>Wrapping-Up</h3><p>Always keep in mind that you are NOT your users, so you must manage your system’s base-level complexity lest you build the next Snapchat of this decade.</p><p>Changes must be introduced gradually unless the original app (or experience) is so disgracefully bad that only a handful would complain — and even so, I’d strongly suggest you try your best to apply the three tips above.</p><blockquote>If you think that good design is expensive (and arduous), you should look at the cost of bad design.</blockquote><h3>Seeking a mentor?</h3><p>Starting a career is not easy: you have to face an insurmountable wave of new info that feels like you need to memorise an encyclopedia before working. <a href="https://www.linkedin.com/in/romarioverbran/"><strong>Connect with me on LinkedIn</strong></a> if you need assistance! ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab63a05706f1" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-psychology-3-how-to-make-foolproof-designs-with-teslers-law-ab63a05706f1">UX Psychology #3: how Tesler’s Law makes your designs fail</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Psychology #2: increasing conversions with the Decoy Effect]]></title>
            <link>https://uxdesign.cc/ux-psychology-2-increasing-conversions-with-the-decoy-effect-272500321df7?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/272500321df7</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Mon, 28 Dec 2020 11:28:47 GMT</pubDate>
            <atom:updated>2024-04-19T20:19:22.715Z</atom:updated>
            <content:encoded><![CDATA[<h4>The cognitive bias that makes us proud of being made fools of.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Og7haUmLJMRLbxUxoaXouQ.png" /></figure><p>Have you ever noticed that some fast food prices seem absolutely clueless? I mean, h<em>ow come a medium Starbucks cup is $4 while an extra-large is $5? </em>Shouldn’t it be twice as much?!</p><p>The funny thing is that most people feel like they have gamed the system when opting for the bigger size — as if they found a breach in the operations — but the fact is that the system has just gamed them.</p><p><strong>Medium portions are not meant to be sold just like many iPhones are planned to flop.</strong> <a href="https://www.wired.co.uk/article/iphone-10-biggest-failures-iphone-history">It’s a huge mistake to say the iPhone 5C was a failure</a> — although it did fail to sell—because that’s exactly what Apple wanted from it.</p><p>Today we’ll talk about the Decoy Effect, also known as the <em>Attraction Effect</em>,<em> </em>an intriguing cognitive bias that uses bad products to make expensive ones seem much cheaper than they actually are. You are gonna love this, I promise. :)</p><h3>What is the Decoy Effect?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*Nc1c4wec0aODDhuPKYGDow.jpeg" /></figure><p><strong>Originally, a decoy is an artificial duck used by hunters</strong> to lure real ducks into gun sight — just like Starbuck’s Tall cups only exist to make you by Ventis.</p><p>Behavioural Economists say <a href="https://www.behavioraleconomics.com/resources/mini-encyclopedia-of-be/decoy-effect/"><em>a decoy is a middle option that is asymmetrically bad compared to your main offer.</em></a> A perfect example would be the iPhone 5C, which was the decoy of the high-end 5S back in 2013. Let’s see how things were before its release:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*_aWCd92qnvEAROpgEw6elA.jpeg" /></figure><p>For $649, an iPhone 5S wouldn’t give you much more than its $449 predecessor. I mean, it had the great Touch ID (the reason I bought it) but everything barely mattered to the average user. (Not to Samsung was catching up in terms of innovation, and both the 4S and the 5S looked strikingly similar to be worth the price difference.)</p><p>This was the perfect time for you to save $200 if you were not one of those crazy Apple fans, right? Especially if you lived in a developing country, where the difference easily amounts to thousands.</p><p><strong>But then came a third model, the iPhone 5C, to shatter your dreams:</strong> costing a whopping $549 — only $100 below the high-end 5S — it was completely made out of plastic, lacked the coveted Touch ID, and also displayed unique colours that screamed to the world:</p><blockquote><strong>“LOOK, I OWN A SHITTY PLASTIC IPHONE!!!”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3aB5YCLZ6Nf2OJoUHqsi9Q.jpeg" /><figcaption>The 5C was so lame that its body and buttons were identical to the 4S!</figcaption></figure><p><strong>See how having three phones changes the landscape:</strong> if before this you could save $200 opting for the 4S, now you have a new model that makes the 4S feel even more outdated and meaningless, thus, completely removing it from your buying decision. Now your options boil down to saving $100 on coloured plastic crap or buying the best iPhone in the world.</p><blockquote><strong>The iPhone 5S was no longer $200 more expensive but $100 more affordable.</strong></blockquote><p>As defined earlier, the 5C was a decoy because it’s a middle option that was clearly superior compared to the low-end model, but also so bad compared to the high-end one that you could literally identify it by its bright colours. Showing a 5C in public was the same as telling everyone: <em>“I’m so poor, look at my unique colourful plastic phone! I couldn’t spend $100 on 5S, guys!”</em></p><p>You see Apple did all it could to ensure having a 5C sucked (social-wise), but since carrying a 4S would also suck (tech-wise), the 5S becomes your only choice. They convinced us the most expensive phone was actually a steal.</p><h4>Don’t mistake Decoys for the Centre Stage Effect!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dirMSiZxxSG5p4d4WKeI1g.png" /><figcaption>THE IPHONE X IS NOT A DECOY!</figcaption></figure><p>I’ve seen many people say that expensive products like the iPhone X are decoys because they make people buy cheaper models like the 8 Plus, but that’s a huge mistake. (A reasonable one, but still a mistake!)</p><p><strong>First, we must remember that decoys must be asymmetrically bad by definition </strong>and that’s definitely not the case with the iPhone X. We are talking about a top-notch model with a Super Retina Screen, Infinite Display, face recognition, better camera, and other features the 8 Plus could only dream of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*iLOseZXvZtufnBLlPaB7hA.jpeg" /><figcaption>Just like the 5C, even the 8 Plus’ body looks old. Do you think Apple wants to be known for that?!</figcaption></figure><p>If anything, the X was asymmetrically BETTER than the 8 Plus, <strong>so why people were buying the 8P instead?</strong></p><p>Probably because of the Centre Stage Effect (or the Middle Option Bias), <em>which makes people buy middle options among products that scale evenly concerning price and quality. </em>Check it out:</p><p>We had the iPhone 8 ($449), the 8 Plus ($799), and the iPhone X ($999).* Those big price differences implied there’s the worst, the average, and the best model—and their features backed this perception since it got better the more you paid for it<em> — </em>thus making the buying process pretty rational.</p><p><strong>What’s the problem with rationality?</strong> Well, many (if not most) people don’t like to show off buying the best stuff (X), but they definitely don’t want to be embarrassed by having the worst either (8), thus putting a spotlight on the Centre Stage where the 8 Plus lied with average features for a $200 price cut.</p><p>People only bought the 8 Plus because it was reasonably inferior. If Apple priced it at $50 or $100 less maximum, people would feel stupid since they could get the latest big thing dropping a single <a href="https://www.wikiwand.com/en/United_States_one-hundred-dollar_bill#:~:text=Statesman%2C%20inventor%2C%20diplomat%2C%20and,has%20been%20used%20since%201928.">Franklin bill</a> at the table.</p><p>So yeah, the Decoy Effect and the Centre Stage are pretty similar on the surface — i.e., a product is favoured due to a price comparison — but their conditions are radically different. Fail to grasp it and you may end up turning your latest release into your greatest failure!</p><h3>How to trigger the Decoy Effect?</h3><p>I forgot to say this, but one reason people mistook the iPhone X for a Decoy is because it had the highest price an iPhone ever had up to 2017.</p><p><strong>But decoys are not about price.</strong> Decoys are about asymmetrically quality and price difference, as The Economist does with its subscriptions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*Z_ht735LKVkxZLB6Gv_bYw.jpeg" /><figcaption>This seems much more unfair than the 5C price difference, right?</figcaption></figure><p>Huge price difference, huh? But did you notice that the price is not the only problem here? I mean, one of the options is obscenely expensive and dares to offer you less than the best offer. That’s an absolute disgrace! (Or an <em>asymmetric</em> disgrace, as I’ve been saying.)</p><p>Although pricing is definitely an important aspect of Decoys, there’s a huge difference between having a higher price (X vs 8 Plus) and having a bad price. <strong>Prices are asymmetrically bad when unfair, not when simply superior.</strong></p><blockquote>Don’t mistake asymmetry for absurdity</blockquote><p>With that said, here’s how you can make a Decoy:</p><ul><li>You must have 3+ competing offers;</li><li>Pick a favourite among those (the high-end offer);</li><li>Make one of those offers absolutely inferior (the irrelevant product);</li><li>Then make one of your products better than the worst (the Decoy);</li><li>But also make it inferior to your favourite;</li><li>Now price your decoy similarly to your favourite offer.</li></ul><p>Oh, you could also make the decoy more expensive than your main offer like The Economist does, but don’t mistake asymmetry for absurdity, please!</p><p>I mean, it would be fine if paper+digital was $30 and paper-only was also $30 or even $40 — they could argue it’s expensive to mail it or that they wanted online readers, for instance — but the same thing for twice the price, buddy? That’s blatant trickery!</p><h4>Closing thoughts</h4><p>The buying process is not rational, so don’t try to make it unless its part of your Product Strategy.</p><p><em>The Decoy Effect is really powerful at making people ignore what best suits their needs and focus on what feels more advantageous at the moment,</em> so be careful as it may end up frustrating your customers on the long run. A competitor may spot an opportunity to price more fairly and take you down, for instance.</p><p>And no, that doesn’t mean Decoys were made to trick people. Anyone who has run a business knows how costly it is to keep things running smoothly, so you could use it to nudge people towards good offers rather than unfair ones.</p><p>Whatever you do, keep in mind that offering a good user experience is the secret of all the most successful business, so be kind to your customers’ hearts and their wallets will be kind to you.</p><p><strong>And if you are unsure of how to craft a Decoy, leave a comment here and I’ll be more than happy to offer you some tips! :)</strong></p><h3>Seeking a mentor?</h3><p>Starting a new career is not easy: our lack of experience is hit by an insurmountable wave of content that makes us feel like we need to memorise an encyclopedia before working. It’s an awful feeling, I know.</p><p>I’m no mentor, but having accomplished a thing or two as a designer, writer, and digital marketer (and now working as a product designer at fashion giant), I know a thing or two about career shifts in order to aid you.</p><p>How about you follow me here or <a href="https://www.linkedin.com/in/romarioverbran/"><strong>connect with me on LinkedIn</strong></a> so we can take this conversation forward? I’ll be happy to provide you with any assistance you might need! : )</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=272500321df7" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-psychology-2-increasing-conversions-with-the-decoy-effect-272500321df7">UX Psychology #2: increasing conversions with the Decoy Effect</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: How I designed a +$70K revenue website menu]]></title>
            <link>https://medium.com/design-bootcamp/how-i-designed-a-70k-revenue-website-menu-ux-case-study-14ff6ef9dabb?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/14ff6ef9dabb</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Thu, 24 Dec 2020 12:13:36 GMT</pubDate>
            <atom:updated>2021-10-14T14:48:44.312Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing a new Category Tree and Menu UI from scratch</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zebXpiZPlLz3Y4VuO_OPoA.jpeg" /></figure><p><strong>Selling over $1 million per month,</strong> OFF Premium offers over 10 thousand clothes for an affordable price — and I mean reaaally affordable price, down to 80% off of the original price!</p><p>The problem: OFF was an experiment that went viral. Sales skyrocketed on a website that had never planned to get so huge, so they ended up with a category tree built by the sellers* rather than a planned architecture. (*Sellers suggest a category when submitting their items.)</p><p>Visual merchandising analysts did their best to make things make sense, but it’s too much work so this resulted in..:</p><ul><li>Categories and menus that disregarded purchase intention;</li><li>Users’ mental models were ignored in most cases;</li><li>Users from Google and other sources had problems navigating;</li><li>Seasonal purchases were not considered as part of the AI;</li><li>And a category tree that made no sense at all, of course.</li></ul><h4>Goal &amp; Proposal</h4><p><strong>To rethink the whole category tree from the user’s perspective,</strong> placing every product and category according to the users’ expectancies rather than what’s convenient for brands and stores listing it.</p><p>I won’t share details about the persona for now (I’m no longer affiliated with OFF Premium), but we are mostly talking about <em>women in their 30s looking for a good fashion bargain </em>—so they are focused on price cuts rather than looking for specific clothes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*Wwli4R7mNKS8rMxZv1aNUg.jpeg" /></figure><h3>The Problem Space</h3><p>It all started when I joined OFF Premium and decided to conduct a user flow analysis to get familiar with the website. Back then I noticed the website’s breadcrumbs made no sense at all:</p><p>You’d navigate to a category such as Women\Apparel\Dresses and, after opening a product, you’d end up at Home\Brand\[Chosen dress].</p><p><strong>What’s worse?</strong> Imagine that you were searching for a watch on Google and you’d landed on a certain watch’s page. Unfortunately, you didn’t like this one, so you decide to look for another one using the breadcrumbs — but you can’t since the crumbs point you to Home\Men, never mentioning Watches.</p><p>This AI was not only bad to follow your own steps when browsing the website, but also to give you an alternative when coming from other sources. This a huge opportunity going down the drain!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*59e_7YJNLu12Df9hx7BNbg.png" /><figcaption>An analysis of how people search and browse for apparel @ OFF Premium</figcaption></figure><p>This is a shortened version of my analysis, comprised of direct accesses, Google visitors, and website searches. Green boxes represent input (user does something) whereas blue ones represent feedback —<em>we get red and orange boxes because the feedback is rarely what the user expected.</em></p><h3>Desk Research</h3><p>I always start my projects with a good reading session, so I paid a visit to <a href="https://baymard.com/">Baymard.com</a> and some scientific papers from the American Market Association to understand how people buy fashion items.</p><p>Here are some findings:</p><ul><li>Traditional filters (colour, size, and price) are not enough. Women check characteristics like neckline, armlength, and much more when in-store.</li><li>Clothes preference change throughout the year (and the pandemic), so your architecture should adapt to those seasonal needs.</li><li>Category trees work better if they are organised exactly like stores.</li><li><strong>And use case scenarios. This is a big deal here, my friend!</strong></li></ul><p>Think of a purse and a backpack, for instance. Both are hollow containers to carry your stuff, right? Be it documents or accessories such as jewellery, you can carry the very same stuff regardless if it’s a backpack or a purse — <em>so you will obviously group those, of course!</em></p><p>I mean, of course not!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*DnSAgv1L67TiGaMgEu2ddg.jpeg" /><figcaption>Same use, but hardly going to the same places</figcaption></figure><p>Just like bikinis and bras serve the same purpose, one takes you anywhere whereas the other only takes you to the beach. Having backpacks and purses together would be a great nuisance to any woman looking for a bag for a specific use case scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xoOWw-b742j2Xx3CakkFrA.jpeg" /><figcaption><a href="https://careerfoundry.com/en/referral_registrations/new?referral=b7nBMQ7w">Join my students and learn from world-leading professionals at CareerFoundry</a></figcaption></figure><p>After learning all this stuff, <strong>I decided to take a tough design decision: ideate first, research later.</strong> I had a new architecture in two weeks! 😱</p><h4>Early Ideation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FBYgNSjijj1RUc08OBjWog.png" /><figcaption>I know, this is impossible to read, but it’s not in English anyway, so…</figcaption></figure><p>This may sound crazy from a UX Research lover, but think for a while: <em>most about fashion apparel architecture is already known.</em></p><p>I mean, we will always need genders (Male, Female, and Kids), dresses will always be a full-body garment and so forth. If I did the complete research process (like conducting many card sorting sessions), I’d spend weeks hearing stuff that my desk research had already made clear.</p><p><strong>That’s why I decided to spend a few days building an MVP tree. </strong>Using my storytelling techniques, I wrote a test script about a woman who wanted to purchase gifts for her friends; then I took my proto-tree to <a href="https://www.optimalworkshop.com/">Optimal Workshop</a> so I could test it with real users asap…</p><p>And that taught me some amazing stuff!</p><h4>Tree Testing our MVTree</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*Wj-xNyw_d-sCHofH9hPU4g.jpeg" /></figure><blockquote>“You want to buy new socks for a friend. Where would you go to find it?”</blockquote><p>It seemed pretty obvious to me that all users would go to Gender/Footwear — socks cover your feet after all — but only one user did that. All the others considered socks what we call “intimate clothing”, just like bras and boxers.</p><p>This shocked me a bit, especially because the idea of a man in briefs and socks horrified all my testees (yes, I asked that!), but here’s the catch:</p><blockquote>“If I was at a real store, I would find socks right where they keep the underwear.”</blockquote><p>Users believe socks and underwear go together <strong>because of a mental model they’ve developed inside brick and mortar stores.</strong> They would always click “underwear” although “footwear” was equally visible on our proto-tree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDc7A1EdChQ4DUdBcpfwVA.jpeg" /><figcaption>We also had a cart sorting session to broaden our project vision</figcaption></figure><p>Another interesting fact is that users will often try a second category if they can’t find the item in the first one. Just to puzzle me further, many of them looked for our sucks under accessories rather than footwear, so that’s when I had a new idea.</p><p>Similar categories. Some items like running shoes inevitably fit within more than one category (Home\Fitness &amp; Men\Footwear), so you must add some redundancy to your architecture if you want to avoid frustration.</p><p><strong>PRO Tip:</strong> Google only takes one category into consideration, so your platform should be able to assign the main category — and you must decide which one will be better for SEO.</p><h4>Filtering like in-store</h4><p>Boobs are a major problem for some women: the bigger they get, the smaller our collection becomes. They just “can’t” buy any dress for any occasion.</p><p>Several women complained that they’d spend a long time scouring our categories because they couldn’t filter characteristics such neckline — meaning they’d have to analyse hundreds of clothes, one by one until they found something that matched their body type, for instance.</p><p>This would be easily solved in-store by asking a seller to show them all the shirts with a small neckline, but when it comes to online shopping, all dresses are simply dresses. That’s why I design a brand new array of filters (some of them found on the menu) so users could find EXACTLY what fits them best.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*aTUtPLWHfjxJam1selVvaA.png" /><figcaption>Filter examples</figcaption></figure><p><strong>But how do you implement that? I told you we had more 10k items,</strong> so it takes a lifetime to configure all those clothes, right?</p><p>We implemented a new categorisation tool that automatically checks our items features, giving us a summary that our analysts simply have to validate. Instead of making them classify all clothes one by one, I ran a workshop to show them what we expected from a new category and showed them how to calibrate the categorisation tool so it will work without their supervision.</p><p>Now I’ve told you before that <a href="https://medium.com/serious-scrum/how-i-made-my-team-deliver-value-after-failing-for-6-months-3c96ea1bc2b3">MVPs are crucial for really Agile brands</a>, and it takes a long time to calibrate this tool, so I started by building landing pages dedicated to the most important filters. Some offers simply can’t wait!</p><h3>New UI Design</h3><p><strong>Sad confession:</strong> I wrote more test scripts to test the new UIs and tested it with 10 real users, but I just can’t find the data anywhere =/</p><p>I remember the test tree fared pretty well, but the UI failed in many aspects — that’s why I’ve designed these and many other versions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*eNw8CHgpNNuKX8MvUlcrJA.png" /></figure><p>Anyway, this right here is the original desktop UI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yU3kDliwCqJ87eA8LnUibA.jpeg" /></figure><p>And this is the brand new UI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DR2spGUjXzAbYDWrBnnyCw.jpeg" /><figcaption>There’s also a MOBILE version, which you’ll see later.</figcaption></figure><p>We start by reducing Cognitive Load: we only have 4 choices in the new UI, whereas the old one had over 10. This is important because it’s not about difficulty but the perception of ease. If it feels easier, it becomes easier.</p><p>Oh, and remember that OFF Premium serves premium brands? That’s what customers come here for, so we must give it some thought!</p><p>That’s why brands are now easily accessible as the first item. This also addresses use cases: if you want just about any dress, you got to Women, but if you want it from a specific Brand, just go to Brands. Never browse more than you need!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Z_vRCQYzfLH7lm5vzrbSQ.jpeg" /><figcaption>Menu interior after hovering “Women”</figcaption></figure><p>Instead of the tiny black stripe you’ve seen on the first image, here we have a mega-menu that shows all OFF Premium has + pictures linking to the hottest opportunities of the moment.</p><p><strong>Talking about opportunities, remember when I told you about seasonal purchases? </strong>The “Mais buscados” (Most searched) at the bottom shows you whatever is trending these days.</p><p>It’s no automated yet so an analyst must calibrate it every few months, but this was very handy during the lockdown. I realised that popular items such as “Nightdresses” no longer made sense since Covid spread, so I visited some Google Analytics reports to spot new trends.</p><p>Jeans and jumpsuits were in a new high, so bringing those to the list made a much-needed change to our bounce rate, resulting in more sales.</p><h3>The Results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*vtvoCkkgu1gf-d13RB51AQ.png" /><figcaption>A/B Test: the green line represents the new menu</figcaption></figure><p>The new desktop version sold $53K more than the old one, reaching up to $76K a week before the tests ended.</p><p>Do you see that grey area above? The new menu one was stomped by the one first 14 days, selling $45K less. That was staggering since we all agreed the new menu was so much better than the original, so I decided to investigate.</p><p>I noticed that someone forgot to update the trends sections of the menu, that’s why the green line suddenly win when the grey block ends: that’s when we updated the menu with current trends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*ihoKv-bEV-FqqrXD_VzPQw.png" /><figcaption>Mobile results. The orange represents the new design.</figcaption></figure><p>Things didn’t go so well with the mobile version although we won by $16K and +1.5% conversions. You can see we had great wins and great losses over and over again.</p><p>We still don’t know why it wasn’t as successful as the desktop, especially because this one was REALLY better than the original, but I have a guess:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ypRgBF6BtrPnujJGM58X_A.jpeg" /><figcaption>Sorry for this awful mockup!</figcaption></figure><p>The new mobile UI relies heavily on images, and Brazil does not have the best internet connections out there. Some people will experience longer load times (I’m talking about a single second) so that may be enough for the user to feel it’s broken or something like that. The team is studying new ways to ensure it will always load perfectly without impacting its page speed.</p><p>It’s also worth saying that the current desktop UI (live on the website) need some adjustments due to a few design and development mistakes we made, which means both UIs still have a lot of potential.</p><p>This was an awesome project to undertake and I’m happy to share it with you. I hope my findings can also inspire you in a future project! :)</p><p>If you have any doubts, please, share it in the comments and I’ll be glad to lend you a hand! =)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14ff6ef9dabb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-designed-a-70k-revenue-website-menu-ux-case-study-14ff6ef9dabb">Case study: How I designed a +$70K revenue website menu</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I made my team deliver value after failing for 6 months]]></title>
            <link>https://medium.com/serious-scrum/how-i-made-my-team-deliver-value-after-failing-for-6-months-3c96ea1bc2b3?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c96ea1bc2b3</guid>
            <category><![CDATA[serious-scrum]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Tue, 06 Oct 2020 06:37:31 GMT</pubDate>
            <atom:updated>2020-10-07T14:34:25.655Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I Made My Team Deliver Value After Failing for 6 Months</h3><h4>Scrum is a framework difficult to learn and dangerous to master</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUYies17WzOK7s0fkRUPQQ.jpeg" /><figcaption>(Created by Romario Eichlig)</figcaption></figure><p>For 180 days, I cranked out endless UX projects that were applauded and then trashed by the end of each and every Sprint. Developers wrote thousands of lines of code that never reached a single one of our customers.</p><p>You’d be surprised to know that <strong>it didn’t happen at a startup, but at a multi-million eCommerce instead.</strong> We were struck by a <em>combination of Covid-19 + the onset of our Agile transformation + new business model </em>— the perfect recipe for this disaster my squad went through.</p><p>After 6 months of failure, I approached our Agile Coach and said: <em>“if our CEO checked the ROI of our squad today, we’d all be unemployed by tomorrow”. </em>That’s when I realised I had to do something — and many things I did, leading to a salary increase 2 months later!</p><p>I’m sharing these hands-on tips with you today because I know there are endless Scrum Teams struggling out there. Feel free to leave any questions in the comments if something is unclear to you. :)</p><h3>1st mistake: an obsession with points and velocity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p7EtWmCrCmhPZEQf4JnjIw.png" /><figcaption>This is our burndown back when we cared so much about it.</figcaption></figure><p>As the great <a href="https://medium.com/u/b40569a4ce51">Maarten Dalmijn</a> states: <em>“companies that worry about velocity are clueless about Scrum.”</em></p><p>I remember this one stakeholder that always joined our Reviews with a look of disbelief in her face. That’s because she knew what the devs and Product Owner were about to say — which was the same they said every Sprint:</p><blockquote>“But see, we delivered these many points and coded all these things here in the done column. You can’t see it, but we are doing work!”</blockquote><p>Yeah, all these <em>worthless</em> things and <em>unnecessary</em> work, you mean. Delivering points and delivering value are two worlds apart, as the Agile Manifesto clearly states below:</p><blockquote>“Working software is our primary measure of progress.”</blockquote><p>Do you have working software that delivers value to the customer by the end of the sprint? No? Then it’s irrelevant: Scrum is not a video game in which you seek points on a leaderboard — we have a <em>Need for Value</em>, not <em>for Speed!</em></p><p>And no, I’m not suggesting points are useless. (Actually, that’s what I like most about Scrum.) I’m just saying that if points and velocity are your main concern, chances are your team is failing hard and, most likely, those metrics are certainly NOT the reason.</p><h3>How I solved it</h3><p><strong>Championing a M-A-N-D-A-T-O-R-Y practice</strong> that many specialists deem to be optional: Sprint f*** Goals, my friend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwW_dByLtUPGbQaoQVEx9w.png" /><figcaption>Enthusiastic manager. Depressed workers. Illustration by Thea Schukken.)</figcaption></figure><blockquote>“The heart of Scrum is a Sprint (so) each Sprint has a goal of what is to be built (and) the resultant increment.”</blockquote><p>Can you live without your heart? So can’t your development team! You either let Sprint Goals pump some purpose into your sprints’ heart or you risk having 6 months of arrhythmia.</p><p>We conducted Plannings making estimates and asking Devs what they could deliver — and we sure worked a lot — but we always forgot to ask: <em>“what do we really want to achieve? How does this task lead us to our North Star Metric?”</em></p><p><strong>Seriously, what’s the purpose of building anything if you don’t really know what you want to achieve?</strong> There’s a misquote from the Cheshire cat which says: <em>“if you don’t know where to go, just about any way goes”.</em> The same applies to Product Management: you either have a clear roadmap or you can simply save time by picking tasks at random. Your results will be the same.</p><blockquote><strong>“If you don’t have a goal, then finishing all tasks becomes the goal,” — Maarten Dalmijn</strong></blockquote><p>This Sprint, for instance, our Visual Merchandising team didn’t have enough people to release our main Epic. Now, do I like VM? Do I like coding that site? No, I despise both, but I immediately volunteered since that was our goal.</p><p>That’s because <strong>Goals make your team rally around what matters most.</strong> Wasn’t for that clear Sprint Goal, this what would follow:</p><ul><li>The VM team would be embarrassed for failing;</li><li>My PO would have to explain herself to our Head;</li><li>Then our Head would have problems with our Director;</li><li>And the same cycle would unravel in the other Tribe;</li><li>Oh, and Customers would continue having a bad experience for weeks!</li></ul><p>Yeah, the Dev Team could simply wash their hands since they had nothing to do with it, but that’s not the corporate mindset we need. Not the values the Scrum Guide preaches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARAzDNRr4sfTFCQQ6Dljag.png" /><figcaption>Focus on what matters; be open to help; commit to common goals. (Image from TechTarget, by AlexDNDZ)</figcaption></figure><h3>2nd mistake: pursuing dream-projects rather than assertive solutions</h3><p>I’m a designer. Designers are trained to design the best possible solution even when things are trivial, so if we could spend a whole month embellishing a single icon, be sure we would!</p><p>That may be a good thing in the arts, but it’s absolutely awful when it comes to product management. <em>Spending too much time on development is one of the best ways to pave your competitors’ road to success.</em></p><p>The funny thing is: all managers I’ve met throughout my life were also accursed by that pursuit of greatness. As humans, all of us want to be part of something great, but if there’s one thing experience will teach you, is that such greatness takes time — and time costs money, so you need to mitigate your expenses along the way.</p><p><strong>To be successful with Scrum and Product Management, it’s crucial that you focus on delivering value as soon as possible,</strong> so you can validate your ideas, mitigate costs, and innovate at a faster pace than musing about perfection would ever allow you to.</p><h4>How I solved it</h4><p>Advocating for <a href="https://medium.com/@joe_lindsay/agile-learning-vertical-slicing-your-training-d8181b6550df">Vertical Slicing</a> and <a href="https://medium.com/serious-scrum/we-scrum-and-we-plan-to-deliver-our-mvp-next-year-42e34c47475f">MVP-driven development</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*NtfEEADsElzdczCiOr0gNw.png" /><figcaption>Check the link above to learn more. (Image by Joe Lindsay)</figcaption></figure><p>Here’s a great example: as a Brazilian marketplace, our clothes are distributed all over 8.5 million kilometres. Shipping costs of a t-shirt can vary between 10 and 200 bucks — it all depends on your (and the clothes’) location.</p><p>Here’s how things unravelled:</p><ul><li>“We need to make our carts show detailed shipping info so people will remove expensive products,” I suggested;</li><li>“The platform restricts our coding efforts there”, the developer objected. “This may take 1–2 months”;</li><li>“Customers are bombarding us every day”, I reminded, “maybe we should start by adding shipping price to product pages”;</li><li>But if they don’t calculate shipping there, they’ll still be shocked during checkout. “It also may take up to a week of development”, the dev said;</li><li>“True thing, so let’s do some UX Writing here: let’s add a short, friendly warning to our product pages and carts explaining how shipping works.”</li><li>“Ok, that may take an hour or two”, the dev said.</li></ul><p>We sliced and MVPed our solution until we found something that could be released in no time — and as a result, our contact rate dwindled; social media haters stopped; our Net Promoter Score rose; cart abandonment rate dropped.</p><p><strong>We achieved all those things in two hours,</strong> ending weeks of endless hate comments in our pages. That was only possible because we focused on the problem rather than the solution —<em> satisfying our customers’ needs before our creative egos.</em></p><p>No, we didn’t give up on that new cart design with all the detailed info. We just delivered a faster proto-solution so we could appease our customers and work on the ultimate design peacefully. (An awesome true win-win situation!)</p><p><strong>My best advice would be:</strong> always ask yourself how to address a problem faster and how to make a project smaller. If most of your user stories can’t be solved within a Sprint, odds are you are planning your sprints the wrong way.</p><p>Most problems can be addressed by targeting specific parts of it; others may require a more encompassing approach, but that can be done with an MVP. Regardless of the case, going step by step will 1) bring you faster results, 2) faster learning, and 3) enable you to design a better final solution to it.</p><h3>3rd mistake: an inexperienced Scrum Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DbjMHJVyd8zDKKbNr88nSQ.jpeg" /><figcaption>(Created by Romario Eichlig)</figcaption></figure><p><strong>I first have to say that I’m not questioning anyone’s abilities.</strong> Here we say <em>we value people above all, </em>and awesome people we have, but weren’t the right people to face Covid-19 + Agile transformation + new business model.</p><p>This was particularly bad to my squad since we work for the least important brand in the group so — although our Agile Coach did his best to aid us — we lacked the appropriate resources to make our squad valuable. <em>(That analogy about changing a tire while driving never felt so real!)</em></p><h3>How I solved it</h3><p><strong>I signed up to Medium and read 70 </strong><a href="https://medium.com/u/3385ff7d728"><strong>Serious Scrum</strong></a><strong> articles </strong>within a month. I also joined a University of Michigan’s Agile program a while ago.</p><p>Sorry if you expected some spectacular resolution to this, but all it took was a burning desire to make things work. Reading was enough to pinpoint our weaknesses during Scrum events and, for my surprise, my managers were happy to hear it from a junior. (I told you we have awesome people!)</p><p>Here are a few suggestions:</p><ul><li><a href="https://medium.com/serious-scrum/definition-of-scrum-2d1f224256c">Road to PSM III</a> by <a href="https://medium.com/u/f60973888071">Sjoerd Nijland</a> renders the Scrum Guide useless</li><li><a href="https://medium.com/serious-scrum/sprint-goals-are-the-beating-heart-of-scrum-bdef2518e828">Sprint Goals</a> by <a href="https://medium.com/u/b40569a4ce51">Maarten Dalmijn</a></li><li><a href="https://medium.com/the-innovation/new-to-product-management-here-are-6-foundations-you-should-build-dbd049659171">New to Product Management?</a> by <a href="https://medium.com/u/b6decaad7496">Rameez Kakodker</a></li><li><a href="https://medium.com/serious-scrum/if-you-dont-say-no-many-times-a-day-you-fail-as-a-product-owner-ac6f7167a8ad?source=bookmarks---------23----------------------------">The importance of saying NO</a> by <a href="https://medium.com/u/2d95ad0e562b">David Pereira</a></li><li><a href="https://medium.com/serious-scrum/what-the-scrum-guide-doesnt-say-56ef9447b961">What the Scrum Guide doesn’t say</a> by <a href="https://medium.com/u/bb131891dd14">Dan Ray</a></li><li><a href="https://medium.com/serious-scrum/lets-face-it-agile-is-a-cursed-name-978591aa837a">Agile is a Cursed Name</a> by <a href="https://medium.com/u/53ee4ac7f11f">Romario Eichlig</a></li></ul><h3>4th mistake: UX, managers, and developers were never aligned</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*Wr0kIvw5CDgAvPiibZAL_g.gif" /></figure><p>You spend weeks reading about the neuromarketing of discounts. You benchmark solutions; you sketch it; you design it — and the dev trashes it.</p><p><em>Actually, It was never even possible to build it in the first place…</em></p><p>We were so velocity-driven that Plannings were a mere formality, never aligning stakeholders and users’ needs. We didn’t do proper Discovery phases because it would delay development, “so why don’t you just design it and later we see if we can build it?” (No one said that, but I heard it in my mind.)</p><p>There were also times that we indeed built everything exactly as requested — except that it wasn’t really requested. That’s because demands were so focused on alleged solutions that we hardly knew what we were building it for — so our products were usable, but rarely useful. (Usable = works perfectly; useful = addresses needs perfectly.)</p><h3>How I solved it:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Esql2AG2YX3Tqoh0I4xbXQ.png" /><figcaption>By <a href="https://unsplash.com/@campaign_creators">@campaign_creators</a> (Unsplash)</figcaption></figure><p><strong>I trained my facilitation skills and group dynamics.</strong> Am I good at it? Hell, no, but it’s enough to fix our processes and — since I survived our performance review — there’ll be plenty of opportunities to keep improving.</p><p>One way I put it to work is by leading design thinking processes so we don’t start major projects with endless unknown-unknowns. Now the UX Designer, known as I, won’t move a finger before we know something can be built.</p><p>No, I don’t host our Scrum events, but such skills brought me the confidence to intervene when the process seems off, so the Dev Team is no longer a passive agent in our meetings.</p><p>There’s this quote I love and would like to share with you: <em>“I don’t suppose anything; I either know or I don’t know”.</em> Always have in mind that design and coding cost money — so don’t turn our wage into a guess.</p><h3>5th mistake: we never said “no”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojl86DSMILIxaXLBph1znA.png" /><figcaption>YOUR TASK SHALL NOT PASS</figcaption></figure><p>Working with the Spotify model, we have 7 brands split between a digital commerce tribe and a product tribe. Since the eCommerce tribe is the one making the money, they get to demand whatever they want — and their short-termism is terrifying.</p><p>Retailers have a new pressing calamity every day — it can be logistics, politics, marketing, finances, etc. — and they can think of megalomaniac ways to solve it in a minute. (Oh, that ought to be delivered by yesterday, of course!)</p><p>That’s when you manage to travel back in time, build the Eighth Product Wonder they needed and suddenly realise they never needed it. Everything is now discarded and so will be everything else for the next 26 sprints.</p><h3>How I solved it</h3><p><strong>I reenforced that the product squad is autonomous, </strong>just like theirs, so we have our OKRs to be met. Also, I started asking <em>“does it really matter?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fwrTGkgxrVc8NMUaUfvYiQ.png" /><figcaption>The upper-right corner is where you want to be! (Art by Stephen Bungay)</figcaption></figure><p>All managers had OKRs in their heads but the development team didn’t even know they existed, thus we didn’t know what we were fighting for. That’s why I built an <a href="https://productcoalition.com/tutorial-how-to-build-a-now-next-later-roadmap-in-jira-with-just-3-easy-steps-a8d393e12e04">Epics roadmap with our OKRs</a> to ensure everyone was aligned and that all backlog items would be assigned to a real goal. <em>(“If it doesn’t fit, maybe we don’t need it.”)</em></p><p>No, I didn’t become a preacher against the eCommerce — we are in this together after all — but they needed to learn we can help them beyond the short-term. (And that we have our own Head to report progress to by the end of the quarter, so…)</p><p><strong>I also suggest you print an Important vs Urgent Matrix</strong> and Stick it to the wall behind your bed so you never forget how to prioritise work. Not knowing the difference between important and urgent tasks is one of the worst sins product managers commit every single Sprint.</p><p>Example: <em>“We need a new coupons page!”</em> Yeah, we sure do; we are an outlet and that’s what customers come here for… But here’s the thing: shipping price has gone haywire and costumers want us dead now.</p><p>Both of those tasks matter, but one is important and one is urgent — just like treating a bad knee is important whereas treating a stab is urgent. Sorry to go criminal here, but the only problems of equal importance I can think of would be having both my parents at gunpoint at the very same time.</p><p>Everything else can be reassessed, ranked, and prioritised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k5cychmCtQZ53_v2DAQAFA.jpeg" /><figcaption>Image from Memory.AI</figcaption></figure><p><a href="https://medium.com/serious-scrum/lets-face-it-agile-is-a-cursed-name-978591aa837a"><strong>“Agile is a curse name”</strong></a><strong>,</strong> I told you last month. The road to true agility is paved with endless pitfalls that can not only ruin your productivity but also your team’s morale and your will to move forward.</p><p>It doesn’t need to be that way.</p><p>We from <a href="https://medium.com/serious-scrum">Serious Scrum</a> share hands-on tips and practical knowledge every single day to make Scrum practitioners more effective and, from my own personal experience, healthier and happier.</p><p>Make sure you follow us and feel free to drop any questions you find suitable; I’ll be more than happy to lend you a hand! = )</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/0*-oPW9i6FWgWROrPD.png" /></figure><p><a href="https://medium.com/serious-scrum/your-invitation-to-the-serious-scrum-slack-workspace-f424aeea4093?sk=e8334e6ee505a85ae6b9d2a1ce37219c">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></p><p><em>Special thanks to </em><a href="https://medium.com/u/b40569a4ce51?source=post_page-----978591aa837a--------------------------------"><em>Maarten Dalmijn</em></a> <em>for saving our squad with his articles, and reviewing this piece, of course!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c96ea1bc2b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/how-i-made-my-team-deliver-value-after-failing-for-6-months-3c96ea1bc2b3">How I made my team deliver value after failing for 6 months</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s face it: “Agile” is a cursed name]]></title>
            <link>https://medium.com/serious-scrum/lets-face-it-agile-is-a-cursed-name-978591aa837a?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/978591aa837a</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Wed, 19 Aug 2020 06:48:33 GMT</pubDate>
            <atom:updated>2020-08-21T13:51:45.837Z</atom:updated>
            <content:encoded><![CDATA[<h4>Language shapes how you think and how bad you do Scrum</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCXEdvZ9IMEN8xFsaKFDCA.jpeg" /><figcaption>How would you describe this scene?</figcaption></figure><p><strong>Let’s do a quick scientific experiment together.</strong> You are in an art gallery and a vase is sitting on a pedestal in the middle of the room. A visitor, fascinated by it, approaches to take a picture — unaware of a second vase right behind him.</p><p>That vase immediately falls and breaks into a hundred. (Just like the man’s heart as he thinks of its price.) <em>Now how would you describe this artsy tragedy?</em></p><p>A Stanford professor carried this same study with both English and Spanish native speakers, revealing a shocking pattern. The English described the scene with agentive expressions, such as <em>“the man broke it”</em>. The Spanish disagreed and said something awkward to English ears: <em>“the vase broke itself.”</em></p><p>But what’s shocking in that? Wel…</p><blockquote><em>The Spanish couldn’t remember who broke the vase.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*ZnHYqCi_zGX3r_WsaK0i1w@2x.jpeg" /><figcaption>A chart from the study showing how speakers differed</figcaption></figure><p>Another study revealed that Germans described a bridge as “elegant and fragile”, although the Spanish labelled it “strong and sturdy”. The secret is also in linguistics: while “die Brücke” is feminine, “el puente” is masculine — so their opinions weren’t based in reality itself but on grammatical gender.</p><p>I know this sounds <a href="https://en.wikipedia.org/wiki/Newspeak">Newspeak-sy</a> at first, but Linguistic Relativity shows that <strong>how you label things inescapably bestows power upon it</strong> — and that brings about assumptions that distort reality. That’s how a singular object can be both “fragile” and “sturdy” at the same time, <em>regardless of how illogical that is.</em></p><p>But does that have to do with Scrum, you may ask? Well, think of all those common Scrum anecdotes you’ve heard, like <em>“sprints made our team miserable”</em>. Remember agilists saying that <em>“you must track velocity to make it work”</em> and other recurring nonsense. What is common in all those issues?</p><p><em>An unreasonable concern with agility.</em> Scrum teams will pursue sprints as if their lives depended on it. Inexperienced agilists will forget value in favour of burn-down charts, trying to rebuild the world every two weeks. Abusive managers will exploit workers since they are “not agile yet”.</p><p>It’s inevitable. Just like turning “ceremonies” into “events” lightens the atmosphere, mentioning “Agile” immediately hastens it. That’s why I say:</p><blockquote>“AGILE” is one hell of a cursed name.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*eovQUMEXlnZyx6q1thnNCA.jpeg" /><figcaption>I’m sure you’ve heard similar stories before</figcaption></figure><p>The Agile Manifesto has 68 words but “speed” isn’t one of those. I also dared to ctrl+f my Scrum Guide for terms such as “velocity”, “fast”, and “quick” but couldn’t find those.</p><p>Here’s what I found in seconds though: <em>“working software is the primary measure of progress”</em>. And yes, the Manifesto does mention a “<em>preference</em> to the shorter timescale”, but that is about avoiding extensive plans — not about whipping your developers. Also, here’s what isn’t a <em>preference</em>: “<strong>our highest priority is</strong> to satisfy the customer through early and continuous <strong>delivery of valuable software,</strong> built around <strong>motivated individuals.</strong>”</p><p>An agile team is not one that moves tasks from Sprint Backlog to Done quickly, but one that delivers value often. And to make sure no one falls into the trap of our plagued name, the Scrum Guide dares to make it clearer:</p><blockquote>“The heart of Scrum is a Sprint (so) each Sprint has <strong>a</strong> goal of what is to be built (and) the resultant increment.”</blockquote><p>So here we have <strong><em>one</em></strong> goal planned to fit within a Sprint. (So it must also be within the team’s output capacity, right?) Since meeting such goal <em>“is our highest priority”,</em> we can assume that velocity is absolutely irrelevant as long as we have a <em>“working software”</em> by the end of the Sprint.</p><p>This means Sprints are meant to deliver continuous value, not burn-down charts, so the velocity hysteria is flawed from birth. <strong>Fast teams are cultivated and earned, not reaped and plucked.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*289KJwPYPALtWiOC7wFQ6A.jpeg" /></figure><p><strong>Just like a curse, this plight is inescapable</strong> although the accursed will strive to escape it. The Agile <a href="https://en.wikipedia.org/wiki/Oedipus_Rex">Oedipus</a> will fall prey to the same curse he cast upon others, failing to provide the value he preaches his traditional competitors do not provide.</p><p>I won’t dare to re-christen our doomed name, but the fact is that “Agile” literally gives us a bad name. One that grows into vigilance and abuse — both in absolute contradiction with our values of Openness, Respect, and our pursuit of value. Here agility turns into indignity.</p><p>A name such as “agilist” ought to be reserved to people like Usain Bolt, not value-driven professionals. (Which are indeed agile, but only <em>agile to provide value.</em>) Whenever a Scrum Team doesn’t know for sure why they are sprinting for, go one unit backwards and contemplate it: <em>they are NOT agile.</em></p><blockquote><strong>“I don’t believe in deadlines. I believe in value.” — </strong><a href="https://medium.com/u/cc9d4b33ab92"><strong>Fred Serrano</strong></a>, Agile Coach @ <a href="https://www.nasdaq.com/articles/brazil-fashion-group-soma-raises-%24348-mln-in-ipo-2020-07-29">Grupo Soma</a>]</blockquote><p>As a closure, I remind you that the Greek myths taught us a simple way to break a curse: facing it and acting upon it.</p><p>So if a backlog or a burn-chart come hammering at the back of your head, pause and think if it’s in the best interest of your customers and squad. You’ll often see you’re chasing vanity metrics, not valuable outcomes.</p><p>Remember the wise words of the Agile Manifesto: “<em>individuals over processes</em>”, “<em>collaboration over contracts</em>” — and value and respect over the velocity BS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/0*jFsMvxN6RQ9DqVl1.png" /></figure><p><a href="https://medium.com/serious-scrum/your-invitation-to-the-serious-scrum-slack-workspace-f424aeea4093?sk=e8334e6ee505a85ae6b9d2a1ce37219c">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></p><p><em>Special thanks to </em><a href="https://medium.com/u/b40569a4ce51"><em>Maarten Dalmijn</em></a> <em>&amp; </em><a href="https://medium.com/u/5944d9fdcbcc"><em>Marty de Jonge</em></a><em> for reviewing this piece!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=978591aa837a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/lets-face-it-agile-is-a-cursed-name-978591aa837a">Let’s face it: “Agile” is a cursed name</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Sprint wasn’t cancelled (but my trust in Scrum was)]]></title>
            <link>https://medium.com/serious-scrum/our-sprint-wasnt-cancelled-but-my-trust-in-scrum-was-a3f263ab5fb5?source=rss-53ee4ac7f11f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3f263ab5fb5</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[serious-scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Romario Verbran]]></dc:creator>
            <pubDate>Tue, 04 Aug 2020 05:54:21 GMT</pubDate>
            <atom:updated>2020-08-04T05:54:21.946Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why you should cancel a Sprint and what happens when you don’t</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fGulIT15afjeK-tZPBbs0g.jpeg" /></figure><p>I’m not here to point fingers. No one could foresee that our <em>sprint goal would go completely obsolete</em>, and it’s easy to understand a manager who feels like cancelling a sprint is like admitting failure, but things shouldn’t be that way:</p><blockquote>A Sprint is just a time-boxed container for Scrum events; arbitrary and independent from the people and work in it.</blockquote><p>When a sprint is cancelled due to obsolescence (the only factor prescribed by the Scrum Guide itself), we don’t set computers on fire nor do we delete the useful stuff in the Sprint. We also don’t exchange blame and crucify managers; we simply review useful tasks and start a retro to understand why our squad has been building useless stuff so we can prevent it in the future.</p><p><strong>Otherwise, what you get is 2 unexpected holidays </strong>for not having the <em>courage</em> to face a Retro and a new Planning. You’ll end up with managers foraging the backlog to pick whatever can fit in the sprint — and devs will greet you in the following morning with “<em>hahaha, I don’t even know if that can be built!”</em> (Meaning more hours lost in wait for the tech lead, which would confirm the disgraceful news.)</p><p>A frustrated team; an obsolete goal; another sprint with no value delivered. Pardon me, but here’s something that should be made clear to all agile teams:</p><blockquote>Agile is 100% NOT about quick task completion, but quick value delivery. Agile brands seek ROI, not clean backlogs.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*cB05OOvlUwS2QW09IoGMIA.jpeg" /></figure><p>Scrum is an empirical process: you analyse what works and what doesn’t to draw your conclusions and make you next sprint better than the last.</p><p>Scrum is also about delivering value better and quicker after learning from retros: if your goal has gone obsolete and the squad is now working on random tasks just to finish the sprint, what you’ll get is a beautiful “Done” column at your end and a miserable customer at the other end.</p><p>No, I’m not suggesting every sprint should be cancelled when there’s a slight issue with your goal — adaptation is one of our pillars, after all — but if it came to the point that your Sprint Goal rendered your Sprint Backlog pointless, why not start a Planning instead of wasting two hours discussing blame and picking random tasks from Product Backlog just for the sake of completion? (And a bit of pride, of course.)</p><blockquote>“Sprint cancellation is a value-based decision” — <a href="https://medium.com/serious-scrum/sprint-cancellation-c9a9c66e8c99">S. Nijland</a></blockquote><p>We are not being <em>transparent</em> if we aren’t willing to face failure, meaning we won’t <em>inspect</em> what went wrong nor will we learn to <em>adapt</em> processes and plans to avoid this sort of debacle. In conclusion, <strong>tasks will keep dashing to the Done column whereas Value will take a backseat in the backlog.</strong></p><p>Maybe we should print our burndown charts and put them on sale instead?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*1UxLKFh8N_MTrTknZaXn5w.jpeg" /></figure><p>Suspecting that my colleagues would try their hardest to forget failure before the sprint ended, I coaxed everyone into a semi-retro which revealed our biggest problem was not having clear objectives.</p><p>The commercial tribe was going through corona chaos and suggesting all sorts of solutions while keeping longterm objectives for themselves — inducing us to help them extinguish the fire while also leaving our OKRs in second place, thus making it easier for nonsensical requests to pass.</p><blockquote>A wild wasterfall appeared. It stealthly leaked tasks from others managers to us, fully unnoticed before drowning us.</blockquote><p>That’s when we agreed that objectives should be visible to all 24/7 so now we can clog those cascades more easily. There was just one problem: how would we ensure everybody would follow objectives now that we no longer have a shared wall to hang our goals?</p><p>Let’s be honest: no matter how easy it is, no one wants to open any page to search for something abstract and boring such as OKRs — but luckily no one will have to, because I stumbled upon Maarten’s guide on <a href="https://link.medium.com/qw8JDDDWw8">Roadmap Epics</a>!</p><p>Turning OKRs into Epics made it all conspicuous to both squads and also brought the roadmap just one click away from every manager as objectives and key results are now following us in the sprint board every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*b7hTtk4PVXRMtmBac_-O1A.png" /><figcaption>[Using Maarten’s example since our board isn’t in English]</figcaption></figure><p>A new task leaked? They now have to show us how it fits our OKRs since the Epic/OKR field is required — and if doesn’t, no problem: there’s a waterfall epic for that, so we have an easier time prioritising what matters and detailed stats to show stakeholders / upper managers where resources were wasted.</p><p>No, we didn’t cancel the Sprint as I pleaded but we’ve discussed and discarded so much that the result was the same (unofficial victory!), paving a new way to this squad that can no longer run a sprint just for its sake.</p><p><em>“Sprint cancellations are often traumatic”</em>, the Scrum Guide states, but I posit that the worst trauma your squad can have is to feel useless day after day.</p><p><em>Special thanks to </em><a href="https://medium.com/u/b40569a4ce51"><em>Maarten Dalmijn</em></a><em> for taking the time to review this article with his insightful feedback. As an avid follower, it’s a huge honour.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*Tf4oBEIamL3qLonL" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/0*mZqZ3DsaI7cfKo8E.png" /></figure><p><a href="https://medium.com/serious-scrum/your-invitation-to-the-serious-scrum-slack-workspace-f424aeea4093?sk=e8334e6ee505a85ae6b9d2a1ce37219c">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3f263ab5fb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/our-sprint-wasnt-cancelled-but-my-trust-in-scrum-was-a3f263ab5fb5">Our Sprint wasn’t cancelled (but my trust in Scrum was)</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>