<?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 Shalini Singh on Medium]]></title>
        <description><![CDATA[Stories by Shalini Singh on Medium]]></description>
        <link>https://medium.com/@shalinisingh_17477?source=rss-e0be3461a1f7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fRvZg5a0nKawLzeJLwFo2g.jpeg</url>
            <title>Stories by Shalini Singh on Medium</title>
            <link>https://medium.com/@shalinisingh_17477?source=rss-e0be3461a1f7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:59:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shalinisingh_17477/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[Why and How to Use AI in Your UI/UX Design Workflow]]></title>
            <link>https://medium.com/@shalinisingh_17477/why-and-how-to-use-ai-in-your-ui-ux-design-workflow-68534ba2e8d1?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/68534ba2e8d1</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 15:35:42 GMT</pubDate>
            <atom:updated>2026-10-26T15:35:42.154Z</atom:updated>
            <content:encoded><![CDATA[<p>AI is changing the way we design products. From generating ideas to creating prototypes, analysing research and exploring different design directions, there are so many ways AI can support our everyday work as UI/UX designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6W8RJXQKzCwSScMnpj0GDg.png" /></figure><p>But here’s something I believe: <strong>AI is not here to replace good designers. It’s here to help good designers work smarter.</strong></p><p>The real question is not whether we should use AI in design, but how we can use it without losing the most important part of our work — understanding people and solving their problems.</p><p>Let’s look at how we can make AI a useful part of our design workflow.</p><h3>1. Start with research, not assumptions</h3><p>One of the most important parts of UX design is understanding users. Traditionally, this involves interviews, surveys, usability testing and analysing user behaviour.</p><p>AI can help us make sense of the information we collect.</p><p>For example, if you have conducted 10 user interviews for a new mobile app, you can use AI to organise interview notes, identify recurring themes, summarise pain points and highlight possible opportunities.</p><p>You can also use it to:</p><ul><li>Group qualitative feedback into themes.</li><li>Identify patterns across survey responses.</li><li>Summarise customer reviews.</li><li>Generate follow-up questions for user interviews.</li><li>Turn research findings into draft personas or journey maps.</li></ul><p>However, there is one important thing to remember: <strong>AI can help analyse research, but it cannot replace actual user research.</strong></p><p>AI-generated personas based on assumptions are not the same as personas grounded in real user behaviour. Always validate the findings against your research data.</p><h3>2. Use AI to explore ideas, not just generate more ideas</h3><p>We have all experienced moments when we get stuck during brainstorming. Sometimes, we keep coming back to the same ideas because we are too close to the problem.</p><p>This is where AI can be helpful.</p><p>Once you have defined your problem statement, you can ask AI to explore different approaches, challenge your assumptions or suggest alternative solutions.</p><p>For example, imagine you are designing a photo-cleanup app. Users have thousands of photos on their phones and struggle to find duplicates or choose the best pictures.</p><p>Instead of immediately designing a dashboard, you could ask AI:</p><p><em>“Suggest five different ways to help users identify duplicate photos and free up storage. Consider users who are not comfortable with technology. Explain the advantages and disadvantages of each approach.”</em></p><p>This gives you different directions to explore before committing to one.</p><p>You can also use AI to challenge your ideas: What could confuse users? What happens when something goes wrong? Are there simpler ways to solve the problem?</p><p>The goal is not to accept every suggestion. It is to expand your thinking and make more informed design decisions.</p><h3>3. Speed up wireframing and prototyping</h3><p>AI-powered design tools can help transform ideas and written descriptions into initial layouts, interface concepts and prototypes.</p><p>This can be especially useful when you want to explore a few design directions before investing time in detailed UI design.</p><p>You can use AI to:</p><ul><li>Generate initial screen layouts.</li><li>Explore different navigation structures.</li><li>Create draft UI copy and microcopy.</li><li>Generate sample content and realistic dummy data.</li><li>Build simple interactive prototypes.</li><li>Explore alternative layouts for complex dashboards.</li></ul><p>For example, if you are designing a fintech dashboard, you could describe the users, their goals and the information they need to see. AI can help you explore possible layouts and information hierarchies.</p><p>But remember that a visually appealing screen is not necessarily a usable one.</p><p>You still need to consider information hierarchy, accessibility, consistency, user expectations and the context in which the product will be used.</p><p><strong>Use AI to accelerate exploration, but use design principles and user feedback to decide what works.</strong></p><h3>4. Make UX writing easier and more effective</h3><p>Writing is an important part of interface design, but it often receives less attention than visuals.</p><p>Error messages, onboarding instructions, empty states, button labels and confirmation messages all influence how users experience a product.</p><p>AI can help you write clearer, more consistent interface copy.</p><p>For example, instead of a generic error message such as “Something went wrong,” you could ask AI to suggest alternatives that explain the problem and guide the user towards a solution.</p><p>You can also use it to:</p><ul><li>Simplify complicated instructions.</li><li>Make copy more conversational.</li><li>Explore different tones of voice.</li><li>Write onboarding content.</li><li>Improve form validation messages.</li><li>Check copy for clarity and consistency.</li></ul><p>Always review the suggestions to ensure they are accurate, inclusive and appropriate for your product. A friendly tone is useful, but clarity should always come first.</p><h3>5. Use AI to improve accessibility</h3><p>Accessibility should be part of the design process from the beginning, not something we check just before launch.</p><p>AI can support accessibility reviews by helping identify potential issues in interface layouts, colour combinations, content and interaction patterns.</p><p>For example, you can use AI to review interface copy for readability, suggest descriptive alternative text for images, or identify potential accessibility concerns in a screen you are designing.</p><p>You can also use AI-assisted coding tools to explore accessible HTML structures and keyboard interactions.</p><p>However, AI cannot guarantee that a design is accessible. You should still use established accessibility guidelines, contrast checkers, automated testing tools, keyboard testing and assistive technologies where appropriate.</p><p>Think of AI as another layer of support, not a replacement for accessibility testing.</p><h3>6. Bring AI into design systems and documentation</h3><p>If you work on large products with multiple screens, components and teams, maintaining consistency can take a considerable amount of time.</p><p>AI can help you document components, draft usage guidelines, organise design feedback and identify inconsistencies across interface patterns.</p><p>For example, you could use AI to draft documentation for a button component, including its variants, states, usage rules and accessibility considerations.</p><p>You can also use AI coding assistants to explore how design tokens map to CSS variables or how reusable components might be implemented.</p><p>The important distinction is that AI can help create and maintain documentation, but your team still needs to establish the underlying design principles, component standards and governance process.</p><h3>7. Use AI to prepare for usability testing</h3><p>AI can help you prepare better usability tests by generating draft task scenarios, interview questions and testing scripts based on your research objectives.</p><p>After testing, it can help organise observations, summarise recurring issues and structure findings for stakeholders.</p><p>For example, if users struggle to complete a payment, AI can help you organise observations around navigation, form errors, trust and payment confirmation.</p><p>But be careful not to confuse observed behaviour with AI-generated explanations. If users abandon a payment, you should not assume why they did so without sufficient evidence.</p><p>Use AI to organise what you know, identify what you still need to learn and communicate findings more clearly.</p><h3>8. A practical AI-powered design workflow</h3><p>Here is how AI can fit into a typical UI/UX project without taking over the design process.</p><p>Design stageHow AI can helpWhat the designer ownsDiscoverySummarise feedback and organise research notesResearch quality and user understandingDefineExplore problem statements and identify assumptionsChoosing the right problem to solveIdeationGenerate alternative concepts and challenge ideasEvaluating ideas against user needsWireframingExplore layouts and information structuresInteraction design and usabilityUI designGenerate visual directions and draft contentVisual quality, consistency and accessibilityPrototypingSpeed up prototype creation and iterationValidating interactions and flowsTestingOrganise observations and identify patternsTesting with users and interpreting evidenceHandoffDraft specifications and documentationAccuracy and collaboration with developers</p><p>The best workflow combines AI’s speed with a designer’s judgement, empathy and understanding of context.</p><h3>9. Some AI tools worth exploring</h3><p>You do not need to learn every AI tool available. Start with a few that solve problems you encounter regularly.</p><ul><li><strong>ChatGPT:</strong> Research synthesis, brainstorming, UX writing, problem framing and critique.</li><li><strong>Figma AI:</strong> Exploring AI-assisted design workflows, content generation and design-file tasks, depending on the features available in your plan.</li><li><strong>v0:</strong> Exploring and generating interface concepts through code.</li><li><strong>Uizard:</strong> Rapidly exploring wireframes and interface concepts.</li><li><strong>Claude:</strong> Analysing long documents, structuring research findings and exploring design approaches.</li><li><strong>GitHub Copilot:</strong> Exploring code, understanding implementation and collaborating more effectively with developers.</li></ul><p>Tools evolve quickly, so focus on learning how to use AI effectively rather than becoming dependent on one particular platform.</p><p>Also, avoid uploading confidential research, customer information or proprietary product data to AI tools unless your organisation’s policies and the tool’s data-handling terms permit it.</p><h3>10. The biggest mistake designers can make with AI</h3><p>The biggest mistake is using AI simply because it is available.</p><p>Generating 20 screens in five minutes is not valuable if none of those screens solves the actual user problem.</p><p>Similarly, creating a polished interface without understanding the user journey, business constraints or technical limitations can lead to designs that look impressive in a portfolio but fail in the real world.</p><p>AI makes it easier to produce design outputs. It does not automatically make those outputs meaningful.</p><p>As designers, we need to move beyond asking, <em>“What can AI generate for me?”</em></p><p>Instead, we should ask:</p><ul><li>What part of my workflow takes too much time?</li><li>What repetitive tasks can I automate?</li><li>What alternative perspectives can AI help me explore?</li><li>How can I use AI to improve the quality of my decisions?</li><li>How will I validate the result?</li></ul><p>These questions lead to much more effective use of AI.</p><h3>Final thoughts</h3><p>I believe the future of UI/UX design will not be about choosing between human creativity and artificial intelligence. It will be about learning how to combine them effectively.</p><p>AI can help us research faster, explore more possibilities, write better content, prototype quickly and communicate ideas clearly.</p><p>But empathy, critical thinking, curiosity, ethical judgement and the ability to understand complex user problems remain essential design skills.</p><p><strong>My advice to fellow designers: Start small. Pick one repetitive task in your workflow and experiment with AI. Measure whether it saves time or improves your output. Then gradually expand its role.</strong></p><p>Don’t use AI just to say you are using AI.</p><p>Use it to become a better designer.</p><p>Because at the end of the day, our job is not to produce more screens. It is to create better experiences for people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68534ba2e8d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storyboards in UX]]></title>
            <link>https://medium.com/@shalinisingh_17477/storyboards-in-ux-d664f1a1d589?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d664f1a1d589</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[storyboard]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Thu, 17 Sep 2026 13:17:46 GMT</pubDate>
            <atom:updated>2026-09-17T13:17:46.797Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Tool Designers Often Underuse</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yIHq-7SZUw4J-L9B3NkwhA.png" /></figure><p><em>Before designing the interface, try designing the situation.</em></p><p>There is something interesting about UX design.</p><p>We spend a lot of time thinking about <strong>screens</strong>.</p><p>What should the user see?</p><p>Where should the button go?</p><p>How should the navigation work?</p><p>Should this be a modal or a separate page?</p><p>Should the card be horizontal or vertical?</p><p>All of these questions matter.</p><p>But sometimes we start asking them <strong>too early</strong>.</p><p>Because before someone interacts with our interface, they are already somewhere.</p><p>They might be:</p><ul><li>Standing in a crowded supermarket</li><li>Sitting in a hospital waiting room</li><li>Commuting to work</li><li>Trying to complete a task while their child is asking for attention</li><li>Sitting at a desk with three other applications open</li><li>Walking into a meeting</li><li>Trying to solve a problem under stress</li></ul><p>The interface is only one small part of that experience.</p><p><strong>This is where storyboards can be incredibly useful.</strong></p><p>Yet compared with personas, journey maps, wireframes and user flows, storyboards often receive much less attention in UX practice.</p><p>I think they’re underused.</p><h3>What is a storyboard in UX?</h3><p>A UX storyboard is a sequence of illustrations or frames that shows <strong>a person using a product or service within a particular context</strong>.</p><p>Think of it as a very simple comic strip.</p><p>For example:</p><p><strong>Frame 1:</strong> A customer realises they need to send money urgently.</p><p><strong>Frame 2:</strong> They pull out their phone while travelling.</p><p><strong>Frame 3:</strong> They open the banking app.</p><p><strong>Frame 4:</strong> They struggle to find the right recipient.</p><p><strong>Frame 5:</strong> They successfully complete the transfer.</p><p><strong>Frame 6:</strong> They receive confirmation and continue their journey.</p><p>Notice something important.</p><p>The storyboard isn’t primarily showing the UI.</p><p>It’s showing <strong>the person</strong>.</p><p>The product appears as part of their situation.</p><p>And that changes the questions we ask.</p><h3>Why do we need storyboards?</h3><p>Because users don’t experience products in a vacuum.</p><p>As designers, it’s very easy to think:</p><blockquote><em>User → Interface → Action</em></blockquote><p>Real life is more like:</p><blockquote><strong><em>Situation → Motivation → Context → Action → Interface → Reaction → Outcome</em></strong></blockquote><p>Imagine you’re designing a food delivery app.</p><p>You might think:</p><blockquote><em>“The user wants to order food.”</em></blockquote><p>That’s true.</p><p>But imagine the actual situation.</p><p>It’s 10:30 PM.</p><p>They’re tired.</p><p>They’ve had a long day.</p><p>Their phone battery is at 8%.</p><p>They’re hungry.</p><p>They don’t want to explore 50 restaurants.</p><p>They want to repeat an order they’ve made before.</p><p>Suddenly, the design problem looks different.</p><p>The opportunity may not be:</p><blockquote><em>“How can we improve restaurant discovery?”</em></blockquote><p>It might be:</p><blockquote><strong><em>“How can we help someone reorder familiar food with minimal cognitive effort?”</em></strong></blockquote><p>The storyboard helped expose the context.</p><h3>Storyboards help us design for situations, not ideal users</h3><p>Personas can tell us who the user is.</p><p>Journey maps can show us what happens across an experience.</p><p>User stories can describe what the user wants to accomplish.</p><p>But a storyboard can answer a different question:</p><blockquote><strong><em>“What is actually happening around this interaction?”</em></strong></blockquote><p>And that context can dramatically affect behaviour.</p><p>Consider two users performing exactly the same task.</p><h3>User A</h3><p>Sitting at home.</p><p>Laptop open.</p><p>Coffee beside them.</p><p>Lots of time.</p><h3>User B</h3><p>Standing at an airport.</p><p>Using a phone.</p><p>Poor connectivity.</p><p>Boarding announcement happening in the background.</p><p>Same goal.</p><p>Completely different context.</p><p>If we only design around the task, we may miss the difference.</p><h3>When should you use a storyboard?</h3><p>You don’t need to storyboard every feature.</p><p>That would quickly become unnecessary work.</p><p>I find storyboards particularly useful in a few situations.</p><h3>1. When context is important</h3><p>Some products are used in very specific environments.</p><p>Think about:</p><ul><li>Healthcare</li><li>Automotive</li><li>Retail</li><li>Travel</li><li>Industrial environments</li><li>Education</li><li>Field services</li><li>Smart-home products</li><li>Wearables</li></ul><p>Imagine designing software for a factory worker.</p><p>They’re not sitting at a desk with a mouse and keyboard.</p><p>They might be:</p><ul><li>Wearing protective equipment</li><li>Working around machinery</li><li>Looking at a large screen from several metres away</li><li>Under time pressure</li><li>Working with other people nearby</li></ul><p>A storyboard can reveal these constraints before you start designing the interface.</p><h3>2. When you’re designing a new product</h3><p>Storyboards are particularly useful during early discovery.</p><p>Suppose someone says:</p><blockquote><em>“We should build an app that helps people manage their household waste.”</em></blockquote><p>Before designing the app, ask:</p><p><strong>When does the problem occur?</strong></p><p>Imagine the story:</p><p><strong>Kitchen → Waste is produced → User isn’t sure which bin to use → Searches for information → Finds conflicting advice → Gives up → Waste goes into the wrong bin</strong></p><p>Now you have a much richer understanding of the problem.</p><p>You might discover that the opportunity isn’t simply “build a waste-management app.”</p><p>Maybe the real opportunity is:</p><blockquote><strong><em>Help people make the correct disposal decision at the moment they are holding an item.</em></strong></blockquote><p>That could lead to a completely different product experience.</p><h3>3. When you need to communicate a problem to stakeholders</h3><p>This is one of the most underrated uses of storyboards.</p><p>Sometimes research findings are difficult to communicate.</p><p>You might say:</p><blockquote><em>“Users experience friction during the transition between online application and offline verification.”</em></blockquote><p>Everyone nods.</p><p>But does everyone actually understand the experience?</p><p>Now imagine showing six frames:</p><p><strong>Customer completes online application → receives an email → doesn’t understand what document is required → calls support → waits → visits a branch</strong></p><p>Suddenly the problem becomes tangible.</p><p>Storyboards turn an abstract problem into a <strong>human story</strong>.</p><p>And humans are generally much better at understanding stories than lists of requirements.</p><h3>4. When you’re designing an end-to-end service</h3><p>Storyboards are particularly powerful for service design.</p><p>Consider a healthcare journey.</p><p>A patient:</p><ol><li>Realises they need medical help.</li><li>Searches for a doctor.</li><li>Books an appointment.</li><li>Travels to the clinic.</li><li>Checks in.</li><li>Meets the doctor.</li><li>Gets a prescription.</li><li>Collects medication.</li><li>Receives a follow-up message.</li></ol><p>There are many touchpoints.</p><p>Some are digital.</p><p>Some are physical.</p><p>Some involve people.</p><p>Some involve systems.</p><p>A storyboard allows you to show the <strong>whole experience as something a human being actually goes through</strong>.</p><h3>5. When you’re designing for unusual or high-stress situations</h3><p>This is where storyboards can become especially valuable.</p><p>Think about:</p><ul><li>Emergency services</li><li>Healthcare</li><li>Financial decisions</li><li>Security</li><li>Travel disruptions</li><li>Customer support</li><li>Workplace incidents</li></ul><p>In these situations, users may not behave like the calm, rational people we imagine in a usability lab.</p><p>They may be:</p><p><strong>Stressed.<br>Distracted.<br>Confused.<br>In a hurry.<br>Scared.<br>Overloaded.</strong></p><p>A storyboard can help the team ask:</p><blockquote><em>“What does this experience feel like from the user’s perspective?”</em></blockquote><p>That question can lead to very different design decisions.</p><h3>The difference between a storyboard and a journey map</h3><p>These two are often confused.</p><p>They’re related, but they do different jobs.</p><h3>Journey map</h3><p>Shows the <strong>experience across stages</strong>.</p><p>It might contain:</p><p><strong>Stages → Actions → Thoughts → Emotions → Pain points → Opportunities</strong></p><h3>Storyboard</h3><p>Shows the <strong>experience as a sequence of moments</strong>.</p><p>It might show:</p><p><strong>Situation → Action → Reaction → Interaction → Outcome</strong></p><p>Here’s an easy mental model:</p><p><strong>Journey map = zoomed-out experience</strong></p><p><strong>Storyboard = zoomed-in human story</strong></p><p>You can actually use them together.</p><p>A journey map might reveal:</p><blockquote><em>“Users become frustrated during the waiting period.”</em></blockquote><p>Then a storyboard can explore what that actually looks like.</p><h3>Storyboard vs user flow</h3><p>There’s another important distinction.</p><p>A user flow looks something like:</p><p><strong>Login → Dashboard → Search → Select → Confirm → Success</strong></p><p>It’s focused on the product interaction.</p><p>A storyboard might show:</p><p><strong>User receives a request while commuting → opens phone → logs in → searches → gets interrupted → returns to the task → completes it → continues travelling</strong></p><p>The flow tells us:</p><blockquote><strong><em>What happens in the interface?</em></strong></blockquote><p>The storyboard tells us:</p><blockquote><strong><em>What happens to the person?</em></strong></blockquote><p>Both can be useful.</p><h3>You don’t need to be good at drawing</h3><p>This is probably one of the biggest reasons designers avoid storyboards.</p><p>They think:</p><blockquote><em>“I’m not an illustrator.”</em></blockquote><p>Good.</p><p>You don’t need to be.</p><p>A storyboard is not an art competition.</p><p>Stick figures are enough.</p><p>Simple shapes are enough.</p><p>You can use:</p><ul><li>Sketches</li><li>Simple illustrations</li><li>Figma shapes</li><li>Icons</li><li>Photos</li><li>Existing design assets</li><li>AI-generated visuals</li><li>Even screenshots combined with annotations</li></ul><p>The goal is <strong>clarity</strong>, not artistic quality.</p><p>If a stick figure communicates the situation better than a beautifully rendered illustration, use the stick figure.</p><h3>How to create a UX storyboard</h3><p>Here’s a simple process.</p><h3>Step 1: Define the scenario</h3><p>Don’t start drawing immediately.</p><p>First write one sentence:</p><blockquote><em>“A customer is trying to change their delivery address after placing an order.”</em></blockquote><p>That’s your scenario.</p><h3>Step 2: Identify the trigger</h3><p>What causes the journey to begin?</p><p>For example:</p><blockquote><em>Customer realises they’ll be away from home when the order arrives.</em></blockquote><p>This gives your storyboard a starting point.</p><h3>Step 3: Identify the user’s goal</h3><p>What are they trying to accomplish?</p><blockquote><em>Change the delivery address.</em></blockquote><h3>Step 4: Identify the context</h3><p>Where are they?</p><p>What device are they using?</p><p>Who is around them?</p><p>What constraints exist?</p><p>For example:</p><blockquote><em>At work, using a mobile phone between meetings.</em></blockquote><h3>Step 5: Identify the key moments</h3><p>You don’t need 30 frames.</p><p>Usually, a handful of meaningful moments is enough.</p><p>For example:</p><p><strong>1. Realisation</strong></p><p>“I won’t be home.”</p><p>↓</p><p><strong>2. Search for solution</strong></p><p>Opens the app.</p><p>↓</p><p><strong>3. Friction</strong></p><p>Can’t find where to change the address.</p><p>↓</p><p><strong>4. Resolution</strong></p><p>Finds the option and updates it.</p><p>↓</p><p><strong>5. Confirmation</strong></p><p>Receives reassurance that the change worked.</p><h3>Step 6: Draw the story</h3><p>Now turn those moments into visuals.</p><p>Keep each frame simple.</p><p>Ask:</p><blockquote><strong><em>If I removed all the words, would I still understand what’s happening?</em></strong></blockquote><p>If yes, you’re probably on the right track.</p><h3>A useful storyboard template</h3><p>You can use a simple six-frame structure:</p><p>FrameQuestion1What triggers the need?2What is the user trying to accomplish?3What do they do first?4Where does friction appear?5How do they overcome it?6What is the final outcome?</p><p>You can then add a small annotation below each frame:</p><p><strong>Context</strong><br><strong>Action</strong><br><strong>Thought</strong><br><strong>Emotion</strong></p><p>Don’t overfill the frames.</p><h3>The most important frame might be before the product appears</h3><p>This is something I particularly like about storyboards.</p><p>Designers often start with:</p><blockquote><em>“The user opens the app.”</em></blockquote><p>But why did they open it?</p><p>Something happened before that.</p><p>Maybe:</p><blockquote><em>They received a message.</em></blockquote><p>Maybe:</p><blockquote><em>Their washing machine stopped working.</em></blockquote><p>Maybe:</p><blockquote><em>They realised their medication was running out.</em></blockquote><p>Maybe:</p><blockquote><em>Their manager asked for a report.</em></blockquote><p>That moment is important.</p><p>It tells us <strong>what triggered the interaction</strong>.</p><p>And understanding the trigger can lead to better product opportunities.</p><h3>What if the best solution isn’t an app?</h3><p>This is where storyboarding gets really interesting.</p><p>Imagine your storyboard starts with:</p><p><strong>User notices a problem → looks for help → opens app → searches → finds information → solves problem</strong></p><p>Now ask:</p><blockquote><strong><em>Does the user actually need an app?</em></strong></blockquote><p>Maybe the best solution is:</p><ul><li>A notification</li><li>A wearable interaction</li><li>A physical sign</li><li>A voice assistant</li><li>An automated message</li><li>A service intervention</li><li>A better process</li></ul><p>Storyboarding can help prevent us from assuming that <strong>the solution must be another screen</strong>.</p><h3>Storyboarding is also a way of challenging assumptions</h3><p>Here’s a useful exercise.</p><p>Create two storyboards.</p><h3>Storyboard A: What we think happens</h3><p>This is the team’s current assumption.</p><h3>Storyboard B: What research tells us happens</h3><p>This is based on actual user behaviour.</p><p>Then compare them.</p><p>The differences can be incredibly revealing.</p><p>Perhaps the team assumes:</p><blockquote><em>User discovers → searches → purchases.</em></blockquote><p>But research shows:</p><blockquote><em>User hears about product from friend → searches reviews → leaves → asks someone → returns → compares alternatives → purchases.</em></blockquote><p>That gap is a design insight.</p><h3>Common mistakes when creating storyboards</h3><h3>Mistake 1: Making it a comic about the interface</h3><p>If every frame is a screenshot of your app, you’ve probably created a prototype presentation rather than a storyboard.</p><p>Show the <strong>person and context</strong>.</p><h3>Mistake 2: Showing only the happy path</h3><p>Real experiences aren’t always smooth.</p><p>Show:</p><p><strong>confusion</strong></p><p><strong>interruption</strong></p><p><strong>failure</strong></p><p><strong>recovery</strong></p><p>These moments often contain the best design opportunities.</p><h3>Mistake 3: Making it too detailed</h3><p>A storyboard isn’t a screenplay.</p><p>You don’t need every click.</p><p>Focus on meaningful moments.</p><h3>Mistake 4: Inventing user behaviour</h3><p>A beautiful storyboard can still be based on assumptions.</p><p>If you’re using it to represent an existing experience, ground it in research.</p><p>Ask:</p><blockquote><em>“Do we actually know this happens?”</em></blockquote><p>If not, label it as a hypothesis.</p><h3>Storyboards can change the question you’re solving</h3><p>And this is why I think designers should use them more often.</p><p>You may begin with:</p><blockquote><strong><em>“How do we make this form easier to complete?”</em></strong></blockquote><p>After storyboarding the experience, you might realise:</p><blockquote><strong><em>“Why does the user have to complete this form at all?”</em></strong></blockquote><p>That’s a much more interesting question.</p><p>You may begin with:</p><blockquote><em>“How can we improve search?”</em></blockquote><p>And discover:</p><blockquote><em>“Users don’t want better search. They want faster reassurance that they’ve chosen the right thing.”</em></blockquote><p>Or:</p><blockquote><em>“The problem isn’t finding information. It’s knowing whether the information can be trusted.”</em></blockquote><p>The storyboard creates enough distance from the interface to let you see the <strong>real problem</strong>.</p><h3>A simple rule I use</h3><p>Before opening Figma, ask:</p><blockquote><strong><em>“Can I tell the story of this problem without drawing the interface?”</em></strong></blockquote><p>If you can, try storyboarding it.</p><p>If you can’t, you may not understand the problem well enough yet.</p><p>And if the story is interesting even without the interface, you’ve probably found something worth exploring.</p><h3>Final thought</h3><p>UX design isn’t really about designing screens.</p><p>It’s about designing <strong>experiences that happen to include screens</strong>.</p><p>A storyboard reminds us of that.</p><p>It puts the person back into the centre of the problem.</p><p>It reminds us that users have environments, emotions, interruptions, motivations, constraints and expectations.</p><p>And sometimes the most important part of the experience happens <strong>before they ever open our product</strong>.</p><p>So the next time you receive a requirement that says:</p><blockquote><em>“We need a new feature.”</em></blockquote><p>Don’t immediately open your design tool.</p><p>Instead, ask:</p><p><strong>Who needs it?</strong></p><p><strong>What happened before they needed it?</strong></p><p><strong>What are they trying to accomplish?</strong></p><p><strong>Where are they?</strong></p><p><strong>What else is competing for their attention?</strong></p><p><strong>What happens after they use it?</strong></p><p>Then draw the story.</p><p>You might discover that the feature you were asked to design…</p><p><strong>isn’t actually the problem worth solving.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d664f1a1d589" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Should You Create a Journey Map?]]></title>
            <link>https://medium.com/@shalinisingh_17477/when-should-you-create-a-journey-map-bd548ce56cff?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd548ce56cff</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-journey-mapping]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Fri, 11 Sep 2026 10:25:06 GMT</pubDate>
            <atom:updated>2026-09-11T10:25:06.712Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Journey mapping isn’t about making another pretty UX artefact. It’s about seeing the experience that your product screens can’t show you.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c9FZulPd6cB2_yBSbSydwg.png" /></figure><p>There are certain UX artefacts that have become almost synonymous with the design process.</p><p>Personas.<br>User stories.<br>User flows.<br>Wireframes.<br>Journey maps.</p><p>And because journey mapping is so widely used, it’s easy to fall into a familiar trap:</p><p><strong>“We need a journey map because we’re doing UX.”</strong></p><p>I think that’s the wrong reason.</p><p>A journey map is valuable when it helps you see something that you <strong>cannot see by looking at a single screen or interaction</strong>.</p><p>It helps you step back.</p><p>Instead of asking:</p><blockquote><em>“How do we improve this screen?”</em></blockquote><p>you start asking:</p><blockquote><strong><em>“What is the user’s experience before, during and after this interaction?”</em></strong></blockquote><p>That shift can completely change what you design.</p><h3>What is a journey map?</h3><p>At its simplest, a journey map is a visual representation of the steps a person goes through while trying to accomplish a goal.</p><p>For example, imagine someone applying for a home loan.</p><p>Their journey might look something like:</p><p><strong>Realise they need a loan → Research options → Compare lenders → Calculate affordability → Apply → Submit documents → Wait → Receive decision → Accept offer → Start repayment</strong></p><p>The interesting part isn’t simply the list of steps.</p><p>A good journey map can also reveal:</p><ul><li>What the user is trying to accomplish</li><li>What they are thinking</li><li>How they feel</li><li>Where they encounter friction</li><li>Which channels they use</li><li>Which people or systems they interact with</li><li>Where opportunities exist</li></ul><p>Suddenly, the experience becomes much bigger than an application form.</p><h3>The first question: Is the problem bigger than a screen?</h3><p>This is probably my favourite test for deciding whether I need a journey map.</p><p>Ask:</p><blockquote><strong><em>“Can I understand this problem by looking at one interaction?”</em></strong></blockquote><p>If yes, you might need a user flow, usability test, or interaction design exercise.</p><p>If no, a journey map might be useful.</p><p>For example:</p><h3>Problem A</h3><blockquote><em>Users don’t understand what the “Submit” button does.</em></blockquote><p>That’s probably not a journey-mapping problem.</p><p>You might investigate:</p><ul><li>Content</li><li>Interaction design</li><li>Information hierarchy</li><li>Usability</li></ul><h3>Problem B</h3><blockquote><em>Customers start an application online, receive emails, upload documents through another system, speak to a support agent and then return to the original application.</em></blockquote><p>Now we’re dealing with a journey.</p><p>The problem isn’t necessarily one screen.</p><p>It’s the <strong>relationship between multiple interactions</strong>.</p><p>That’s where journey mapping becomes powerful.</p><h3>1. Create a journey map when the experience crosses multiple touchpoints</h3><p>Modern products rarely exist in isolation.</p><p>A customer might interact with a company through:</p><p><strong>Website → Mobile app → Email → Phone call → Physical store → Support → App</strong></p><p>Each individual interaction might work reasonably well.</p><p>Yet the overall experience can still feel terrible.</p><p>Why?</p><p>Because the customer doesn’t experience these touchpoints as separate teams or departments.</p><p><strong>They experience one journey.</strong></p><p>Imagine ordering a new internet connection.</p><p>You:</p><ol><li>Search for plans online.</li><li>Purchase one.</li><li>Receive an installation email.</li><li>Get a message from the technician.</li><li>Wait for installation.</li><li>Discover there’s a problem.</li><li>Contact support.</li><li>Explain the issue again.</li><li>Wait for another appointment.</li></ol><p>If you only redesign the website, you’re missing most of the experience.</p><p>A journey map makes those connections visible.</p><h3>2. Create one when different teams own different parts of the experience</h3><p>This is one of the most useful applications of journey mapping.</p><p>Imagine a healthcare service.</p><p>The patient’s experience might involve:</p><p><strong>Marketing → Booking → Reception → Doctor → Lab → Pharmacy → Follow-up</strong></p><p>Different teams may own each stage.</p><p>And that’s exactly the problem.</p><p>Every team may optimise its own part of the experience.</p><p>The booking team might say:</p><blockquote><em>“Our booking completion rate is excellent.”</em></blockquote><p>The clinic might say:</p><blockquote><em>“Our consultations are running efficiently.”</em></blockquote><p>The pharmacy might say:</p><blockquote><em>“Orders are being processed quickly.”</em></blockquote><p>But the patient might still feel:</p><blockquote><strong><em>“This whole experience is exhausting.”</em></strong></blockquote><p>A journey map puts all those pieces on the same canvas.</p><p>Suddenly, the team can see the experience from the <strong>user’s perspective rather than the organisation’s structure</strong>.</p><h3>3. Create one when you don’t know where the real problem is</h3><p>Sometimes the problem statement is too vague.</p><p>For example:</p><blockquote><em>“Customers are unhappy with our service.”</em></blockquote><p>That’s not particularly useful.</p><p>Where exactly are they unhappy?</p><p>Before purchase?</p><p>During onboarding?</p><p>When something goes wrong?</p><p>When contacting support?</p><p>After the purchase?</p><p>A journey map can help break down that vague problem.</p><p>You might discover that:</p><p><strong>Discovery:</strong> 😊<br>Easy to understand</p><p><strong>Purchase:</strong> 😊<br>Simple checkout</p><p><strong>Onboarding:</strong> 😐<br>Too many forms</p><p><strong>First use:</strong> 😟<br>User doesn’t know what to do</p><p><strong>Support:</strong> 😡<br>Has to repeat information</p><p>Suddenly, “customers are unhappy” becomes a much more actionable problem.</p><p>You can now ask:</p><blockquote><strong><em>Where is the biggest experience gap?</em></strong></blockquote><p>That’s a much better design question.</p><h3>4. Create one when the user’s experience happens over time</h3><p>Some experiences are not a single interaction.</p><p>They unfold over hours, days, weeks or even years.</p><p>Think about:</p><ul><li>Buying a car</li><li>Managing a chronic condition</li><li>Learning a new skill</li><li>Applying for a university</li><li>Finding a job</li><li>Moving to a new city</li><li>Getting a mortgage</li><li>Starting a new job</li></ul><p>In these experiences, <strong>time matters</strong>.</p><p>A user might feel excited at the beginning.</p><p>Then confused.</p><p>Then anxious.</p><p>Then relieved.</p><p>Then frustrated.</p><p>Then satisfied.</p><p>A single user flow cannot capture that emotional progression.</p><p>A journey map can.</p><h3>5. Create one when emotions influence behaviour</h3><p>Users don’t make decisions based purely on functionality.</p><p>Emotion matters.</p><p>Consider an online banking experience.</p><p>A user transferring ₹50,000 isn’t simply moving money from A to B.</p><p>They might be thinking:</p><blockquote><em>“Did I enter the correct account number?”</em></blockquote><blockquote><em>“Has the money actually gone through?”</em></blockquote><blockquote><em>“What if something goes wrong?”</em></blockquote><p>The functional journey might be:</p><p><strong>Enter details → Review → Authenticate → Submit → Confirmation</strong></p><p>But the emotional journey could be:</p><p><strong>Confidence → Uncertainty → Anxiety → Relief</strong></p><p>That emotional layer can reveal opportunities.</p><p>Perhaps the problem isn’t that the transfer takes too many steps.</p><p>Perhaps users simply don’t receive enough reassurance during the process.</p><p>That’s a very different design problem.</p><h3>6. Create one when you’re redesigning an existing experience</h3><p>Journey maps are especially useful before a major redesign.</p><p>Imagine you’re redesigning an existing product.</p><p>The obvious approach might be:</p><blockquote><em>“Let’s look at the current screens and improve them.”</em></blockquote><p>But this can lead to <strong>screen-by-screen optimisation</strong>.</p><p>Instead, step back first.</p><p>Map the existing experience.</p><p>Ask:</p><ul><li>What triggers the user to start?</li><li>What happens before they reach our product?</li><li>What happens inside it?</li><li>What happens afterwards?</li><li>Where do they leave?</li><li>Where do they switch channels?</li><li>Where do they ask for help?</li><li>Where do they experience frustration?</li></ul><p>You may discover that the biggest opportunity isn’t actually inside the product.</p><p>That’s a valuable insight.</p><h3>7. Create one when you’re entering a new domain</h3><p>Journey mapping is also an excellent learning tool.</p><p>Suppose you’re designing for a domain you don’t know well.</p><p>Maybe:</p><ul><li>Insurance</li><li>Healthcare</li><li>Fintech</li><li>Logistics</li><li>Waste management</li><li>Legal services</li></ul><p>You may understand the interface.</p><p>But you don’t necessarily understand the ecosystem.</p><p>A journey map forces you to ask:</p><p><strong>What happens before this?</strong></p><p><strong>What happens after this?</strong></p><p><strong>Who else is involved?</strong></p><p><strong>What systems are connected?</strong></p><p><strong>What happens when something goes wrong?</strong></p><p><strong>What does the user have to do outside our product?</strong></p><p>This is where journey mapping becomes more than a design artefact.</p><p>It becomes a <strong>research and learning tool</strong>.</p><h3>What should a journey map actually contain?</h3><p>There isn’t one universal format.</p><p>That’s another thing I think designers sometimes overcomplicate.</p><p>Start with the basics.</p><h3>1. Persona or user</h3><p>Who are we mapping?</p><p>Don’t try to represent everyone.</p><p>A journey map should usually represent a <strong>specific user type and goal</strong>.</p><h3>2. Scenario</h3><p>What is the situation?</p><p>For example:</p><blockquote><em>“A first-time investor is trying to invest ₹10,000 through a mobile investment platform.”</em></blockquote><p>The scenario gives the map context.</p><h3>3. Stages</h3><p>What are the major phases?</p><p>For example:</p><p><strong>Discover → Evaluate → Invest → Monitor → Withdraw</strong></p><h3>4. Actions</h3><p>What is the user actually doing?</p><h3>5. Thoughts and questions</h3><p>What are they thinking?</p><h3>6. Emotions</h3><p>How are they feeling?</p><h3>7. Pain points</h3><p>Where does the experience break down?</p><h3>8. Opportunities</h3><p>Where could the organisation improve the experience?</p><p>You don’t always need all eight.</p><p><strong>The map should serve the question you’re trying to answer.</strong></p><h3>Don’t make the journey map too detailed</h3><p>This is where journey maps can go wrong.</p><p>You can spend days creating a huge map containing:</p><ul><li>47 touchpoints</li><li>12 personas</li><li>30 emotional states</li><li>18 departments</li><li>63 pain points</li><li>dozens of sticky notes</li></ul><p>And end up with something nobody uses.</p><p>More information doesn’t automatically create more insight.</p><p>I prefer starting small.</p><p>Ask:</p><blockquote><strong><em>What decision are we trying to make with this map?</em></strong></blockquote><p>Then include only the information that helps answer that question.</p><h3>Journey maps aren’t just workshops with sticky notes</h3><p>There’s another misconception worth challenging.</p><p>A journey map doesn’t have to begin with:</p><p><strong>“Let’s get everyone in a room and put sticky notes on a wall.”</strong></p><p>The workshop can be useful.</p><p>But the evidence should come from somewhere.</p><p>Good journey maps can incorporate:</p><ul><li>User interviews</li><li>Usability testing</li><li>Analytics</li><li>Customer-support conversations</li><li>Surveys</li><li>Reviews</li><li>CRM data</li><li>Observational research</li><li>Existing business knowledge</li></ul><p>The map is a <strong>representation of the evidence</strong>, not the evidence itself.</p><p>And that’s an important distinction.</p><h3>What happens after the journey map?</h3><p>This is where the real value begins.</p><p>A journey map shouldn’t simply sit in a presentation deck.</p><p>Use it to identify opportunities.</p><p>For example:</p><p><strong>Pain point</strong></p><blockquote><em>Users don’t know whether their documents have been successfully submitted.</em></blockquote><p>↓</p><p><strong>Opportunity</strong></p><blockquote><em>Provide clear document-status feedback.</em></blockquote><p>↓</p><p><strong>Design exploration</strong></p><blockquote><em>Status tracker / confirmation / notifications / dashboard</em></blockquote><p>↓</p><p><strong>Prototype</strong></p><p>↓</p><p><strong>Usability testing</strong></p><p>↓</p><p><strong>Measure the outcome</strong></p><p>Now the journey map has become part of the product-development process.</p><h3>Journey map or user flow?</h3><p>Here’s a simple way to think about it.</p><h3>Journey map</h3><p><strong>What is the overall experience?</strong></p><p>It can span:</p><ul><li>Time</li><li>Channels</li><li>People</li><li>Emotions</li><li>Organisations</li><li>Systems</li></ul><h3>User flow</h3><p><strong>How does the user move through the product?</strong></p><p>It focuses more closely on:</p><ul><li>Screens</li><li>Decisions</li><li>Actions</li><li>Navigation</li><li>States</li></ul><p>You might actually use both.</p><p>The journey map could reveal:</p><blockquote><em>“Users become anxious while waiting for their application.”</em></blockquote><p>Then the user flow could help you design:</p><p><strong>Application → Status → Progress information → Expected timeline → Notifications</strong></p><p>One helps you understand the <strong>experience</strong>.</p><p>The other helps you design the <strong>interaction</strong>.</p><h3>The biggest mistake: mapping the product instead of the journey</h3><p>This is probably the most common problem I see.</p><p>A team creates:</p><p><strong>Homepage → Search → Product page → Checkout → Confirmation</strong></p><p>And calls it a journey map.</p><p>That’s really a product flow.</p><p>A journey map asks a bigger question:</p><blockquote><strong><em>What is the person trying to accomplish, from their perspective?</em></strong></blockquote><p>For example:</p><p><strong>Realise a need → Search for information → Compare options → Build confidence → Make a decision → Complete purchase → Wait → Receive product → Start using it → Need help</strong></p><p>Now we’re mapping the journey.</p><p>The product is only one part of it.</p><h3>A simple test before you create one</h3><p>Before opening Figma, Miro or FigJam, ask these five questions:</p><h3>1. Is there a meaningful user goal?</h3><p>If you can’t define the goal, you’re probably not ready.</p><h3>2. Does the experience have multiple stages?</h3><p>If everything happens in one simple interaction, another UX tool may be more appropriate.</p><h3>3. Are multiple touchpoints or channels involved?</h3><p>If yes, journey mapping becomes more valuable.</p><h3>4. Do we need to understand emotions, pain points or context?</h3><p>If yes, a journey map can help.</p><h3>5. Will the map change a decision?</h3><p>This is the most important question.</p><p>If the answer is <strong>no</strong>, don’t create it just because it’s part of the UX toolkit.</p><h3>The journey map is not the deliverable</h3><p>This is perhaps the biggest lesson I’ve learned.</p><p>The map itself isn’t the outcome.</p><p><strong>The insight is the outcome.</strong></p><p>And the insight should lead to a decision.</p><p>For example:</p><blockquote><em>“The biggest problem isn’t the application form. It’s the uncertainty users experience after submitting it.”</em></blockquote><p>That’s useful.</p><p>Or:</p><blockquote><em>“Customers aren’t struggling with the app itself. They’re switching to email because the information they need isn’t available inside the product.”</em></blockquote><p>That’s useful.</p><p>Or:</p><blockquote><em>“Three different teams are solving the same problem independently.”</em></blockquote><p>That’s useful.</p><p>The map simply helped us <strong>see it</strong>.</p><h3>Final thought</h3><p>UX tools aren’t a checklist.</p><p>You don’t need a persona because it’s Monday.</p><p>You don’t need a journey map because the project plan says “UX phase.”</p><p>And you don’t need a storyboard because someone has added it to a template.</p><p>The best designers aren’t necessarily the ones who create the most artefacts.</p><p>They’re the ones who know <strong>which artefact will help the team understand the problem better</strong>.</p><p>So before creating your next journey map, don’t ask:</p><blockquote><strong><em>“How do I create a journey map?”</em></strong></blockquote><p>Ask:</p><blockquote><strong><em>“What am I trying to understand that I can’t see from a single interaction?”</em></strong></blockquote><p>If the answer involves <strong>time, context, emotions, multiple touchpoints, or the wider ecosystem</strong>, you may have just found a good reason to create one.</p><p>And that’s when a journey map stops being a pretty diagram —</p><p><strong>and starts becoming a design tool.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd548ce56cff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When and How to Use User Stories in UX Design]]></title>
            <link>https://medium.com/@shalinisingh_17477/when-and-how-to-use-user-stories-in-ux-design-08b5e49155e0?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/08b5e49155e0</guid>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 12:13:01 GMT</pubDate>
            <atom:updated>2026-09-10T12:13:01.062Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Not every UX problem needs a user story. Here’s how to know when to use one — and how to write it well.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nH2M--IZS-fGaVSv_KxRsg.png" /></figure><p>One of the first things we learn in UX is how to understand the user.</p><p>We conduct interviews.<br>We observe behaviour.<br>We analyse data.<br>We create personas.<br>We map journeys.</p><p>And somewhere along the way, we start writing <strong>user stories</strong>.</p><blockquote><em>“As a user, I want to save my favourite products so that I can find them later.”</em></blockquote><p>Simple enough.</p><p>But here’s the question I’ve found more interesting over the years:</p><p><strong>When should we actually use a user story?</strong></p><p>Because a user story isn’t simply another UX deliverable to add to your process. Used well, it can help a team move from <strong>what a user is trying to accomplish</strong> to <strong>what the product needs to enable</strong>.</p><p>Used badly, it can become a box-ticking exercise.</p><p>Let’s unpack it.</p><h3>What exactly is a user story?</h3><p>A user story is a short statement describing something a user wants to accomplish and the value they expect from it.</p><p>The most common format is:</p><blockquote><strong><em>As a [type of user], I want to [action], so that [benefit].</em></strong></blockquote><p>For example:</p><blockquote><strong><em>As a first-time investor, I want to understand the risk of an investment, so that I can decide whether it is right for me.</em></strong></blockquote><p>Notice what this tells us.</p><p>It tells us:</p><ul><li><strong>Who</strong> we’re designing for</li><li><strong>What</strong> they want to do</li><li><strong>Why</strong> they want to do it</li></ul><p>But it deliberately doesn’t tell us <strong>how</strong> to solve the problem.</p><p>That’s important.</p><p>A user story shouldn’t say:</p><blockquote><em>“As an investor, I want a risk score displayed as a coloured badge.”</em></blockquote><p>That’s already a solution.</p><p>Instead:</p><blockquote><em>“As an investor, I want to understand the risk of an investment, so that I can make an informed decision.”</em></blockquote><p>Now the design team can explore multiple solutions.</p><p>Maybe it’s a risk score.</p><p>Maybe it’s a visual indicator.</p><p>Maybe it’s a comparison.</p><p>Maybe it’s an explanation generated from several data points.</p><p>The story defines the <strong>need</strong>, not the interface.</p><h3>So when should you use a user story?</h3><p>There are several situations where user stories are particularly useful.</p><h3>1. When you’re translating research into product requirements</h3><p>Imagine you’ve just completed ten user interviews.</p><p>You have pages of notes.</p><p>Users have mentioned:</p><ul><li>difficulty finding previous transactions</li><li>uncertainty about whether payments went through</li><li>frustration with complicated filters</li><li>wanting to export information</li><li>concerns about security</li></ul><p>Research gives you a lot of information.</p><p>But research findings aren’t necessarily product requirements.</p><p>User stories can help translate those observations into something the wider team can work with.</p><p>For example:</p><p><strong>Research finding:</strong></p><blockquote><em>Users frequently check whether a payment has actually gone through.</em></blockquote><p><strong>User story:</strong></p><blockquote><em>As a customer, I want to quickly confirm the status of a payment, so that I know whether I need to take further action.</em></blockquote><p>Now product, design and engineering have a shared starting point.</p><h3>2. When you’re working with Agile teams</h3><p>User stories are particularly common in Agile product development.</p><p>A product backlog might contain stories such as:</p><blockquote><em>As a customer, I want to reset my password so that I can regain access to my account.</em></blockquote><blockquote><em>As a manager, I want to download a report so that I can share it with my team.</em></blockquote><blockquote><em>As an administrator, I want to manage user permissions so that I can control access to sensitive information.</em></blockquote><p>These stories give the team a common language.</p><p>The designer can ask:</p><p><strong>What experience would allow the user to accomplish this successfully?</strong></p><p>The developer can ask:</p><p><strong>What needs to be built?</strong></p><p>The product manager can ask:</p><p><strong>Is this valuable enough to prioritise?</strong></p><p>And everyone is talking about the same user need.</p><h3>3. When there are multiple user types</h3><p>User stories become particularly useful when a product has different types of users.</p><p>Consider a healthcare platform.</p><p>You might have:</p><ul><li>Patients</li><li>Doctors</li><li>Care coordinators</li><li>Administrators</li></ul><p>Their goals can be completely different.</p><p>For example:</p><blockquote><strong><em>As a patient, I want to see my upcoming appointments so that I know when I need to attend.</em></strong></blockquote><p>versus:</p><blockquote><strong><em>As a doctor, I want to see my upcoming appointments so that I can prepare for my consultations.</em></strong></blockquote><p>Both users are looking at appointments.</p><p>But their <strong>needs and motivations are different</strong>.</p><p>This distinction can prevent teams from designing a generic experience that doesn’t properly serve anyone.</p><h3>4. When you’re defining an MVP</h3><p>User stories can also help answer an important question:</p><p><strong>What do we actually need to build first?</strong></p><p>Imagine you’re designing a food delivery app.</p><p>There are hundreds of possible features:</p><ul><li>restaurant discovery</li><li>search</li><li>filters</li><li>favourites</li><li>recommendations</li><li>reviews</li><li>loyalty</li><li>offers</li><li>social sharing</li><li>order tracking</li><li>scheduled orders</li></ul><p>Instead of starting with features, start with user goals.</p><p>For example:</p><blockquote><em>As a hungry customer, I want to find suitable food quickly, so that I can place an order without spending too much time searching.</em></blockquote><blockquote><em>As a customer, I want to know where my order is, so that I know when to expect it.</em></blockquote><blockquote><em>As a customer, I want to pay securely, so that I can complete my order with confidence.</em></blockquote><p>Now you can start asking:</p><p><strong>Which stories are essential for the core experience?</strong></p><p>That conversation is much more valuable than simply asking:</p><blockquote><em>“Which features should we put in the MVP?”</em></blockquote><h3>When NOT to use a user story</h3><p>This is perhaps the more important part.</p><p>Not every UX activity needs a user story.</p><h3>Don’t use user stories to replace research</h3><p>A user story doesn’t tell you whether something is actually a problem.</p><p>You might write:</p><blockquote><em>As a user, I want AI recommendations so that I can discover relevant content.</em></blockquote><p>But where did this need come from?</p><p>Did users actually ask for it?</p><p>Did behavioural data reveal it?</p><p>Is there another underlying problem?</p><p>Perhaps users don’t actually want recommendations.</p><p>Perhaps they simply can’t find the content they’re already interested in.</p><p><strong>Don’t use a user story to manufacture a problem.</strong></p><p>Research should establish the problem first.</p><h3>Don’t use them when you’re still exploring the problem</h3><p>Early in discovery, you may not know enough about the user yet.</p><p>You might be exploring:</p><blockquote><em>Why are customers abandoning the checkout?</em></blockquote><p>At this stage, jumping immediately to:</p><blockquote><em>“As a customer, I want a simpler checkout…”</em></blockquote><p>could prematurely narrow your thinking.</p><p>First understand the problem.</p><p>Then define the opportunity.</p><p>Then use user stories when they help translate that understanding into something actionable.</p><h3>User story vs user journey</h3><p>These are often confused.</p><p>They’re actually very different tools.</p><p>A <strong>user journey</strong> looks at the broader experience.</p><p>For example:</p><p><strong>Discover → Evaluate → Purchase → Receive → Use → Get support</strong></p><p>You might identify emotions, pain points, touchpoints and opportunities across the journey.</p><p>A <strong>user story</strong> zooms in on a specific need.</p><p>For example:</p><blockquote><em>As a customer, I want to track my delivery so that I know when it will arrive.</em></blockquote><p>Think of it this way:</p><p><strong>Journey mapping = the bigger picture</strong></p><p><strong>User story = a specific goal within that picture</strong></p><p>You can use both together.</p><h3>User story vs user flow</h3><p>A user story describes <strong>what the user wants to accomplish and why</strong>.</p><p>A user flow describes <strong>how the user moves through the product to accomplish it</strong>.</p><p>For example:</p><h3>User story</h3><blockquote><em>As a customer, I want to change my delivery address so that my order arrives at the correct location.</em></blockquote><h3>User flow</h3><p><strong>Order → Delivery details → Edit address → Enter address → Validate → Save → Confirmation</strong></p><p>The story comes before the flow.</p><p>The flow explores how the product can support the story.</p><h3>User story vs storyboard</h3><p>A storyboard brings something different again.</p><p>It shows the user’s situation and context visually.</p><p>Imagine:</p><p><strong>User receives a notification → Opens the app → Realises their delivery address is wrong → Changes it → Receives confirmation → Feels reassured</strong></p><p>A storyboard helps us understand the <strong>human context around an interaction</strong>.</p><p>A user story gives us a concise representation of the <strong>goal</strong>.</p><p>That’s why these tools work nicely together rather than competing with each other.</p><h3>How to write a good user story</h3><p>A good user story should be:</p><h3>1. User-centred</h3><p>Start with the user, not the technology.</p><p>❌ “As a system, I want to generate a notification…”</p><p>✅ “As a customer, I want to know when my order has shipped…”</p><h3>2. Focused on the outcome</h3><p>Don’t describe the UI.</p><p>❌ “I want a button on the dashboard…”</p><p>✅ “I want to quickly download my report…”</p><h3>3. Valuable</h3><p>Ask:</p><p><strong>Why does the user care?</strong></p><p>The “so that” part is often the most valuable part of the story.</p><p>Compare:</p><blockquote><em>I want to download a report.</em></blockquote><p>with:</p><blockquote><em>I want to download a report </em><strong><em>so that I can share it with my team.</em></strong></blockquote><p>The second version gives the team much more context.</p><h3>4. Small enough to act on</h3><p>Avoid creating enormous stories.</p><p>For example:</p><blockquote><em>As a customer, I want to manage my entire account so that I can control everything.</em></blockquote><p>That’s probably too broad.</p><p>Break it down.</p><blockquote><em>As a customer, I want to update my email address so that I can keep my account information current.</em></blockquote><blockquote><em>As a customer, I want to change my password so that I can keep my account secure.</em></blockquote><blockquote><em>As a customer, I want to manage my notification preferences so that I only receive relevant updates.</em></blockquote><p>Smaller stories are easier to design, build and test.</p><h3>A simple formula I use</h3><p>When writing a user story, I ask three questions:</p><h3>WHO?</h3><p>Who is trying to accomplish something?</p><h3>WHAT?</h3><p>What are they trying to accomplish?</p><h3>WHY?</h3><p>Why does it matter to them?</p><p>Then:</p><p><strong>Who + What + Why = User Story</strong></p><p>For example:</p><p><strong>Who:</strong> Facility manager<br><strong>What:</strong> Identify unusual waste patterns<br><strong>Why:</strong> Take action before the problem affects operations</p><p>Becomes:</p><blockquote><strong><em>As a facility manager, I want to identify unusual waste patterns so that I can take action before they affect operations.</em></strong></blockquote><p>Now we have a meaningful design problem to explore.</p><h3>And here’s the most important thing…</h3><p>A user story isn’t the end of the UX process.</p><p>It’s a <strong>bridge</strong>.</p><p>It can connect:</p><p><strong>Research → User need → Product requirement → Design → Testing</strong></p><p>But the process doesn’t have to be linear.</p><p>You might discover something during usability testing that changes the story.</p><p>You might discover that two stories are actually the same need.</p><p>You might discover that the user’s stated need isn’t their underlying problem.</p><p>That’s good UX.</p><p>The goal isn’t to produce perfect user stories.</p><p>The goal is to build a shared understanding of <strong>what people are trying to accomplish and why it matters</strong>.</p><p>And sometimes, the best user story is the one that makes your team stop and ask:</p><blockquote><strong><em>“Wait… is this actually what the user needs?”</em></strong></blockquote><p>That’s when the story has done its job.</p><h3>A quick checklist</h3><p>Before adding a user story to your backlog or design process, ask:</p><p>☐ Do we know who the user is?<br>☐ Is this based on an actual need or problem?<br>☐ Does it describe an outcome rather than a UI solution?<br>☐ Is the benefit clear?<br>☐ Is it small enough to act on?<br>☐ Can we test whether the user successfully achieved the goal?<br>☐ Does this story help the team make a better product decision?</p><p>If the answer is yes, you’ve probably got a useful user story.</p><h3>Final thought</h3><p>UX has a lot of artefacts: personas, journey maps, storyboards, user flows, wireframes, prototypes, service blueprints, user stories…</p><p>The important skill isn’t knowing <strong>how to create every artefact</strong>.</p><p>It’s knowing <strong>when each one helps you think better</strong>.</p><p>That’s the difference between following a UX process and actually doing UX.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=08b5e49155e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Variables vs styles in figma]]></title>
            <link>https://medium.com/@shalinisingh_17477/variables-vs-styles-in-figma-5260285cce0f?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5260285cce0f</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Sat, 23 May 2026 04:22:45 GMT</pubDate>
            <atom:updated>2026-05-23T04:22:45.418Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why Most Designers Use Them Incorrectly</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TeehOSkw5rtSpyva3Cimw.png" /></figure><p>For a long time, styles were enough.</p><p>Color styles.<br> Text styles.<br> Effect styles.</p><p>Design systems felt organized.<br> Teams felt consistent.</p><p>And then variables arrived in Figma… and suddenly many designers became confused about what should use styles, what should use variables, and whether styles even matter anymore.</p><p>I’ve noticed something interesting though.</p><p>Most teams are not struggling because variables are complicated.</p><p>They’re struggling because they still think statically in a world that is becoming increasingly dynamic.</p><p>And that’s the real difference between styles and variables.</p><h3>Styles Store Appearance</h3><p>Styles are essentially saved visual decisions.</p><p>For example:</p><ul><li>a text style</li><li>a color style</li><li>a shadow style</li></ul><p>You define something once and reuse it consistently.</p><p>Which is great.</p><p>Instead of manually choosing:</p><ul><li>font size</li><li>weight</li><li>line height</li><li>colors</li></ul><p>…you simply apply styles.</p><p>This creates visual consistency across files.</p><p>And honestly, styles were a massive improvement over chaotic manual design systems.</p><p>But styles have limitations.</p><p>They are static.</p><p>A color style is just:</p><blockquote><em>“Use this exact color.”</em></blockquote><p>It doesn’t adapt intelligently.</p><h3>Variables Store Logic</h3><p>Variables are fundamentally different.</p><p>Variables are not just visual values.</p><p>They are dynamic design tokens.</p><p>And that changes how systems work.</p><p>For example:<br> instead of assigning a button background directly to blue…</p><p>You assign it to:</p><blockquote><em>Primary / Background</em></blockquote><p>Now if the value changes:</p><ul><li>dark mode updates automatically</li><li>themes switch instantly</li><li>multiple components update together</li><li>responsive logic becomes easier</li></ul><p>Variables separate the decision from the actual value.</p><p>And this is exactly how modern frontend systems work too.</p><p>Which is why developers love token-based systems.</p><h3>Styles Answer “What”</h3><p>Variables Answer “Why”</p><p>This distinction helped me understand the difference clearly.</p><p>Styles define:</p><blockquote><em>what something looks like</em></blockquote><p>Variables define:</p><blockquote><em>why it looks that way</em></blockquote><p>For example:</p><p>A style may say:</p><ul><li>16px semibold text</li></ul><p>A variable may say:</p><ul><li>text-primary</li><li>spacing-medium</li><li>radius-large</li></ul><p>Variables create semantic meaning.</p><p>And semantic systems scale much better than purely visual systems.</p><p>Because products evolve constantly.</p><h3>Dark Mode Changed Everything</h3><p>Honestly, variables became truly important once interfaces started becoming more adaptive.</p><p>Dark mode exposed the limitations of static styling immediately.</p><p>Without variables:</p><ul><li>updating themes becomes painful</li><li>managing colors becomes repetitive</li><li>maintaining consistency becomes harder</li></ul><p>Variables solve this elegantly.</p><p>One token update can affect the entire product system instantly.</p><p>And suddenly design starts behaving much closer to code.</p><p>That’s why variables feel less like a “design feature” and more like infrastructure.</p><h3>Variables Do Not Replace Styles Completely</h3><p>This is where many designers misunderstand things.</p><p>Variables and styles are not enemies.</p><p>They solve different problems.</p><p>In fact, the strongest systems often use both together.</p><p>For example:</p><ul><li>variables manage tokens and logic</li><li>styles package reusable visual combinations</li></ul><p>Think of styles as reusable presentation.</p><p>Think of variables as the foundation underneath.</p><p>Good systems usually layer them together instead of choosing one over the other.</p><h3>Most Design Systems Fail Because They Are Too Literal</h3><p>A common mistake:<br> naming tokens visually instead of semantically.</p><p>Like:</p><ul><li>Blue-500</li><li>Gray-dark</li><li>Large-radius</li></ul><p>Looks organized initially.</p><p>Breaks later.</p><p>Because what happens when branding changes?</p><p>Now “Blue-500” might become purple.</p><p>Semantic naming scales better:</p><ul><li>Primary</li><li>Surface</li><li>Accent</li><li>Text-secondary</li></ul><p>The system becomes flexible instead of visually trapped.</p><p>And flexibility is the entire point of variables.</p><h3>The Bigger Shift Is Mental</h3><p>What I find most fascinating is this:</p><p>Variables are quietly changing how designers think.</p><p>Designers are moving from:</p><ul><li>screen-based thinking</li></ul><p>to:</p><ul><li>system-based thinking</li></ul><p>And that shift is incredibly important.</p><p>Because modern products are no longer single experiences.</p><p>They are ecosystems:</p><ul><li>responsive</li><li>theme-aware</li><li>multi-platform</li><li>constantly evolving</li></ul><p>Static design methods eventually collapse under that complexity.</p><p>Variables help manage that complexity.</p><h3>Final Thought</h3><p>Styles made design systems reusable.</p><p>Variables make them adaptive.</p><p>And adaptive systems are the future of product design.</p><p>The designers who understand this early will not just create prettier files.</p><p>They’ll create products that scale gracefully across teams, platforms, and future changes.</p><p>And honestly, that’s where design is heading now:</p><p>Less decoration.<br>More systems thinking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5260285cce0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frames vs Groups in Figma]]></title>
            <link>https://medium.com/@shalinisingh_17477/frames-vs-groups-in-figma-6deb394ce42d?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6deb394ce42d</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Mon, 11 May 2026 11:37:31 GMT</pubDate>
            <atom:updated>2026-05-11T11:37:31.843Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Small Decision That Quietly Affects Your Entire Design File</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BmKBf1hXRsijwS4ROFxROg.png" /></figure><p>One of the easiest ways to identify whether a designer truly understands Figma is surprisingly simple.</p><p>Open their layers panel.</p><p>If everything is inside random groups… chaos is probably coming.</p><p>At first, frames and groups seem almost identical.</p><p>Both let you organize layers.<br> Both can contain multiple elements.<br> Both visually “work.”</p><p>So naturally, many beginners use them interchangeably.</p><p>But the difference between frames and groups is not cosmetic.</p><p>It completely changes:</p><ul><li>responsiveness</li><li>scalability</li><li>prototyping</li><li>auto layout behavior</li><li>developer handoff</li><li>overall file structure</li></ul><p>And honestly?</p><p>Once you deeply understand frames, you almost stop using groups entirely.</p><h3>Groups Are Just Visual Containers</h3><p>A group simply keeps layers together.</p><p>That’s it.</p><p>It does not create structure.<br> It does not create layout behavior.<br> It does not understand spacing relationships.</p><p>A group is basically:</p><blockquote><em>“These layers should move together.”</em></blockquote><p>Useful? Yes.</p><p>Scalable? Not really.</p><p>The biggest issue with groups appears the moment your design starts evolving.</p><p>You resize something… and everything behaves unpredictably.</p><p>Padding breaks.<br> Alignment shifts awkwardly.<br> Elements overlap unexpectedly.</p><p>Because groups are passive.</p><p>They do not understand how components should behave.</p><h3>Frames Actually Create Layout Logic</h3><p>Frames are intelligent containers.</p><p>The moment you use a frame, Figma starts understanding:</p><ul><li>boundaries</li><li>positioning</li><li>resizing behavior</li><li>constraints</li><li>auto layout</li><li>clipping</li><li>responsiveness</li></ul><p>And this changes everything.</p><p>Frames allow designs to behave more like real interfaces instead of static drawings.</p><p>That’s why almost every advanced Figma workflow depends heavily on frames.</p><p>Not groups.</p><h3>Auto Layout Exists Because of Frames</h3><p>This is where many designers suddenly realize why their files become difficult to manage.</p><p>Auto layout only works properly with frames.</p><p>And auto layout is honestly one of the most important features in modern UI design.</p><p>Without it:</p><ul><li>buttons become manual work</li><li>responsive components break</li><li>spacing becomes inconsistent</li><li>design updates become exhausting</li></ul><p>With frames + auto layout:</p><ul><li>components adapt naturally</li><li>spacing remains consistent</li><li>content changes become manageable</li><li>interfaces scale faster</li></ul><p>You stop “placing pixels.”</p><p>You start building systems.</p><p>And that mindset shift changes the quality of your work dramatically.</p><h3>Developers Think in Structure — Frames Help That</h3><p>Developers do not see your design the way designers do.</p><p>They see hierarchy.</p><p>Containers.<br> Sections.<br> Components.<br> Nested layouts.</p><p>Frames mirror this logic much better.</p><p>A properly framed Figma file often translates more cleanly into frontend structure.</p><p>And good frontend developers immediately notice the difference.</p><p>Messy groups create confusion:</p><ul><li>what is the parent container?</li><li>what controls spacing?</li><li>which elements resize together?</li><li>where does padding actually begin?</li></ul><p>Frames answer these questions naturally.</p><p>Good design files reduce developer guesswork.</p><p>And reducing guesswork is one of the most underrated design skills.</p><h3>So… Should You Never Use Groups?</h3><p>Groups are still useful sometimes.</p><p>Especially for:</p><ul><li>temporary organization</li><li>quick selections</li><li>illustration work</li><li>non-UI exploration</li><li>combining decorative elements</li></ul><p>But for product design?</p><p>Frames should usually be the default.</p><p>A simple rule I follow:</p><blockquote><em>If the element behaves like UI, it should probably be a frame.</em></blockquote><p>And once you adopt this mindset consistently, your files become dramatically cleaner.</p><h3>The Real Difference Is Not Technical</h3><p>Honestly, the real difference between groups and frames is philosophical.</p><p>Groups help organize visuals.</p><p>Frames help build interfaces.</p><p>And modern product design is no longer about creating beautiful static screens.</p><p>It’s about designing adaptable systems that survive real-world usage.</p><p>That’s why experienced designers obsess over structure.</p><p>Because eventually every messy file becomes expensive:</p><ul><li>expensive to update</li><li>expensive to scale</li><li>expensive to handoff</li><li>expensive to maintain</li></ul><p>Good structure quietly saves teams hundreds of hours.</p><h3>Final Thought</h3><p>Most beginners discover Figma through visuals.</p><p>Experienced designers eventually discover it through systems.</p><p>And the shift from groups to frames is usually one of the first signs that a designer is starting to think structurally instead of visually.</p><p>It feels like a small decision.</p><p>But small structural decisions are what separate scalable design from temporary design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6deb394ce42d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Make Your Design Match the Final Dev Version]]></title>
            <link>https://medium.com/@shalinisingh_17477/how-to-make-your-design-match-the-final-dev-version-2e72435e8a9c?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e72435e8a9c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Mon, 11 May 2026 11:14:51 GMT</pubDate>
            <atom:updated>2026-05-11T11:14:51.339Z</atom:updated>
            <content:encoded><![CDATA[<h4>There’s a strange moment every designer experiences.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AMLQH880WMDpHoeZPuBIWw.jpeg" /><figcaption>Image credit <a href="https://www.linkedin.com/company/cortechsols/posts/?feedView=all">CorTechSols</a></figcaption></figure><p>You open the staging build after weeks of designing polished screens in Figma… and suddenly your beautiful interface looks like its distant cousin.</p><p>Spacing feels off. Typography looks heavier. Buttons somehow lost their elegance. The alignment you obsessed over for hours now feels “almost correct” — which in product design usually means wrong.</p><p>And then begins the classic conversation:</p><blockquote><em>“But it looked perfect in Figma.”</em></blockquote><p>Over the years, I’ve realised something important:</p><p>The gap between design and development is rarely caused by lack of skill.<br> It is usually caused by lack of shared systems.</p><p>Designers think visually. Developers think structurally.<br> And products suffer when these two worlds only meet during handoff.</p><p>The truth is — a design is not complete when the mockup is done.<br> It is complete when the shipped product feels identical to the intended experience.</p><p>So how do we actually make designs match the dev version?</p><p>Here are the practices that genuinely work.</p><h3>Stop Designing “Pictures”</h3><p>One of the biggest mistakes designers make is treating screens like static artboards.</p><p>Real products are alive.</p><p>Text changes.<br> Devices resize.<br> States appear unexpectedly.<br> APIs fail.<br> Users behave unpredictably.</p><p>Yet many designs are still created in ideal conditions:</p><ul><li>perfect content</li><li>one screen size</li><li>no edge cases</li><li>no loading states</li><li>no empty states</li></ul><p>Then developers are forced to “figure out the rest.”</p><p>And that’s exactly where inconsistency begins.</p><p>Instead of designing pages, design systems of behavior.</p><p>Ask:</p><ul><li>What happens when the title becomes two lines?</li><li>What if the user has no profile image?</li><li>What happens on smaller devices?</li><li>How does this component behave on hover?</li><li>What is the disabled state?</li></ul><p>The more ambiguity exists in design, the more interpretation happens in development.</p><p>And interpretation is where visual mismatch begins.</p><h3>Learn a Little Frontend</h3><p>Not because designers should become developers.</p><p>But because understanding implementation changes the way you design.</p><p>The moment you understand:</p><ul><li>flexbox</li><li>responsive grids</li><li>spacing systems</li><li>CSS constraints</li><li>component reuse</li></ul><p>…your designs become dramatically more realistic.</p><p>You stop creating impossible alignments.<br> You stop using random spacing values.<br> You stop designing components that break instantly in production.</p><p>And most importantly:<br> you start speaking the same language as developers.</p><p>That changes collaboration completely.</p><p>I’ve seen designers spend hours arguing over 14px vs 15px spacing while developers struggle with inconsistent component logic underneath.</p><p>Visual perfection matters.</p><p>But scalable structure matters more.</p><h3>Your Design System Should Be Stronger Than Your Screens</h3><p>A weak design system creates strong-looking mockups and weak products.</p><p>A strong design system creates consistency even when multiple teams work together.</p><p>The easiest way to spot a mature product team is this:</p><p>The shipped product feels boringly consistent.</p><p>Not because creativity is missing.<br> But because decisions are already standardized.</p><p>Things that should exist clearly:</p><ul><li>typography scale</li><li>spacing tokens</li><li>color tokens</li><li>button behaviors</li><li>elevation rules</li><li>grid structure</li><li>component variants</li><li>icon sizing</li><li>responsive behavior</li></ul><p>Without these, developers make assumptions.</p><p>And assumptions slowly create UI drift.</p><p>One button becomes 44px height.<br> Another becomes 48px.<br> One modal uses 24px padding.<br> Another uses 32px.</p><p>Months later everyone wonders why the product feels “messy.”</p><p>Messiness rarely arrives dramatically.<br> It accumulates silently.</p><h3>Handoff Is Not Collaboration</h3><p>Many teams still treat handoff as the finish line.</p><p>Designer finishes screens → developer receives file → implementation begins.</p><p>But great products are not built through file transfers.</p><p>They are built through continuous conversations.</p><p>The best designer-developer relationships I’ve seen involve:</p><ul><li>discussing feasibility early</li><li>reviewing components together</li><li>clarifying interactions before implementation</li><li>checking staging builds collaboratively</li><li>fixing gaps quickly</li></ul><p>Not “throwing designs over the wall.”</p><p>Because once development starts, new realities appear:</p><ul><li>technical limitations</li><li>accessibility issues</li><li>performance concerns</li><li>responsive constraints</li><li>business logic</li></ul><p>And products improve when both sides solve these problems together instead of defending their own territory.</p><h3>Pixel Perfect Is Not Always Experience Perfect</h3><p>This one is important.</p><p>Sometimes designers focus so much on visual accuracy that they ignore actual usability.</p><p>A developer may slightly increase padding for better responsiveness.<br> Or simplify an animation for performance.<br> Or adjust contrast for accessibility.</p><p>And honestly?</p><p>Sometimes that is the correct decision.</p><p>The goal is not ego-driven perfection.<br> The goal is product quality.</p><p>Users do not care whether your card radius became 14px instead of 12px.</p><p>They care whether the experience feels smooth, intuitive, and reliable.</p><p>Design maturity is knowing which details are sacred… and which are negotiable.</p><h3>QA is also a Designer’s Job</h3><p>Many designers disappear after handoff.</p><p>But implementation review is one of the most important parts of the design process.</p><p>Always review:</p><ul><li>staging builds</li><li>responsive behavior</li><li>spacing consistency</li><li>typography rendering</li><li>interaction feedback</li><li>animations</li><li>accessibility</li><li>dark mode (if applicable)</li></ul><p>And review them in real environments:</p><ul><li>mobile devices</li><li>slower internet</li><li>different browsers</li><li>actual user flows</li></ul><p>Figma is controlled.</p><p>Reality is not.</p><p>The closer designers stay to the shipped product, the smaller the design-dev gap becomes.</p><h3>Final Thought</h3><p>I used to think the best designers were the ones who created the most beautiful screens.</p><p>Now I think the best designers are the ones whose products survive implementation beautifully.</p><p>Because real design is not the mockup.</p><p>Real design is what users finally experience.</p><p>And the strongest product teams understand this deeply.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e72435e8a9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Most critical questions in UI/UX design interview and my answers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@shalinisingh_17477/most-critical-questions-in-ui-ux-design-interview-and-my-answers-7649bd8b4218?source=rss-e0be3461a1f7------2"><img src="https://cdn-images-1.medium.com/max/2600/1*rAdDfBaeghCTt8PzXaxnFg.jpeg" width="6000"></a></p><p class="medium-feed-snippet">As I complete 10 years in this area, here are my learnings (horizon)</p><p class="medium-feed-link"><a href="https://medium.com/@shalinisingh_17477/most-critical-questions-in-ui-ux-design-interview-and-my-answers-7649bd8b4218?source=rss-e0be3461a1f7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@shalinisingh_17477/most-critical-questions-in-ui-ux-design-interview-and-my-answers-7649bd8b4218?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7649bd8b4218</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Thu, 05 Mar 2026 05:51:57 GMT</pubDate>
            <atom:updated>2026-03-12T04:22:57.138Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Design Apps That Users Love]]></title>
            <link>https://medium.com/@shalinisingh_17477/how-to-design-apps-that-users-love-f5fe8601fe63?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5fe8601fe63</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Sun, 02 Mar 2025 05:32:53 GMT</pubDate>
            <atom:updated>2025-03-02T05:32:53.906Z</atom:updated>
            <content:encoded><![CDATA[<h4>A UX Designer’s Guide to Creating Delightful Experiences</h4><p>Designing an app that users love goes far beyond aesthetics — it’s about creating seamless, intuitive, and enjoyable experiences that meet users’ needs. The best apps not only solve problems but also create emotional connections with users.</p><h3>Understanding User Needs</h3><p>Before a single screen is designed, understanding user needs is the foundation of creating lovable apps. This involves:</p><ul><li><strong>User Research:</strong> Conduct interviews, surveys, and usability testing to understand what users truly want.</li><li><strong>Jobs-to-Be-Done (JTBD) Framework:</strong> Identify the core jobs users are trying to accomplish with the app.</li><li><strong>Empathy Mapping:</strong> Understand users’ thoughts, feelings, and pain points throughout their journey.</li></ul><h4>Example:</h4><p>Spotify uses extensive user research to understand how people listen to music, which led to features like personalized playlists and Discover Weekly</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v1DLCZefmHYLKHFjSnRuQA.png" /><figcaption>Empathy map</figcaption></figure><h3>Designing for Simplicity</h3><p>Simplicity is at the heart of user satisfaction. The fewer steps and decisions users have to make, the better the experience.</p><ul><li><strong>Clear Navigation:</strong> Design intuitive navigation patterns that guide users naturally.</li><li><strong>Minimal Interfaces:</strong> Use whitespace, clear typography, and consistent layouts.</li><li><strong>Prioritized Features:</strong> Highlight the most important features upfront.</li></ul><h4>Example:</h4><p>Google Search maintains a clean, minimal interface despite its powerful backend capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XtZd7xXl1QTTGEw_N7RBA.png" /><figcaption>Google minimal homepage</figcaption></figure><h3>Creating Emotional Connections</h3><p>Users don’t just love apps for their functionality — they love how apps make them feel.</p><ul><li><strong>Microinteractions:</strong> Delight users with small, playful animations (like the pull-to-refresh animation on Twitter).</li><li><strong>Personalization:</strong> Offer tailored experiences based on user preferences.</li><li><strong>Visual Design:</strong> Use colors, typography, and illustrations that evoke positive emotions.</li></ul><h4>Example:</h4><p>Duolingo uses playful illustrations and encouraging messages to make learning a language fun. Language plays an important role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rkBzTumosuKFLg3wD0Xhhg.png" /><figcaption>Good vs bad copy</figcaption></figure><h3>Usability Testing and Iteration</h3><p>No app is perfect from the first version. Continuous testing and iteration help refine the product.</p><ul><li><strong>Prototype Testing:</strong> Validate designs before development.</li><li><strong>A/B Testing:</strong> Test different variations to see what resonates best with users.</li><li><strong>Feedback Loops:</strong> Regularly gather user feedback to identify pain points.</li></ul><h4>Example:</h4><p>Instagram frequently tests small interface tweaks with limited user groups before rolling them out widely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*0XIocuuuvAnN48szXyKGcA.jpeg" /><figcaption>Iterative design process</figcaption></figure><h3>Accessibility and Inclusivity</h3><p>Great apps are designed for everyone.</p><ul><li><strong>Contrast and Readability:</strong> Ensure text is legible for all users.</li><li><strong>Keyboard Navigation:</strong> Support users who rely on keyboards or assistive technologies.</li><li><strong>Localization:</strong> Adapt content for different languages and cultures.</li></ul><h4>Example:</h4><p>Apple’s iOS includes robust accessibility features like VoiceOver and screen magnification.</p><h3>Delight Through Details</h3><p>Small details make a huge difference in user experience.</p><ul><li><strong>Loading Animations:</strong> Engage users during wait times.</li><li><strong>Error Messages:</strong> Write friendly, helpful messages instead of technical jargon.</li><li><strong>Celebratory Moments:</strong> Congratulate users on completing tasks.</li></ul><h4>Example:</h4><p>Google Pay’s subtle confetti animation when a payment is successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5reORl53QxuH_i6VYzQUw.png" /><figcaption>Sucess screen with animation</figcaption></figure><h3>Final Thoughts</h3><p>Designing apps that users love requires a combination of functionality, simplicity, and emotional connection. By understanding what users truly need and paying attention to every detail, designers can create experiences that not only solve problems but bring delight.</p><p>In the end, the best apps are those that make users feel empowered, understood, and valued — turning everyday interactions into moments of joy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5fe8601fe63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How many features is too many features?]]></title>
            <link>https://medium.com/@shalinisingh_17477/how-many-features-is-too-many-features-404e5654b7ad?source=rss-e0be3461a1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/404e5654b7ad</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Shalini Singh]]></dc:creator>
            <pubDate>Sun, 02 Mar 2025 05:12:32 GMT</pubDate>
            <atom:updated>2025-03-02T05:12:32.045Z</atom:updated>
            <content:encoded><![CDATA[<p>A ux designer’s take on app complexity</p><p>In the race to create the next must-have app, it’s tempting to cram in as many features as possible. More features mean more value, right? Not always. In fact, too many features can dilute the user experience, making an app harder to use and less enjoyable. The real challenge for UX designers is finding the delicate balance between functionality and simplicity.</p><h3>The Feature Creep Trap</h3><p>Feature creep — the gradual addition of unnecessary features — is one of the most common pitfalls in product design. It often starts with good intentions: adding a small tweak to meet user requests or outdo competitors. However, every new feature adds complexity, which can lead to a cluttered interface and confused users.</p><h4>Example:</h4><p>Think of early smartphone apps that tried to do everything — from messaging to gaming to document editing — all within one app. Users struggled to navigate, and these apps quickly fell out of favor.</p><p>Another example is Microsoft Word, which evolved from a simple word processor into a feature-rich software suite. While power users appreciate the advanced functions, casual users often find the interface overwhelming</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*Cv7C6Q7pK1uQHWwn3JrCMg.png" /><figcaption>Cluttered vs simple app UI</figcaption></figure><h3>Why Too Many Features Hurt UX</h3><ul><li><strong>Cognitive Overload:</strong> Too many options overwhelm users, making it harder to make decisions.</li><li><strong>Slower Onboarding:</strong> Complex apps require more tutorials and explanations, which frustrates new users.</li><li><strong>Hidden Value:</strong> The best features might go unnoticed because they’re buried beneath layers of functionality.</li><li><strong>Higher Maintenance:</strong> More features mean more bugs, more updates, and more customer support inquiries.</li></ul><h4>Example:</h4><p>Snapchat faced backlash when they introduced too many features at once, including games, news, and maps, which left many users confused and frustrated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*6tBXIjzak2t3jZHbdTgo6w.png" /><figcaption>Curve demonstrating the relationship between cognitive load and task performance</figcaption></figure><h3>How to Avoid Feature Overload</h3><ol><li><strong>Prioritize Core Functionality:</strong> Identify the app’s primary purpose and build around that. <br>Example: Spotify focuses on music streaming, with secondary features like podcasts added gradually without overwhelming the primary experience.</li><li><strong>User Feedback, Not Just Requests:</strong> Listen to what users struggle with, not just what they ask for. <br>Example: Google Chrome continuously refines its minimalist design based on performance feedback rather than adding unnecessary features.</li><li><strong>Minimal Viable Product (MVP) Approach:</strong> Start with the essentials and expand only when absolutely necessary.</li><li><strong>Progressive Disclosure:</strong> Show advanced features only when users need them, rather than overwhelming them upfront.</li><li><strong>Jobs-to-Be-Done (JTBD) Framework:</strong> Understand the job users are trying to accomplish, and build features that directly support those jobs. Example: Airbnb uses the JTBD approach by focusing on helping users <strong>find a place to stay easily</strong> rather than adding unrelated features like social networking or travel guides.</li><li><strong>Kill Your Darlings:</strong> Regularly audit features and remove those that aren’t adding value.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*O942vu4lHL92T1VgShu_WA.jpeg" /><figcaption>MoSCoW analysis for features</figcaption></figure><h3>Less Is Often More</h3><p>Successful apps like Instagram and Airbnb became popular by doing <strong>a few things really well</strong>. Instagram focused on photo sharing with minimal filters. Airbnb simplified booking accommodation. Both apps could have added dozens of features — but their simplicity became their strength.</p><h4>Example:</h4><p>WhatsApp became the world’s most popular messaging app by offering simple, reliable messaging without unnecessary bells and whistles.</p><h3>Final Thoughts</h3><p>As UX designers, our job is not just to build features — it’s to craft experiences. Every feature should serve a purpose, solve a problem, and enhance the user’s journey. When in doubt, <strong>simplify</strong>.</p><p>The <strong>Jobs-to-Be-Done (JTBD)</strong> framework can serve as a powerful tool to guide feature decisions — ensuring every feature supports what the user is trying to accomplish, rather than simply adding surface-level functionality.</p><p>In the end, the best user experiences are not those with the most features — but those with the most thoughtful ones.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=404e5654b7ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>