<?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 Niloofar zabardast on Medium]]></title>
        <description><![CDATA[Stories by Niloofar zabardast on Medium]]></description>
        <link>https://medium.com/@niloozabardast?source=rss-c72715b4f99c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6Is9-zdOrnGleYZlceR1SA.png</url>
            <title>Stories by Niloofar zabardast on Medium</title>
            <link>https://medium.com/@niloozabardast?source=rss-c72715b4f99c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:14:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@niloozabardast/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[Lessons learned: a UX Designers journey]]></title>
            <link>https://medium.com/@niloozabardast/lessons-learned-a-ux-designers-journey-51b6c0319eb?source=rss-c72715b4f99c------2</link>
            <guid isPermaLink="false">https://medium.com/p/51b6c0319eb</guid>
            <dc:creator><![CDATA[Niloofar zabardast]]></dc:creator>
            <pubDate>Thu, 25 May 2023 10:59:20 GMT</pubDate>
            <atom:updated>2023-05-26T09:42:34.867Z</atom:updated>
            <content:encoded><![CDATA[<h4>Practical advices for navigating the challenges of cross-functional teams</h4><figure><img alt="illustrated by me" src="https://cdn-images-1.medium.com/max/1024/1*hQdW94ltwB61cWUDzsTuWQ.png" /><figcaption>illustrated by me</figcaption></figure><p>It has been nearly two years since I began my journey as a UX Designer at Divar, the Leading online classified ads platform in Iran with over 35 million registered users across its website, Android and iOS applications with 350,000 new daily listings. Prior to Divar, I had been working as a product designer at Sociext for approximately two years, where I gained valuable experience in designing and developing digital products.</p><p>Through my experiences, I’ve encountered challenges and setbacks in various projects. However, instead of dwelling on the negatives, I’ve taken the opportunity to reflect on what went wrong and how things could have been improved. Over time, I’ve collected valuable insights and lessons that I believe can benefit other designers and professionals in the field.</p><p>I’ve distilled these experiences into six key bullet points which I’ll be sharing with you.</p><p><strong>1-The Art of Asking the Right Questions</strong></p><p>I’ve realized that one of the most important aspects of my role as a UX designer is to ask the right questions to understand the users’ needs and pain points. This involves asking questions that go beyond the surface level and digging deeper to uncover the underlying issues.</p><p>asking the right questions is not just about being curious but also about being strategic. It’s about knowing what questions to ask and when to ask them, and how to phrase them in a way that elicits the most useful responses. It’s about knowing how to listen actively and ask follow-up questions to get to the heart of the matter.</p><p><strong>2- The Pitfalls of Treating Hypotheses as Facts</strong></p><p>As UX designers, sometimes we rely on hypotheses to guide our decision-making processes. However, it’s important to remember that hypotheses are not facts, and treating them as such can lead to serious pitfalls.</p><p>One of the most significant dangers of treating hypotheses as facts is that we may become too invested in them. We might ignore evidence that contradicts our assumptions, or we might focus too much on proving ourselves right rather than exploring all possible options. This can lead us down a dangerous path of confirmation bias, which can ultimately lead to poor design decisions.</p><p>instead, we should approach our hypotheses with a healthy dose of skepticism. We must be willing to test and iterate on our ideas, even if it means abandoning them altogether. We should also seek out diverse perspectives and feedback from others, including our teammates and users. By doing so, we can avoid the pitfalls of treating hypotheses as facts and make more informed design decisions.</p><p><strong>3- The Importance of Incremental Design</strong></p><p>As a perfectionist designer in an agile team, I’ve learned the importance of speeding up my design process without sacrificing quality. Incremental design has been the solution that worked for me. It involves breaking down the big problem into smaller pieces, which takes less time for each step while still maintaining a high level of quality.</p><p>Incremental design also allows for regular check-ins and user feedback, which helps to ensure that the final product meets the needs and expectations of users. This approach also allows for more flexibility in the design process, allowing for changes and adjustments to be made along the way.</p><p>4- <strong>Avoiding Solution Bias</strong></p><p>It’s important to avoid solution bias and instead focus on the problem at hand. While it’s common for designers to be presented solutions, it’s important to take a step back and analyze the problem objectively. This means considering all possible solutions and evaluating them based on their efficiency, cost, and potential impact on the user experience. By focusing on the problem first, we can avoid developing solutions that don’t address the root issue and ensure that our designs are truly effective.</p><p><strong>5-</strong> <strong>Balancing Analysis and Action</strong></p><p>As a detail-oriented person who enjoys diving deep into analysis, I found myself getting lost in analysis paralysis at times. However, I realized that this approach didn’t always align with the needs of my agile team. To address this, I started balancing my analysis with action. For smaller tasks, I limited the time spent on analysis and focused on action, while for bigger tasks, I allowed for more analysis to ensure we’re on the right track. I learned that finding the right balance between the time spent on a project and the outcome presented is crucial, especially when the two don’t match. It’s essential to make sure the team understands and agrees that the time spent was worth it.</p><p><strong>6- The Myth of One Magical UX Approach</strong></p><p>This is a common misconception that there is a one-size-fits-all solution to all design problems. However, I’ve learned that each problem and project is unique and requires its own approach and there is no single solution or template that fits every situation.</p><p>While there may not be a single solution, there are principles and best practices that can be applied to ensure success. it’s important to recognize that each project presents new challenges, and it’s essential to approach them with an open mind and a willingness to adapt to each situation. The key is to stay curious, be willing to learn from others, and stay flexible in your approach.</p><p>I would love to hear your thoughts and feedback on my article, or even any personal experiences you have had with the topics discussed. Please feel free to reach out to me at <a href="http://niloozabardast@gmail.com/">niloozabardast@gmail.com</a> with any comments or questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51b6c0319eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>