<?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 Shuchi Sinha-Saxena on Medium]]></title>
        <description><![CDATA[Stories by Shuchi Sinha-Saxena on Medium]]></description>
        <link>https://medium.com/@shuchisaxena?source=rss-bef478f52829------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ukt8YPgDj5jO3cB2.</url>
            <title>Stories by Shuchi Sinha-Saxena on Medium</title>
            <link>https://medium.com/@shuchisaxena?source=rss-bef478f52829------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:51:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shuchisaxena/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[Rethinking Problem-Solving]]></title>
            <link>https://medium.com/@shuchisaxena/rethinking-problem-solving-9111e8550389?source=rss-bef478f52829------2</link>
            <guid isPermaLink="false">https://medium.com/p/9111e8550389</guid>
            <category><![CDATA[emotional-intelligence]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[critical-thinking]]></category>
            <dc:creator><![CDATA[Shuchi Sinha-Saxena]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 21:03:25 GMT</pubDate>
            <atom:updated>2024-09-09T21:03:25.597Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Understanding the Problem is More Important Than Finding the Solution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-VbWwvKeyHBDIs7p" /><figcaption>Photo by <a href="https://unsplash.com/@rosssneddon?utm_source=medium&amp;utm_medium=referral">Ross Sneddon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever been in a situation where you needed to think of a solution? If you answered yes, this topic is relevant to you. All of us are problem solvers - whether you’re a parent who must figure out a way to manage school drop-off with chores or a C-suit person who has important decisions to make for the company. As long as we are alive, problems exist that need solutions. And today, I hope to show you another way of solving our problems.</p><p>We are all capable of solving problems and have been doing so from the dawn of time. That is how we have survived as a species. Thinking of the problem in terms of solutions comes naturally to us. And that is what I am here to challenge with this article.</p><p>Very often, as soon as we encounter a problem of any kind or any level, our mind starts to think of all the ways to correct it, to find a solution to fix it. Very rarely, if at all, we pause to reflect on the problem itself. Yes, there are times when we must act quickly and make decisions. But when solving a problem that is large and complex, we don’t spend nearly as much time on the problem itself, instead jump to talking about solutions quickly.</p><h3>Why do we jump to solutions so quickly?</h3><ol><li><strong>‘System 1’ vs ‘System 2’ brain </strong>- As the famous psychologist <a href="https://en.wikipedia.org/wiki/Daniel_Kahneman">Daniel Kahneman</a> puts it, we have two brains - a fast reactive brain aka System 1 and a slow logical brain aka System 2. By default system 1 is always on. It’s also the older brain that evolved hundreds of million years ago that is in charge of our instincts and emotions. After all, we needed to make quick decisions in the savannah whether to run or hide when we heard a rustle in the bushes. This is our default brain as it helped us survive from pre-historic times. System 2, the one responsible for language learning, and strategic thinking is also a younger brain about two-three million years old. Engaging system 2, the logical—critical thinker brain requires effort. Our brain relies on less effortful ways to make decisions to conserve energy. Else it will be metabolically very expensive to process every single thing in detail.</li><li><strong>Friction - Fuel approach </strong>- A framework put forth by <a href="https://www.amazon.com/Loran-Nordgren/e/B08Y79LDB8/ref=dp_byline_cont_book_1">Loran Nordgren</a> , <a href="https://www.amazon.com/David-Schonthal/e/B08Z4H12B5/ref=dp_byline_cont_book_2">David Schonthal</a> which says when we think about a problem our default way is to think about Fuel aka the appeal needed, the incentives required to keep propelling it forward to a solution space. We don’t spend time thinking about the Friction. For example, you woke up to a kitchen sink full of dirty dishes, which your partner promised to do, but didn’t. Your natural reaction is to express disappointment on this under-delivered promise. We don’t think about what might have caused them to not deliver on this. Maybe it was a misunderstanding or just them being extremely tired that evening to take care of it. The ‘Friction’ portion of that framework would require us to think about this exact friction that might have come in their way to not deliver on this.</li><li><strong>Fundamental Attribution Error </strong>- It’s a cognitive bias about how we judge others. It is the bias where we overemphasize a person’s characteristics and ignore situational factors when judging others&#39; behaviour. This error can lead to misunderstanding and oversimplification in perceiving things. And we can see how this bias is also situation-based. We oversimplify the root of the problem ‘Oh! They didn’t do the dishes because they’re lazy or not pulling in their weight in this partnership’ etc. It prevents us from challenging the status quo when applied to systems, processes or a situation at hand.</li></ol><p>Now that we know what our factory settings are, let’s talk about why we need to focus on the problem.</p><h3>Why focus on the problem space?</h3><p>Our minds are systems for establishing patterns, the maps of predictions. These pattern predictions help us free that mental real estate that can be used for other things. We use theories to provide explanatory simplicity to a vast overwhelmingly complex world. And over time, as we get familiar with an environment we lose a lot of the wonder that we once experienced as a newbie. As the patterns get established, it helps but it also puts blinders on and gives us tunnel vision. But there is strength in naivety- approaching a situation with a curious mind. Looking at things with a fresh set of eyes. The curse of knowledge is real as it comes with a curse of blinders and a lot of assumptions.</p><blockquote>“Assumptions are the earplugs of the mind.” ~ Kate Murphy</blockquote><p>Let’s talk about the benefits of focusing on the problem space:</p><ol><li>Focusing on the problem statement allows us to see these assumptions and blinders and lift them. It shows us new ways that a challenge can be approached. It gives us a new perspective on how to approach the problem. It also helps us establish a common understanding by drawing all the parameters to the board that we need to work within.</li><li>The core of the problem always ranges from one to a maximum of a few issues, but solutions can be endless. And that is an important factor to understand. If you don’t know what the problem is, any solution implemented is just a shot in the dark. So, you hope it works.</li><li>It is nearly impossible for you to know everything there is about everything. You should be humble enough to admit that to yourself. Focusing on the problem statement helps us to seek collaboration and formulate open-ended questions to understand other’s points of view. There is a high chance that the solution requires multiple systems to work in synchrony with one another for the solution to be successful. And focusing on the problem space, helps us identify these systems.</li></ol><h3>Practical ways to focus on a problem</h3><p>Daniel Kahneman once said that when you’re in a cognitive minefield, sometimes it’s better to stand still and figure it out instead of rushing ahead. Become more mindful of the challenges you face.</p><ol><li><strong>Uncover the friction by engaging with people </strong>- Have a dialogue about the problem (not the solution) and follow the conversations with the affected parties involved, whether it’s just your partner or 7 different groups of stakeholders. Discussing their frictions will help you with:</li></ol><p>a. building relationships and interpersonal skills,</p><p>b. enhancing your emotional intelligence,</p><p>c. establishing a shared understanding,</p><p>d. seeing a new perspective, and</p><p>e. helping you challenge your assumptions.</p><p>This dialogue to understand people’s friction will go a long way toward building trust with others and ultimately help influence your solution down the line.</p><p>2. <strong>Make and share a list of assumptions </strong>- It literally is that. Write down the list of assumptions made. Start any meeting by sharing the list of assumptions. Making and sharing a list will help us question the status quo and get everyone on the same page. It’s only when things are questioned, that they can be improved.</p><p>3. <strong>Focus on ‘what’s in my control?’</strong>- Once you have an understanding of the frictions others are facing and the assumptions you as a group are making, maybe even correcting a few along the way, it’s time to focus on what can you and/ or as a group can do to make it a little better than it was before? For example, once there were these young people in San Fransisco, thinking about how to pay rent because it was becoming increasingly difficult to meet their rent obligation. They had a spare bedroom in their apartment and had an air mattress. They focused on what they had- a spare room with an air mattress and a problem at hand- rent! They thought ‘How can we make a little extra side cash with this to sustain ourselves and pay rent in SF?’ ‘Can someone pay us rent to use our spare bedroom?’. ‘Why not put it up on a website and see if anyone will show up?’. They were not thinking about what a great million-dollar idea this is and how to make it a business. And this is how AirBnb was born.</p><p>This also ties into the <strong>principle of affordable losses </strong>- It’s thinking about maximum losses (time, money, effort) you can afford. In the case of AirBnb, when you combine a burdened hand —a spare bedroom with an air mattress with affordable loss- no one showing up, it gives you control over the downside. Because if things are going to fail, you’re going to lose nothing more than you can afford to lose.</p><h4>Bonus questions to ask yourself when discussing problem space:</h4><p>Am I creating a new problem by selecting one solution over the other? What are the trade-offs? You can even take it to another level by thinking about what impact this solution has at an organizational level/overall relationship perspective if it’s a more personal matter.</p><h3>Final words</h3><p>It is tempting to rush to the solution right way. But focusing on the problem space forces us to talk to others. A lot of our best ideas don’t come from our minds but from the conversation space between us. There is power in group intelligence when discussing the problem space. People’s ability to understand each other&#39;s emotions (interpersonal sensitivity) and share conversations to collaborate has immense power to drive a solution that works for everyone and stands the test of time. But it all begins with discussing the problem space because the core of the problem always ranges from one to a maximum of a few issues, but solutions can be endless.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9111e8550389" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design System- Grouping and naming components]]></title>
            <link>https://medium.com/@shuchisaxena/design-system-grouping-and-naming-components-7cef856906b5?source=rss-bef478f52829------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cef856906b5</guid>
            <category><![CDATA[components]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Shuchi Sinha-Saxena]]></dc:creator>
            <pubDate>Thu, 11 Jan 2024 21:24:26 GMT</pubDate>
            <atom:updated>2024-01-11T21:24:26.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FGAzcPM1HldtyVDC" /><figcaption>Photo by <a href="https://unsplash.com/@martinadams?utm_source=medium&amp;utm_medium=referral">Martin Adams</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Today, most professionals working in the digital space are familiar with a Design System. Just in case you are curious about what a design system is?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F1zgOBEmZk2M8vSJxqD%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F1zgOBEmZk2M8vSJxqD%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F1zgOBEmZk2M8vSJxqD%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/698c3726fe50dc8d28199f0de06095f7/href">https://medium.com/media/698c3726fe50dc8d28199f0de06095f7/href</a></iframe><p>A design system is a portal that contains guidelines, principles, and best practices that inform <strong>components and patterns </strong>to formulate<strong> </strong>an<strong> </strong>organization’s identity. Here is what it looks like:</p><ul><li>Visual identity: brand color, images, typography ….</li><li>Principles: Voice and tone, brand values, objectives…</li><li>Best practices: Accessibility, UX, training documents….</li><li><strong>Components and patterns: the building block of digital products</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K47Pj_XdouvrNnal.jpeg" /><figcaption>Credit: <a href="https://uxdesign.cc/everything-you-need-to-know-about-design-systems-54b109851969">What is a design system by Audrey Hacq</a></figcaption></figure><p>If you want to learn a bit more about Design System, here’s a really good article by <a href="https://medium.com/u/a174f7ac9f65">Audrey Hacq</a> on <a href="https://uxdesign.cc/everything-you-need-to-know-about-design-systems-54b109851969">what is Design System?</a></p><p>Here are some design systems by different organizations to build their digital space:</p><h4>Private sector:</h4><ul><li><a href="https://spectrum.adobe.com/">Adobe — Spectrum</a></li><li><a href="https://material.io/design">Google- Material Design</a></li><li><a href="https://www.lightningdesignsystem.com/">Saleforce- Lightning Design System</a></li><li><a href="https://www.audi.com/ci/en/guides/user-interface/introduction.html">Audi — UI</a></li><li><a href="https://developer.apple.com/design/human-interface-guidelines/ios/overview/themes/">Apple — Human Interface Guidelines</a></li><li><a href="https://polaris.shopify.com/">Shopify — Polaris</a></li><li><a href="https://developer.microsoft.com/en-us/fluentui#/">Microsoft — Fluent</a></li><li><a href="https://www.bbc.co.uk/gel">BBC — Global Experience Language (GEL)</a></li><li><a href="https://atlassian.design/">Atlassian Design System</a></li></ul><h4>Pubic sector:</h4><ul><li><a href="https://design-system.service.gov.uk/">Gov.uk — Design System</a></li><li><a href="https://designsystem.gov.au/">Australian Government — Design System</a></li><li><a href="https://designsystem.digital.gov/">U.S. Web Design System (USWDS)</a></li><li><a href="https://www.digital.nsw.gov.au/digital-design-system">NSW — Government</a></li><li><a href="https://www.canadapost.ca/cpc/en/designsystem/mercury/home.page">Canada Post- Mercury</a></li><li><a href="https://design.gccollab.ca/">Government of Canada</a></li></ul><p>These are just to name a few and there are many others that are just as good.</p><h3>Components and patterns</h3><p>Before we talk about the different ways to group components, let’s clarify what a component is and how are they different from patterns, so we can get on the same page since different organizations use them differently.</p><p><em>Components are reusable </em><a href="https://www.usertesting.com/blog/ui-vs-ux"><em>UI elements</em></a><em> that form the basic building blocks of digital space. E.g., Banner, Button, Checkbox, Spinner, Tooltip.</em></p><p><em>Patterns are repeatable, reusable combination of components that solve common user problems. E.g., </em><a href="https://spectrum.adobe.com/page/cards/"><em>‘Cards’ as pointed out by Adobe</em></a><em> is made up of Card container, Preview (image/ illustration), Avatar or logo, Action menu, Footer, etc.</em></p><p>Although design systems have a lot of information that makes them unique to every organization, components are an integral part of it. And that is what I will discuss today. Grab your coffee and let me show you:</p><ul><li>different ways to group components with pros and cons for each</li><li>naming the groups</li></ul><p>All from a UX/ product designer perspective who needs to use such systems to work every day.</p><h3>Grouping components</h3><p>Organizations, dependent on their size in the digital space, may contain anywhere from as little as 10 to 100+ library of components. Here are three different, most common ways to group them:</p><ol><li>Alphabetical order</li><li>Complexity based grouping</li><li>Functional grouping</li></ol><h4>1. Alphabetical order</h4><p>Listing your components in <strong>alphabetical order</strong> is the simplest way. This is technically not a “grouping” of components, but worth a mention as it’s seen quite often.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/1*kwa3mm0c3SZ88cWuDGP2zA.gif" /><figcaption>Alphabetical listing of components on <a href="https://www.lightningdesignsystem.com/">Lightningdesignsystem.com</a></figcaption></figure><p><strong>Pros:</strong></p><p>a. It’s a simple list in alphabetical order that is a no-brainer for the design system gatekeepers and its frequent users.</p><p>b. It is easy to scale.</p><p>c. It keeps the organization of the library simple.</p><p>d. It’s the best for the findability of components.</p><p><strong>Cons:</strong></p><p>a. You need to know what you’re looking for.</p><p>b. You need to be familiar with the naming of each component.</p><p>c. It can be a nightmare for a new member joining your organization.</p><p>c. It’s not the best for the discoverability of an alternate solution.</p><p>Findability and discoverability are two separate things. <a href="https://uxplanet.org/difference-between-findability-discoverability-in-less-than-2-minutes-baabfd06d988">Learn more on it with this great article by</a> <a href="https://medium.com/u/44260e16fd53">Sumeet</a>.</p><h4>2. Complexity based grouping</h4><p>This is classifying the components based on their <strong>ability to be broken down into smaller identifiable parts</strong>. This is a methodology proposed by Brad Frost in his book <a href="http://atomicdesign.bradfrost.com/">Atomic Design</a>. This method is based on a framework of nested taxonomy as pointed out in this book.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/1*gy9qOyVCGJ5udWl111NxuQ.gif" /><figcaption>Complexity based model of grouping components on <a href="https://protocol.mozilla.org/fundamentals/principles.html">Mozilla</a></figcaption></figure><p><strong>Pros:</strong></p><p>a. It works wonder for a mature design system and design system teams which has set rules and tight governance in place.</p><p>b. They’re an excellent choice for creative flexibility by combining atomic level items to form molecular and organism level components. Hence they need to be governed with very tight rules and a clearly defined vision.</p><p>c. It also requires a deep understanding of how the levels are defined; which needs to be understood by every team member of any given project (you need to know how the Lego blocks work together before you start making a building or a spaceship out of it. Hence a clearly defined vision- a building vs spaceship)</p><p>d. They are also a great choice when the teams are either relatively small or not as diverse.</p><p><strong>Cons:</strong></p><p>a. It needs tight governance.</p><p>b. It needs a clearly defined organizational level vision that everyone is familiar with.</p><p>c. The question of “what goes where?” can easily creep up as the organization grows. As companies grow, hire new programers, designers, planners, different business units, new ideas for color pallets, typography, patterns, page templates, marketing solutions appear in the digital product, grows inconsistencies, and increases maintenance costs. Every new hire increases entropy.</p><p>d. They run the risk of being a ‘dumping ground’ if not managed extremely tight.</p><h4>3. Functional grouping</h4><p>This is based on the usage of the component, the <strong>problem they are trying to collectively solve</strong>, AKA the function they provide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/1*kEB9VjTJzrCX93aGiWtLwA.gif" /><figcaption>Functional based grouping on <a href="https://spectrum.adobe.com/">Adobe Spectrum</a></figcaption></figure><p><strong>Pros:</strong></p><p>a. They are clearly defined by the common problem they are trying to solve.</p><p>b. They leave less room for misuse of a component and encourage consistency of user experience on a similar digital product no matter the medium/ device. Although <a href="https://www.thoughtco.com/labeling-theory-3026627">Labelling theory in psychology</a> is applied to people but is relevant in this case too.</p><p>c. They help findability and discoverability of an alternate solution (other similar components) that may be under the common (problem) umbrella.</p><p>d. The groups can be scaled in the future.</p><p>e. The familiarity with the name of groups coupled with the problem that you are trying to find a solution to; helps get to the solution faster.</p><p>f. Any project member, designer, or non-designer can get to the right solution to their problem as it is a very ‘fail-proof’ way of grouping.</p><p><strong>Cons:</strong></p><p>a. It requires oversight to make sure components are being assigned to the right functional groups.</p><h4>Conclusion on the grouping of components</h4><ol><li>Setting the users up for success is what the real challenge is. Our main job as UX professionals is to provide ‘fail-proof’ solutions to any problem.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JFv-O2ZNhdIePpu7" /><figcaption>Guard rails at a bowling alley. Setting users up for success. Photo by <a href="https://unsplash.com/@karla_rivera?utm_source=medium&amp;utm_medium=referral">Karla Rivera</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>2. Decreasing user&#39;s cognitive load is another main task we are forever responsible for. As clearly stated by <a href="https://lawsofux.com/hicks-law/">Hick’s law</a></p><blockquote>The time it takes to make a decision increases with the number and complexity of choices.</blockquote><p>We need to reduce the cognitive load for the user by simplifying their choices. A user may or may not understand what the difference between an Atomic component vs Molecular component is.</p><p>3. Users always gravitate to things that they are familiar with as explained by the <a href="https://thedecisionlab.com/biases/mere-exposure-effect/">Mere exposure effect</a></p><blockquote>Our tendency to develop preferences for things simply because we are familiar with them.</blockquote><p>Give users the options they are already familiar with. Ideally based on the problem they are trying to solve. Every organization addresses the same component with different names. E.g., Bottom navigation vs Footer. It makes it very difficult for new members of an organization to find what they need. But, as a designer, for example, if it’s a navigation issue you are trying to resolve; identifying it with an issue you are familiar with, makes it very easy to find the solution.</p><h4>A final recommendation for component grouping</h4><p>Although the solution you may choose for your organization may be based on parameters that are unique to your setting but in most cases, <strong>Functional grouping </strong>will always make it easier and faster for users to navigate to the component they are looking for.</p><h3>Naming the (functional) groups</h3><p>Here are some considerations to keep in mind before picking names for a functional group.</p><ol><li>The name chosen for categories is how users will end up working with the components inside it.</li></ol><p>2. An effective name of a category determines how the component will be used and helps to ensure that it’s used consistently by everyone.</p><p>3. Effective category names help the team use the components inside <strong><em>correctly</em></strong> and <strong><em>consistently</em></strong>.</p><p><strong>So, what makes an effective category name?</strong></p><ul><li>Avoid presentational names for groups.</li><li>Describe the function of the components inside.</li></ul><h3>Closing notes</h3><p>Grouping and naming components are unique to every organization’s structure, the size of their teams, their aspirations to scale and so much more. There is no ‘one size fits all’ solution. Designing a design system that can grow with time while keeping the entropy as low as possible will always be the challenge. A solution on basic cognitive principles will always result in a product that does not need re-thinking and revamping every time a new component is added.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cef856906b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Architecture to User Experience Design]]></title>
            <link>https://medium.com/@shuchisaxena/from-architecture-to-user-experience-design-49d73fd65300?source=rss-bef478f52829------2</link>
            <guid isPermaLink="false">https://medium.com/p/49d73fd65300</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Shuchi Sinha-Saxena]]></dc:creator>
            <pubDate>Tue, 22 Oct 2019 16:44:01 GMT</pubDate>
            <atom:updated>2019-10-22T16:44:01.171Z</atom:updated>
            <content:encoded><![CDATA[<h4>How my architecture experience helped me become a UX designer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*chfXBG9_iroiFLie" /><figcaption>Photo by <a href="https://unsplash.com/@elijahsad?utm_source=medium&amp;utm_medium=referral">Elijah O&#39;Donnell</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I am a User Experience (UX) designer by profession and an architect by training. After graduating from architecture school, I worked as an architect (Alberta Association of Architects intern) for a couple of years. While architecture is a form of human-centered design, the user is bound by walls and the path is set in concrete. Based on my love for human-centered design and looking for a medium where users have the freedom to find their own path; I found UX design and made the career change. I’ve been working as a UX Designer for a couple of years now and, I find myself borrowing more and more from the principles of architecture. In this post, I would like to outline the 5 traits of architecture that helped me in my UX practice.</p><h3>Top 5 traits:</h3><p>5. Working in a Cross-Functional Team</p><p>4. Client Service Industry</p><p>3. Design Process</p><p>2. Navigation &amp; Wayfinding</p><ol><li>User-Centered Design</li></ol><h3>5. Working in a Cross-Functional Team</h3><p>As an architect, you are constantly working with Planners, Drafts-people, Structural Engineers, Site Inspectors, Interior Designers and more to fit all the pieces of a puzzle. For example, you have to make sure your air ducts don’t run into hot water pipelines and can be concealed for esthetics. It starts from the drawing board to the construction site.</p><p>While transitioning to UX design, the experience of working with a multi-disciplinary team came in handy. To design a holistic product experience, the ability to form cross-functional partnerships with Interface Designers, Researchers, Copy Writers, and Developers and many others, is indispensable.</p><p>To simplify the experience, one must completely understand the product. To do so, everyone involved in designing and building the product needs to come together.<strong> It is up to the designer to make sure the intent of the product isn’t lost while maintaining the aesthetics of it. </strong>Making the experience coherent and seamless. Or in some cases a logical one!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*aa3BmDMpbJcutyopPgOtQA.jpeg" /><figcaption>Example of miscommunication between designers and site engineers leading to failed construction. via <a href="https://www.pinterest.ca/pin/166844361171016269/?autologin=true">Pinterest</a></figcaption></figure><h3>4. Client Service Industry</h3><p>Architecture is a client service industry. Understanding that client needs are different from end-user needs, is important. Most times, a client may not know why their existing design doesn’t work and what goes behind-the-scene to make a product successful. Guiding them to the right design which meets clients’ needs without compromising user experience is never easy.</p><p><strong>Some of the questions to ask yourself are:</strong></p><p><em>a. What is the underlying problem here?</em></p><p><em>b. Is this the right experience for the users of the product?</em></p><p><em>c. Does the solution meet clients’ needs without sacrificing good user experience?</em></p><p><strong>Identifying client needs is a skill set that should be in every designer’s tool-belt.</strong></p><h3>3. Design Process</h3><p>This is my favorite one!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lLXRFMvpR_O2Da2tCh4o1g.png" /><figcaption>Design process- architecture and UX design</figcaption></figure><p><em>(Disclaimer: process in both disciplines have been over-simplified for this post. In both cases, the process is usually cyclical and often chaotic</em>.<em>)</em></p><p>The timelines between the two disciplines vary drastically but the essence of a good product, be it physical or digital, doesn’t change.</p><p><strong>Every good product:</strong></p><p><em>a. Has a meaningful purpose</em></p><p><em>b. Solves the real problem</em></p><p><em>c. Provides seamless experience</em></p><p>To arrive at the real problem, to deliver a seamless experience; a deep foundation that will stand the test of time, one has to dig deep<em> </em>into the problem<em>. </em>This is where my background as an architect helped me develop my:</p><p>a. Analytical thinking</p><p>b. Logical questioning</p><p>c. Research methodologies</p><p>Before sketching (wireframing), or even formulating the needs of the product, you need to do a few important things:</p><p><em>a. Interview the user and identify user groups and the goals for each; map out the path currently taken.</em></p><p><em>b. Decipher stakeholder needs.</em></p><p><em>c. Identify &amp; understand the root of the problem that needs a solution.</em></p><p><em>d. Conduct research, collect data and plan the right experience.</em></p><p>Then you can sketch mock-ups and involve users as often. UX design gave me the ability to see it through the lens of a user before it gets built so I can fail faster and succeed sooner. An opportunity to iterate on your design- improve it until it solves the problem you identified. <strong>Because when you solve the real problem, the solution will always be beautiful and seamless.</strong></p><blockquote><em>“Good design is invisible” </em>— <strong>Dieter Rams</strong></blockquote><blockquote><em>“Less is more” — </em><strong><em>Mies van der Rohe</em></strong></blockquote><p><strong>An architecture design process</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*KRbkVud2z3b02fyeGq3X8g.gif" /><figcaption>An Architecture render gif by <a href="http://rebloggy.com/post/gif-design-architecture-render-2016-architecture-render-v-ray-arkitekcher-arkite/140944649863">rebloggy</a></figcaption></figure><p><strong>A UX design process</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*tisKl--x7ogIh56yO6D4jA.gif" /><figcaption>Wireframe gif of each step via <a href="https://cacoo.com/blog/8-must-see-wireframe-examples-inspire-next-design/">Cacoo</a></figcaption></figure><p>Mockups in any design profession always start with sketches and (ugly) grey box.</p><p><strong>Problem-solving and a purposeful idea lead to a strong concept for a design. Combine that with a beautiful and smooth experience, it will results in a delightful product.</strong></p><h3>2. Navigation &amp; Wayfinding</h3><p>When designing architectural places, navigation of people will always be the way to experience designer’s creation. Wayfinding is how people get to their destination, in the quickest way possible. If the design doesn’t provide for the shortest path, the user will create one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*MU3AHmghNb8zcyQ4.png" /><figcaption>Desire Path by <a href="https://99percentinvisible.org/article/least-resistance-desire-paths-can-lead-better-design/">99% Invisible</a></figcaption></figure><p>UX design, in a similar fashion, opens doors to entries from unusual paths where sometimes the users may end up feeling unsure, and sometimes they might be entirely lost.</p><p><strong>Some of the questions to ask yourself are:</strong></p><p><em>a. What is the task at hand for the user and the shortest path to every task?</em></p><p><em>b. Where are users coming from and where are they going?</em></p><p><em>c. What information do the users have/ can see to get to where they are going?</em></p><p><strong>Here’s an example from architecture:</strong></p><p>Say you arrive at a new location, looking to meet your friend over lunch. You get to their building of business, enter through a lobby, look for the reception (hoping to find quick answers). If reception doesn’t exist, an information board with business names listed will suffice. You look for the business they work at and take the elevator to the floor it is on. You meet your friend at work.</p><p>Let’s do a mental mapping from physical to digital world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3FvkarQKt8Q2rZbB2IadFA.jpeg" /><figcaption>Mental mapping between a building and <a href="https://www.bmw.com/en/index.html">BMW website</a></figcaption></figure><p>Building = Website</p><p>Lobby/ reception = Home page</p><p>Levels listed = Menu</p><p>Individual business/ level = Landing page</p><p><strong>It’s human nature to be aware of our surroundings. The easier and quicker we make it for the users to get from point A to B, the less cognitive load design will impose. The experience will eventually result in more satisfied users.</strong></p><h3>1. User-Centered Design</h3><p>The user is the heart &amp; soul of any human-centered design. As UX designers, we are designing for the screen but in reality, we are designing for the user behind the screen. Users will always behave the same to choices and hurdles, no matter the medium!</p><p>In and around buildings, people navigate physical spaces. Being something we have interacted with most of our lives, it has created a mental map of expectation in our minds. E.g, when we see a door, we expect to experience a different environment on the other side of it; when we see a corner, we anticipate a turn coming.</p><p>In the digital world, a user may run into a virtual wall, which cannot be perceived from a distance or unable to find what they’re looking for. The frustration is real. One bad experience and the user is out.</p><p><strong>The following qualities in a product will always provide the best experience for the users:</strong></p><p><em>a. It anticipates user’s needs</em></p><p><em>b. It doesn’t make a user think! A.K.A it is simple</em></p><p>A physical object has a clear advantage in its affordance. E.g, a child still learning to walk, knows how to interact with a chair right away- climb it, either to sit or stand on it. It doesn’t make you think!</p><p>A digital object can attempt to imply affordance by being simple. When a product/ task has only one way of approaching it, it will be straightforward. Just like a chair. There is no (or minimal) learning involved, it does not require picking up new habits. The process becomes natural, the task becomes easier!</p><p><strong>Understand the user, the task, and design in a way that will always set them up for success.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-zcqNMukXYSGll-n" /><figcaption>Guard rails at a bowling alley. Setting user up for success. Photo by <a href="https://unsplash.com/@karla_rivera?utm_source=medium&amp;utm_medium=referral">Karla Rivera</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Conclusion</h3><p>UX design is relatively newer than some of the other, more established design professions. It has attracted people from a variety of roles and diverse backgrounds, which is now its strength. Many disciplines can contribute to it, so it can live within each discipline. The diverse minds we design for, need diverse minds to be designed by.</p><blockquote><em>“To create, one must first question everything.” — </em><strong><em>Eileen Gray</em></strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49d73fd65300" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>