<?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 askthecrowd on Medium]]></title>
        <description><![CDATA[Stories by askthecrowd on Medium]]></description>
        <link>https://medium.com/@askthecrowd?source=rss-a66d6101438b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4S8xEH58JMDex4n_v6yjyg.png</url>
            <title>Stories by askthecrowd on Medium</title>
            <link>https://medium.com/@askthecrowd?source=rss-a66d6101438b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:18:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@askthecrowd/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[The project I failed, the experience I gained]]></title>
            <link>https://medium.com/@askthecrowd/the-project-i-failed-the-experience-i-gained-347f2175a7ef?source=rss-a66d6101438b------2</link>
            <guid isPermaLink="false">https://medium.com/p/347f2175a7ef</guid>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[self-care]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[askthecrowd]]></dc:creator>
            <pubDate>Thu, 28 Apr 2022 15:42:34 GMT</pubDate>
            <atom:updated>2022-04-28T16:35:06.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOuYq8beDCnM6XAjc5l47w.png" /></figure><p>Medium is filled with stories about failed design projects. Now It’s time to tell mine.</p><p>I knew when I started my product design career that it would be hard. I was severely anxious that I don’t have the right degree or the right skill to be successful. I can imagine the picture of a final product in my head but don’t know how to build it nor immediately implement a solution. When you feel like a tree in the forest of your ambitions and self-doubt, it’s hard to keep things cool in your head and not to fall apart.</p><p><strong>But before that the backstory.</strong></p><p>I am a digital product designer (ux/ui and all that stuff) and at that time I worked in a small graphic design studio and my daily routine was creating small landing pages, posters and other print stuff. So imagine my experience and knowledge about user experience and product development. Yes, you are right. Absolutely none. To be clear, I took some courses on product design. It taught me some basics on how to do market research, comparative analysis and gave some understanding on how to develop and prototype. But I never applied it to real life.</p><p>The question was could I manage to pull the project up just based on a vision rather than skills, principles, rules and guidelines. <em>(If you don’t want to read the whole thing the answer is no)</em></p><p><strong>How it started</strong></p><p>I got an invitation from one of the biggest local studios to do a freelance project for one of the biggest tech companies in the country. It started off cool. I was excited. The dream team of an art director, two product managers, a digital producer and me — a green designer who doesn’t know shit about how the real world works.</p><p>Throughout my very short but ambiguous career I have only worked in small studios where all my troubles, worries and mistakes were virtuously hidden from the eyes of a client and all my failures were nicely covered. And here I am, standing alone in front of a blank Figma file constantly thinking how not to fuck this up. I was so obsessed with the idea of how this would look and how many likes it would get me on Behance. The best project of my life that I have an opportunity to make by myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UnuiXC644kKMBY76NgUeXA.png" /></figure><p><strong>The brainstorm</strong></p><p>Before we started working we had to prioritize what the stakeholders wanted and what customers actually needed. I’ve done a similar project where I implemented some gaming features into the banking app, so it could be more engaging to the younger generation. I think having that in my portfolio was the main reason why they chose me for this project. My ability to put fun things where they possibly can not be put. When reflecting on these experiences, I thought: “oh sure, everything is meant to succeed!”. They are a big company with a design system. Their target audience is mostly young, tech-savvy people between 25–35. They love memes and fun stuff so it’s all should be pretty simple.</p><p>After some brainstorming sessions we came up with a plan: we decided to build a simple text game where a person plays as a fictional character and walks through the different parts of an imaginary city and different life situations, where he can both learn, test some platform features and find out what the company offers. The aim was to help people understand the whole ecosystem and keep them engaged at the same time. Overall, to give them a sneak peak of what they are getting, when they actually start using the product.</p><p><strong>The Plot</strong></p><p>The main hypothesis was that since everybody does gamification now how could we turn that around to teach the customers about our platform, what it offers and finally get them to pay for the service and stay satisfied.</p><p>We couldn’t just make a game. I am not a game designer and the studio didn’t offer game development. We simply didn’t have enough time and budget to do a whole game in 3 months. We had to think creatively how to implement gaming features into the boring platform, tell a story about the company and other products they have. And when you have a lot of dissatisfied consumers you can’t just abuse game mechanics, tell them now the whole product is fun so that’s why you should pay us. We needed to understand the confusion behind the previous solution and naturally win the customers’ trust back. So I slowly started to untangle this giant mess of different ideas and users’ insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r5UDuI3xUBxYNFrnhY85NA.png" /></figure><p><strong>The Problems</strong></p><p>First, we had to onboard users and tell them what the whole idea was and what was going to happen. It was meant to give us some information about “the person behind the computer”. In theory, it looked like a basic form where we asked the general questions regarding age and what they are looking for in a perfect end solution. I turned that into the character setting where the user creates his digital self. Players can choose between different paths and personalities. Each decision or an input generates a unique scenario based on their needs and emulates a situation where the product can be used and how it practically solves all problems.</p><p>The second part was the gameplay. The aim was to tell a story about the character’s struggles and seamlessly show everything we have. Not to over abuse the sales patterns so he wouldn’t find out that it’s a sales trap.</p><p>And finally, after he reached the final level we wanted to congratulate them and give them a personal discount based on how much coins they collected during the game.</p><p>To me it sounded smooth and clear, so I switched to a non-sleeping mode and started writing dialogues and assembling the prototype.</p><p><strong>The beginning of an end</strong></p><p>3 months have passed. The client was getting nervous about the amount of time we’ve spent on conceptualizing our ideas and arguing about how we should name this button or that chapter. The whole scenario grew more and more. It started to take 30 minutes to get to the end. When the UX editor came, I got anxious. When the business analyst<strong> </strong>came and asked why it looks like a game rather than just a landing page with a pricing option, I lost it. My perfectly built house of cards went spiral from the thought that i won’t be the next Hideo Kojima to how I’ve spent all this time designing a “game” where the client needed something else. Where exactly did I miss the turning point?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LZjFIaehraevCCQz4O71Rg.png" /></figure><p><strong>The Finale</strong></p><p>They took my Figma file (yes, 500 frames of nonsense). Went on doing user interviews. They did 10 full gameplay walkthroughs with 10 different users. After 3 weeks they wrote:</p><p><em>”We failed. Only one person understood what was going on. The rest were miserable.”</em></p><p>They also kindly wrote that they would take some features for future development and disappeared.</p><p><strong><em>What I have learned</em></strong></p><p><em>Everything must be made ready for development</em>. It’s an MVP. Don’t try to squeeze in the whole concept before you actually prove that your idea works.</p><p><em>The more time you spend on design, the harder it is to turn the broad conceptual principles into actual real-life products</em>. And being a really good designer or having a very creative mind won’t help. Some issues can be only discovered after the product was built. It’s the rule of this world that you can’t simply avoid.</p><p><em>To do small parts of a project</em>, user test them, acknowledge the feedback to improve and change the strategy before it is too late. That’s why, in addition to keeping things organized and not so dreamy, we should apply the magic of user research to the most uncertain part of your product and not spend precious time arguing over names and colors.</p><p><strong><em>*A note to future self*</em></strong></p><p>It is always gut-wrenching when your product dies before he has a chance to live. I went through all 5 stages of grief from declining that it all happened to accepting that i failed. But I have failed in the past. In fact, I fail all the time, so why not to use it as an opportunity to learn and grow. The whole thing taught me to work quicker, more strategically and differentiate between how I assume something may work and how it actually works. But most importantly, not to eat myself alive and keep going with the rest of the day. Because the hardest part of growing up is letting things go.</p><p>/drxplr</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=347f2175a7ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is this thing really on?]]></title>
            <link>https://medium.com/@askthecrowd/is-this-thing-really-on-110a10642859?source=rss-a66d6101438b------2</link>
            <guid isPermaLink="false">https://medium.com/p/110a10642859</guid>
            <dc:creator><![CDATA[askthecrowd]]></dc:creator>
            <pubDate>Tue, 05 Apr 2022 17:12:14 GMT</pubDate>
            <atom:updated>2022-04-13T11:41:19.166Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DXonBPWqFspU8qP7kVMmaw.png" /></figure><p>Many things around us have two simple states: they are either on or off. From light switches and microwaves to apps and spaceships. Many designers while designing a toggle switch, often misuse them or get so innovative with the design that it no longer looks like an action element at all. So what if user can’t tell which option is chosen? Do you think users can click on it and quickly find out? In theory, yes… But in reality, when users have to second guess elements in their everyday apps, they want to grab an extra Xanax pill. The way to avoid that is to <em>test your product decisions</em>.</p><p>When it comes to digital products, users don’t like to think. What’s more, people in general don’t like to think. And if something takes more than 5 seconds of our attention, we tend to give up (we know we do). Therefore, perhaps the most common feedback designers get is that something in their design wasn’t obvious or took a long time to figure out.</p><h4><strong>The devil is in the details</strong></h4><p>Toggle buttons are generally meant to show whether something is active or not, and when people tap or click them, they expect an immediate reaction. And designers often don’t use them correctly or simply overuse their creative powers.<br>You can use labels or a slight color change to show that something is selected and then use them consistently throughout the interface and on other platforms to make people less anxious and frustrated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4waZT4rUHoTFdcabN1Qyw.png" /><figcaption><a href="https://askthecrowd.app/r/376bbe03">What if in one app there are <strong>colors</strong> to show the selected option and in another the selected option is left <strong>achromatic</strong>? How will people understand what is active? (guess what, they won’t)→</a></figcaption></figure><p>The main problem is that we simply fail to correctly predict how users perceive our design<strong>. </strong>Why? Because we’re used to the product, and we take certain knowledge for granted. What’s apparent to us, though, may be confusing for ordinary users. And with a million other products available, the user can just as quickly move on to another that doesn’t make them guess.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ESaJzG5xvhSr2azAj0Y-Hw.png" /><figcaption><a href="https://askthecrowd.app/r/4e851b6a">This one may seem harmless, but look, 30% of people still got confused→</a></figcaption></figure><p>Always thinking like your target audience is almost impossible, but we should at least correlate our creative intentions with what people already know and are used to, and do whatever we can to create a design that lies somewhere between what we want and what the user wants.</p><h4>Knowing when and how</h4><p>The higher purpose of design is to be invisible, seamless and intuitive. Where every click and gesture is considerately calculated, so the users get their job done. Being conceptual and unique is good and we should all strive for creativity, but there is a misconception that our philosophy is rooted in equating “technical” with “non-original.” Debunk this myth and use your common sense.</p><p>In the end, we need to democratize our design decisions, keeping in mind when and how people will use our product. Asking questions and digesting valuable insights, proving that you were wrong (but we hope you weren’t), more than anything else.</p><p>by/drxplr</p><p><em>One way to do it is to </em><a href="https://askthecrowd.app/"><em>askthecrowd</em></a><em> (get the joke?) It’s a tool that helps creators test their products on people before things go wild. You can sign up for a free run, ask a question, share screenshots of your interface, and find out exactly what the average user thinks in minutes. Care to join?:)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=110a10642859" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>