<?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 Sepide Moqadasi on Medium]]></title>
        <description><![CDATA[Stories by Sepide Moqadasi on Medium]]></description>
        <link>https://medium.com/@Sepide_moqadasi?source=rss-91ec67f44c3c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*W29ccAClW8uW-x5wtadXfg.png</url>
            <title>Stories by Sepide Moqadasi on Medium</title>
            <link>https://medium.com/@Sepide_moqadasi?source=rss-91ec67f44c3c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:12:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Sepide_moqadasi/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[Feedback Culture: The Invisible Skill That Defines Great Design Teams]]></title>
            <link>https://medium.com/@Sepide_moqadasi/feedback-culture-the-invisible-skill-that-defines-great-design-teams-0e1b82e90ecc?source=rss-91ec67f44c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e1b82e90ecc</guid>
            <dc:creator><![CDATA[Sepide Moqadasi]]></dc:creator>
            <pubDate>Thu, 19 Feb 2026 18:51:45 GMT</pubDate>
            <atom:updated>2026-02-19T18:51:45.082Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started working in product teams, I thought being a good designer was all about visuals, systems, and tools. I quickly learned: the hardest part is not Figma — it’s feedback.</p><p>It’s how you handle disagreement. How you give input. How you respond when someone tells you your work could be better.</p><p>Over the years, I’ve worked in teams of all shapes — freelance gigs, fast-moving startups, long-term products — and one thing is always true: how a team handles feedback shapes everything.</p><p>Here are a few patterns that stuck with me:</p><h3>✦ Choose kindness over niceness</h3><p>Nice is easy. You avoid tension, smile, sugarcoat.<br>Kindness is harder. You say the truth — with care.<br>One helps people grow. The other keeps them stuck.</p><h3>✦ Control your emotions first</h3><p>If you’re in a position of leadership (even informally), your tone carries weight. One reactive moment can shift the team’s mood.<br>Pause. Reflect. Talk it through. Ask for help.</p><h3>✦ Avoid public blame</h3><p>When one person makes a mistake, don’t talk to the whole team as if they all failed. That’s not feedback — that’s shame.<br>Address issues privately. Keep team feedback about the team.</p><p>These aren’t theories — I’ve lived them. I’ve faced the tension and all, but I’ve also learned to treat these moments as challenges in themselves.</p><p>Not every challenge lives in components or layouts — some live in how we communicate, how we adapt, and how we show up in different environments. As designers, we have the tools to navigate complexity — and feedback culture is part of that design space.</p><p>If you’re in a design team — or leading one — consider this an invitation.<br>Reflect on how your culture handles feedback. It might be the most important design tool you have.</p><p>↳ Let’s share and Learn together. <br>🌐 <a href="https://sepide.design/">sepide.design</a><br>🔗 <a href="http://linkedin.com/in/sepidemoqadasi/">LinkedIn</a> | <a href="http://twitter.com/sepide_moqadasi">Twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e1b82e90ecc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Iteration Over Perfection]]></title>
            <link>https://medium.com/@Sepide_moqadasi/iteration-over-perfection-a3c3eb4cdd71?source=rss-91ec67f44c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3c3eb4cdd71</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Sepide Moqadasi]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 21:01:40 GMT</pubDate>
            <atom:updated>2025-08-08T21:01:40.554Z</atom:updated>
            <content:encoded><![CDATA[<p>Working at a fast-moving company taught me how powerful small improvements can be — especially when they’re consistent and intentional. At first, it may not seem like much. But when you keep shipping, updating, and learning along the way, those little changes add up. That’s how you grow a huge platform: step by step.</p><p>The company I joined had multiple projects running in parallel, all in different stages of development. I came on board as an interface designer and got involved in a full redesign of a platform called “Genome”. There were two other senior designers, and several development teams working on different parts of the product.</p><p>We didn’t wait for “perfect.”<br>We shipped.<br>We tested.<br>We adjusted — again and again.</p><p>That’s where I truly learned the importance of function over form. Prioritizing user experience over just the look. Letting go of the perfectionist mindset and embracing the idea of <strong>start small, improve later.</strong></p><p>This shift didn’t just affect my work in the team — it changed how I viewed my personal projects, too.</p><p>When I started building my portfolio website, I didn’t wait for it to be perfect. I iterated through version after version before landing on what’s live now. And even now, I see it as an ongoing task, not something “done.”</p><p>That helped me see portfolios differently:<br>Not just as a static showcase,<br>but as a <strong>living product</strong>.<br>A space we own. A place to reflect, experiment, and learn how to present our skills in the best possible way.</p><p>And yes — I still care deeply about quality. Details, hierarchy, balance, consistency — those matter from day one. <br>But I’ve learned to value momentum over perfection. A good product evolves. A great process allows room for that evolution.</p><p>This mindset didn’t just change how I work — it changed how I think. <br>It taught me that progress isn’t loud or dramatic. It’s quiet. Intentional. <br>It happens every time you choose to ship, learn, and refine — rather than wait.</p><p>That’s how products grow. <br>That’s how designers grow too.</p><p>↳ find me here<br>🌐 <a href="https://sepide.design/">sepide.design</a><br>🔗 <a href="http://linkedin.com/in/sepidemoqadasi/">LinkedIn</a> | <a href="http://twitter.com/sepide_moqadasi">Twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3c3eb4cdd71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Toastification : Yearly Highlights]]></title>
            <link>https://medium.com/@Sepide_moqadasi/toastification-yearly-highlights-783bec8c09ef?source=rss-91ec67f44c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/783bec8c09ef</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Sepide Moqadasi]]></dc:creator>
            <pubDate>Sun, 17 Nov 2024 08:26:45 GMT</pubDate>
            <atom:updated>2024-11-17T08:26:45.597Z</atom:updated>
            <content:encoded><![CDATA[<h3>⚡️ Toastification : Yearly Highlights</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PNAJjhCJkT8b5KpvVMmFDg.png" /></figure><p>Over the past few months, Toastification package has garnered numerous positive feedbacks from different platforms and channels. So, it’s time to review!</p><h4>Before we go, you’ll find references here:</h4><p>📍 Toastification <strong>Website</strong> (<a href="http://payamzahedi.com/toastification/"><strong>Link</strong></a>)<br>📍 Toastification <strong>Github Source</strong> (<a href="https://github.com/payam-zahedi/toastification"><strong>Link</strong></a>)</p><p>The very first version, which was just a preview and not fully functional, still had its own users and received about <strong>120 stars</strong> on GitHub before we published the next version.</p><p>We not only enhanced the visual aspects but also developed an interactive tool! This allows users to interact with controllers and obtain the component code. We’ve reduced complexity and significantly improved the user experience.</p><p>Below, I’m gonna highlight some news about Toastification and its community:</p><h3>🧩 Toastification Used in About 1.3K Open Source Projects!</h3><p>Already about <strong><em>1.3K open source projects</em></strong> are using this package. This Flutter package, shared on GitHub, aims to improve user experiences with its intuitive and customizable notifications. Its extensive use and positive feedback highlight its value in the open-source community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9S8ZSBcmyG8644HoBnxqDg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnPGkw8y_WDO20GV_7kEDg.png" /><figcaption>Link to projects: <a href="https://github.com/AppFlowy-IO/AppFlowy">AppFlowy</a>, <a href="https://github.com/hiddify/hiddify-next">Hiddify-next</a>, <a href="https://github.com/MDeLuise/plant-it">Plant-it</a>, <a href="https://github.com/FlutterFlareLine/FlareLine">FlareLine</a></figcaption></figure><p>I’ve started reaching out to the owners of these open-source projects through emails and LinkedIn messages to get their feedback. This is one of the first testimonials I’ve received, and we’re really grateful for it. (we’ll highlight them all on website.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaihhN52d977MKc1YnaooA.png" /><figcaption>Link to <a href="https://plant-it.org/">Plant-it</a> by <a href="https://www.linkedin.com/in/massimiliano-de-luise?miniProfileUrn=urn%3Ali%3Afs_miniProfile%3AACoAADTtQwQBQmKHq8rSHmvzSLywFWs85095Z14&amp;lipi=urn%3Ali%3Apage%3Ad_flagship3_search_srp_all%3BqKg%2B%2FYnFS7GS4iu3P4ojcA%3D%3D">Massimiliano De Luise</a></figcaption></figure><h3>💙 A Big Thanks to Our 10+ Contributors</h3><p>This project began with the vision and dedication of Payam. Alongside him, I played my role as a designer in clarifying the mission, helping to create the entire product. As the project progressed, several talented contributors joined in to enhance and expand its capabilities.</p><p>We are incredibly grateful for the contributions from the community, and we would like to highlight our top four contributors who played significant roles in this journey:</p><p>— <a href="https://github.com/payam-zahedi"><strong>Payam Zahedi</strong></a><strong><br></strong> — <a href="https://github.com/mahmoud-eslami"><strong>Mahmoud Eslami</strong></a><strong><br></strong> — <a href="https://github.com/SamadiPour"><strong>Amirhosein Samadipour</strong></a><strong><br></strong> — <a href="https://github.com/ayoubrajabi"><strong>Ayoub Rajabi</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gyX34pWXNSzWSVOofk0GNA.png" /></figure><h3>🔭 Github &amp; PUB.dev Metrics</h3><p>And everything we’ve done in designing the tool and the package source has brought significant positive results for the project. Alright, here are some stats that highlight our journey so far, reflecting the progress and improvements we’ve made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YTEfa2HXdKDJK9hhHRHIQ.png" /></figure><h3>What Are These Factors on Pub.dev and Why they Matter?</h3><p><strong>🎉 — Popularity:</strong><em> 99%</em><strong><br></strong>The Popularity section gauges the usage rate of a package. This metric reflects the number of applications that depend on the package over the past 60 days and is presented as a percentile. For instance, a package with a popularity score of 73% is more widely used than 73% of the packages available on <a href="https://pub.dev/"><strong>pub.dev.</strong></a></p><p><strong>⚡️ — Pub points: </strong><em>160 /160</em><br>Reflect the quality of a package. They are determined by evaluating aspects like adherence to Dart file conventions, documentation quality, and the inclusion of examples. Higher pub points indicate a well-maintained and reliable package, helping users to gauge the quality at a glance.</p><p><strong>❤️ — likes:</strong><em> 802</em><br>Essentially user ratings that indicate how much the community appreciates or recommends a package. A higher number of likes suggests that a package is well-regarded and trusted by other developers.</p><h3>🚀 Next Up: We’re adding more Pre-built Notifications into the library!</h3><p>If you haven’t checked out this tool before, this is your sign to explore it now. We’re eager to hear your feedback or answer any questions, so don’t hesitate to share your thoughts or DM us if you’re interested in contributing. We’re currently working on writing test cases for our project, and we’d love your input.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zmnQ6cgXYXOvdXSGg8yzEw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=783bec8c09ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Toastification No-Code Tool v.1]]></title>
            <link>https://medium.com/design-bootcamp/toastification-case-study-b8a1eb622511?source=rss-91ec67f44c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8a1eb622511</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[toastification]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Sepide Moqadasi]]></dc:creator>
            <pubDate>Sun, 03 Sep 2023 06:38:41 GMT</pubDate>
            <atom:updated>2024-10-25T10:21:38.216Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s make interesting notifications as easy as a piece of cake!</p><p>Well, in this story, I’m going to tell you the journey of how could we scale an initial idea to a website like this, which is a free tool for developers!</p><p><strong><em>📄 (</em></strong><a href="https://github.com/payam-zahedi/toastification"><strong><em>Check it on Github</em></strong></a><strong><em>) <br></em></strong>🌐 <a href="https://payamzahedi.com/toastification/"><strong><em>(Live Website)</em></strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pLge81iOJGw1jxA4rpKwYw.png" /></figure><h3>Introduction</h3><p>Flutter is a free and open-source UI toolkit that enables the development of fast, beautiful, and natively compiled applications for mobile, web, and desktop platforms. Our library leverages the simplicity and flexibility of Flutter’s notification and toast styles to provide an open-source solution for creating custom toast and notification widgets.</p><p>I joined <a href="https://medium.com/@payam-zahedi">Payam Zahedi</a>, Senior Flutter Developer at Snapp X, in developing this project. He had already created the initial version, which received about 120 stars on GitHub. To scale up the project, he needed a landing page to showcase this package. That was where I contributed to this project!</p><p>Our initial design goal was to create a landing page. We started by analyzing the websites, and features of our competitors, whether direct or indirect. We realized that we could create a panel for developers, where they could select their preferences and copy the code.</p><h4>So, The process started with Emphasis and understanding...</h4><p>After conducting several meetings to understand the project in-depth, We noticed that our indirect competitors had many features, but they lacked visual appeal and it was as if we never had a direct competitor. Therefore, I proposed some ideas for the concept and the functionalities that we could offer to our users. For instance, enabling them to customize the colors, the placement of the notifications on the screen, and so on. We also provided some additional features, such as real-time overviews of both the code and the notification itself.</p><p>I proceeded to create some hi-fi wireframes for this single-page website and implemented all the features. I also planned some further versions with more features to be developed in the future. We’ll go through the details.</p><h3>Toast types &amp; styles</h3><p>Our notification system has 5 categories, namely Success, Info, Warning, Error, and Custom (the custom category provides different options for users and will be integrated into the next versions) and we called them “Toast types”. Regardless of the category chosen by the user, they will have the option to customize the color style of the notification contents in the next step called “Toast Style”, including texts, icons, and backgrounds.</p><p>When creating a notification for a specific category (except Custom), users can only choose from a limited set of icons and colors. For instance, if users want to create a success notification, they can only choose from a few green colors and icons such as checkmarks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_wpMNx76i2J_jjMVe1h4oQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8hsVSepwvqLdjeYhDuA6w.png" /></figure><h3>Concept of the Logo</h3><p>I enjoy experimenting in my field of expertise, as well as challenging myself with something new, something that I may not have much knowledge about. Designing the logo was such an experience for me, and I am satisfied with the outcome. It was an exciting and rewarding process that helped me discover my potential and talents.</p><p>The primary idea behind the logo is to represent the integration of “Toast” and “Message” in a layered system, which I depicted in a perspective view.</p><p>I also applied the logo mark to create a captivating illustration for the hero section that conveys the idea of crafting notifications with Toastification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gl7cdScuE4T7PLYubtayvw.png" /></figure><h3>User flow</h3><p>The initial idea for the user flow was as follows: Users would select about five options for styling and animating their notification and customizing it. Then, they would see two buttons, one for previewing the result and another one for copying the code.</p><p>After all, I noticed a <strong>usability issue</strong>: users had to click on the preview button every time they wanted to see a preview of the notification and see how it looked with new small changes. This is inconvenient and frustrating. To solve this, I suggest adding a live preview feature that automatically updates the notification as users change the options. Moreover, I added a live preview of the code, which also provided other benefits for users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oHHoQupJQflVmMkaLHdFSw.png" /></figure><p>There are other steps that will be integrated into the next versions like “Notification layout”, which involves designing how icons, titles, descriptions, and other elements should harmonize in a layout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FJmwALPzwdaDiuU3oOcdzQ.png" /></figure><h3>Design a single-page website</h3><p>Our design objective was to create a website that was mobile-friendly and optimized for small devices, considering the panel options and preview sections that we wanted to provide. So I applied grids to create a two-column layout for the content and as the preview sections were important to keep visible for the users, I allocated one of the columns for them and made them sticky to the top.</p><p>Responsive web design is not a one-size-fits-all solution. It requires testing, tweaking, and refining to ensure that your website works well on different devices and browsers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9uhGMKv2mt4KT-Jnc-EEQ.png" /></figure><p>Content that is useful or relevant on a desktop version may not be necessary or appropriate on a mobile version. To address this issue, you can use accordions, tabs, or buttons to hide or show the content as needed. The “Code preview” feature demonstrates this tip well. It is attached to the top of the screen and can be hidden or shown in a dropdown menu. Users can collapse the dropdown to view the code details or expand it to free up more space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ymHt21Jj4SnEh-xSSbnFnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ZR-yEEpwQYW2czSN_FgDA.png" /></figure><p>Also, Toastification offers two ways to preview the notifications that users create. The main preview is the one that appears at the top of the screen and stays fixed. The other preview can be accessed by clicking on the Preview button in the floating group button at the bottom edge of the website, This preview allows users to see how the notifications would look on a realistic screen, whether it is a monitor or a mobile device, and modify the placement, the shadow, and other features as needed.</p><h3>Conclusion</h3><p>Flutter has its own design pattern for different elements, and it also has its own limitations. For instance, only one notification can appear on the screen at a time, and a system for managing toast styles didn’t exist.</p><p>However, by using these design patterns, developers can create customized notifications that are consistent with the overall style of their product and more visually appealing. They can apply different animations, control the time at which toast is on the screen, and even manage the order of notifications. This means that when there is more than one notification on the screen, the next notification will come to the top or at the end of the list! These features will help improve the user experience and make it easier for users to compare digital products with each other.</p><p>Hope you liked it. 🤍</p><p>—</p><p>My email address<br><strong><em>hey@sepide.design</em></strong></p><p>and I’m active these days on<br><a href="https://twitter.com/sepide_moqadasi"><strong><em>Twitter</em></strong></a><strong><em> , </em></strong><a href="https://www.instagram.com/sepide_moqadasi/"><strong><em>Instagram</em></strong></a><strong><em> , </em></strong><a href="https://www.linkedin.com/in/sepidemoqadasi/"><strong><em>Linkedin</em></strong></a><strong><em> , </em></strong><a href="https://dribbble.com/sepide_moqadasi"><strong><em>Dribbble</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8a1eb622511" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/toastification-case-study-b8a1eb622511">Toastification No-Code Tool v.1</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[Activity Focused Design]]></title>
            <link>https://medium.com/design-bootcamp/activity-focused-design-eb6984311953?source=rss-91ec67f44c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb6984311953</guid>
            <category><![CDATA[evaluation]]></category>
            <category><![CDATA[analysis]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Sepide Moqadasi]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 07:48:44 GMT</pubDate>
            <atom:updated>2023-06-14T06:39:05.481Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Activity-Focused design or Activity-Centred design is an approach to identify tasks that users performance with a product.</strong></p><blockquote>As a student of the Experience Design course on IxDF, I have been introduced to the concept of activity-focused design. I would like to share with you a summary of what I have learned.</blockquote><h4>In this method;</h4><p>You’ll find out “What” and “How” users work through the steps to achieve their goals on your app. It could be a part of the Research Phase to find the Task flows or a part of the Test phase to check the user’s steps and improve them.</p><p>There are some methods to design by focusing on activities, like <strong>Task Analysis</strong>, <strong>Jobs to Be Done</strong>, <strong>Activity Theory,</strong> and <strong>Activity-based Design</strong>. I wanna give you some quick tips about the first one “Task Analysis”; keep reading!</p><h3>Task Analysis</h3><p>Before delving into the details of this method, it is important to define some key terms:</p><p><strong>Goal</strong>: End state which the user wanna reach<br><strong>Activity</strong>: A series of tasks that the user do to achieve a goal<br><strong>Task</strong>: Every single unit of action or work</p><p><strong>The task analysis process</strong> involves identifying the user’s goal, documenting the tasks step-by-step, and refining and improving the steps. It can be conducted in both phases of the app development process: Research and Test.</p><p>When analyzing activities in the Research phase for a brand-new app, it is recommended not to mention UI elements in the task’s phrases. However, when working on Test activities for an existing app in the Test phase, UI elements can be used to make it easier to understand.</p><p># We gonna learn with an example, analysis of <strong>Calendar </strong>software!</p><figure><img alt="Mailum — mailbox and calendar service, the product which I’m working on." src="https://cdn-images-1.medium.com/max/1024/1*sra5-_i0s8vLuMQ3ZmQlTQ.png" /><figcaption>Mailum — mailbox and calendar service, the product which I’m working on.</figcaption></figure><p>When analyzing the user’s goal of creating an event in a calendar application during the research and test phases, the task phrases may differ. Let’s explore how they would vary.</p><ul><li><strong>Brand-new Calendar (Task-analysis in Research phase):<br> — </strong>Open the Add Event page<br> — Type a title<br> — Set the date<br> — Set start and end times<br> — Add other participant’s emails<br> — Set a reminder<br> — Add to Calendar<br> — Save the information and event<br><br><em>We did not specify any UI elements, so it is more flexible now to use any elements for each state. For example, if you use “Tap on the save button” instead of saying “Save the information and event”, then it may limit the design options for other interaction methods such as dragging or pushing up anything it might work there.</em></li><li><strong>Existing Calendar (Task-analysis in Test phase):<br> — </strong>Click on the <strong><em>Create button</em></strong><br>— Choose the Event option<br> — Type the title<br> — Set the time<br> — Type the guest’s email address<br> — Add a location or a Google Meet video conferencing link<br> — Add to Calendar<strong><em><br> —</em></strong> Write a Note<br> — Tap on the <strong><em>Save button<br></em></strong><em><br>In this case, we utilized UI elements to clarify the process for users. Let’s see how it works on Mailum — as an existing calendar:</em></li></ul><figure><img alt="Click on the Create button" src="https://cdn-images-1.medium.com/max/1024/1*eRlSOvIyGo41CQGpfh8JAw.png" /><figcaption>1. Click on the <em>Create button</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OIX7C5XnQqVCDfB1l75I4Q.png" /><figcaption>2. Choose the “Event” option</figcaption></figure><figure><img alt="Type the Title" src="https://cdn-images-1.medium.com/max/1024/1*qnp6snbeLFoj5gZMRF4ZLg.png" /><figcaption>3. Type the Title</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_ysA61lGHBlwpp6paw8Tg.png" /><figcaption>4. Set the Date and Time</figcaption></figure><figure><img alt="Type the guest’s email address" src="https://cdn-images-1.medium.com/max/1024/1*5l_O8CZ5s5B34V0NKQh85g.png" /><figcaption>5. Type the guest’s email address</figcaption></figure><figure><img alt="Add a location or a Google Meet video conferencing link" src="https://cdn-images-1.medium.com/max/1024/1*F88skYVQUvI2sA3S9ECuFQ.png" /><figcaption>6. Add a location or a Google Meet video conferencing link</figcaption></figure><figure><img alt="Add to Calendar" src="https://cdn-images-1.medium.com/max/1024/1*-yeFZGmB89FjIIzhvwgPTQ.png" /><figcaption>7. Add to Calendar</figcaption></figure><figure><img alt="Write a Note" src="https://cdn-images-1.medium.com/max/1024/1*cGGMnCKe7JpVUXopMzanVg.png" /><figcaption>8. Write a Note</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XLmu1Llipg6cQFlzNypUKA.png" /><figcaption>9. Click on the Save button</figcaption></figure><p>The ways and templates that can be used to display the results include <strong>Task Analysis Diagrams</strong>, <strong>Hierarchical Task Diagrams</strong>, <strong>Sequence Diagrams</strong>, <strong>Flowcharts,</strong> or any other way which is work for your team.</p><p>This method fails to consider the user’s emotional state and pressures at different stages. When conducting task analysis for an existing application, focusing solely on the current flow and goals can lead to limitations and a design that is backward-looking. However, It works well when you are working on design solutions that they depend on task orders and completion.</p><p><strong><em>Reference</em></strong><em>:</em> <a href="https://www.interaction-design.org/courses/user-experience-the-beginner-s-guide?r=sepide-moqadasi"><em>“User Experience: The Beginner’s Guide” is a course offered by the “Interaction Design Foundation” school</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb6984311953" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/activity-focused-design-eb6984311953">Activity Focused Design</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>
    </channel>
</rss>