<?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 Vandana Prajapati on Medium]]></title>
        <description><![CDATA[Stories by Vandana Prajapati on Medium]]></description>
        <link>https://medium.com/@vandanaprajapati?source=rss-18536f5803b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9-KmzSpxWqiT9iND.</url>
            <title>Stories by Vandana Prajapati on Medium</title>
            <link>https://medium.com/@vandanaprajapati?source=rss-18536f5803b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:44:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vandanaprajapati/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[This framework transforms UX case studies from blank to brilliant]]></title>
            <link>https://medium.com/@vandanaprajapati/this-framework-transforms-ux-case-studies-from-blank-to-brilliant-ea6e14ff2036?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea6e14ff2036</guid>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 07:32:38 GMT</pubDate>
            <atom:updated>2026-04-30T07:34:19.303Z</atom:updated>
            <content:encoded><![CDATA[<h3>Everything Is Storytelling. You Just Haven’t Noticed Yet.</h3><p>Think about the last ad that stopped you mid-scroll. The last pitch that made you lean forward. The last comedian you genuinely couldn’t stop watching.</p><p>None of them were listing features. None of them were walking you through a process step by step. They were doing something else entirely — pulling you into a world, building a tension you needed resolved, and landing you somewhere different from where you started.</p><p>That’s not talent. That’s structure.</p><p>And the moment you understand that structure, you can’t unsee it anywhere.</p><p>The greatest communicators — on stage, in boardrooms, on screen, all follow the same invisible pattern. They start with a current state you immediately recognize. They introduce a tension that makes you uncomfortable. They move through a decision. And they deliver you to a different place than where you began.</p><p>Before and after. Movement. Change.</p><p>That’s what makes something stick in the brain. Not the information itself but the <em>journey</em> through it. Neuroscience backs this up: when we hear a story, the brain doesn’t just process language. It releases dopamine when there’s tension and anticipation. It releases oxytocin when there’s human stakes and emotion. The brain is wired to follow a story the way water follows a slope. It can’t help it.</p><p>This is why the best creators, filmmakers, and brands don’t explain — they <em>pull</em>. They create a gap between what you know and what you want to know, and they make you walk through it yourself. That gap is the story. That gap is what keeps you watching.</p><p>Everything that actually works every product that spreads, every speech remembered years later, every pitch that earns trust in a room — uses this same mechanism. Not because the people behind them are more creative. Because they understand how human attention actually moves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4qXmzLTe_NYtmSAMGBpnAQ.jpeg" /></figure><h3><strong>Now look at your UX case studies.</strong></h3><p>Most of them read like documentation. Here’s the problem we found. Here’s the research we did. Here’s the wireframe we made. Here’s the result. Next case study.</p><blockquote>Blank. Forgettable. Replaceable.</blockquote><p>A hiring manager or client reads it the same way they read a hundred others. No tension. No stakes. No moment where they lean forward and think, <em>“Wait, that’s actually brilliant.”</em></p><p>The work might be brilliant. The thinking might be solid. But the case study itself the way you’re telling the story of that work is missing the one thing that makes it stick: <em>narrative structure</em>.</p><p>A strong UX case study doesn’t just show what you designed. It shows <em>what changed</em> because you designed it. It doesn’t list research findings it takes the reader <em>through</em> the confusion and discomfort the users felt, so they understand why your solution was the only answer. It doesn’t show wireframes in isolation it reveals the <em>decision</em> behind each one, the tension it solved, the shift it created.</p><p>That’s the difference between a case study and a <em>story about</em> a case study. One disappears. The other gets you hired.</p><p>This is exactly what the framework below fixes.</p><p>It’s built specifically for UX case studies — the ones that live on portfolios, the ones that get studied in job interviews, the ones that need to convince someone in five minutes that you don’t just design interfaces. You solve human problems. You see what others miss. You move people from confusion to clarity.</p><p>The framework maps five invisible layers onto your UX work:</p><p><strong><em>The Hook</em><br></strong>why this problem mattered right now, what made it uncomfortable, what was at risk if nothing changed.</p><p><strong><em>The Research Journey</em><br></strong>not a list of findings, but the <em>path</em> you took the reader through. What questions emerged. What assumptions broke. Where the real tension lived.</p><p><strong><em>The Decision Point</em></strong><em> </em><br>the moment where you chose a direction. Not because it looked good. Because it solved something real.</p><p><strong><em>The Implementation</em><br></strong>how the solution moved from idea to reality, what changed as you built it, where the thinking shifted.</p><p><strong><em>The Outcome and Perspective</em><br></strong>Not just metrics, but what those metrics <em>mean</em>. Who benefited. What became possible now that wasn’t before. What this taught you about solving problems.</p><p>When your case study is structured this way, you’re not just showing a portfolio piece. You’re demonstrating how you think, how you see, how you move people from one place to another. That’s what gets remembered. That’s what gets you in the room.</p><p>And here’s the thing: this isn’t about writing more beautifully or adding more words. It’s about <em>organizing</em> what you already know into a shape that the human brain is wired to follow.</p><p>Your UX case studies could be brilliant. Most of them are just blank because no one taught you the difference between <em>documenting work</em> and <em>telling the story of work</em>.</p><blockquote>This framework is that difference.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea6e14ff2036" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Designers Don’t Lose Influence Because of Bad Design.]]></title>
            <link>https://medium.com/@vandanaprajapati/ux-designers-dont-lose-influence-because-of-bad-design-0da7d3abcfb7?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/0da7d3abcfb7</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 01:39:55 GMT</pubDate>
            <atom:updated>2026-04-22T01:39:55.402Z</atom:updated>
            <content:encoded><![CDATA[<p>No One Tells UX Designers This Early Enough: You’re Always Negotiating</p><p>No one teaches negotiation in design school.</p><p>You learn grids.<br>You learn heuristics.<br>You learn how to defend a button placement.</p><p>But the real work?<br>It happens <em>outside</em> the tools</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWIWlwE308Sm5NuUW-MwUQ.png" /></figure><h3>The First Time You Realize UX Isn’t Just About Design</h3><p>Early in my career, someone looked at my screen and said:</p><blockquote><em>“I don’t like this. Can you change it?”</em></blockquote><p>No explanation. No context. Just… dislike.</p><p>I remember staring at the screen, unsure what to do next.<br>Was the design wrong?<br>Was I wrong?<br>Or was this just someone’s opinion?</p><p>That was the day I learned something important:<br><strong>Good UX work can disappear if you don’t know how to talk about it.</strong></p><p>That wasn’t a design problem.<br>That was a negotiation problem.</p><h3>Junior Designers Negotiate Before They Even Know the Word</h3><p>As a junior designer, you negotiate <em>every day </em>even if you don’t call it that.</p><p>You negotiate:</p><ul><li>Whether your idea gets considered or dismissed</li><li>Whether feedback is about the user or personal taste</li><li>Whether you’re allowed to explain your thinking or expected to just execute</li></ul><p>The quiet negotiation sounds like this:</p><blockquote><em>“I’m happy to update this can you help me understand what isn’t working for the user?”</em></blockquote><p>That one sentence changes everything.<br>It shifts the conversation from <em>preference</em> to <em>problem</em>.</p><p>And slowly, confidence replaces hesitation.</p><h3>Seniors Don’t Fight for Pixels. They Fight for Time.</h3><p>Later, the problems change.</p><p>No one questions <em>whether</em> you can design anymore.<br>Instead, they ask:</p><blockquote><em>“Can we do this quickly?”<br>“Do we really need research for this?”<br>“Can design just adapt to what engineering has already built?”</em></blockquote><p>This is where senior designers live between intention and reality.</p><p>You’re no longer negotiating <em>what</em> to design.<br>You’re negotiating <strong>time, scope, and trade-offs</strong>.</p><p>Sometimes you say:</p><blockquote><em>“If we skip research here, we risk fixing the wrong problem.”</em></blockquote><p>Other times you say:</p><blockquote><em>“Let’s solve the core flow now and refine the rest post-release.”</em></blockquote><p>Neither is perfect.<br>Both are thoughtful.</p><p>This is negotiation with context, not ego.</p><h3>Leadership Is Negotiation Without a Screen</h3><p>When you move into lead or director roles, something strange happens.</p><p>You design less.<br>But you negotiate more.</p><p>You negotiate:</p><ul><li>Design time in roadmaps</li><li>UX capacity vs feature pressure</li><li>Budgets, headcount, and priorities</li><li>User impact when users aren’t in the room</li></ul><p>You’re no longer defending <em>a screen</em>.<br>You’re defending <strong>a system, a team, and a standard</strong>.</p><p>And sometimes the hardest negotiation is saying no<br>not to stakeholders, but to unrealistic expectations placed on your team.</p><h3>UX Is Collaborative. Which Means UX Is Political.</h3><p>This part is uncomfortable, but true.</p><p>UX doesn’t exist in isolation.<br>It exists in:</p><ul><li>Business constraints</li><li>Engineering realities</li><li>Organizational pressure</li><li>Human egos</li></ul><p>Calling UX “collaborative” sounds nice.<br>But collaboration only works when someone actively balances power, priorities, and perspectives.</p><p>That someone is often the UX designer.</p><p>Not by force.<br>Not by being loud.<br>But by being clear, calm, and prepared.</p><h3>What Good UX Negotiation Actually Looks Like</h3><p>It doesn’t look like arguments.<br>It looks like:</p><ul><li>Asking better questions instead of giving faster answers</li><li>Framing design decisions around outcomes, not opinions</li><li>Knowing when to push — and when to let go</li><li>Protecting users <em>without</em> blocking progress</li></ul><p>Most of the time, it’s subtle.<br>Almost invisible.</p><p>But without it, UX slowly fades into “just UI.”</p><h3>The Quiet Truth</h3><p>Negotiation isn’t a soft skill in UX.<br>It’s a survival skill.</p><p>If you don’t negotiate:</p><ul><li>UX becomes optional</li><li>Design becomes decorative</li><li>Decisions get made without users in mind</li></ul><p>And no matter your title<br>intern, junior, senior, lead, or director If you’re doing UX,<br><strong>you’re already negotiating.</strong></p><p>The only question is:<br>Are you doing it consciously… or learning the hard way?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0da7d3abcfb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Systems Aren’t Just UI Libraries; They’re Essential Infrastructure for the Long Haul.]]></title>
            <link>https://medium.com/@vandanaprajapati/design-systems-arent-just-ui-libraries-they-re-essential-infrastructure-for-the-long-haul-11eba5bd91f8?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/11eba5bd91f8</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[build-design-system]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 07:37:55 GMT</pubDate>
            <atom:updated>2026-02-06T07:37:55.598Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZsUvZ4rNl7ZZmAaYz59jA.jpeg" /></figure><p>As I explored various design systems across different organizations, I kept spotting a recurring theme. Most of these systems were visually stunning, well-documented, and packed with components — but there was something crucial that was missing. It wasn’t about the polish or completeness; it was about having a solid foundation and the ability to scale over time. Today’s design systems often prioritize UI delivery, addressing immediate needs like consistency, speed, and reusability. While these aspects are certainly important, they only scratch the surface of what a design system is truly meant to achieve. When a system is primarily treated as a UI library, it might perform well in the short term, but it often falters when faced with future challenges. It’s essential to understand that a design system is not synonymous with UI. UI is what users interact with, while a design system is what empowers teams to create, adapt, and sustain those interfaces over time.</p><p>A Design System Benefits the Entire Organization, Not Just Designers A well-developed design system isn’t just for designers; it operates at the crossroads of design, engineering, and product development. Designers turn to it for clarity and consistency, engineers rely on it for reliable implementation, and product teams leverage it to scale features without having to rethink decisions at every turn. When a design system functions effectively, it becomes a common language for everyone involved. If it doesn’t, it can quickly turn into a bottleneck. This is why focusing solely on components can be limiting. Components are just the end products. The true value lies in the principles, foundations, and guidelines that support those components and allow them to grow and adapt.</p><p><strong>Thinking in Components vs Thinking in Time<br></strong>One of the biggest pitfalls when designing a design system is focusing solely on immediate needs. What components do we need right now? Which patterns address our current challenges? However, a much more crucial question often gets overlooked: Where is this organization headed in the next five to ten years? Products evolve. Platforms shift. Teams expand. Branding transforms. Technology stacks change. A design system that fails to anticipate these changes will ultimately struggle to keep up. When we talk about scalability in a design system, it’s not just about the number of components it has. It’s really about how seamlessly the system can adapt to change without needing a complete overhaul. If a minor visual tweak requires teams to revise every single component, then the system is already on shaky ground.</p><p><strong>Foundations Are What Make Systems Scalable</strong> <br>The real power of a design system comes from its foundations. Elements like tokens, spacing logic, typography scales, semantic naming, and layout principles do much more heavy lifting than the visible components ever could. Strong foundations allow for style changes without compromising the underlying structure. They enable a gradual modernization of the system rather than disruptive redesigns. Without this foundational layer, systems become tightly interwoven, hard to update, and increasingly costly to maintain. In this context, modernization isn’t about constant redesigns or visual updates. It’s about creating a system that can quietly adapt in the background — remaining relevant without constant upheaval.</p><p><strong>Keeping the System Alive Over Time <br></strong>A design system shouldn’t feel like a static relic or a legacy product stuck in the past. It needs to be treated as a living, breathing system.</p><p>This requires clear guidelines on:</p><p>• How updates are made and rolled out <br>• How frequently changes happen <br>• Who makes the decisions <br>• How contributions are reviewed and accepted</p><p>Today, a lot of teams are leaning heavily on tools like Figma for branching, reviews, and approval workflows. While these tools can be incredibly useful, they can’t take the place of proper governance. Tools are there to support the system, but they don’t actually define it. Without clear models for contributions and publishing cycles, systems can either spiral into chaos or become too restrictive. Both scenarios can really hold back scalability.</p><p><strong>Designing for the People Who Keep It </strong><br>Running One aspect of design systems that often gets overlooked is the experience of the folks who maintain them. If a system is tough to update, understand, or explain, people will likely avoid it or find ways around it. Design systems should be easy to grasp, not just in terms of visuals but also conceptually. Engineers and product managers need to understand how decisions are made and how changes flow through the system. This shared understanding helps reduce friction and fosters trust among teams.</p><p><strong>Key Principles for Designing a Design System<br></strong>There are certain principles that consistently distinguish scalable systems from those that don’t last:</p><p>• Establish design foundations before diving into components <br>• Prepare for change, not for stability <br>• Focus on long-term scalability rather than quick fixes <br>• Make governance clear and explicit <br>• View the design system as a product, not just a project These principles aren’t limitations; they’re protective measures.</p><p>A design system isn’t something you just finish and forget about. It’s a living entity that you need to continuously shape, maintain, and evolve as your organization grows. When built on solid foundations with scalability in mind, a design system can become an invisible driver of growth. But if it’s treated as just a UI solution, it risks turning into another legacy system that will eventually need to be replaced. The key difference is made early on, at the foundational level, long before the first component is ever shipped.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11eba5bd91f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Copying a Design System Won’t Work for Your Product]]></title>
            <link>https://medium.com/design-bootcamp/why-copying-a-design-system-wont-work-for-your-product-9ecc50b118c9?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ecc50b118c9</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Thu, 18 Sep 2025 05:54:30 GMT</pubDate>
            <atom:updated>2025-09-19T16:24:26.809Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why copying a design system won’t work for your product</h3><p><strong>Design systems are not one-size-fits-all — here’s why tailoring them to your product matters.</strong></p><figure><img alt="Design System Image" src="https://cdn-images-1.medium.com/max/1024/1*WkOmC8U0OSJmQyj7KXtRbQ.png" /><figcaption>Design System Image</figcaption></figure><p>Recently, I was interviewing a designer who proudly shared their design system with me. At first glance, it looked sleek — polished components, neat documentation, and familiar patterns. But as I started asking questions, something didn’t quite add up.</p><blockquote>“Why did you choose this navigation pattern?” I asked.</blockquote><p>There was a pause. The answer hinted back at another source:</p><blockquote>“Well, it’s from Apple’s design system.”</blockquote><p>The more I looked, the clearer it became: many of the components were borrowed directly from well-known design systems — Uber, Ant Design, Apple.</p><p>On the surface, it wasn’t a bad move. After all, these systems are brilliant references, carefully crafted by teams with massive design maturity. But here’s the problem: they didn’t fit the product’s actual needs.</p><h3>Why copying design systems is misleading</h3><p>Every product tells a different story. Every product has its own users, contexts, and requirements. Copying a design system might give you a short-term boost, but in the long run, it breaks down.</p><p>Here’s why:</p><p>Different users, different devices: The devices and environments your customers use could be completely different from the companies you’re copying. What works for Apple’s ecosystem may fail in yours.</p><p>Unique product journeys: Your product’s workflows, feature sets, and cross-platform expectations are unique. A copied pattern often feels forced when the underlying product story is different.</p><p>Sustainability and scalability: A borrowed system rarely scales with your product. The moment your business needs customization or alignment across platforms, cracks start to show.</p><h3>References are fine — but not enough</h3><p>There’s nothing wrong with taking inspiration. In fact, big design systems are excellent for ideation and benchmarking. But they are references, not blueprints.</p><p>If you stop at copying, you risk building something that looks good in Figma but doesn’t make sense in real use.</p><h3>The takeaway</h3><p>Design systems are not one-size-fits-all. They are living frameworks tailored to the story of your product and the needs of your users.</p><p>So, instead of just reusing Apple’s or Uber’s playbook, ask yourself:</p><p>Does this component align with my product’s journey?<br>Will this pattern hold when scaled across my platforms?<br>Am I building for my users, or someone else’s?</p><p>Because in the end, a design system isn’t about copying what already exists — it’s about creating what makes sense for your unique product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ecc50b118c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-copying-a-design-system-wont-work-for-your-product-9ecc50b118c9">Why Copying a Design System Won’t Work for Your Product</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common Mistakes to Avoid When Building an Icon System]]></title>
            <link>https://medium.com/@vandanaprajapati/common-mistakes-to-avoid-when-building-an-icon-system-03c081b4d3fc?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/03c081b4d3fc</guid>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Fri, 04 Oct 2024 15:06:25 GMT</pubDate>
            <atom:updated>2024-10-04T15:06:25.207Z</atom:updated>
            <content:encoded><![CDATA[<p>While icons might seem deceptively simple, constructing a well-structured icon system is a nuanced process. Whether you’re designing icons from scratch or leveraging libraries, meticulous attention to detail is essential for achieving consistency, scalability, and user-friendliness. Despite their diminutive size, icons play a pivotal role in the overall design system. Errors in their creation can lead to significant downstream issues. Here are some common mistakes to avoid:</p><p><strong>1. Unclear Layer Naming</strong></p><p>Precise and consistent layer naming is crucial. Label arrows as “arrow-left,” or “arrow-right,” rather than generic terms like “arrow.” This not only enhances clarity but also streamlines navigation and maintenance, especially as your design system grows.</p><p><strong>2. Flattening Icons</strong></p><p>Avoid flattening icons by combining layers through union operations. While this might seem to simplify the icon, it can hinder future adjustments. Scaling or modifying strokes becomes challenging, leading to inconsistencies.</p><p><strong>3. Excessive Grouping</strong></p><p>Nested groups can complicate your icon structure. Limit grouping to essential levels. Overly complex hierarchies can hinder property application and maintenance.</p><p><strong>4. Overloaded Layers</strong></p><p>Resist the urge to cram all icon properties into a single layer. Design tools like Figma offer variable systems for managing sizes and states efficiently. This approach not only streamlines your file but also makes your design system more adaptable and lightweight.</p><p><strong>Conclusion</strong></p><p>Building a successful icon system demands meticulous attention to detail and adherence to best practices. By prioritizing clear layer naming, avoiding flattening, maintaining a simple layer structure, and leveraging variable systems, you’ll create a scalable, manageable, and adaptable icon set. This investment will save your team time and effort in the long run.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03c081b4d3fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of Simple Questions in Problem-Solving:]]></title>
            <link>https://medium.com/@vandanaprajapati/the-power-of-simple-questions-in-problem-solving-c8552e274136?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8552e274136</guid>
            <category><![CDATA[methods]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Mon, 27 Nov 2023 04:26:42 GMT</pubDate>
            <atom:updated>2023-11-27T04:26:42.051Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Step-by-Step Guide</h3><p>Solving problems is an integral part of life, and the effectiveness of the solutions often hinges on the questions asked during the process. These questions serve as guiding lights, steering the problem-solving journey toward optimal outcomes. Adopting a structured approach supported by simple yet powerful questions can make a significant difference in the problem-solving process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kDr2keyUu-qidjtD.jpg" /></figure><h3>Identifying the Problem: “What’s Going On?”</h3><p>Every problem-solving endeavor commences with identifying the issue at hand. This initial step involves understanding the situation, recognizing the challenge, and defining the problem clearly. Asking, “What’s going on?” helps in setting the foundation for problem-solving by pinpointing the core issue.</p><h3>Gathering Data: “What Do We Know?”</h3><p>Once the problem is identified, the next crucial step is gathering relevant information. This involves collecting data, facts, and insights related to the problem. Asking, “What do we know?” encourages a comprehensive exploration of available information, ensuring a well-informed approach to problem-solving.</p><h3>Analyzing Data: “What Are the Root Causes?”</h3><p>Understanding the root causes behind a problem is pivotal for effective solutions. This phase involves diving deep into the gathered information to discern the underlying factors contributing to the issue. Asking, “What are the root causes?” aids in unraveling the core elements that need addressing.</p><h3>Generating Solutions: “What Could We Do?”</h3><p>With a clear understanding of the problem and its causes, it’s time to brainstorm potential solutions. This step encourages creativity and open-mindedness. Asking, “What could we do?” sparks a multitude of ideas and possibilities, laying the groundwork for potential resolutions.</p><h3>Selecting a Solution: “What’s the Best Thing to Do?”</h3><p>Among the generated solutions, the focus shifts to evaluating and selecting the most viable one. This involves considering various factors such as feasibility, impact, and resources required. Asking, “What’s the best thing to do?” aids in the critical decision-making process.</p><h3>Planning Implementation: “How Do We Go About It?”</h3><p>Once a solution is chosen, the next step is to devise a plan for its implementation. This phase involves outlining the steps, assigning responsibilities, and establishing a timeline. Asking, “How do we go about it?” ensures a structured approach to executing the chosen solution.</p><h3>Implementation and Testing: “Have We Solved the Problem?”</h3><p>With the plan in place, the solution is put into action. This step is accompanied by continuous monitoring and testing to gauge the effectiveness of the implemented solution. Asking, “Have we solved the problem?” prompts ongoing assessment and adjustment if necessary.</p><h3>Continuing Improvement: “Can We Improve What We Have Done?”</h3><p>Even after a problem is seemingly resolved, there’s always room for improvement. Reflecting on the process and outcomes is essential for future problem-solving endeavors. Asking, “Can we improve what we have done?” fosters a culture of continuous improvement.</p><p>In conclusion, the journey of problem-solving is guided by a series of simple yet powerful questions. These questions provide structure, clarity, and direction, leading to more effective and sustainable solutions. Incorporating them into problem-solving processes can significantly enhance problem-solving capabilities, enabling individuals and teams to tackle challenges more proficiently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8552e274136" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to use Stock Images on Social Media.]]></title>
            <link>https://medium.com/@vandanaprajapati/how-to-use-stock-images-on-social-media-5d49b8f476aa?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d49b8f476aa</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[stock-images]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Mon, 04 Sep 2023 14:45:21 GMT</pubDate>
            <atom:updated>2023-09-04T14:45:21.952Z</atom:updated>
            <content:encoded><![CDATA[<p>Numerous novice designers and startups often resort to using images directly from open sources like <a href="https://www.linkedin.com/company/google/">Google</a> <a href="https://www.linkedin.com/company/shutterstock/">Shutterstock</a> <a href="https://www.linkedin.com/company/istockphoto/">iStock</a>, They sometimes neglect to pay for these images, while others go to the extent of hacking into copyrighted images. However, it’s crucial to understand that these practices are ethically and legally incorrect.</p><p>Before you dive into using free images, it’s crucial to grasp these terms that frequently arise when discussing image sources. Make sure to carefully review the terms and conditions of each platform you explore. This way, you’ll have a clear understanding of when and how attribution is required.</p><p>1. Royalty-Free:<br>Royalty-free images don’t necessarily come for free. Typically, you’ll need to pay a one-time fee to acquire the rights for image usage. Subsequently, you can utilize the image multiple times without any further payments. The term “free” in “royalty-free” signifies that you don’t need to pay royalties to the image owner each time you use it.</p><p>2. Creative Commons:<br>Creative Commons, a nonprofit organization, facilitates the sharing and utilization of creativity and knowledge through legal tools. Different Creative Commons licenses offer varying permissions, ranging from unrestricted use without attribution to limited usage with no modifications allowed.</p><p>3. Public Domain:<br>Works in the public domain are those whose copyrights have either expired, been relinquished, or are inapplicable. It’s important to note that just because something is available online doesn’t mean it’s automatically in the public domain.</p><figure><img alt="Image credits: blog.hootsuite.com" src="https://cdn-images-1.medium.com/max/1024/0*yWDOWwkD7WgGo5bD" /></figure><p>Image credits: <a href="http://blog.hootsuite.com/">blog.hootsuite.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d49b8f476aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating Through the Depths of Research Methods]]></title>
            <link>https://medium.com/@vandanaprajapati/navigating-through-the-depths-of-research-methods-9f84eb2f1a8a?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f84eb2f1a8a</guid>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Thu, 17 Aug 2023 16:28:40 GMT</pubDate>
            <atom:updated>2023-08-17T16:28:40.811Z</atom:updated>
            <content:encoded><![CDATA[<p>The role of research in UX design is profound. It acts as a guiding light, shaping the core of creating a better user experience. Research is the compass that reveals the true essence of understanding user needs and behaviors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uXszhO1EzXyje5M7.png" /></figure><p><strong>What is research?</strong><br>Research means seeking answers, solutions, and facts. It involves delving into questions, unraveling doubts, and even explaining things that seem puzzling. Research serves a purpose it helps us understand. <br>“As defined by American sociologist Earl Robert Babbie, research is a systematic investigation to describe, explain, predict, and control observed phenomena. It involves both inductive and deductive methods.”</p><p>In the realm of UX design, many novice designers are familiar with only two types of research: qualitative and quantitative. However, there’s a whole spectrum of research approaches beyond these. Exploring these lesser-known methods can significantly enrich your UX projects.</p><p><strong>1. Basic Research:</strong><br>In UX design, basic research could involve exploring the fundamental cognitive processes behind user decision-making when interacting with an e-commerce website. This research could enhance our understanding of how users navigate online shopping platforms.</p><p><strong>2. Applied Research:</strong><br>Applied research in UX design might focus on improving the checkout process on an e-commerce website. By analyzing user behavior and testing different design elements, designers can contribute to practical solutions that enhance the overall user experience and increase conversions.</p><p><strong>3. Problem-Oriented Research:</strong><br>Problem-oriented research could involve investigating why users are abandoning a mobile app shortly after installation. By identifying the pain points and addressing them, designers can enhance user retention and satisfaction.</p><p><strong>4. Problem-Solving Research:</strong><br>A design agency might engage in problem-solving research when their client’s website experiences slow loading times. By conducting performance audits, identifying bottlenecks, and implementing optimizations, the designers contribute to solving the specific problem.</p><p><strong>5. Qualitative Research:</strong><br>Qualitative research in UX design might involve conducting user interviews to understand how individuals with visual impairments interact with a website’s user interface. This insight can lead to more inclusive and user-friendly design choices.</p><p><strong>6. Quantitative Research:</strong><br>Quantitative research could entail analyzing data from A/B testing to determine whether changing the color of a call-to-action button affects conversion rates on a landing page. By collecting and statistically analyzing large-scale data, designers can make informed design decisions.</p><p>Each type of research in UX design serves a unique purpose, contributing to a better understanding of user behavior, problem-solving, and the creation of more user-centered digital experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f84eb2f1a8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to kick start as a designer when you don’t feel creative enough.]]></title>
            <link>https://medium.com/@vandanaprajapati/how-to-kick-start-as-a-designer-when-you-dont-feel-creative-enough-148566e9b288?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/148566e9b288</guid>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Sat, 03 Dec 2022 18:40:09 GMT</pubDate>
            <atom:updated>2022-12-03T18:40:09.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tg3XFAg5APbygirO.jpg" /></figure><h3><strong>“We all heard this common myth “you are either born creative or not.”</strong></h3><p>In my view, creativity is not binary, Either you have it, or you don’t but in reality, we do all have it. Many believe that creativity belongs to the arts and do not recognize themselves as the “creative person” but it is just a matter of how we interpret it. Trust me it’s not rocket science.</p><p>Did you know that design is considered one of the key skills of the future? and you can become a designer at any point of your life whether you feel like a creative person or not. I am not saying creativity is not required at all but to start as a designer it’s not mandatory for you, you can build it over time while going on your design journey. Creativity was always present in you and it will be always there for you, all you need to do is polish it over time. So it is clear you don’t need to worry about this factor to kick-start your journey as a designer.</p><p>Now what will help you to become a sensible designer, here’s what you can do:</p><h4><strong>Clear your design principles:</strong></h4><p>To start with I can suggest not to directly hop on the software but the best practice is to read more about design, every skill set has certain rules and laws. Designs also have it. Read theories and clear your concepts, to begin with.</p><h4>Read about colors:</h4><p>Colours are a crucial part of the design and every design is incomplete without proper colors. Read about the colors and the psychology behind them, and why certain colors are used in famous brands. Colour evokes many emotions and expressions, and the meaning of it could be different on cultural community level, it is better to have expertise in it when you are a beginner as a designer. I count it as half work is done if you get command of colors and their usage</p><h4>Take inspirations:</h4><p>Take inspirations from other designers, try to learn about the trends, read brand stories, when I say inspiration it doesn’t mean you see and copy it but try to understand why the thing is created I the way that it is. What could be the reason behind adding those particular set of colors, elements, or what the designer try to convey through a particular image/illustration. Ask questions to yourself as much as you and when you work on your next project just approach it in the similar way.</p><h4>Tools:</h4><p>Now most awaited part once you are clear with common designing principle rules and its theory, Now a time for being filmier with some SOFTWARES/TOOLS. To be honest, once you develop the design thinking in you the tools will be never a much issue for you. You can go with any tool of your choice and start creating your design on it or you can be more of traditional designer using pen and paper to ideate, just like me.</p><h4>Copy other’s work:</h4><p>Steel other designers’ work… hold on! what ? To be designer, copying other designers’ work is one of the best practices that help you to grow quickly, Trust me we all have done it, You can choose any designer’s work to replicate and the cache is while replicating their work you need to think like them the colors the spacing the font-weight the particles of the element, Everything you can copy from them and build habit to create useful, aesthetic designs but make sure you keep this work with you only don’t share it publicly or to my advice after finishing it just delete it from your system.</p><h4>Find your design taste:</h4><p>It is important to get maturity after following all the steps and be aware of what kind of designer you are and what is your design taste. It’s very important to develop some kind of design taste that make you stand out from other designers, so over time you can identify for your design style.</p><p>How to build your own design taste? If you observe good design you will develop good design taste but if you get inspiration from bad design sources you will end up having a taste of design. It’s important to choose wisely.</p><h4>Be a part of design community:</h4><p>Try to connect as many designers as you can. You can be a part of design groups, attend workshops, and meet similar kinds of people. How this will help you to accomplish your goal? The answer is it will help you in many ways by joining the communities you can keep updated about latest design trends, and other designing thought processes also whenever you feel stuck, You can exchange your knowledge and be recognized you can ask them without the fear of being judged. You can utilize the power of people.</p><h4>Find a mentor:</h4><p>It could be a life Changer for you if you get the right mentor or a guiding person they will help you in growing your skill set, and in making the right decisions, and gaining new perspectives in designing they will share their knowledge and experience with you and help you where ever you feel stuck.</p><p>And last but not least your learning should never be ended. Always be curious and ready to learn new things it’s your first day, and my only suggestion is to grab as much as you can from others’ experiences.</p><p>Designing is not limited to learning about a tool just be curious to learn everyday things, logic, and the physiology behind it, find solutions to daily life problems and soon you will notice that you become more seasoned in your craft. woohoo! It’s time to celebrate.</p><p>Eventually, you will realize the creativity inside nurtured itself you will feel more open-minded and a confident designer. MY wishes are with you, all the best in your creative design journey we are on the same path and we’ll meet soon again</p><p>thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=148566e9b288" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first INTERNATIONAL TRIP to Dubai.]]></title>
            <link>https://medium.com/@vandanaprajapati/my-first-international-trip-to-dubai-7e6ad4a9130a?source=rss-18536f5803b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e6ad4a9130a</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[dubai]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[international-trip]]></category>
            <dc:creator><![CDATA[Vandana Prajapati]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 19:19:53 GMT</pubDate>
            <atom:updated>2022-11-23T06:48:40.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehCBPesP2e2nkbIg2N0E9Q.jpeg" /></figure><h3>“ Travel is the best investment in yourself” Indeed… YES!</h3><p>Life is about experiences, unlike materialistic things, it’s experience stays with us forever. I must agree our life is a collection of experiences and its intensity.<br>I think it’s enough to give you an idea of what this story is about. This story is about my recent and very first international trip. I want to share this because this experience was very unique for me being a design person. So it started on the 1st of Jan 2022 when I was creating my bucket list for this adventurous new Year. I was motivating myself to add things that I could never imagine doing, I was telling myself that this year I need to push my limits and wanted to be extraordinary someone that I can be proud of so much.</p><p>On my bucket list, I have added that this year I will travel internationally. As it was on my bucket list so I made it possible this year. I went to <strong>Dubai</strong> recently this year in October. and the life lessons I have taken from this trip are priceless. <strong>The first international trip was truly once in a lifetime experience for me.</strong></p><h3>1. If you think it, believe on it you can achieve it</h3><p>Might be I am sounding like a motivational speaker here but trust me it was not easy for me to just pack my bags and travel internationally. It was like dream come true movement for me. If you ask me 5 years back I would have laughed on myself . I was that underconfident, justifying it to family was another case but if you can believe you can achieve somewhere I know that it is on my bucket list and I need to achieve it and I did. No constraints can stop you if you really don’t want to stop yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*3glCRNeUow2LQBW-0h7v2w.jpeg" /></figure><h3>2. Travelling is the best therapy</h3><p>Being a non Traveller requires a lot of effort to prepare my mind to pack my bag, maybe I am not ready for it, or not confident enough or so occupied with other things in life. The past few years my concentrating on my education and career has locked me up to go out and explore. This trip has changed it all it opened up my mind to new aspects of life it gave me the sense that life is not to Limit yourself, but to fly over the rainbow so high, so high.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*a3lDgI0lrIrMMk_WPYyC8Q.jpeg" /></figure><h3><strong>3. I got to know more about myself</strong></h3><p>Being in a comfort zone I have never realized and thought about the aspects of my life. But the movement I step out for my trip I got to know more about myself like- What are my fears, my happiness, and my management skills when I landed in some other country with no internet, no connection in a foreign country that’s courageous for me. I also got to know about my traveling taste all though Dubai is very sweet and kind but it’s all artificially made and I am more of a nature lover kind of person I shouldn’t realize that if I don’t travel to this country.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZSW49-CPNg_lquxXD-GCRQ.jpeg" /></figure><h3>4. World is limitless… yet Limited</h3><p>Before landing in Dubai I was super nervous and had multiple thoughts in mind like how this country gonna look, how their people would be, how they gonna treat me, and what kind of food I am going to find there, but trust me I am all stunned by seeing the kindness and authenticness of the people. It gives me the sense that we all are the same no matter where we live what language we speak what we eat we are all “kind beings.”</p><h3>5. Art is everywhere</h3><p>During my trip, I discovered that I am more of nature loving person rather than liking the artificial thing, Dubai the city of oil and gold is all artificially created but that doesn’t mean I am disappointed. It was a new experience for me to see such a great infrastructure and architecture that is built so precisely, perfectly, and uniquely that deserves a lot of applause. Last but not least after coming back I have seen that I have a limited number of photos on my mobile Dubai but it left me with a smile because I observed everything directly from my eyes, not through a camera might I don’t have many pictures to showcase but I have tons of experiences and feelings to tell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1J91-hDDTdqBC11bOsCsTQ.jpeg" /></figure><p>In the end, this trip gives me a lot of lessons about myself and about other people. It opens my perspective about my beliefs and the world. I wrote this with intention of motivating you to travel around the world and explore your inner self and outer world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e6ad4a9130a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>