<?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 Laura Kadamus on Medium]]></title>
        <description><![CDATA[Stories by Laura Kadamus on Medium]]></description>
        <link>https://medium.com/@LauraKadamus?source=rss-e29b3007f28a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zPrrSteQLOEi0q5KfN5Dpg.png</url>
            <title>Stories by Laura Kadamus on Medium</title>
            <link>https://medium.com/@LauraKadamus?source=rss-e29b3007f28a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:26:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@LauraKadamus/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[Empathetic forms: designing the US citizenship application]]></title>
            <link>https://uxdesign.cc/empathetic-forms-designing-the-us-citizenship-application-4231933a36ef?source=rss-e29b3007f28a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4231933a36ef</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Laura Kadamus]]></dc:creator>
            <pubDate>Sun, 16 Jun 2019 22:28:03 GMT</pubDate>
            <atom:updated>2019-06-18T16:04:21.925Z</atom:updated>
            <content:encoded><![CDATA[<h3>Empathetic forms: designing the U.S. Citizenship Application</h3><p>I learned how to design forms as I built the Application for Naturalization, the form Green Card holders submit to apply for U.S. Citizenship. The paper version of the form is nearly 20 pages, with an additional 20 pages of instructions. The web form is still long, but it takes applicants through a plain language experience tailored to their specific situation. It’s a huge improvement, and since its launch in 2016 it helped set the standard for government form design.</p><h4>Interactive, intelligent forms are now standard.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eb1TfI_SNJpmT92t5z7eMQ.png" /><figcaption>The new Application for Naturalization confirms eligibility and proactively checks answers.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*IrRetq_qg72P9f4t6XGXUQ.png" /><figcaption>It’s a huge improvement from the 20 page paper form.</figcaption></figure><h4>Building upon these standards</h4><p>Throughout the government, technology teams are trying to speed up and simplify projects like this by creating form builders. The Department of Veterans Affairs is doing this successfully with the <a href="https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/forms">VA Forms System</a>, and the U.S. Digital Service got close to scaling their model with the <a href="https://github.com/usds/us-forms-system">U.S. Form System</a>. These tools are great for simple forms and we see their success across Federal websites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*i4xSAHcEG9zLXFrxfQ_VQQ.png" /><figcaption><em>A wizard helps </em><a href="https://www.va.gov/education/how-to-apply/"><em>veterans find education benefits</em></a><em>.</em></figcaption></figure><p>The interactions are clean and simple. The language is direct and users can easily access help or more information. We will see forms like this scale across the government in the coming years, to all of our benefit.</p><h4>Sometimes, form builders are not enough.</h4><p>Where these form builders fall short is when they are tasked with complex scenarios like entering 5 years of consecutive employment (to the day!), or submitting fingerprints and other documentation for a minor crime you committed years ago. We can’t rely on form design best practices to solve problems like these. Instead, we need to learn how our users understand these questions, and tailor the design to meet their understanding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*zVrwqQ-hNAPINjCC-A9KQg.png" /><figcaption>Empathy is the most important skill in a designer’s toolkit.</figcaption></figure><h4>Let’s walk through an example:</h4><p>The 8(a) Application consists of multiple forms that small business owners fill out in order to get privileges for federal contracting. One of these forms, 912, the Statement of Personal History, asks:</p><blockquote>For any criminal offense — other than a minor vehicle violation — have you ever: 1) been convicted; 2) pleaded guilty; 3) pleaded nolo contendere; 4) been placed on pretrial diversion or 5) been placed on any form of parole or probation (including probation before judgment).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dn4EBiRH4e9BJdAo" /><figcaption>This question is hard to read and understand.</figcaption></figure><h4>This is a scary question.</h4><p>If I was answering it, I would think that any violation would make me ineligible for the benefit (it does not). I might even pass over it if there is a minor conviction in my past that I had forgotten long ago. When I observed someone fill out the digital version of this form, she forgot that she had a DUI 20 years ago (which is a common scenario, as over 1 million people get charged with a DUI every year in the United States). This is not a disqualifying event, but it sure does feel like it. The user in this scenario went back and amended her answer, but then she had to fill out another form (FD-258), go to the police station and get fingerprinted, upload those fingerprints to the system, and write a description of the incident. To make things worse, the online form only saved responses upon progression to the next page, meaning her excursion to the police department caused her to loose the answers she had already recorded on the page.</p><p>When I worked on the digital version of this form, we unfortunately didn’t improve this question, and it has bothered me since.</p><h4>What if it worked like this?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*g7Mah17b3cqD8XUvSiH5fA.png" /><figcaption><em>A simple nested form using plain language and expected software integrations brings some humanity to this difficult question.</em></figcaption></figure><p>Regardless of whether or not this redesign is possible (I expect integration with FBI records to be difficult), it demonstrates how we can use what we know about users to build empathy into forms. Explaining the reason behind the question helps put the applicant at ease.</p><p>We can take it further with options like “I’m not sure” or “I don’t know,” and use those as opportunities to provide additional information. In addition to triggering the applicant’s memory, these techniques may help them feel like they are not the only ones in this situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*uyEUMOpe4nwTM40M4pXA0g.png" /><figcaption><em>This common crimes list is not accurate — I made it for illustrative purposes.</em></figcaption></figure><h4>Public sector designers must advocate for empathetic form design.</h4><p>This is more important than ever as governments across the country continue to ramp up their efforts to digitize forms. So, when faced with complex forms, do your user research. Observe users filling out the existing form in their own environments. Listen to them. Understand why the benefit is important and the barriers that stand in their way. Test your solutions with a diverse set of users early and often. Listen to feedback and iterate until you get it right.</p><p>Share what you learn. If more designers practice empathetic form design, people across the country will get the benefits they need and deserve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4231933a36ef" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/empathetic-forms-designing-the-us-citizenship-application-4231933a36ef">Empathetic forms: designing the US citizenship application</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why “make it work like Turbotax” is my least favorite request]]></title>
            <link>https://uxdesign.cc/why-make-it-work-like-turbotax-is-my-least-favorite-request-53196931dded?source=rss-e29b3007f28a------2</link>
            <guid isPermaLink="false">https://medium.com/p/53196931dded</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Laura Kadamus]]></dc:creator>
            <pubDate>Thu, 04 Apr 2019 23:22:34 GMT</pubDate>
            <atom:updated>2019-04-04T23:22:34.000Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong><em>How to set up a user experience design practice in a development-driven culture.</em></strong></h4><p>If you have heard this request over and over again you’re not alone…it has followed me from small financial startups to the largest government platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ml1lvqwgc8k7CGQWiKvXgA.png" /><figcaption>Turbotax uses conversational UI to make a complicated process feel easy</figcaption></figure><p>It’s not a bad thing to work like Turbotax — it’s simple, usable software that makes it easy for folks to file their taxes — <strong>my issue with the request is it expects good UX to be effortless, as if it can be added on top of development rather than serve as the driving force behind development.</strong></p><p>The Turbotax request is often a signal that project leadership expects UX designers to work within an existing agile practice without modifications, increased cost, or…god forbid…slowing the project down.</p><p>In my ideal world, I would turn projects like this down because they are fundamentally flawed (i.e. UX is an afterthought instead of the project’s backbone). But since we all have to eat, there are a few tactics I use to set up a user experience design practice in development-driven teams.</p><h3>Step 1: Get a handle on what’s going on</h3><p>As you onboard, the first thing to do is learn what has been done so far. Even if there are no designers on the project, chances are there are some folks advocating for the users. Find them and download their brains. Review any documentation about user needs and how the product will solve them. Familiarize yourself with business goals, the funding model, the products competitive advantage. Ask your new teammates why they made the decisions they did. Make sure you know your stuff so when you start working you can add to what has been done rather than reinventing the wheel.</p><h3>Step 2: Start working within the existing structure</h3><p>When on-boarding to a new project, designers typically want to run a “Sprint Zero” to understand user needs, validate assumptions, and test the software that has been built so far. This can be a tough sell when the project is already in motion — when I have suggested it in the past, the room gets quiet really quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*PIjlE2DxJzl5_2_O6-7HOw.png" /><figcaption>GV outlines steps to complete a <a href="https://www.gv.com/sprint/">design sprint</a></figcaption></figure><p>Stakeholders tend to have their reasons (budget, deadlines, promises, etc.) for resisting design sprints, so I accept that as a constraint to design my UX practice around.</p><p>I start by plugging gaps in the team. If a developer is struggling with a table pattern, redesign it based on best practices. If the color palette is not 508 compliant, suggest new colors and make it easy for them to be implemented. Small wins build buy-in for good design. When you demonstrate progress early, your stakeholders will be more open to taking a chance on larger asks later.</p><p>If you adopt this strategy, track the assumptions you are making, so you can test them later.</p><h3>Step 3: Make space for design in agile sprints</h3><p>The entire team is responsible for addressing both user and business needs; they need to believe in the necessity of user-centered design to deliver a useful product. When teams aren’t held to this standard, user stories are developed before their purpose is understood, features are accepted for production without usability testing or design QA, and unsuccessful products launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wAuWKsWnTAxmZY-C4sOjjQ.jpeg" /><figcaption>Illustration by Maya Stepien for <a href="https://www.behance.net/gallery/53324483/Google-Design-Sprint-Kit">Google Design Sprint Kit</a></figcaption></figure><h4>How can you hold your team responsible for user and business needs?</h4><p>When designers are embedded on agile teams, I don’t think it’s useful for them to “sprint ahead” of the rest of the team. When they do, getting stories ready tends to fall squarely on the shoulders of the designer. Instead, development needs to get involved in the design process, and design needs to assist development.</p><p>You can ensure this happens with two scrum or kanban-style boards — one for getting stories ready, and one for developing them.</p><h4>The ready board</h4><p>You can assign columns that make sense for the team, but it’s important that:</p><ol><li>User value is defined up front.</li><li>The team has time to explore both business objectives and user needs.</li><li>Development reviews designs, user flows, business logic, integration needs, etc., before they start working on it.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/0*fj1wgFkC92BeVu0u" /><figcaption>The ready board</figcaption></figure><p>Depending on the story, work can sit on this board for hours, days, or weeks. Often, backlog items start as an epic and get broken out into smaller pieces as they make their way to the right side of the board.</p><p>The work completed in the ready board will vary based on the needs of the particular feature. Activities within the “business and design” vertical can include everything from user research, business analysis and determining the logic or flow, to prototyping, content writing, and usability testing.</p><p>The “development review” vertical guarantees engineers are involved in the process. Engineers are the only team members who can move the story out of this column, once feasibility is discussed and outstanding questions are answered.</p><h4>The development board</h4><p>This is your more traditional scrum board, where developers spend most of their time. The only change I request is for the team to add a “design review” column. Like the “development review” vertical on the ready board, this gives designers space to work with the engineers before stories are accepted to production.</p><p>If the development and design review columns work as intended, the engineers and designers will start working together on a daily basis, recognizing the value each discipline provides, and collaborating on features to make exceptional products.</p><h3>Step 4: Conduct research within an agile sprint structure</h3><p>When moving work through the ready board, it’s important to figure out what features need in-depth research and extensive usability testing, and what can be completed by relying on existing knowledge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tg5CBw4N-RyUdGajwYOKfw.jpeg" /><figcaption>Illustration by Maya Stepien for <a href="https://www.behance.net/gallery/53324483/Google-Design-Sprint-Kit">Google Design Sprint Kit</a></figcaption></figure><h4>Directional research = fast and actionable</h4><p>Some design problems can be solved by conducting small experiments to validate product decisions. These are fast studies that can be completed within a sprint. Directional research answers specific usability questions and is turned into product improvements in quick, incremental cycles.</p><p>Directional research methods include guerrilla testing, usability sessions, A/B testing, and card sorting.</p><p>Outputs can be UI and copy recommendations that are ready to implement, prototypes and wireframes to guide development, user stories to go into the next sprint, or further questions to explore. While directional research is aimed at answering a specific question, sometimes that answer leads you to more unknowns.</p><h4>Foundational research = ongoing and insightful</h4><p>Larger discovery efforts should be conducted to understand users’ needs, goals, and motivations. Foundational research is vital when developing new features or reaching a new group of users. This type of research spans sprints and influences multiple stories or epics.</p><p>Foundational research methods include ethnographic research, contextual inquiry, user interviews, content audits, and competitive analyses.</p><p>Outputs can be archetypes, journey and scenario maps, ideas for new products or features, or early stage prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-LUH5z1-gsnXb-Y5mQAX0g.png" /><figcaption>Directional and foundational research explained by <a href="https://medium.muz.li/how-to-stop-ux-research-being-a-blocker-225d91105de8">Ben Ralph</a></figcaption></figure><h4><strong>Share research with the team as much as possible</strong></h4><p>When you do research in development-focused environments, you may need to demonstrate its value over and over again. Without continual emphasis, it’s easy for the team and stakeholders to slip back into the habit of delaying user research in favor of meeting development deadlines.</p><p>There are a lot of ways to get your team excited about user research:</p><ul><li>Bring them with you! If developers or stakeholders can’t travel, set up a remote video connection so they can observe research sessions from the office.</li><li>During sprint planning and demos, start each story by explaining the problem it solves and the specific user feedback received to date.</li><li>Include relevant insights from research in user story tickets — you never know who will take the time to read it and learn more.</li><li>Take 10–20 minutes out of regularly scheduled meetings to come up with solutions to usability issues. To do this, start with a quick overview of the problem and spend a few minutes individually brainstorming solutions. Next, share out ideas and discuss development viability. With additional time, dot-vote or use another design method to come to consensus on a solution.</li></ul><p>To learn more about how to conducting user research in an agile sprint, read <a href="https://medium.muz.li/how-to-stop-ux-research-being-a-blocker-225d91105de8">How to Stop UX Research From Being a Blocker by Ben Ralph</a> or use the <a href="https://methods.18f.gov/">18F method cards</a>.</p><h3>Step 5: rinse and repeat</h3><p>After following these steps, the entire team should be more focused on delivering real user value. So what next? Keep doing it. Continue to advocate for the users and make more room for user experience design and research. To make a product like Turbotax, user experience needs to be everyone’s responsibility. If you can make this happen, you’ll see the culture start to shift from development-driven to driven by user needs.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53196931dded" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-make-it-work-like-turbotax-is-my-least-favorite-request-53196931dded">Why “make it work like Turbotax” is my least favorite request</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</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 learned to compartmentalize: tactics to find work life balance and become a better designer]]></title>
            <link>https://uxdesign.cc/how-i-learned-to-compartmentalize-tactics-to-find-work-life-balance-and-become-a-better-designer-fadc1009336b?source=rss-e29b3007f28a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fadc1009336b</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Laura Kadamus]]></dc:creator>
            <pubDate>Wed, 20 Mar 2019 00:18:16 GMT</pubDate>
            <atom:updated>2019-03-20T14:08:21.627Z</atom:updated>
            <content:encoded><![CDATA[<p>Someone once told me sociopaths are really good at compartmentalization. Bill Clinton was famous for it. I laughed it off because for me, while it is difficult at first to turn your work brain on and off, it is the only way I can get good work done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xNwlrwp-NfmLCD733Px_DA.jpeg" /><figcaption>Original photo by <a href="https://unsplash.com/photos/af5vFlDUHeg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ricardo Gomez Angel</a></figcaption></figure><h3>Why do so many designers struggle with work life balance?</h3><p>It’s obviously an understatement to say that people struggle with work life balance — there are probably thousands of Medium articles about it — and designers are no different. As user experience professionals, it’s easy to get overwhelmed by the day-to-day urgency of solving problems that directly impact other people.</p><p>The first step is to realize that no matter what you do, <strong>you are not the only person who can do that job</strong>. If you are, chances are it’s not the end of the world if the job doesn’t get done. That’s why there are always backups for brain surgeons.</p><p>This shouldn’t make you feel less important; your combination of skills helps you solve problems in a unique way. The same is true for your colleagues who bring their own skill sets to the table and can solve problems in ways you can’t imagine. It’s not necessarily better or worse, just different. If you can embrace this way of thinking you’ll become excited to see what your colleagues do with your work. You will build more trust in your team and it will become easier to step away from your work.</p><h3>How I worked through this realization and applied it to my life</h3><p>When I was getting my master’s degree in Design for Social Innovation, it was easy to feel self-important. As we learned to solve systemic problems with design, I started to see those problems everywhere, and I became convinced I was getting the qualifications I needed to solve them. As my conviction grew, it became hard to understand why others weren’t also 100% focused on these pressing issues.</p><p>I started to get annoyed with friends when they applied for jobs with companies I thought were immoral, or if they didn’t consider the broader impacts of their work.</p><p>It only took one or two fights for me to realize that if I wanted to hold the people in my life to my newfound standards, I would not have many friends left. I needed to put in a boundary, something that would help me focus on the big problems at work and prevent me from taking them home with me.</p><p>Spoiler alert — I did it! Rather than focusing on the exact steps I took to compartmentalize, (which are likely different for everyone) I will share some tactics that will help you set up your boundaries successfully.</p><h4>Be intentional about the compartments you put up</h4><p>There are big risks to compartmentalizing, including ignoring the broader context of a project and its downstream impacts. Before sticking different parts of your work and life in neatly labeled boxes you need to be intentional about the walls you put up.</p><p>Before starting a project, I try to understand and accept the downstream impacts of the software or service I am designing. They need to be in line with my morals, because if they are not, I know I’ll obsess over it when I get home rather than leave my work at work.</p><p>As a designer with the U.S. Digital Service, I worked on immigration projects at a time when immigration was a hugely political topic. I was stressed out by the possibility of designing something that made it harder for immigrants to get their benefits, and this stress started to manifest itself in existential crises at home. I needed to counter my fear of potential misuse of the system, so I went out into the field, watched immigration agents at work, and made sure they were using the system as intended. I learned the context for each decision as well as agents’ personal motivations, which helped me design a better product that I was proud to deliver. Best of all, as I learned more, the existential crises started to recede.</p><h4>Make sure you don’t cut off cross-pollination</h4><p>A strength many designers have is the ability to connect seemingly incongruous ideas. One project can impact another, or something your kid says at home can help you connect the dots at work. Any compartments you build should allow for this. In my mind, compartments are made of mesh walls — they are see-through and adaptable, and allow me to breeze through them and connect ideas subconsciously. Just because you separate work from life doesn’t mean good ideas will stop coming to you in the shower.</p><h4>Clearly communicate your expectations</h4><p>While you will be successful in setting up your boundaries, the people around you might not be. Your co-workers will call you at home to discuss a problem, email will interrupt you constantly, or your boss may expect you to respond to Slack messages at all times.</p><p>To combat this, have a clear conversation with your team and supervisors, as early on in your compartmentalization journey as possible. I recently started a new position and taking time to let my boss know that work life balance is important to me was a useful way to frame how we will work together. I’ll respond to email after work hours if it’s a busy time for my project, otherwise I won’t check email at home. For urgent matters she will text me. During slow times I will leave my computer at work. These details help me stop worrying about work when I’m at home.</p><h4>Recognize when work is crossing over into your personal life and come up with coping mechanisms to deal with it</h4><p>Sometimes my work makes me anxious, and I take it home with me. When I feel lost, if there is a problem I can’t solve, or a decision I don’t agree with, I tend to spend an unhealthy amount of time thinking about it. Sometimes I take it too personally.</p><p>For compartmentalizing to work, you need to realize when work is crossing over into your personal life and learn how to redirect your attention.</p><p>During the most stressful times at work, I take a “quiet time” when I get home, spending 30 minutes reading before joining in my home life. According to my partner, this makes me a much more pleasant person to be around. Find out what works for you, whether it is video games, exercise, or chatting with a friend. The key is to direct your attention on something else entirely, so whatever happened at work is tucked away in a space to be easily accessed the following day.</p><h3>The impact of compartmentalizing</h3><p>Before going into how compartmentalizing has made me a better designer, I want to emphasize that this strategy is not possible for everyone. I am in a privileged position where I can speak up at work, I have autonomy and plenty of opportunities for new projects. I also don’t have a stressful home life that crosses over into work. There are a lot of people at the other end of the spectrum, who have less choice at work and more stressors at home.</p><h4>The good</h4><p>For those that can compartmentalize, it will make you better at what you do. This exercise helps prevent my mind from wandering so I give people my full attention. Whether I’m designing a new feature or trying to rekindle an old friendship, I’m a better listener when I can focus on the task at hand. I’m more in tune with the needs of those around me, which helps me succeed personally and professionally.</p><h4>The bad and the ugly</h4><p>As I mentioned, there is danger that compartmentalization makes it easy to segment work and morals. I assume lots of folks do this, otherwise how could someone lobby against climate change during the day and take care of their baby at night? Compartmentalization can also make it easy to ignore context, scope your projects too small, and justify your actions as temporary. That’s why it’s so important to start this exercise with intention and planning.</p><p>That’s it — good luck on your compartmentalization journey! I wish you focus, intention, and success.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fadc1009336b" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-i-learned-to-compartmentalize-tactics-to-find-work-life-balance-and-become-a-better-designer-fadc1009336b">How I learned to compartmentalize: tactics to find work life balance and become a better designer</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>