<?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 Mohamed Ansari on Medium]]></title>
        <description><![CDATA[Stories by Mohamed Ansari on Medium]]></description>
        <link>https://medium.com/@mohamed.ansari?source=rss-c0795dab5d6a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_7Ph1AZLwNQ3q5LjOKfOlA.png</url>
            <title>Stories by Mohamed Ansari on Medium</title>
            <link>https://medium.com/@mohamed.ansari?source=rss-c0795dab5d6a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:37:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mohamed.ansari/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 Tasty Design Process: A Story about Influence, with Love ❤️]]></title>
            <link>https://medium.com/design-bootcamp/the-tasty-design-process-from-solo-designer-to-design-driven-org-with-love-%EF%B8%8F-77733759c230?source=rss-c0795dab5d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/77733759c230</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Mohamed Ansari]]></dc:creator>
            <pubDate>Tue, 23 Dec 2025 23:14:15 GMT</pubDate>
            <atom:updated>2026-09-09T08:33:59.625Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbcFf1xGapgLKbcCvCznUQ.png" /></figure><h3>The Tasty Design Process: Building Design Influence from Zero</h3><p>I joined <a href="https://spectral.energy/">Spectral</a> as the first UX Designer on the team.</p><p>Spectral is an energy tech startup that builds software for renewable energy management in the Netherlands. The kind of products where a bad interface means wind farms lose money or buildings waste energy.</p><p>The team was small but international. Brilliant control engineers and energy consultants who understood power systems better than anyone.</p><p>But design? That was the thing they’d hired me to “do.”</p><blockquote>“Achieving great UX design is not just a function or talent of individuals, it is an organizational characteristic.“</blockquote><p>— <a href="https://community.sap.com/t5/technology-blog-posts-by-sap/boost-ux-maturity-in-your-team-with-these-free-tools/ba-p/13517267">Chapman and Plewes</a>, 2014 International Conference of Design, User Experience, and Usability</p><h3>The Pattern</h3><p>In meetings with engineers, I noticed a pattern. Every conversation jumped straight to solutions.</p><blockquote>“Users need this” <br>“Here’s how we’ll build this.”</blockquote><p>No exploration. No hypothesis. No validation.</p><p>I tried explaining the design process to everyone.</p><blockquote>“We should spend more time in the problem space. Diverge here, explore before we converge on a solution.”<br>“Maybe create some concepts, see if they’re feasible to build, and check with business if they’re viable.”</blockquote><p>But no takers. Engineers just said, “Can you just show us what it should look like?”</p><p>That’s when I knew we had a bigger problem at Spectral.</p><h3>Design philosophy</h3><p>My design philosophy is simple:</p><blockquote>Everything and everyone that is a part of the system contributes to the solution.</blockquote><p>If I wanted everyone to contribute to design, I needed to stop speaking designer and start speaking human.</p><p><a href="https://nataliehanson.com/2017/02/13/ux-maturity-models/"><strong>UX Maturity Models</strong></a> assume you have a design team, formal processes, and organizational buy-in that doesn’t exist when you’re solo.<br>They measure structural maturity over years when you needed immediate influence and impact, measured in quarters, not decades.</p><p><a href="https://www.designcouncil.org.uk/our-resources/the-double-diamond/"><strong>Design processes</strong></a><strong> </strong>are written in jargon for designers, not in language that resonates with engineers and energy consultants. They assume you already understand “convergent/divergent thinking” and “problem space.”</p><blockquote>We gatekeep our own discipline, then wonder why other departments don’t value design thinking.</blockquote><h3><strong>The Food Connection</strong></h3><p>At Spectral, we had a culture of sharing food at various occasions like festivals, when back from a vacation or just like that because why not?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-cWF6UROVuR381AmQJBkQ.jpeg" /></figure><p>People would often cook something and bring it for everyone to share.<br>We also had a Slack channel <strong>#cooking</strong> for sharing recipes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qq-KHv5KXfuVOKBvaonTEQ.jpeg" /></figure><p>These engineers who “didn’t get design” were already practicing convergent/divergent thinking every time they tried a new recipe.</p><p>They understood iteration and feedback loops. They just did it with food instead of features.</p><p>So I decided to explain design with cooking. <strong>The most human language.</strong></p><h3>Influence with Love ❤</h3><p>I surveyed the office: “What would you like me to talk about?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XE2wNQnmKsX7rLgPwNjmYw.jpeg" /></figure><p><strong>72% wanted to know about the UX design process. <br>61% asked about design thinking.</strong></p><p>These weren’t people resisting design. They genuinely wanted to understand it.</p><p>A few responses showed how much they cared:</p><blockquote>“I‘m a big believer, hope you build a strong case for it. Let me know if you need any support!”</blockquote><blockquote>“How our customers will benefit from good design?”</blockquote><h4>Presentation</h4><p>I began with everyday examples of bad design around the office.</p><p>The office front door was a Norman door.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1sN4bhOczaBHX_g-WkntWg.jpeg" /><figcaption>The Norman Door</figcaption></figure><p>We all pushed when we should’ve pulled.</p><p>Then came the microwave ovens.<br>Everyone used the basic one instead of the fancy one because it was easy to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yYkc8tnCn8j12KswRFlBSg.jpeg" /><figcaption>Everyone used the simple one on the left.</figcaption></figure><p>With everyone warmed up about how it feels to use products others built, I got to the main course: the design process itself.<br>I showed them the double diamond and explained how it mapped to something they already knew: <strong>cooking.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vIZ51yd8ikQj27qWx17t2Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cyzr0cwNjb9s6VJcVQMCuw.jpeg" /></figure><p>When the problem is <strong>hunger</strong>:</p><p><strong>Discover = </strong>“What do I cook?” When you’re deciding what to make, you think of everything. Pasta? Stir fry? Soup? You’re discovering, exploring all possibilities. What do I want to eat?</p><p><strong>Define</strong> = “Ingredients.” Now you narrow down. Based on what you have, what’s realistic, what you’re craving. You’re converging on what you’ll actually make.</p><p><strong>Develop</strong> = “Let’s cook!” You’re back to exploring. Try it sautéed. Maybe add garlic and a bit of salt. What if you roast it instead? Diverging again.</p><p><strong>Deliver</strong> = “Serve.” You pick the best version, plate it, make it look good. Converging on the final dish.</p><p><strong>Test</strong> = “Tasty?” Just like testing a product with users and asking: does this work for you?</p><p>I saw people nodding, they could see the process mapped out in front of them.</p><p>Then I asked,</p><p>“What’s the most important ingredient when we cook?”</p><p><a href="https://medium.com/u/a9c879cb5258">Andrea</a>, my manager shouted from the back <em>“Love!”</em> and the whole room lit up.</p><p>That was it.</p><p>“And that’s how we’re going to design products. With love.” ❤</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xjwPcuRaoROb-eFlFeBkSQ.png" /></figure><h4><strong>What Changed</strong></h4><p>Engineers who would’ve rolled their eyes at “user-centered design” started paying attention to user needs. Backend engineers started asking how their API decisions would affect users. Feedback got better. People stopped jumping to solutions and started talking about the problem.</p><p>The shift showed up in meetings. Someone would pitch a feature and the room would push back: “But what problem does this solve for the user?” Not me asking. Them asking each other.</p><p>Great design isn’t just what designers do. It’s what everyone does when they have the right mindset.</p><p>And a little love. ❤️</p><p>Special thanks and lots of love to <a href="https://www.linkedin.com/in/andrea-lamelas-puga/">Andrea</a>, <a href="https://www.linkedin.com/in/vjacobs/">Vincent</a> &amp; <a href="https://www.linkedin.com/in/alxbrg/">Alex</a>. ️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQQ18ehuGw2SvRjcNzsBNg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77733759c230" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-tasty-design-process-from-solo-designer-to-design-driven-org-with-love-%EF%B8%8F-77733759c230">The Tasty Design Process: A Story about Influence, with Love ❤️</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 We Built a Winning Prototype with AI and Zero Wireframes ]]></title>
            <link>https://medium.com/design-bootcamp/the-seven-hour-design-sprint-how-we-prototyped-campfire-at-a-figma-hackathon-f017bd91d84a?source=rss-c0795dab5d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f017bd91d84a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[figma-make]]></category>
            <dc:creator><![CDATA[Mohamed Ansari]]></dc:creator>
            <pubDate>Thu, 30 Oct 2025 08:01:55 GMT</pubDate>
            <atom:updated>2026-04-17T15:21:33.310Z</atom:updated>
            <content:encoded><![CDATA[<h4>Five strangers, one crazy Friday, and what I learnd from AI-powered prototyping under pressure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jmrLb2kCWCj8WQMNH6hgw.jpeg" /></figure><p>It’s 8:30 AM on a Friday at The Social Hub, Amsterdam. Clutching a coffee, I’m making small talk with people as they arrive.</p><p>By 5 PM, our team would win the hackathon. But right now? I’m wondering where the snacks are.</p><p><strong>Explore the prototype here 👉 </strong><a href="https://ebony-eagle-05050608.figma.site/"><strong>https://blurb-koala-06850723.figma.site/</strong></a></p><h3>The event begins</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zMNhHEvjbMwm8X_V9gwjQ.jpeg" /></figure><p>The event was called “Hack the Beat,” a Figma Make hackathon hosted by <a href="https://qonto.com/en">Qonto</a>, <a href="https://www.malt.com/">Malt</a> and <a href="https://friends.figma.com/amsterdam/">Friends of Figma Amsterdam</a>.</p><p>Everyone was asked to form teams of five.<br>The challenge: <strong>solve a problem of your choice using Figma Make</strong> <strong>only</strong> and present the solution by 5PM.</p><p>I ended up with <strong>Maria, Laurel, Jane, and Jun</strong>. Complete strangers, all of us.</p><h4><strong>We decided to solve problems faced by freelancers.</strong></h4><p>During introductions I realized three out of five of us were actively freelancing and the other two had freelanced at some point.</p><p>Our team name: <strong>FigMates</strong>. We were using Figma, and we were about to become teammates.</p><h3>Structuring chaos: the Double Diamond</h3><p>We decided to follow the <a href="https://www.designcouncil.org.uk/our-resources/the-double-diamond/">Double Diamond design process</a> and split our 7 hours as such:</p><ol><li>Discover the problem (10–11 AM)</li><li>Define the solution (11 AM-12 PM)</li><li>Develop the prototype (12–3 PM)</li><li>Deliver the presentation (3–5 PM)</li></ol><p>With our structure set, we jumped in.</p><h3>Discover: sticky notes and isolation (10:00–11:00)</h3><p><em>Output: one clear “How might we” statement.</em></p><p>Everyone started dumping ideas on sticky notes. Everything we knew about freelancing from our own experiences. The wall filled up quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bBxtfaCqZuq8AqI0P7Jz1A.jpeg" /><figcaption>The FigMates team brainstorming freelancer pain points</figcaption></figure><p>Three major pain point categories emerged:</p><h4>1. Work-related</h4><ul><li>How do I find work?</li><li>Can I pick up extra work from others?</li><li>Can I pass on work I don’t have time for?</li></ul><h4>2. Payment-related</h4><ul><li>Getting paid on time</li><li>Setting the rate</li><li>Invoicing &amp; accounting</li></ul><h4>3. Community-related</h4><p><strong><em>This is where most of the sticky notes clustered.</em></strong></p><ul><li>“I need help on something, like feedback on a design.”</li><li>“I feel alone doing all of this by myself.”</li><li>“I go to public places just to feel like I’m around other people.”</li></ul><p>If you’re a remote employee, you can just open Slack or Teams and chat with a coworker. If you’re in an office, you can walk over to your favorite work buddy and take a break together. It’s built into the structure of employment. But not for a freelancer.</p><p>The problem:</p><blockquote><strong>“How might we help freelancers feel less isolated during work?”</strong></blockquote><p>This was our focus.</p><h3>Define: from isolation to coffee breaks (11:00–12:00)</h3><p><em>Output: short brief + MVP scope.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ujcYBF-yZSLBDQWdBnMqMQ.jpeg" /></figure><h3>Develop: first prompt to prototype (12:00–15:00)</h3><p>This is where things got different.</p><p>Usually, at this stage, we’d be sketching wireframes, mapping user flows, debating button placements. Instead, we opened Figma Make and typed our first prompt, focusing on the ‘coffee break’ feature. <strong>The concept was simple.</strong> Not a formal meeting. Not networking. Just a moment to connect with another freelancer.</p><p><strong>And here’s where it gets interesting.</strong> We didn’t really write our own prompt. We just described the coffee break feature to ChatGPT and copy-pasted that into Figma Make.”</p><p><strong>First prompt in Figma Make:</strong></p><blockquote>Freelancers often work alone for long stretches of time, missing the casual chats and spontaneous moments that happen in team environments. What if we could recreate that friendly “coffee break” — a short, easy way for freelancers to connect, share, and recharge together?<br>Your Challenge: Design an interface that helps freelancers easily connect with each other for a 15-minute virtual coffee break.<br>Goal: Make it feel human, effortless, and warm — not like a meeting, but like a friendly pause in the day.<br>Consider:</blockquote><blockquote>How might the system match freelancers (by interests, location, skills, or random)?</blockquote><blockquote>How might you design the invitation flow so it feels casual and low-pressure?</blockquote><blockquote>What does the 15-minute experience look and feel like (before, during, after)?</blockquote><blockquote>How can the interface encourage authentic conversation and not just small talk?</blockquote><blockquote>How might freelancers stay connected afterward — or simply walk away refreshed?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MUYtkeVmx4zxIew1ptHRlg.png" /></figure><p>And just like that, we had a working feature. The team lit up. This was real. This was something we could build on.</p><p>After lunch, we started thinking about a name for the product.</p><blockquote>We wanted to capture what we were trying to create: a place for freelancers to gather, share warmth, and connect, even if just for a moment.</blockquote><h4><strong>CampFire</strong> 🔥</h4><p>With a name in hand, we fed it back into Figma Make along with our concept. After more prompting, we had something that felt like a product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BwfuJ3Pa3Anul_qrcL425A.png" /></figure><h3>Deliver: when the wheels almost came off (15:00–17:00)</h3><p>What was supposed to happen after 3 PM: <strong>polish the prototype, prepare slides, rehearse the presentation.</strong></p><p>What actually happened: <strong>CHAOS</strong></p><p>The team was too excited. We wanted to build all the features: the chitchat feature, the help requests, the status updates, the freelancer-friendly places map, the payment integrations.<strong> All of it.</strong></p><p>But only <strong>one person could work on the prompts at a time</strong>. And suddenly, we weren’t aligned anymore.</p><blockquote>“We should do the status feature next.”</blockquote><blockquote>“No, we need to finish the chat flow first.”</blockquote><blockquote>“What about the help request feature? That’s critical.”</blockquote><p>We hadn’t discussed priority. We hadn’t decided what was essential versus nice-to-have. The clock was ticking and emotions were high. The team spirit began to fracture.</p><p>We stopped talking to each other. For a few minutes, everyone just did their own thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-4rD0hM3baQc41sCNNSuMA.jpeg" /><figcaption>The essential “serious” pic</figcaption></figure><p>Finally someone broke the silence.</p><blockquote><strong>“This isn’t working.”</strong></blockquote><p>We split up, divided the features we wanted to build and paired off:</p><ul><li><strong>Jun and I focused on the homepage</strong></li><li><strong>Maria and Jane took the social connection features</strong></li><li><strong>Laurel became our integration lead</strong></li></ul><p>We regrouped again. More focused.</p><p>P<strong>rofile status</strong> feature working after a few prompts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yXX5M-MXYOLRHj3fDTnaeg.png" /><figcaption>Profile status feature</figcaption></figure><p>The homepage started taking shape with focus on the “I need help” feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VQ70o5K2peKudpU9EOw_vw.png" /><figcaption>More options to refine the search when seeking help</figcaption></figure><p>We tried creating a <strong>schedules page</strong>, a way to see when others might be available, and in the process Figma Make gave us a <strong>“Campfire Requests”</strong> page instead. Changing this would take more time, so we decided to go with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PPERFytITyOkiKQi1SmebA.png" /><figcaption>Campfire requests page we decided to go along with</figcaption></figure><p>We agreed on what we had actually built:</p><ul><li><strong>Chitchat</strong> — the 15-minute connection feature</li><li><strong>I Need Help</strong> — a way to request feedback or advice from other freelancers</li><li><strong>Profile Status </strong>— a simple indicator showing if you’re busy, free, available for a chat, or taking a break</li><li><strong>Campfire Requests</strong> — a way to see and post requests to the community</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O6dFLDjnL9t26SRzsohmSw.jpeg" /><figcaption>Us feeling proud of the progress we made</figcaption></figure><p>After a few more prompts, the product felt real and we were back in business.</p><p>It wasn’t everything we had imagined. It was functional. And it solved the problem we set out to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I7TLU7dB9L8EeY7FYzQBTw.png" /></figure><p>Parkinson’s law states that:</p><blockquote><strong>“</strong>Work expands to fill the time available.<strong>”</strong></blockquote><p>For us, work narrowed down to fill the time we had.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MO3CMaQgiDLobZojFAGqXA.png" /><figcaption>Click to zoom in</figcaption></figure><p>Just to check if everything worked, we published it and tried it ourselves. Voila!</p><p>This was the best part of the day. The flow actually ended with opening the chat window for a chitchat. There was a new excitement. The team felt confident.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*7GVKOhmoM-BPPMwFVeaj4w.jpeg" /><figcaption>A moment of surprise when the camera opened up</figcaption></figure><h3>The presentation: no script, just a story (16:45–17:00)</h3><p>It was 4:45 PM. Fifteen minutes until showtime.</p><p>Maria quickly polished a few slides. Laurel cleaned up the persona. Jun made sure the demo would work.</p><p>Jane and I decided on a plan. She would introduce the persona and set up the problem. I would tell the story and demo the product.</p><p>We tried it once. That was all we had time for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iy5eRyfxX4NIthD34bsVzw.png" /></figure><h3>The win</h3><p>After all four teams presented, the judges announced it.</p><p><strong>“The winner is… FigMates, with CampFire.”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*KQjjM6bC07nSjzNhWm_1bQ.gif" /></figure><p>We hadn’t built the most features. We hadn’t had the flashiest design. But we had focused on a <strong>genuine pain point, validated it with our own lived experience as freelancers, and prototyped a solution that had potential</strong>.</p><p>We had built something closest to a working product that solved a real problem.</p><p>The judges saw that. And it was enough.</p><h3>What I learned</h3><p><em>This hackathon taught me more in seven hours than some projects teach in seven weeks.</em></p><h4>1. AI tools change the design process, but don’t replace it.</h4><p>The Develop stage looked nothing like traditional design work. No wireframing. Just prompting, generating, and iterating. Figma Make handled the visuals, but we made every decision about what to build and why.</p><h4>2. Disagreements happen. Rebound quickly by finding the middle ground.</h4><p>When the team stayed stuck. Instead, we paused, regrouped, and found a way forward. That flexibility saved us.</p><h4>3. Collaboration on Figma Make isn’t seamless yet.</h4><p>Only one person can prompt at a time. That creates bottlenecks. (Figma is releasing riffs soon, which should help.)</p><h4>4. Don’t skip the presentation prep.</h4><p>We barely had the energy to rehearse. If we’d carved out even 20 minutes earlier to plan the pitch, we would have been far more confident.</p><h4>5. Authentic design wins.</h4><p>Minimal assumptions. Real insights. A solution that genuinely addressed the problem. The design wasn’t polished, but it was real, and that mattered more.</p><h3>Thank you, FigMates</h3><p>This wouldn’t be possible without you guys.</p><p><a href="https://www.linkedin.com/in/ACoAAAJemqoBXB43oXjctYYiLe3CclG8REMt9jo"><strong>Laurel Wright</strong></a>, for sharing your Figma workspace and being the foundation that held everything together.</p><p><a href="https://www.linkedin.com/in/ACoAADSn4YIBrjdWo8N9KLXZBkTUaFZKhauG56w"><strong>Maria Voicu</strong></a>, for the Figma slides and pulling the team out of a difficult moment when we needed it most.</p><p><a href="https://www.linkedin.com/in/ACoAADIOPJ8BNqshrxw5nB2hCnvYi-ruieo5xiM"><strong>Jane Warren</strong></a>, for fiercely defending the most important problem, seeking help, and making sure we stayed focused on user needs around it.</p><p><a href="https://www.linkedin.com/in/ACoAACU74fAB5pNN8DyzqkYsQkbZhE4YKOsEaIo"><strong>Jun Li Jeung</strong></a>, for asking the hard questions and being a total badass prompting away like a machine.</p><p>We were five strangers in the morning. By evening, we were a team. And we had built something real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T1AOhpfDMOP01MGU3uADqA.png" /></figure><p><strong>Explore CampFire here 👉 </strong><a href="https://ebony-eagle-05050608.figma.site/"><strong>https://blurb-koala-06850723.figma.site/</strong></a></p><p>If you’ve ever felt isolated working alone, you’re not the only one. Sometimes, all you need is a virtual campfire to gather around.</p><p>🔥</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f017bd91d84a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-seven-hour-design-sprint-how-we-prototyped-campfire-at-a-figma-hackathon-f017bd91d84a">How We Built a Winning Prototype with AI and Zero Wireframes 🔥</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[The self-taught’s guide to UX Research]]></title>
            <link>https://uxdesign.cc/the-self-taughts-guide-to-ux-research-10edaa5ff5f7?source=rss-c0795dab5d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/10edaa5ff5f7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Mohamed Ansari]]></dc:creator>
            <pubDate>Wed, 12 Jun 2019 13:06:12 GMT</pubDate>
            <atom:updated>2020-01-06T16:43:18.024Z</atom:updated>
            <content:encoded><![CDATA[<h4>What I learnt in a year doing user research.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LaONdqTL_n47Ng5csMA9NA.png" /></figure><p>March of 2018, I joined a product company as a UX Designer whose responsibility was to conduct research and design interactions.</p><p>Coming from a service company where ‘user research’ was only done if the client wanted to, which is never, I realised I had never done any actual research! This made me nervous/twitchy, hell I thought they hired the wrong person for the job.</p><p>To all those who feel like an imposter, know that like you, everyone around is figuring out stuff too.</p><p><strong>More than a hundred phone interviews, a </strong><a href="https://uxdesign.cc/smart-link-invisible-by-design-497a1365de7c"><strong>UX Case Study</strong></a><strong> and a </strong><a href="https://www.instamojo.com/smart-links/"><strong>product launch</strong></a><strong> later, this is what I have learnt (and still learning) about UX Research.</strong></p><h3>1. Define the outcome</h3><blockquote><em>Ask yourself, “What is the outcome of this research?”</em></blockquote><p>your answer should be something like…</p><ul><li>I want to <strong>define user personas</strong>.</li><li>I want to <strong>validate a hypothesis</strong>.</li><li>I want to find out ‘<strong>why?’ is something happening.</strong></li></ul><h3>2. Define the users</h3><blockquote>Talking to random users will take you nowhere.</blockquote><ul><li>Handpick your users based on their behaviour specific to the outcome you have defined.</li><li>If you are researching businesses, gather some background information before calling them, it would be much appreciated. However, for individuals, it would be nice to start by asking them about their background before diving into the script.</li><li>From a list of 100 users consider yourself lucky if you can get 20 users to talk to you.</li></ul><h3>3. Prepare the script</h3><blockquote><em>Have a script ready but never use it.</em></blockquote><ul><li>The script is only to refer to the important points during the conversation to avoid missing anything.</li><li>Have a genuine conversation with your user, talk to them like you share their pain.</li></ul><h3>4. Shut up and listen to the user</h3><blockquote>Its all in the emotions</blockquote><ul><li>Once you connect with the user on a personal level, the emotional floodgates open and you need to let the users speak their heart out.</li></ul><h3>5. Take notes</h3><blockquote>What do they <strong><em>say</em></strong> and <em>feel?</em></blockquote><ul><li>Write down not just what the user <strong>said</strong> but also what they <strong>felt</strong> while saying it.</li></ul><h3>6. Document as soon as possible</h3><blockquote>One tends to forget the bits and pieces over time</blockquote><ul><li>Document the research while it is fresh in your head or you will end up staring at your team with a pile of notes you can’t make sense of.</li></ul><h3>7. How much research should you do?</h3><blockquote>There is an end to the ‘aha’ moments</blockquote><ul><li>At first, a similar pattern starts to appear in what the users say and feel.</li><li>Continue your research until you have answers to your questions and are able to make sense of the defined outcomes to a reasonable degree.</li><li>At this point, the team/project defines how deep and long you go into the research.</li></ul><h3>8. Convey the findings</h3><blockquote>Research isn’t complete until it is conveyed</blockquote><ul><li>Don’t just send an email listing the insights, instead, gather the team and narrate a story about the user and the seven dwarfs.</li></ul><h3>Take it to the next level</h3><ul><li>Travel, understand different cultures, read books and let your mind open up to new possibilities.</li><li>Talk with different domains and teams, learn to speak their language.</li><li>Research takes time and patience, so do not give up if you get stuck.</li><li>Most importantly, teach what you learnt, so hire an intern, write an article, share what you know.</li></ul><p>To the beginners, what are you waiting for? Get started in user research.</p><p>To the pros, do let us know what you think in the comments below.</p><p><em>These learnings would not be possible without the help of </em><a href="https://medium.com/u/ea17deaeaa97"><em>@kingsidharth</em></a><em> who was my mentor all year.</em></p><p><em>Special thanks to Animesh, </em><a href="https://medium.com/u/73d6046bc359"><em>Rapti Gupta</em></a><em>, &amp; </em><a href="https://medium.com/u/a85536dbf98e"><em>Ruchita Lodha</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10edaa5ff5f7" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-self-taughts-guide-to-ux-research-10edaa5ff5f7">The self-taught’s guide to UX Research</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[Smart Links: invisible by design — a UX case study]]></title>
            <link>https://uxdesign.cc/smart-link-invisible-by-design-497a1365de7c?source=rss-c0795dab5d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/497a1365de7c</guid>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Mohamed Ansari]]></dc:creator>
            <pubDate>Tue, 15 Jan 2019 12:52:56 GMT</pubDate>
            <atom:updated>2019-08-24T10:39:59.635Z</atom:updated>
            <content:encoded><![CDATA[<h4>Achieving a non-disruptive user experience.</h4><p>Ask any seller on the <a href="https://www.instamojo.com/">Instamojo</a> platform what a “<a href="https://www.instamojo.com/smart-links/">Smart Link</a>” is; they won’t be able to describe it. But ask them how they collect payments on Instamojo and they will tell you about what we, at Instamojo, call “Smart Links.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AL0hq_ZYTgQtgyURsNX-gQ.png" /></figure><h4><strong>What is Instamojo?</strong></h4><p>Instamojo is an online platform that allows anyone on the internet to collect payments with a simple, shareable link. Sellers collect payments by sending a “<a href="https://www.instamojo.com/payment-links/">Payment Link</a>” to their customers.</p><p>Instamojo also offers a free <a href="https://www.instamojo.com/online-store/">Online Store</a> to sell products and offers simple payment <a href="https://www.instamojo.com/developers/">API integrations</a> for sellers with a website.</p><h4>What are Payment Links?</h4><p>Sellers can create <a href="https://www.instamojo.com/payment-links/">Payment Links</a> from the dashboard. It is a simple form where they input the “Purpose of Payment” and “Amount”. This Link is then shared with customers who make the payment using their choice of online payment options like credit card, debit card, net banking, UPI, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8lBSS5b-Pull5bBS4nAG-w.png" /><figcaption>Instamojo Payment Link</figcaption></figure><h4>Why Smart Links?</h4><p>A simple payment link was functional but our sellers wanted more. Especially, service sellers.</p><p>Service sellers were creating products on the Instamojo store and using it as a Payment Link. This was because Payment Links have limitations:</p><ul><li>The “Purpose of Payment” is just 30 characters long.</li><li>There is no way to describe the service or the product for which the payment is being made.</li><li>No option to add images.</li><li>The payment amount cannot be changed by the customer.</li></ul><p>This encouraged us to delve deeper.</p><h4>Talking to our Users (Sellers)</h4><p>We wanted to find out what was frustrating the users. What did they want? What did they need? Were they figuring out hacks to get around the limitations of the links?</p><p>It was not practical to gauge user behaviour without understanding how they exclusively used Instamojo payment links and product pages.</p><p>Just picking up the phone and calling them randomly didn’t work either. Their reply to our calls went something like…</p><blockquote>“Kaam ki baat bolo Sir, ye dhande ka time hai”.</blockquote><p>Getting the sellers to talk to us was a rather difficult task.</p><p>This prompted us to try a different approach. We sent them a survey with an option to leave their phone number. This worked well for us. <strong>We got more sellers to talk to us and for longer.</strong></p><p>Here is what we learned from talking to the Instamojo sellers:</p><ul><li><strong>Businesses want to give customers more information about the product/service they are selling.</strong></li></ul><blockquote>“I sell services by making products on the online store so that the customer can get more information about the service.” — Instamojo seller.</blockquote><blockquote>“My students want to see more information about the course they are paying for.” — Instamojo seller.</blockquote><blockquote>“I send a breakdown of the payment in an email and attach the Payment Link there.” — Instamojo seller.</blockquote><ul><li><strong>Businesses need to collect customer information.</strong></li></ul><blockquote>“Once the payment is made, customers send me their shipping address via SMS or Whatsapp.” — Instamojo seller.</blockquote><blockquote>“Customer sends me their GST information so that I can make the invoice for the payment.” — Instamojo seller.</blockquote><ul><li><strong>Businesses need more control over Payment Links.</strong></li></ul><blockquote>“I conduct workshops and have a fixed batch of students so I need to control the number of students paying on the Link.” — Instamojo seller.</blockquote><blockquote>“I need to sell early bird tickets, so I need to expire the Payment Link on a particular date.” — Instamojo seller.</blockquote><ul><li><strong>Businesses want to create an impression on their customers.</strong></li></ul><blockquote>“I want to make a good impression on my buyer by looking professional while collecting payments.” — Instamojo seller.</blockquote><blockquote>“I want the Payment Link to look more like my website.” — Instamojo seller.</blockquote><blockquote>“I want to customise branding on the payment link page because customers get confused with different branding and do not trust the payment method.” — Instamojo seller.</blockquote><ul><li><strong>Businesses want to let customers choose the payment amount.</strong></li></ul><blockquote>“Sometimes my customer wants to pay only a certain amount so I make a new Payment Link for them.” — Instamojo seller.</blockquote><blockquote>“I just use the Default Payment Link (link with editable amount) so that my customer can enter the amount they want to pay themselves.” — Instamojo seller.</blockquote><blockquote>“We use the Default Payment Link for donations but cannot set a minimum.” — Instamojo seller.</blockquote><h3>Interaction Design</h3><p>It was clear that there were a number of things the sellers were doing to get their work done. Even when regular payment links failed to meet their needs.</p><p>We decided to create a new “Smart Link” to cover the most common use-cases.</p><p>We could come up with several features but we didn’t want to overwhelm the seller. Therefore, we decided to prioritise.</p><p><strong>We divided the “Smart Link” into 3 steps:</strong></p><p><strong>Step 1:</strong></p><p>Features that have a bigger business impact took first priority.</p><p>For eg: A business runs the risk of overselling inventory without automatically expiring payment links.</p><p><strong>Step 2:</strong></p><p>Features like collecting additional customer data, changing the colours, were optional. It doesn’t have a drastic impact on the business itself and the sellers can choose to skip this step.</p><p><strong>Step 3:</strong></p><p>The third step would enable the sellers to use and send the Link on various online platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2vy0c9BL0xQN8E9_-J-xA.png" /></figure><p>We also renamed “Payment Links” to “Quick Links”. They were quicker to create than the Smart Links.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FlZMKkVUgc_A%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DlZMKkVUgc_A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FlZMKkVUgc_A%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/717affc442c506624f385fe806c1f226/href">https://medium.com/media/717affc442c506624f385fe806c1f226/href</a></iframe><h3>Validation and Insights</h3><p>Smart Links adoption was better than we expected. About <strong>10% of our active user base adopted Smart Links within 90 days from the launch.</strong></p><p>We decided to call up users who used Smart Links on a regular basis. Here is what they had to say:</p><blockquote>“It is nice to thank people after they make a donation.” — Instamojo seller.</blockquote><p>(<strong>42% of all Smart Links have a thank you note.)</strong></p><blockquote>“I have to give the details of the travel package to the customer so I use the Smart Link.” — Instamojo seller.</blockquote><p>(<strong>27.9% of Smart Links have a description.)</strong></p><blockquote>“I sell exclusive products so my offer is time-bound plus I can get the customer’s shipping address too.” — Instamojo seller.</blockquote><p><strong>(19.7% of all Smart Links collect Shipping address and 19.5% expire based on time.)</strong></p><blockquote>“I redirect my students to a registration form after they make the payment.” — Instamojo seller.</blockquote><p>(<strong>20.7% of Smart Links redirect the customer to a different page.)</strong></p><p>Even some API users started using Smart Links, although they can implement these features easily on their end.</p><p><strong>Here is what they had to say:</strong></p><blockquote>“I use Smart Links, my tech team uses the API.”</blockquote><blockquote>“I want to give loyal customers discounts, so I send them a Link.”</blockquote><blockquote>“Some customers find it difficult to pay on the website so I just send them a Link.”</blockquote><h3><strong>The icing on top?</strong></h3><p>Many users were not aware that they were using a “Smart Link”. <strong>To them, these features were obvious and the complexity behind them, invisible.</strong></p><p><em>Smart Link was built by these awesome people: </em><a href="https://medium.com/u/ea17deaeaa97"><em>@kingsidharth</em></a><em>, </em><a href="https://medium.com/u/2173a49b75e4"><em>Sreenath Kotteri</em></a><em>, </em><a href="https://medium.com/u/a85536dbf98e"><em>Ruchita Lodha</em></a><em> and Adesh.</em></p><p><em>Special thanks to </em><a href="https://medium.com/u/ea17deaeaa97"><em>@kingsidharth</em></a><em>, </em><a href="https://medium.com/u/b08a4d69b916"><em>Harshad Sharma</em></a><em>, </em><a href="https://medium.com/u/73d6046bc359"><em>Rapti Gupta</em></a><em>, </em><a href="https://medium.com/u/e1741a4c7899"><em>Mj</em></a><em> and </em><a href="https://medium.com/u/32099bd882bb"><em>Shivangi Kumar</em></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=497a1365de7c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/smart-link-invisible-by-design-497a1365de7c">Smart Links: invisible by design — a UX case study</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>
    </channel>
</rss>