<?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 Nardos Mechal on Medium]]></title>
        <description><![CDATA[Stories by Nardos Mechal on Medium]]></description>
        <link>https://medium.com/@nardosiam?source=rss-5cf1369a8781------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3ICOz55RRucCn3Mh09gsZw@2x.jpeg</url>
            <title>Stories by Nardos Mechal on Medium</title>
            <link>https://medium.com/@nardosiam?source=rss-5cf1369a8781------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:24:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nardosiam/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The design of making an impact]]></title>
            <link>https://medium.com/design-bootcamp/the-design-of-making-an-impact-501ce651c5ec?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/501ce651c5ec</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Wed, 25 Oct 2023 23:31:05 GMT</pubDate>
            <atom:updated>2024-01-09T02:27:39.291Z</atom:updated>
            <content:encoded><![CDATA[<h4>How are we shaping people and the future with our work?</h4><figure><img alt="the design of making an impact title on a green background" src="https://cdn-images-1.medium.com/max/1024/1*DfsI-JVQVxQhfb0f05sP0Q.png" /></figure><p>One of the first things one of my design mentors warned me about that I still carry with me is the dangers of being reckless — or worse indifferent — to people and our planet. He stressed the importance of never allowing myself to misuse the responsibilities I have as a designer. At the time I thought, “<em>are all designers this dramatic?” &amp; “what does this have to do with components?” </em>But now I get it.</p><p>What he meant was, we cannot be indifferent towards the people and the realities in which they live in when designing experiences. Not only does our work have the potential to shape people’s behavior and their interactions around our product, it can also shape how they navigate the world on a wider context. If we want our designs and work to resonate with our users’ humanity and deep understanding of the world, we need a careful examination of our audiences and the culture, world and thinking that define how they perceive visuals and products.</p><p>On the planetary side of things, we need to conceptualize our products and services in ways that fit within our planet’s boundaries. It is no longer enough to focus on desirability and viability, we have to create designs and solutions for society that are also responsible and transparent.</p><blockquote>Indifference towards people and the reality in which they live is actually the one and only cardinal sin in design.</blockquote><blockquote><em>-Dieter Rams</em></blockquote><p>The desire to create change and work on projects that aim to do so has always been a great source of fuel for me. I’ve contributed at educational apps aimed at different age groups including children with ADHD and websites for local non-profits. I’ve pursued personal projects addressing maternal healthcare and eco-sustainability. In my personal life, I’ve worked in neuroimaging research for Alzheimer’s patients, volunteer in cancer centers for chemo patients, and build efforts to reduce health disparities in dentistry for underserved communities, including children with neurodevelopmental disorders. I am constantly searching for work that fulfills me and uses me as a vessel to bring some good in the world.</p><p><strong>But the thing is <em>how</em> do we take on such a grand responsibility as designers?</strong> I suspect it&#39;s something we continuously learn throughout our lives as I’m still figuring it out especially early in my career.</p><h4>The design of sustainability</h4><p>Recently, I’ve been really interested in the concept of <a href="https://planetcentricdesign.com/">planet centric design.</a> It is a branch of UX with a methodology for designing products and services that do not create harm for our planet. Sure, I reuse and recycle, and try to incorporate other eco-friendly practices in my life as much as I can but I have never really considered the ramifications of my job on the planet. Not many consider the environmental footprint of the Internet, and when they do, they often perceive digital content and services as a greener option compared to conventional products and services. And since we are problem solvers, what better problem to tackle than one of the <strong>most </strong>pressing problems we are experiencing collectively.</p><p>Every email sent, every click, every image posted uses energy and starts a dialogue with data banks that are run by non-renewable energy sources and fed with an <em>insane </em>amount of electricity and water. With billions of users every day, it’s no wonder that <em>“If the internet were a country, it would be the 6th largest user of electricity behind China, the US, Japan, India and Russia”</em> according to one report in 2014 by Greenpeace. This is where designers come in since the energy consumption of digital products are determined largely by our decisions made during the design phase. Providing a streamlined workflow that minimizes action, information overload and distractions for users so they can be more efficient is crucial. This enables our users to spend less time and therefore less energy while browsing our sites.</p><figure><img alt="Graphic showing how to optimize interface by removing background videos,, carousels, gifs and buttons" src="https://cdn-images-1.medium.com/max/1024/0*iaQ-WjZow3MvaKq-.jpg" /><figcaption>Image from <a href="http://pixetic.com/">Pixetic.com</a></figcaption></figure><p><strong>Some tips on minimizing the negative impact of UX and doing our part.</strong></p><ul><li>Reduce the number of typefaces. This allows for faster page loading and uses less energy.</li><li>Do you really need all of those images and gifs on one page? And if you insist, how about less auto-play for videos and lazy load for images?</li><li>Reduce number of data-heavy components and complicated interactions as reducing image file size.</li><li>Optimize your website’s performance by looking at insights and with things like reducing the number of HTTP requests.</li><li>Are constant push notifications necessary? (I’m looking at you MyFitnessPal).</li></ul><p>These are just some ways to reduce the impact of our design on the climate, making sure its cost efficient and resource (planet) efficient.</p><h3>What does it mean for design to be impactful?</h3><p>We think of ourselves as problem solvers, and we are. And lately I’ve been thinking about how almost all design is a form of redesign. Each problem we solve adds to a collection of solutions, growing and evolving through time, shaped by the successes and lessons of those that came before it. And our solution now sets a precedent for how this problem can be solved subsequently. If successful, this solution is not only going to impact its intended users but other people who will come after this and deal with the same problem you’re solving. It seems uncomplicated but it is really cool to think about.</p><p>Whether you want to champion sustainability or drive positive change in causes that matter to you, design is an artform that empowers us to create a meaningful impact through our work. And with that comes a responsibility to help build a sustainable and accessible future to our fellow humans and our planet.</p><h4>Word from writer</h4><p><em>This is just the beginning of the rabbit hole I’ve found myself in and I’ll probably (definitely) write more detailed articles on this topic. Thanks for reading my ramblings so far &amp; find me on Linkedin if you want to talk or </em><strong><em>work together!</em> </strong><em>Stay Joyful -N</em></p><p><strong>Resources:</strong></p><ul><li><a href="https://pixetic.com/blog/sustainable-design/">What is a sustainable design and why should we care?</a></li><li><a href="https://www.wholegraindigital.com/team/tom-greenwood/">Tom Greenwood - Wholegrain Digital</a></li><li><a href="https://planetcentricdesign.com/">Planet Centric Design - Planet Centric Design</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=501ce651c5ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-design-of-making-an-impact-501ce651c5ec">The design of making an impact</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I boosted productivity by 35% after crafting a semantic color system.]]></title>
            <link>https://medium.com/design-bootcamp/how-i-boosted-productivity-by-35-after-crafting-a-semantic-color-system-81858a29f5f3?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/81858a29f5f3</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 15:17:16 GMT</pubDate>
            <atom:updated>2023-10-24T18:15:02.671Z</atom:updated>
            <content:encoded><![CDATA[<h4>Colors that improve communication and just make sense.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6yS4Oy7flk-y4NP0Fy00eA.png" /></figure><p>I recently worked as a solo designer for an edtech b2c that provides customized help for college students. <strong>While working on improving onboarding and subscription growth, one of the main challenges I saw was the lack of standardization in current color use</strong>. As the tutoring platform is rapidly expanding and more institutions adopt it, it has become exceedingly important to establish a unified language and consistent visual system across all aspects of our product. And using Semantic Color Theory, I was able to <em>propel our team’s productivity by 35%.</em></p><p>(I know what you’re thinking; she’s writing yet another article about design systems, but this is it I promise… for now!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*H_igzj65qLJfTprJ.gif" /><figcaption>Check out my article on <a href="https://medium.com/@nardosiam/using-an-atomic-framework-to-recreate-apple-maps-design-system-17a1e1ae9286">using an atomic design framework for Apple Maps here!</a></figcaption></figure><p>As designers, you’ve likely heard the terms “semantic” and “color” tossed around in design circles. Semantic color theory is another theory that makes our job easier by naming colors based on how they’re used rather than how they look. This system can help <strong>present a scalable, efficient and collaborative solution </strong>to reduce development timelines and high internal effort.</p><h4>How we managed colors before vs now</h4><p>While we had color palette, we had no clear guidelines on how and where to use them. It was up to the discretion of whoever was using them at the time. We also had multiple color variations and version of the same component.</p><p><strong>From an appearance-based color scheme…</strong></p><figure><img alt="our old color guide annotated on one of the screens" src="https://cdn-images-1.medium.com/max/1024/1*j5ZqzGhXlbLL_-OkYUI8rQ.png" /></figure><p><strong>… to a semantic-based color scheme</strong></p><figure><img alt="our new color guide annotated on one of the screens" src="https://cdn-images-1.medium.com/max/1024/1*hWiEoN2y7iJ8c0dBXyM4vA.png" /></figure><p><strong>Triumph in the midst of initial pushback</strong></p><p>Per the Design System Efficiency Curve, implementing a new design system initially lowers productivity before soaring to new heights. Despite initial hesitation from the front-end team, I strongly advocated for its adoption, emphasizing the long-term benefits and reduced workload.</p><p><strong>After conducting meetings and testing with the team to define the best way possible to name our colors and best practices with naming design tokens, it was game on.</strong></p><h4>⚡<strong>Advantages of implementing a Semantic Color System</strong></h4><ol><li><strong>Improved flexibility: </strong>Since the system uses clear guidelines and is able to be modified easily, it helps the product stay unified even as it evolves.</li><li><strong>Eliminates uncertainty &amp; guess work:</strong> Rather than needing to memorize every different combination to decide what color to use, you can just simply update the value for the primary color. This helps streamline the design and development process entirely.</li></ol><p>I looked into many different approaches during my research because I knew that we could potentially end up with a lot of color variables for every UI element in every state and adding too much detail can even be more complicated. I found companies such as Shopify that utilize this system for inspiration before delving into our product.</p><figure><img alt="Design system with naming convention from Shopify Polaris" src="https://cdn-images-1.medium.com/max/1024/0*t5FHpu5Sh9xQAj3X.png" /><figcaption>Shopify Polaris</figcaption></figure><h4>🔑Our new semantic color system using tokens</h4><p>Having never done this before, I wanted to make sure this system has a clear set of guidelines so everyone in our team can benefit from it rather than just me. Having the naming refer to the UI element and state of said elements makes implementation so much easier than having an appearance based system that can be very subjective.</p><p>I created the following problem statement so my solution can address all parts of our most pressing issues:</p><blockquote>How can we create a color system with strong guidelines that is easy to understand so we can improve communication and productivity?</blockquote><p><strong>Creating our base palette</strong></p><p>I looked at our brand and selected core colors that were already used throughout our product as well as adapted more shades to create a larger pool of colors that can be combined to create all the colors we can use in our designs.</p><figure><img alt="display of colors for our base palette" src="https://cdn-images-1.medium.com/max/1024/1*OC1RWbKSL5ytVE8ycaFoCQ.png" /><figcaption>Base palette</figcaption></figure><p><strong>Our new semantic colors</strong></p><p>Using our base colors as reference, I began to build our semantic colors by working closely with our front-end team since they were a lot more familiar with tokens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S9sitjvyAPYwLN9dQ_rJNA.png" /><figcaption>Guidelines for our naming using tokens.</figcaption></figure><p>Using our naming conventions as a guide, I began to construct our large semantic color design system with all the colors that are used throughout our product and their role for easy referencing. This document was to serve as a straightforward source of truth that improves communication between everyone.</p><figure><img alt="Soure of truth document created form guidelines for easy reference with colors listed alongside their roles and token" src="https://cdn-images-1.medium.com/max/1024/1*lHmiq0oOwx2qVM1o5Kq_wA.png" /><figcaption>Source of truth document created form guidelines for easy reference</figcaption></figure><h4>🌈<strong>Happy ending &amp; impact</strong></h4><p>Through utilizing design tokens, we crafted a shared language to improve communication throughout our teams. Thanks to our unified guidelines, we eliminated multiple versions of the same component and color variations that were a main source of confusion. Our front-end developers reported a 35% increase in their work speed. And because it reduced the need to make manual choices regarding colors for components and made designing new interfaces easier, I was able to complete my designs almost 50% faster and give more time to my design process.</p><blockquote><strong><em>Just by changing our approach to color and naming conventions, we unlocked new heights in our productivity where our work can focus on </em>making intentional and purposeful design decisions for our students!!</strong></blockquote><p><em>Thanks for reading! Stay joyful -N</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81858a29f5f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-boosted-productivity-by-35-after-crafting-a-semantic-color-system-81858a29f5f3">How I boosted productivity by 35% after crafting a semantic color system.</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[Using an atomic framework to recreate Apple Map’s design system]]></title>
            <link>https://medium.com/@nardosiam/using-an-atomic-framework-to-recreate-apple-maps-design-system-17a1e1ae9286?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/17a1e1ae9286</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Sun, 23 Apr 2023 15:32:17 GMT</pubDate>
            <atom:updated>2023-10-26T15:20:28.372Z</atom:updated>
            <content:encoded><![CDATA[<h4>what better way to learn design systems than to deconstruct and rebuild…</h4><p>When I first started the journey of learning design systems, I was instantly fascinated by Brad Frost’s Atomic Design. Entire systems made up of elements that serve as building blocks to create digital products. It satiated both my neurochemistry background and my newly found interest in design systems. It just all made sense.</p><blockquote>Brad Frost first describes Atomic Design as a framework to craft design systems resulting from five separate steps working to build a more cohesive and hierarchical interface system.</blockquote><figure><img alt="gif showing the 5 stages of atomic design ranging from Atoms, Molecules, Organisms, Templates, and Pages." src="https://cdn-images-1.medium.com/max/1024/0*Py-nEVv8TTyE1Fuh.gif" /><figcaption>The five stages of Atomic design (<a href="https://bradfrost.com/blog/post/atomic-design-in-one-gif/">bradfrost.com</a>)</figcaption></figure><h4>How I (re)built an atomic design system: Apple Maps version</h4><p>It was a passion project I started involving adding a new feature <a href="https://www.nardosiam.com/work/applemaps">(Case study here)</a>, <strong>showing eco-friendly routes or businesses to encourage sustainability practices among users</strong>, that sparked the interest. I decided that the best way to put what I was learning about design systems to good use was attempting to recreate a system that not only exists (thank you Apple Human Interface Guidelines!!) but is so widespread.</p><p>In order to utilize Frost’s bottom-up approach in creating reusable elements, I actually utilized a framework that built upon Frost’s ideas but has a very basic nucleus level which is the visual stylings like the shapes, shadow effects, color guide and typography of the system. I pulled hex codes on Figma from screenshots of Maps I had taken on my phone.</p><figure><img alt="the color palette and typography" src="https://cdn-images-1.medium.com/max/1024/1*c3xAmOiG39Gm_4YHapumwg.png" /></figure><p>I then went on to what Frost calls the Atoms which are individual elements like buttons, input boxes, icons and badges that aim to create consistency and cohesiveness in the design. I also created the “eco-leaf” or “Go Green badge”, an icon resembling a green leaf, to indicate the new eco friendly feature and increase discoverability.</p><figure><img alt="buttons, sheets and other elements that serve as the atoms in the design" src="https://cdn-images-1.medium.com/max/1024/1*YCqbPrQzosvuTkYAPe2lhQ.png" /></figure><p>These groups of nuclei and atoms helped me create the more complex and truly functional elements of my page such as the molecules and organisms.</p><figure><img alt="elements serving as organisms in the design" src="https://cdn-images-1.medium.com/max/1024/1*QUSrwteEwcRVFX5LoPwU2A.png" /></figure><h4><strong>How recreating a design system using Atomic Design helped me save time</strong></h4><ol><li>By breaking the whole system down, I was able to easily assemble the basic components to make bigger components.</li><li>It helped me document design components and patterns clearly which allowed me to <em>focus on the other complexities</em> of adding a new feature to an existing product and challenging current systems.</li></ol><figure><img alt="6 Selected screens from adding an eco friendly feature design for apple maps" src="https://cdn-images-1.medium.com/max/1024/1*g4QbJbJVXK6bt5PvivOjYg.png" /><figcaption>Selected screens from my design (see full case study here)</figcaption></figure><h4>Adopting an Atomic mindset</h4><p>Although this framework revolutionized the way we create digital products and experiences today, this hierarchy of elements is still interpreted differently from person to person. It certainly is not a fix all to problems we encounter as designers. While this framework helps us create consistent and scalable systems that can be reused anywhere, designers need to be able to build and expand upon it in ways that our team/product needs.</p><h4>Next on learning</h4><p>I want to continue along this path and create a UI Kit for an existing brand to share with the design community on Figma. That way, I can aid other designers in working on their ideas rather than spending hours creating components from scratch.</p><p><em>If you have any feedback or want to connect and work together, here’s me on</em><strong><em> </em></strong><a href="http://linkedin.com/in/nardosmechal"><strong><em>LinkedIn</em></strong></a><em>👀</em></p><p>Stay joyful-N</p><p>Resources to learn about design systems: <a href="https://www.nngroup.com/articles/design-systems-101/">https://www.nngroup.com/articles/design-systems-101/</a></p><p><a href="https://developer.apple.com/design/human-interface-guidelines/guidelines/overview/">https://developer.apple.com/design/human-interface-guidelines/guidelines/overview/</a></p><p><a href="https://atomicdesign.bradfrost.com/chapter-2/">https://atomicdesign.bradfrost.com/chapter-2/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17a1e1ae9286" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The UX case study that didn’t get me hired- failure to success]]></title>
            <link>https://medium.com/design-bootcamp/the-ux-case-study-that-didnt-get-me-hired-2675c3974d1a?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/2675c3974d1a</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Tue, 18 Apr 2023 17:36:42 GMT</pubDate>
            <atom:updated>2023-10-24T18:13:08.550Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sometimes it’s nice to be candid… take a breather and rethink your process.</h4><p>A few months ago, I wrote about <a href="https://medium.com/@nardosiam/nebulla-app-a-ux-case-study-39fc64dc4183">Nebulla</a>, a project I worked on to address the maternal health divide in communities of color in the US. It was a topic I was well versed in through my studies in health disparities and one that was dear to my heart. I set out to tackle a daunting project that I initially felt confident in but unfortunately, it just did not hit the mark.</p><p>While tirelessly shifting through hundreds of articles showing brilliant case studies that got designers their jobs, I figured it might also be worthwhile for others to see those that are in the<em> process of evolving</em>. Iterating is part of the job right?</p><blockquote>😪</blockquote><blockquote>It’s always soul crushing seeing something you spent hours researching, story boarding, customer journeying, sketching, wireframing, prototyping, — you get it — failing to communicate what you set out to do.</blockquote><figure><img alt="screenshot of screens from Nebulla app" src="https://cdn-images-1.medium.com/max/1024/1*7oHNONtBnOGyMeLzvDX43g.png" /></figure><h4>What went wrong?</h4><blockquote><em>It is important to filter every single decision made through the lens of intention.</em></blockquote><p>Designing an end-to-end experience goes beyond simply optimizing systems to make them enjoyable. As designers, it is crucial to be focused on the continuous improvement of our users’ journey. Knowing this now, I want to reflect on some parts of my design process for Nebulla that were less than optimal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*gUW_XhkO2FOjLpWU" /></figure><p><strong>Fell in love with the solution, not the problem</strong></p><p>While attempting to solve the problem, I was coming up with too many contradicting solutions that testing proved to be ineffective and confusing for users. Its important to note that <strong><em>the design is only as effective as the user who understands it the least. </em></strong>Developing a deep understanding of the problem and its impact on the users is vital to carving a path that gives value to our users.</p><figure><img alt="visual of painpoints and opportunities" src="https://cdn-images-1.medium.com/max/1024/1*qk71WLJlRS1SWW5Vtu6J6A.png" /><figcaption>Understanding and organizing the problem in the early stages</figcaption></figure><p><strong>Did not have any methods to measure success</strong></p><p>I did not have a clear method of measuring impact that would otherwise provide data to inform my decision making. Defining metrics is key in uncovering news ways to shift the project’s focus, examine my key tasks and create accountability which are all essential in driving progress for my product.</p><p>Some ways I could have utilized core UX metrics to track my products success are measuring the increase in the number of “saves” of practitioners after incorporating filters, or measuring conversion rate after users complete the questionnaire to match them to their preferred pre-natal providers. After revisiting these methods and pairing them with my qualitative research, I was able to track changes over time and gain a bigger picture of how my product performs.</p><p><strong>Was not seeing the full picture</strong></p><p>Another mistake I made, perhaps the worst one was not taking a step back to regularly do a reality check. I was so focused on perfecting every detail, I lost sight of who I was designing for. I became tied to the end goal rather than the process and users. I needed to ask myself questions to ensure that my goals was aligned with the intention of the project. Was I solving the problem or was I creating more problems? I then began to <strong><em>filter every single decision I made through the lens of intention.</em></strong></p><p>When designing an end to end experience, it’s important to ask these questions:</p><ul><li>What are the constraints?</li><li>How can I work around said constraints?</li><li>What are the assumptions I’m making here?</li><li>How does the solution provide value to my users?</li><li>How can the solution measure up against success metrics? In fact, how do I even measure success?</li></ul><p>These help us towards a design that successfully communicates its intention and purpose.</p><h4>Rethinking my design process</h4><p>I had to take a step back and deconstruct my design process form the ground up. Before jumping into iterating to fill the gaps between my understanding of my users and their experiences, I began by organizing all my work into manageable pieces.</p><p><strong><em>💡 Tip for Figma users:</em></strong><em> </em><a href="https://www.figma.com/community/plugin/801195587640428208/Design-Lint"><em>Design Lint</em></a><em> is a great plugin to help you keep your designs consistent and quickly find errors.</em></p><p>I revisited my customer journey map and added to it to get a clearer view of how users engage with my product and how I can guide them to meet their goals. This exercise was particularly helpful to me because it helped me redefine the project’s goal and scope. I was then able to conduct deeper usability studies early on that helped me understand key performance metrics related to my product’s usability and task success using the System Usability Scale framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*GoF6qiuKPl2556sM.gif" /></figure><h4>Lessons through failure</h4><p>Obviously, one case study does not make or break your career. You have to judge yourself as an applicant holistically. But since then, I have received so much valuable feedback from other designers (shoutout ADPlist and my mentors) on how I can strengthen this project specifically. Although I am still in the process of searching for a role, I can now confidently explain every design decision I made and feel proud of this project (glass is half full situation if you will).</p><p><strong>The success is in creating a design that effectively communicates what you set out to do.</strong></p><p>It’s always good to learn from our process and pinpoint where it went wrong. There’s no shame in failure and being able to communicate what we could have done differently, demonstrates flexibility and ability to apply feedback. I wrote this because it is equally important to share our failures and what we learned from them. And <em>that</em> my friends is essential in any design job. <strong>The time will come, we just need to improve in any way that we can to prepare in the meantime.</strong></p><figure><img alt="Gif of man with green orbs on his hands screaming “finally, I’ve found my glorious purpose” probably a scene from a movie" src="https://cdn-images-1.medium.com/max/498/0*yrN9nHli4RbpOXGd.gif" /></figure><h4>Word from writer</h4><p><em>Anyone else in the same boat as me, </em><strong><em>focus and keep improving</em></strong><em> it will all be worth it!! 🌟</em></p><p><em>If you want to connect or want to work together, find me on Linkedin, I&#39;d love that!</em></p><p>Stay Joyful — N</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2675c3974d1a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-ux-case-study-that-didnt-get-me-hired-2675c3974d1a">The UX case study that didn’t get me hired- failure to success</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[Nebulla App — a UX case study]]></title>
            <link>https://medium.com/@nardosiam/nebulla-app-a-ux-case-study-39fc64dc4183?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/39fc64dc4183</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[maternal-health]]></category>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Thu, 20 Oct 2022 03:18:42 GMT</pubDate>
            <atom:updated>2022-10-20T03:18:42.569Z</atom:updated>
            <content:encoded><![CDATA[<h3>Nebulla App — a UX case study</h3><p><strong>Designing an end-to-end app to address the maternal health divide in communities of color in the US.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9kmgBgU4DwXVye9jjLwbYg.png" /><figcaption>Check out the simplified version on <a href="https://www.nardosiam.com/work/nebulla">Nardosiam.com</a> :)</figcaption></figure><p>I spent the latter parts of June 2022 grappling with the supreme court’s decision to overturn Roe vs Wade, the landmark case that protected the fundamental right to privacy. Studying health disparities and working with medically underserved communities for about 3 years, this hit too close to home. This life altering decision impacts everyone in the country in some way but it especially heightens the disproportional rates of maternal mortality in the US that put people of color, especially Black women at risk.</p><p>And so while thinking of a solo project I could embark on, I wanted to choose a problem I’m deeply passionate about helping solve and this seemed like the perfect fit. I wanted to find a way to amplify POC voices when it comes to the quality of healthcare they receive, and thus, <strong>Nebulla was born…</strong> (a name formed while watching the James Webb telescope image release which I thought was well fitting)</p><h4><strong>Clarifying the problem space</strong></h4><p>Despite advancements in medical care, there remains a huge racial disparity in maternal and infant health in the United States. A statistic that utterly shook me was the fact that<em> over 60 percent </em>of pregnancy-related deaths are preventable according to the CDC. One major contributor is implicit bias.</p><p><strong>Implicit bias, including your race, class, gender identification, marital status, or even sexual orientation can impact the quality you receive from healthcare providers.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QsMRBzO-p7fsMPhBvSdX_w.png" /><figcaption>CDC.gov</figcaption></figure><p>When crafting the idea for Nebulla, I wanted the focus to be on the last two factors that shape health outcomes in our communities: community social context and the health care system. How can we do better?</p><h4><strong>Research</strong></h4><p>My research plan revolved around one central question; How can I amplify the voices of pregnant people of color when it comes to the quality of healthcare they receive while also providing a community based support system to reduce the racial disparities in maternal health in the US? I listed qualitative goals to reach from my user interview insights.</p><p><strong>Goal #1: Identify the most challenging aspects of pregnancy and seeking care as a pregnant person of color</strong></p><ul><li>Do users have a support system while they navigate through pregnancy?</li><li>Are users satisfied with the healthcare they receive?</li><li>How much do users feel that their healthcare provider understands or listens to them?</li><li>How are users documenting their medical care visits or their pregnancy history?</li></ul><p><strong>Goal #2: Identify my target group’s habits and needs when finding healthcare or relevant information and determine what features of this product can allow them to efficiently gain more control of their care.</strong></p><ul><li>What content do users need/want and how do they want this content to be presented to them?</li><li>What would make users trust the information displayed to them?</li><li>Do users feel as though their questions are answered?</li></ul><p>After my competitive analysis and data from my interviews and survey, I gathered my main insights</p><ul><li>Lack of access, awareness and overall distrust of the medical system are sources of frustration</li><li>There were patterns of fear of not really knowing what they’re doing, getting sick, delivery and feeling of isolation due to the pandemic and lack of support system</li><li>Limited insurance options in certain areas limit the type of care you get -quality care dependent on where you live and the amount of money you have</li></ul><blockquote>“I kept waking up with headaches, seeing spots and not feeling good in general but everyone around me including my doctor kept saying that its just part of pregnancy, it was very frustrating”</blockquote><blockquote>“you constantly have to advocate for yourself because there are times where you’re going to know your body better than anyone but thankfully my last OB I switched to was really helpful”</blockquote><h4><strong>Design principles</strong></h4><p>After determining digital interface elements that allow users to efficiently find relevant information and gain more control over their health care, I went on to create the Nebulla experience. The inclusion of holistic prenatal providers and reviewer transparency can help decrease the cultural gap and mistrust between provider and patient.</p><ol><li><strong>Giving users a choice: </strong>Users can filter through different provider categories and pick one that best fits their identity as well as set preferences. There is also inclusion of holistic prenatal providers available.</li><li><strong>Experiential sharing platform:</strong> Experiential sharing for different providers from patients with a similar backgrounds. There is provider background and credentials available as well as ability to save &amp; contact preferred provider.</li><li><strong>Clear navigation + information conveys trust:</strong> Customized home and match pages based on user answers and preferences.</li></ol><h4>The prototype</h4><p>Personalized matches from 3 different provider categories: OBGYNS, Certified Doulas &amp; Certified nurse midwives</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*nxMQvMSGeTQvClSCaR2q7Q.gif" /></figure><p>Strengthening the experiential sharing aspect by making it an integral part of the app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*_KWcAukG0UtAp4jHpxl-Xg.gif" /></figure><h4><strong>Major improvements in the designs</strong></h4><p>Based on usability testing and feedback from peers + mentor, I iterated on my design continuously. These are the major changes:</p><p><strong>Addition of relevant filters</strong></p><figure><img alt="Before and after of the design for Nebulla showing the addition of filters" src="https://cdn-images-1.medium.com/max/1008/1*pAm115uQapSJjT6Wg3CvcA.png" /><figcaption>Matches page with additional filters</figcaption></figure><p><strong>Better hierarchy of information</strong></p><figure><img alt="before and after of provider’s detail page" src="https://cdn-images-1.medium.com/max/1008/1*GS8GgDGBrWGxZf5jDuD-Ew.png" /><figcaption>Provider details page</figcaption></figure><h4>Designing visual elements</h4><p>I created reusable elements and components to make the design process more efficient and establish a more consistent experience all around. This paired with micro-interactions and brand visual elements, the app is able to offer a delightful user experience. Check out the <strong>prototype.</strong></p><h4>Lessons + Next steps</h4><p>Nebulla started with the idea that everyone should have a chance at an equal birth experience. Sadly, that’s not the world we live in. Building an end-to-end product was challenging at times, especially for a cause that’s very near my heart. The main takeaway was; don’t make users do extra work. There’s not always time to read through charts or scroll through hundreds of providers nearby that may not be the best fit. <strong>Personalize the experience by asking relevant questions and prioritizing the important information.</strong></p><p>I’m very interested in where Nebulla can go and will continue to work on it in the future. My goal for then is to strengthen the experiential sharing aspect and make reviews based on different social categories an integral part of the app. I also want to widen the scope to answer this question;</p><p><strong>How can Nebulla encourage users to seek healthcare during their pregnancy to lower the risk of pregnancy complications?</strong></p><p>Thank you for making it this far! Leave any valuable feedback so that I can improve, I would appreciate it immensely :’)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39fc64dc4183" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Figma is the best spec tool — for me.]]></title>
            <link>https://medium.com/@nardosiam/why-figma-is-the-best-spec-tool-for-me-2b77c188c1ba?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b77c188c1ba</guid>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Thu, 21 Apr 2022 16:59:38 GMT</pubDate>
            <atom:updated>2023-10-24T18:08:46.072Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Figma is the best spec tool — for me</h3><p>There are countless spec tools that exist out there to achieve effective cooperation with developers. But so far, I have found myself comfortable with Figma by a mile compared to many of them. Now, working with it throughout my internship, I am realizing how valuable and helpful it is as a design <em>and</em> spec tool. I’ll go over its most important attributes that lead me to believe this below.</p><p><strong>Easy collaboration and communication</strong></p><p>With communication being one of the pillars of the design process, Figma allows easy communication in the form of comments directly on the design. From other designers on your team to developers and project managers, this ability to comment ensures that designers can further explain ideas and their design decisions as well as get feedback.</p><p><strong>Easy sharing</strong></p><p>One of the pros of Figma being a web based platform is that it allows designers to share an editable file with others early in the design process. The hand off process is also made easier because designers can send developers a view-only version of the file so that developers can inspect design and code without editing the file. Since Figma works on all devices and browsers, anyone with the link can access, view or edit the file which makes cross team collaborations a piece of cake.</p><p><strong>Ease of prototyping</strong></p><p>Prototyping is an extremely important aspect of the design process. Not only does it gives us a visualization of the product to understand the concept and look of it, it allows designers to test the design to make ensure functionality before production. Since Figma has prototyping directly integrated, it can it eliminates the need to use third party tools for prototyping and allows designers to test earlier and as often as they need.</p><p>In summary, Figma works as a design <em>and </em>spec tool that makes the developer handoff process smooth and seamless. It promotes effective teamwork and real time collaboration with different members of your team by creating a more streamlined process without the need to use third party tools.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b77c188c1ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Apple Watch: A staple in usability]]></title>
            <link>https://medium.com/@nardosiam/the-apple-watch-a-staple-in-usability-78162adb5d75?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/78162adb5d75</guid>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Mon, 14 Feb 2022 04:33:28 GMT</pubDate>
            <atom:updated>2022-02-14T04:33:28.688Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Overall, I think it is a great device that is shaping how we interact with technology and one that helps make our lives easier.</blockquote><p>Although not digital, one product that instantly came to mind when pondering usability and accessibility principles was my Apple watch. It was something I have been wanting to get since its first arrival in 2015 so naturally, I was ecstatic to finally get one last year. From its minimalistic and human-centered design, to how convenient and functional it is, I’ve found it to be one of the most useful gadgets I own. Below, I want to share some of the reasons why I think this — in terms of usability principles.</p><figure><img alt="2 Apple watches side by side displaying different apps." src="https://cdn-images-1.medium.com/max/1024/0*VhE9d5fdwKaLnhyD.jpg" /><figcaption>Apple watch series 5, Wareable.com</figcaption></figure><p>In terms of efficiency, the Apple watch is great at only showing the needed information on the screen. This makes absorbing information easy on the user and allows for increased focus on the task at hand (no pun intended). Users can access secondary information via the “digital crown” — the external control on the side. Another great thing about the watch is the ability to switch tasks from the device to another such as an iPhone.</p><p>Admittedly, the watch does have a steep learning curve, especially for those not familiar with the technology. For example, it took me a long time before I realized you can do more than scroll with the digital crown. Both external buttons have a wide variety of functions if used properly and I do not think that is advertised very well. Although once you figure it out, they become quite intuitive and muscle memory, this issue still lowers the watch’s score on learnability and memorability for me.</p><p>When it comes to accessibility, the watch also has great positives. Coupled with its simple and content focused UI, it has a high contrast ratio. This means whether you are glancing at it indirect sunlight or rain, it ensures that it has a legible font and vibrancy. Large font sizes make it so you can read even during physical activity and while you&#39;re closing out your exercise rings.</p><figure><img alt="an image of an apple watch screen showing the 6th step of a recipe and the time remaining to take pan out of the oven." src="https://cdn-images-1.medium.com/max/220/0*fVAkzt30EpPkoRBj.png" /><figcaption>Content focused display with large font sizes and a high contrast ratio.</figcaption></figure><p>After a year of using my Apple watch regularly, there is still no regret behind my purchase. It has recognized my exercise habits and offers solutions for them which helps me meet my fitness goals. It helps me quickly check messages and emails without the need to pick up my phone. Overall, I think it is a great device that is shaping how we interact with technology and one that helps make our lives easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78162adb5d75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The short life of Microsoft’s Windows phone.]]></title>
            <link>https://medium.com/@nardosiam/the-short-life-of-microsofts-windows-phone-4c5e0ef8233a?source=rss-5cf1369a8781------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c5e0ef8233a</guid>
            <dc:creator><![CDATA[Nardos Mechal]]></dc:creator>
            <pubDate>Wed, 02 Feb 2022 20:38:38 GMT</pubDate>
            <atom:updated>2022-02-02T20:57:15.203Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“To succeed, you either have to be the first, the best, or the cheapest. And Microsoft’s phone was none of these things.”</em></p><p>Sometime later in 2010, Microsoft introduced its first iteration of the Windows phone 7. Even as a child, I remember that Apple and Android were dominating the mobile market. It was not a surprise to see Microsoft finally take on Apple and Google in the modern smartphone market. However, a series of mistakes meant that in about seven short years, Microsoft will announce that they will no longer sell or manufacture new Windows Mobile devices; the reasoning being low market share and third party application development. There is a saying that to succeed in a market, you either have to be the first, the best, or the cheapest. And Microsoft was none of these things. As for the existing phones with users, they will only provide security updates and bug fixes. Now lets dive into some assumptions that led to the phone’s failure.</p><figure><img alt="3 screens of the microsoft windows phone 7 released in 2010." src="https://cdn-images-1.medium.com/max/600/0*tsauxX3Nsk_TKJgM.jpg" /><figcaption><a href="https://www.engadget.com/2010-02-17-windows-phone-7-series-everything-you-ever-wanted-to-know.html">Microsoft’s Windows phone 7 released in 2010.</a></figcaption></figure><h3>So what went wrong?</h3><p><strong>Assumption 1: Underestimating competitors impact</strong></p><p>One reason for the failure of these phones was the fact that Microsoft decided to run their phones on an entirely separate operating system (OS). Instead of Microsoft adopting Android, an open sourced product licensed by Google, it went with Windows. At the time, Android and iOS (Apple’s OS) were the dominating development models that many app developers were accustomed to. If Microsoft adopted the Android OS, their phones could have easily supported Google services such as Youtube, Gmail, and the Google play-store that were already valuable to users and developers. This means that there was no compelling reason for users to switch from iPhone or Android phones to a Windows phone that lacked these essential features and apps. The assumption that their OS could be as easily adopted and could attract developers was a huge oversight.</p><p><strong>Assumption 2: Substituting quality for quantity would work</strong></p><p>After the Windows phone 7 and 8, Microsoft decided to buy Nokia and make more phones that were low end models. In addition to apps on the Windows phone being inferior, the low cost but low quality phones did not attract users as they were meant to. Nokia phones were not as competent and innovative as other phones on the market such as the iPhone.</p><h3>Lessons learned?</h3><p>Windows phone initially had a lot of potential but ultimately failed due to repeated mistakes and huge assumptions that turned out to be false. The phones failed to keep up with the fast changing market while simultaneously failing to meet users needs. The lesson learned here is that products should be made to solve problems. Another is the importance of constantly evolving your products to meet the needs of your users. Although the phones were promising at first and not all bad, they ended up creating problems for the users that were too late to fix by the time Microsoft tried to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c5e0ef8233a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>