<?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 Katherine Lu on Medium]]></title>
        <description><![CDATA[Stories by Katherine Lu on Medium]]></description>
        <link>https://medium.com/@lukatherine?source=rss-678c809bd7b1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*bf-m06zR51axQS2i4dm-TA.jpeg</url>
            <title>Stories by Katherine Lu on Medium</title>
            <link>https://medium.com/@lukatherine?source=rss-678c809bd7b1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:17:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lukatherine/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[Crafting a 2-Day Design Workshop that People Actually Enjoyed]]></title>
            <link>https://lukatherine.medium.com/crafting-a-2-day-design-workshop-that-people-actually-enjoyed-530c97504d98?source=rss-678c809bd7b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/530c97504d98</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[design-workshop]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[facilitation]]></category>
            <dc:creator><![CDATA[Katherine Lu]]></dc:creator>
            <pubDate>Sun, 10 Dec 2023 22:19:25 GMT</pubDate>
            <atom:updated>2023-12-10T22:26:30.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qqbJabOPinUUWxTzRxYSg.png" /></figure><p>In June 2023, I hosted a design workshop for 4 product squads. Not only was this an exciting challenge, I wanted to make this a rewarding experience for my participants, consisting of Product Managers, Product Designers, and Tech Leads. The official goal was to push the envelop on what a product homepage can do to retain users. <strong>My personal motivation was to align our product teams on a unified vision, and to convince the squads we need more cross-team collaboration.</strong></p><p>Initially, I imagined the workshop as a 2-day event, and I got feedback from a hesitant workshop participant. “Two days is too long!” they lamented. “Can it just be one day?” I tried to pare it down to just 1 day, but after reviewing the entire schedule, it would be more than 4 hours; I knew this would be a hard sell, and wouldn’t garner the excitement I wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3I2PgZ7s8DVSCHtXjaxsfw.png" /><figcaption>I doodled quite a bit to think through the schedule, theory, and how to organise the groups. I considered various ideas that I soon scrapped, such as asking our UX researcher to function more as a consultant.</figcaption></figure><p>To set myself up for success, I sought feedback from researchers and designers. I asked myself…</p><blockquote>“How might I create a workshop experience where every activity feels purposeful and the ideas generated are user-focused?”</blockquote><p>Much of my decision making was rooted in what to prevent. I wanted to avoid:</p><ul><li>ideas based on technical or product constraints</li><li>misalignment on our user persona</li></ul><p>I thought the best way to achieve this was with a two day format, where the first day featured small talks and exercises (like the <a href="https://medium.com/@davegray/updated-empathy-map-canvas-46df22df3c8a">empathy map canvas</a>), and the second day got to the core of the workshop with HMWs, wireframes, and voting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p8abqexaPrZKHcXtRuB1XA.png" /><figcaption>I brainstormed the 2-day workshop as a user flow with milestones. This also helped me with timing.</figcaption></figure><h3>Day 1— Inform</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFiFLHjjAytaSWCfWTqsUQ.png" /><figcaption>Day 1 Workshop Schedule</figcaption></figure><p>I wanted to “share the why” on Day 1, and did this with short talks, persona exercises, and creating an open environment to ask questions. (My days as a Resident Advisor in university helped me in creating a safe atmosphere where people could speak up and be transparent.)</p><p>I also coupled each activity with a desired outcome to keep myself on track, as seen in the Day 1 Workshop Schedule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0O_VBitnziIf7Mo90pPrg.png" /><figcaption>Completing the Circles Exercise, a creative kickstart to ideating.</figcaption></figure><p>After a shortened round of Ideo’s <a href="https://www.ideo.com/journal/build-your-creative-confidence-30-circles-exercise#:~:text=Step%201%3A%20Give%20each%20participant,quantity%20or%20fluency%20of%20ideas">Circles Exercise</a>, we jumped into talks from our UX Researcher and product manager to contextualise the topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2gfNSUDCl7SLMM05uFmhvQ.png" /><figcaption>Our UX Researcher Jiji giving a summary on our user research and traits on our target demographic.</figcaption></figure><p>The highlight of Day 1 was a little pocket guide I made so participants could refer to a proto-persona during the workshop for our empathy exercise and wireframing. This was inspired by Natalie Harney’s blogpost “<a href="http://www.workovereasy.com/2020/01/18/what-i-learned-running-visual-thinking-workshops/">What I’ve Learned Running Visual Thinking Workshops</a>.” Spoiler alert: many of the participants <em>did</em> refer to it throughout the day!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*-XTs_8D8SkWmdp5DDa6oZA.gif" /><figcaption>I gave everyone a pocketbook, which included the proto-persona, his behaviour, needs &amp; goals.</figcaption></figure><p>At the end of the day, I asked for people’s takeaways and gave a quick preview of day 2, so that information and exercises could “marinate” before we jumped into group-wireframing the next day.</p><h3><strong>Day 2 — Ideate</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Sbm7_dD9j2EF5uaDtrnKQ.png" /><figcaption>Day 2 Workshop Schedule</figcaption></figure><p>After a quick recap, I started the second day with another warmup: come up with a mascot for our product that would appeal to Joachim, our proto-persona. Again, I wanted to bring the focus on the proto-persona instead of relying on participants’ existing knowledge about our users because many have their own takes on who our target audience is. Our users vary in real estate portfolio size, financial mindset, and experience level as property owners. For the homepage concept, I wanted to de-emphasise power-users (they skew feature creation, in my humble opinion!). So, I asked participants to focus on a more “everyday” property owner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*dbn-SkjbOf54jzNI-Jr8kw.png" /></figure><p>The questions I posed to the participants on the 2nd day were:</p><blockquote>How might we encourage users to subscribe to the premium membership? <br>How might we get users to explore or engage with the portal?<br>How might we get users to come back?</blockquote><p>I formed teams so people would collaborate with others outside of their squads. I wanted to shake up the influence others had on their closest teammates in the hopes there may be different ideas shared and expanded on during the workshop Q&amp;H (Question &amp; Hypothesis as opposed to Q&amp;A, as we don’t have Answers yet). Once the HMW exercise was complete, we moved into the sketching, and each team presented 1–2 wireframes for the group to vote on.</p><h3>How We Voted</h3><p>I have an unpopular opinion: <strong>I hate dot voting</strong>. The dots give no indication on the voter’s mindset. Are they coming with the perspective that we’re tight on deadline? Does their vote also speak to their respective team goals?</p><p>Instead, we voted along a quadrant to distinguish which concepts were voted <strong>Most Potential, Easiest to Solve, </strong>or<strong> Most Want to Work On</strong>.</p><p>By placing the concepts along a quadrant, we could see which ideas rested in the sweet spot of <strong>Easiest to Solve</strong> and <strong>Most Potential</strong>. Other great ideas, such as ones within <strong>Most Potential</strong> and <strong>Most Potential</strong>, could be tabled for later discussions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ys_sBS3mx3TlH74iZbz8iQ.png" /></figure><p>The workshop concluded with a bit of a stalemate, as a discussion would have been needed to move forward with a final conclusion. I did not anticipate voting in such a way would be so open-ended as there is no “clear winner,” whih would have been the with traditional dot voting. As a result, it was difficult for me to bring workshop realities into a clear summary. However, new ideas and ways to configure the homepage were brought up, which later made their way into the next iteration of designs.</p><h3>Lessons and Takeaways</h3><p>People were enthusiastic, inspired even! One tech lead said: “Can we have a workshop for my team’s own initiatives?” Despite the accolades, I knew there were areas that can be improved for next time.</p><ol><li><strong>A good workshop must be intentional and clear in goals</strong>. Even though this takes deliberate work and seeking feedback, the effort directly correlates with the quality of the workshop.</li><li><strong>Matrix dot voting was not a straightforward means towards a “winning concept.” </strong>The website is a tool that was designed in a modular way, where each tile in the product dashboard is dedicated to either a datapoint or specific piece of information. Therefore, there were overlapping concepts, so the winning concept would actually be an amalgamation of different ideas. This did not leave me with a clear direction unfortunately.</li><li><strong>Overplan, but save room for flexibility and creativity.</strong> I was not off schedule by more than 4 minutes, which means no one had to stay past lunch. (I also didn’t want to deal with any hangry participants!) I’m glad I allocated a strict time for each activity, but I also checked in on the teams during the work sessions.</li></ol><p>All in all, the workshop was a great experience in terms of facilitation and gathering knowledge from the smart people I worked with. And judging from the survey I sent out afterwards, I believe participants would agree.</p><p>What have you learned from your own workshops, and how have you managed to bridge workshop results into reality? Please comment and share, or reach out via <a href="https://www.lukatherine.com/">my website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=530c97504d98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Unexpected Tips to be a Successful Design Manager]]></title>
            <link>https://lukatherine.medium.com/5-unexpected-tips-to-be-a-successful-design-manager-51b743dac729?source=rss-678c809bd7b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/51b743dac729</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[satire]]></category>
            <dc:creator><![CDATA[Katherine Lu]]></dc:creator>
            <pubDate>Fri, 08 Dec 2023 14:43:31 GMT</pubDate>
            <atom:updated>2024-02-03T16:04:44.064Z</atom:updated>
            <content:encoded><![CDATA[<p>These are meant to be taken as suggestions for design managers and managers to-be, so read with a healthy dose of skepticism and apply what you find relevant. <em>(In no way is the tone sarcastic!)</em></p><h3><strong>1. Never have an agenda</strong></h3><p>Throw predictability and safe space to the wind! By taking the back seat on clear guidelines and expectations, you create an environment where the designer will learn to navigate ambiguity and be proactive with setting their own agenda. The benefit of miscommunication is that you will train your designer to ask the right questions, which is one of the main skills of product design. In no time, they will gain the toolkit to become senior designer as they grow more autonomous in their one-on-ones with you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_hB8EneHguXWP5pEo3P2eQ@2x.png" /></figure><p>What if the designer takes the initiative and asks you what the agenda is before the meeting? The right thing to do here is to give one or two cursory bullet points, nothing more. Keep the points vague, but lull them into thinking they know the meeting objectives. To up the ante here, throw a curveball and do not even address the bullet points once the meeting comes. This tells the designer that they should be prepared to pivot and remain calm in the face of change. In the current job landscape,this is a useful skill to have.</p><h3>2. Criticise and antagonise</h3><p>Picture this — while the designer is working intently on a prototype, you walk up to them and exclaim “No, no no!” Couple this with a disapproving look, and we have a designer growth moment. They were likely not expecting this type of response while they were in a deep work moment. Keep them on their feet, and they will develop a quick mindset that is eager and prepared to defend their work at a moment’s notice. A lot of designers don’t know how to take feedback, and flounder under pressure. Give them a bootcamp for success by turning each interaction into an unexpected sparring session.</p><p>After many high pressure situations, the designer will learn to successfully recite canned responses, such as:</p><blockquote>“That’s a great idea, I will put that into consideration.”<br>“That was brought up with the team and not within the project scope.”<br>“I don’t have all the details to answer this at the moment, how about I set a meeting so all parties can align?”</blockquote><p>Though the designer can misinterpret your apparent disdain and disappointment as hostile, you must remain steadfast in your goodwill, which unfortunately will come across as a putdown. After you question their work ethic and output in some other instances, they’ll learn to handle themselves in any situation.</p><h3>3. Lead with your emotions</h3><p>I understand that the work of a manager is sometimes difficult due to politics and shielding individual contributing designers from unnecessary noise. However, to create an emotionally transparent workplace, show (don’t tell!) how anxious you are. This humanises you so that you come across relatable to the team. You will gain the team’s sympathy as behavior that is typically lauded in managers (i.e. professional, judicious) actually alienates you from your reports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZyoSTh1JtybdElubLiSyg@2x.png" /></figure><p>If you are a calm person, you’re likely creating a predictable and psychologically safe environment, which will stunt your team’s growth.</p><p>Instead, here are some effective ways to cause emotional turbulence:</p><ul><li>Raise your voice and escalate the situation</li><li>Apologise afterwards, thus creating an exciting cycle of anger and reflection</li><li>Gaslight your designer and proclaim they are the one creating an unsafe environment</li><li>Stray from an agenda or talking points (see point 1)</li></ul><p>You get extra brownie points if you also start commiserating with your team about how much you dislike the job and company to show that you’re a “cool manager.” If possible, colour your communication style with aggression, but this is only if you are comfortable bringing your full self to the workplace. A combative nature coming from a manager will encourage the designer to stand up for their own concepts and ideas.</p><h3>4. Be Dishonest</h3><p>Do not worry about psychological safety — if the designer is past their probation period, that should be enough safety as it is. And if they are an at-will employee, the type of chaotic environment you’ve cultivated will motivate the designer to keep their portfolio up-to-date and encourage them to survey the landscape for new and better opportunities.</p><p>You’ll also demonstrate how important it is to write documentation, which will expand the designer skillset since documentation is usually reserved for Product Managers or Engineers. During this time, the designer will also practice active listening and ask clarifying questions, such as “What I am hearing is (insert phrase), is that correct?” The ability to rephrase and reflect is an excellent skill that will set the designer apart from their peers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*duQlNO1yl6SHA44scAoaaQ@2x.png" /></figure><p>By backtracking between what you say and do, coupled with emotional outbursts (see point 3), you become a primary example of why one should take notes and keep a work journal. Normally, a work journal is useful for logging achievements and wins, which can be referenced when asking for raises or promotions. However, most likely your designer is procrastinating on this. (We know how designers are with their portfolios!) You can “light a fire” under the designer, so to speak, and give them a good reason to document.</p><h3><strong>5. Advise with Concepts, Avoid Clear Guidance</strong></h3><p>Designers are generally a curious bunch. They love learning, have a growth mindset and want to pursue the best version of the product they’re responsible for. They’ll be thankful if meetings with you become opportunities for you to summarise all the concepts and best practices you’ve learned from Ideo and other design thought leaders. To directly address the problem that the designer has brought to you wouldn’t be a wise use of time. It’s safe to say not everyone will have read Nir Eyal’s <em>Hooked</em> or Teresa Torres’s <em>Continuous Discovery Habits</em>, so your team will sigh with relief once you start pontificating on the high-level takeaways of these books.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*beSA0gjroIKW9e5Jvnh6vA@2x.png" /></figure><p>Give them the leeway to figure it out themselves after sharing some YouTube links to videos on good product onboarding. Again, the key is to set them up for success by providing vague and minimal instructions so they must problem solve and advocate alone. Once they know how to operate independently without seeking answers from you, they will be able to handle any situation that their future roles throw at them.</p><p>These are my five humble tips that I have for design managers or anyone aspiring to be a manager. Just remember — your role is deeply important, and how you behave as a manager is pivotal to the experience of the product designer. Take your role seriously, and you will see your designers grow into the best versions of themselves.</p><p><em>Stay in touch! Katherine has other </em><a href="https://lukatherine.medium.com/"><em>Medium posts</em></a><em> on the topic of design. You can check out her UX design portfolio </em><a href="http://www.lukatherine.com/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51b743dac729" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Updating Our Design System Post-Acquisition: A Tale of Swift Rebranding]]></title>
            <link>https://lukatherine.medium.com/updating-our-design-system-post-acquisition-a-tale-of-swift-rebranding-6aa41934486f?source=rss-678c809bd7b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6aa41934486f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[rebranding]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Katherine Lu]]></dc:creator>
            <pubDate>Mon, 19 Jun 2023 16:12:17 GMT</pubDate>
            <atom:updated>2023-06-19T16:12:17.828Z</atom:updated>
            <content:encoded><![CDATA[<p>We navigated uncharted territory in a rebrand by creating a process that was tailor-made for our unique situation. This was done in two months to update our fintech portal’s UI to match with the parent company.</p><p><strong>By </strong><a href="https://medium.com/u/fab8362c95e6"><strong>Federico Marroni</strong></a><strong> and Katherine Lu</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AzmLUUGhNE5J2QGY" /></figure><h3>Situation</h3><p>Vermietet.de, a startup that addresses property management in Germany, was acquired by Immobilienscout24 (IS24), Germany’s largest real estate marketplace. After acquisition, it took about one year of negotiation before push came to shove, and finally it was decided:<br><strong>The designers are tasked with a rebrand!</strong></p><p>In a team of three, we came up with a timeline by working backwards from the deadline. The goal was to be as speedy as possible as we had to rebrand the entire portal and while we were at it, create a design system alongside this endeavour. Up until this point, we had a small working design system set up by one designer, as a design system had not been considered a strategic priority by the organisation.</p><p>One of our main challenges was how to integrate our parent’s company design system to our needs, as the plan was to integrate two tools that had very different use cases.</p><p>In a sense, we faced a new problem:</p><blockquote><strong>How might we incorporate brand in a portal-type tool when the brand guidelines don’t directly apply to a fintech portal?</strong></blockquote><p><strong><em>How to include the new primary colors?</em></strong> Our original primary color was blue, which was used as a background, to color icons, alerts and also our primary CTA. We could not simply adopt IS24’s primary color or else we would run into color contrast issues, not to mention the portal would be very teal!</p><p><strong><em>How to adapt our current customised components?</em></strong> in Vermietet.de, we had a number of components that were not available in IS24’s design system.</p><p><strong>What would be the quickest wins, we asked ourselves?</strong></p><p>During our talks, we defined the touchpoints for designers, working meetings to unblock and approve each other’s work (as we would all be using the new design system), and carve out milestones for us. In the meanwhile, another designer researched the best options for existing component libraries to adapt for our needs. In the end, we went with <a href="https://mui.com/store/items/figma-react/">Material UI for Figma</a> because it suited our needs well with its range of components that were easy to customise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/0*_BpOkM_Gy6TqGs8V" /></figure><p>We adoringly named our Design System “<em>Chameleon</em>” to represent the quick change of the portal’s original skin and color scheme to the parent company’s new one. (Also, chameleons are super cute and make for a nice mascot.)</p><p>The way we divided the work was based on the file itself. We each claimed different components to re-skin, and asked another designer to approve our update. We also needed conversations on main elements of our portal, like navigation elements, as there was no equivalent on the parent company’s side.</p><p>To prioritise components (from atoms to templates) we considered the product as three layers.</p><figure><img alt="circle diagram to demonstrate how we approached the rebrand in 3 steps" src="https://cdn-images-1.medium.com/max/588/0*SpH5FYzAdK0KCfou" /></figure><blockquote>Level 1: what site visitors would see during the first login or session<br>Level 2: The beginning of user flows<br>Level 3: granular pages and smaller actions that seasoned users would see</blockquote><p>We considered this process to yield the highest impact, as we wanted to prioritise aspects of the portal that would have the most eyes on it, and also be able to communicate to users as soon as possible that we were going to have a new look!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EHlUmRQFCTM1nulE3i3oYw.png" /><figcaption>Our roadmap to rebrand starting from September until December.</figcaption></figure><p>Engineers obviously were also essential to this process, and so we also worked with the two main frontend engineers on this project to check if the way we broke down the process made sense from their point of view, and would give them enough time to develop. Most of the technical foundation was there as our team of engineers already pull components from <a href="https://storybook.js.org/">Storybook</a>. Still, it was time consuming and company wide agreement was needed to understand that designers were supposed to allocate the majority of their time for the<strong> next month </strong>on this.</p><h3>Encountering Gray Areas</h3><p>As we got deeper into our rebrand project, we learned a lot of the styles could not be applied 1:1 because there was no equivalent. It was like making a square peg fit into a round role. This was frustrating as there was no time to hash out these differences. As we were pressed for time due to the business need, we simply had to do our best to reach a consensus, and move forward.</p><figure><img alt="a girl staring into the distance, to communicate venturing into unknown territory" src="https://cdn-images-1.medium.com/max/1024/0*figxq-qbL0O_urtk" /><figcaption>Image from: <a href="https://undraw.co/)">https://undraw.co/</a></figcaption></figure><p>Another issue we had faced was the topic of illustrations and graphics. IS24’s illustrations are hand drawn calligraphy-based graphics, which were created for flashy landing pages, as opposed to a fintech tool with emphasis on data entry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LajbviKim7YErujH" /></figure><p>On top of that, the colours designated for infographics could not be applied 1:1 to how we visualised data in Vermietet.de’s bar graphs and circle charts.</p><p>In the end, we did our best to make use of the illustrations when appropriate, but continue to face the challenge of fully doing justice to the new brand, simply due to the nature of these two products being different.</p><h3>Conclusion</h3><p>Not only did we reach our goals and the deadline, we also discovered that the project boosted our morale as this was one of the most collaborative projects between designers and developers we’ve experienced. We worked together closely to ensure we were all on the same page. Even though communication was frequent, the collaboration went smoothly. And as designers, we learned that fast changes can be easy with stakeholder buy-in, prioritisation due to business needs, and strategic planning.</p><p>In the present day, we face common design system issues like maintenance. However, it’s been almost half a year and it has also sped up designer workflows, promoting consistency between design and development as well.</p><p>Writing credits to <a href="https://medium.com/u/fab8362c95e6">Federico Marroni</a> and <a href="https://medium.com/u/678c809bd7b1">Katherine Lu</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aa41934486f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX portfolio tips I live by]]></title>
            <link>https://medium.com/design-bootcamp/ux-portfolio-tips-i-live-by-7d90abd9a4c8?source=rss-678c809bd7b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d90abd9a4c8</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Katherine Lu]]></dc:creator>
            <pubDate>Mon, 08 Mar 2021 12:11:47 GMT</pubDate>
            <atom:updated>2021-05-09T21:08:35.484Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Illustration of a girl on her laptop and the leftside is a simplified image of what a portfolio landing page looks like." src="https://cdn-images-1.medium.com/max/1024/1*0jypYIWijdoqc5CJ9LL7pg.png" /></figure><p><a href="https://outintech.com/">Out in Tech</a> hosted “What’s In Your Portfolio” in February 2021, an event that went through three portfolios reviewed by a mix of those on the hiring side for UX design roles. The live review aimed to provide candid feedback from those whom our portfolios are normally directed at, and ideally, would impress!</p><p>Many of the great tips shared during the panel echoed the feedback I heard when I was also putting my own portfolio together after finishing my UX bootcamp with <a href="https://careerfoundry.com/en/referral_registrations/new?referral=REX5eK7B">Careerfoundry</a> in 2019. Though the portfolios reviewed were from those seeking entry-level or internship roles, these tips can be applied to UX and product design portfolios across experience levels. It’s important to note that everyone has different perspectives and opinions when it comes to portfolios and how they should be constructed. The advice here is a combination of what was shared in the panel, feedback I’ve received from designers and those on the hiring side, and also what I believe are the basics of a good portfolio.</p><h3><strong>1. Keep it bold above the fold</strong></h3><p>Though (most of us) are not in the sector of newspapers, you still want to make a great impression in the top panel of your portfolio. This is the attention grabber, and should encourage the portfolio reviewer to scroll down and click into your case studies. Some aspects to include are a photo, and some sentences to explain who you are. You can speak to what your role is, background, specialization, what you’re passionate about, or anything else that makes you different from the rest! It’s basically the elevator pitch of a website, which should give a summary to who you are as a designer.<em> The portfolio is not a time for humility</em>, so be clear about who you are, and what you can and want to do!</p><figure><img alt="my design portfolio header used as an example." src="https://cdn-images-1.medium.com/max/1024/1*oHw-owt0bStbmkvRr-owHg.png" /><figcaption>This is what mine looks like, as an example. I’ve gotten positive feedback from this because it showcases personality and a basic summary of what I do. It’s not perfect, but done is better than perfect!</figcaption></figure><h3><strong>2. Who, What, Where, When, How (long was the project)</strong></h3><p>Case studies should mention your role and involvement in the project, who you worked with (or if it was solo), what tools you used, and the length of a project. This is feedback I heard at the event as well as advice I personally received, so I feel confident sharing this. Design is not about mastery of Figma or Sketch. However, including the methods and software you used will help make the case study feel more grounded. You should feel comfortable using “I” instead of “we” when applicable, so the person visiting your portfolio is not left wondering about your level of involvement.</p><p>Adding your work environment is important because recruiters are not only hiring for a role, but also a team. When reviewing your portfolio, they are asking themselves a range of questions.</p><blockquote>Does this person look like a first design hire?</blockquote><blockquote>Are they better for a startup or on a team with established roles?</blockquote><blockquote>Was this project completed remotely?</blockquote><p>Instead of making the other person guess around what your role was, you can directly state if you worked with other designers, project managers, and others on your team.</p><h3><strong>3. The Medium is the Message</strong></h3><p>Just as a case study is a demonstration of your design capabilities, so is your portfolio. One piece of advice that I’ve heard multiple times is that your visual assets should be legible and clear. For example, visual assets can be screenshots, graphs, or photos of sticky notes that document your process. If it’s small, make sure it can be clicked to enlarge. An image that is too small will leave the hiring manager or recruiter wondering what it trying to be communicated. Everything counts in your portfolio, so it’s best to be intentional with what is included.</p><p>Other ways to make your portfolio count as an example of good UX is through consistent and thoughtful hierarchy. For example, make it easy for your portfolio visitor to scan for what they need with clear headers and navigation. Just as you want to show off how user-centered you were in your design process, you should showcase it in your case study with aspects like line spacing, content width, and accessible contrast. And in case they want to dig deeper into your case study, you can give them the option by linking out to a report or supplementary media in a drive. As <a href="https://www.bombshell.is/">Avantha Arachchi</a>, an operations and talent consultant and one of our event panelists, mentioned, “Make it easy to find the diamonds.” That is to say, give them all the evidence they need to know you’re a great designer and candidate!</p><p>And lastly, where you house your portfolio shouldn’t matter. You don’t need a fancy URL or aim to code our own website (unless your goal is to show off your frontend dev skills). Avantha also mentioned a favorite hire in the past used Google Drive to store their portfolio. What is important is that you’re doing a great job of telling the story of your case study, who you are, and what you can do as a designer.</p><h3>Commonly Asked Questions</h3><p>Some other questions were asked during the last round of Q&amp;A that I hear whenever the topic of portfolios comes up. I personally follow this advice, but again, these are simply opinions! There are no hard and fast rules when it comes to portfolios.</p><h4>What is the standard number of case studies?</h4><p>There is no standard number! It’s not about quantity or the number of projects. Also, recruiters won’t click into all your case studies. At most, they’ll look at the first two or three, so definitely put your favorite case studies at the top! I personally recommend having two very good case studies. What I mean by good is that they are thorough and detailed. By only showcasing two or three case studies in my own portfolio, I have control over what I’m showing to recruiters. If I were to display four or five, I’d run the chance of someone looking at a project that’s not indicative of my best work.</p><h4>Do case studies need to be in the same format?</h4><p>It’s best to lay out information in consistent ways so that there is no need to relearn the format for each case study. I don’t find portfolios to be the best time to get creative with how information is presented. Since I try to contain certain elements of information to communicate the basics of what happened in each project, my case studies naturally take on more or less the same format.</p><h4>Should I separate work from fun things I do outsid<strong>e of wo</strong>rk?</h4><p>I think a portfolio should first and foremost showcase your work as a designer. (After all, it’s to get hired!) If the work side is ironed out, then I don’t see why there shouldn’t be a playful side. Many of the designers I know have an interesting hobby, such as writing, illustrating, woodworking… you name it! It’s great to showcase your personality in a separate section because it makes you someone that others can connect and relate to. And I saw “separate section” because maybe someone wants to glean through your portfolio just for the professional bits.</p><p>I hope you found these tips helpful, and good luck to all designers working on portfolios! You can do this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d90abd9a4c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ux-portfolio-tips-i-live-by-7d90abd9a4c8">UX portfolio tips I live by</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[What I learned about UX in Frank Gehry’s MasterClass]]></title>
            <link>https://uxdesign.cc/what-i-learned-about-ux-in-frank-gehrys-masterclass-f751b0091f25?source=rss-678c809bd7b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f751b0091f25</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Katherine Lu]]></dc:creator>
            <pubDate>Tue, 22 Sep 2020 19:18:31 GMT</pubDate>
            <atom:updated>2020-09-25T10:50:28.948Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Frank Gehry sketching" src="https://cdn-images-1.medium.com/max/1024/1*KUnpGdi5Um2zXnOrQUrOmw.png" /><figcaption>Source: MasterClass, Frank Gehry: Teaches Design and Architecture</figcaption></figure><p>I took MasterClass’s course with Frank Gehry to understand the world of architecture, and ended up learning more about human-centered design and UX principles. For those who don’t know, <a href="https://www.masterclass.com/">MasterClass</a> is an online resource that features industry leaders speaking on topics of which they are experts. For example, you can learn about filmmaking with Martin Scorsese, or cooking with Alice Waters, among many others. I decided to go with Gehry’s as it was the course most directly correlated to design that I could find.</p><p>Frank Gehry, notable architect responsible for Walt Disney Concert Hall and any building that looks like that, speaks on a range of topics during his 17 video, 2-hour 32-minute course: he discusses creativity and creative blocks, how to work with clients and teams, ideating, and prototyping. Much of his lessons can also be applied to UX design, especially the third lesson “Design Philosophy: Part One.” In it, he mentions the <a href="https://farnsworthhouse.org/">Farnsworth house</a> in Illinois, designed by Mies van der Rohe. Even though it is a “beautiful sculpture” where “everything is organized and spotless to conform to that aesthetic,” he caveats, “it’s overpowering” and “they [inhabitants] can’t escape it… the architecture would organize your life in maybe a negative way, an unfriendly way.”</p><p>This reminds me of beautiful interfaces that are clean, pleasant to look at, but how do users respond to this UI? If the experience is too clean, it’s possible this leaves little room for users to adapt the tool to their own lives. Instead, they must conform to the experience created by the designer, whose personal visual goals potentially collide with the user’s goals. They no longer become a part of the user’s lifestyle, and are more akin to homes like the Farnsworth house — “pristine houses [that] become museum things” or buildings “that are ice cold,” erring on the side of sterility. This begs the question: <strong>are architects, and designers in general, creating the experiences that people seek?</strong></p><figure><img alt="Farnsworth House in Plano, Illinois" src="https://cdn-images-1.medium.com/max/1024/1*5M-iwOikIobwltGu322iUw.jpeg" /><figcaption>Victor Grigas / CC BY-SA (<a href="https://creativecommons.org/licenses/by-sa/3.0">https://creativecommons.org/licenses/by-sa/3.0</a>)</figcaption></figure><p>Ironically enough, Gehry mentions, “Mies van der Rohe himself lived in a house with all kinds of tchotchkes and books.” Gehry beseeches the creation of spaces that are “user friendly” where “there’s a kind of comfort. You walk in, and you want to sit on the couch.” Furthermore, he states “it doesn’t detract to make something comfortable.”</p><p>His own design principles regarding architecture speak to my own user-centric approach to product design and my focus on accessibility. I aim to create experiences that people will find useful, to help them save time or effort in a technological ecosystem that seeks to capitalize on how time and energy can be drained as a means of profit. Also, I prioritize experience over aesthetic. In a perfect world, something can be immediately beautiful while also being extremely functional. But, if forced to pick between one or the other, I’d go for the house full of tchotchkes and a comfortable couch versus the harshness of a house like the Farnsworth.</p><p>Here are my other takeaways from Gehry’s MasterClass and how they relate to UX design.</p><h3>1. Advocate for Your User and Keep Their Interests in Mind</h3><p>Gehry emphasized the importance of truly knowing his clients, or users, in the case of UX. For example, the purposes of the house and the cultures of the client should and could very well affect the end result. <strong>While his interpretation of understanding his user is through meetings and even dinners, as a UX designer, we should put in the same time and energy through user research, interviews, and exploratory questions. </strong>The purpose of these meetings for Gehry is to “internalize everything pertinent to your client, from the location of their home, to the contents of their art collection, to the size of their family.”</p><p>During the initial user interviews, we may also become aware of edge cases, which should also be taken into account while designing. Rather than viewing them as annoyances to the design, think of them as constraints that will make the design more accessible and holistically useful. By being high touch with clients, Gehry also espouses open communication and sharing often.</p><p>And lastly, in regards to users, never assume your needs are their needs. The course mentions: “leave yourself open to the preferences of clients that might not have occurred to you; a feature of the land that you originally intended to highlight may be a component your client would rather diminish.” For example, an architect may find a view absolutely beautiful and want the house to showcase that. However, the client may simply want it contained so as to look like a frame in a room. In the same vein, it’s important for UX designers not to assume we share the same likes and dislikes with the user.</p><p>This brings me to my second takeaway:</p><h3>2. Design Iteratively and Share Your Work Often</h3><p>In any project, there are stakeholders to account for. As I’ve learned from experience, the trouble comes from a lack of communication, leaving one party in the dark. When meeting clients, Gehry “finds it helpful… to have a pencil in hand so he can sketch freely as they converse.” The class recommends that we “[t]ry thinking out loud with your clients and drawing as you go in order to create a visual, spatial response to their words.” This is especially important when working with clients or cross-functional teams.</p><p>Because much of our design work can be tied up with jargon, I find that having the design drawn out, even low-fidelity, can be a great conversation starter and ensures everyone is on the same page. Sometimes words don’t cut it, and the extra time spent designing initial mockups to share with others on your team or with users will save you time and unnecessary pain further down the line. (Trust me on this!)</p><p>And, just as important as showing your work the first time around, is also to keep others in the loop as the design progresses. <strong>By keeping clients engaged — or conversely, seeking user feedback throughout the design phase — these small touch points can help us feel more confident that our design is on the right track.</strong></p><p>The last lesson I want to share is:</p><h3>3. There is Room for Creativity Despite Constraints</h3><figure><img alt="Disney Concert Hall in Los Angeles" src="https://cdn-images-1.medium.com/max/1024/1*1jKH7IcJ3Az7jeHSzJyhVw.jpeg" /><figcaption>Visitor7 / CC BY-SA (<a href="https://creativecommons.org/licenses/by-sa/3.0">https://creativecommons.org/licenses/by-sa/3.0</a>)</figcaption></figure><p>When designing Walt Disney Concert Hall, Gehry noticed the women’s restroom line was consistently longer than the men’s any time he went for a concert. Despite the physical constraints, he managed to fit extra stalls for the women’s restroom into the blueprints, which no one noticed or mentioned. I personally loved this anecdote because it draws on observation and user empathy to create a better (concert) experience.</p><p>In his seventh lesson “Design Obstacles,” he said constraints provide for “15% of freedom,” which are “opportunities to explore things.” Design constraints — such as time, money, or project scope — can provide direction and encourage creative problem thinking. Another example he provided are the limitations of physical resources. Commonplace materials such as brick or chain-link fences can be made new and interesting with unconventional applications, while still being accessible and palatable because of their ubiquity. This reminded me that with design, experiences can delight users even without deviating from the norm, or mental model. It’s not to say that I encourage using whatever precedent has been set, but rather to evaluate or test if a new design or solution is one that is intuitive and accessible to users. Even with familiar patterns and experiences, a product can still be enjoyable and memorable for users.</p><p>From Gehry’s MasterClass, I learned that listening to your user and acting in their best interests will result in the most practical and well-received experience. I like to think of designers as a medium for the user that bridges their goals to the product. Though the course speaks to architecture, it proves that being user-focused serves all industries and job roles. The next MasterClass I take will likely relate to cooking, which I bet will also tie nicely into user-centered experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*4m-1fwnRCUJaRPgE" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f751b0091f25" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-i-learned-about-ux-in-frank-gehrys-masterclass-f751b0091f25">What I learned about UX in Frank Gehry’s MasterClass</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[Adobe and CZI Creative Jam]]></title>
            <link>https://medium.com/design-warp/adobe-and-czi-creative-jam-710243fa3052?source=rss-678c809bd7b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/710243fa3052</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[adobe-xd]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Katherine Lu]]></dc:creator>
            <pubDate>Wed, 20 May 2020 20:18:40 GMT</pubDate>
            <atom:updated>2020-10-23T05:55:40.590Z</atom:updated>
            <content:encoded><![CDATA[<h3>Adobe and CZI Creative Jam 2020</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQWldODvTlE9dviW_SdD6w.jpeg" /></figure><p><strong>What is the Creative Jam?</strong></p><p>Last week, Adobe hosted their a <a href="https://www.facebook.com/adobecreativejam/">Creative Jam</a>, a weekend-long event where teams work to address a project brief provided by the Chan Zuckerberg Initiative. I participated in the jam back in 2019, and was expecting a similar structure. For those unfamiliar, the Creative Jam normally takes place in-person where participants create a concept based on a theme set by the event judges. At <a href="https://nvite.com/CreativeJam/laUX2019">last year’s Jam in Los Angeles</a>, the theme was “A Little Bit Spicy.” The open-ended theme gave way for a variety of ideas, from food apps to body modification. Because the event was only three hours, participants had to figure out how to use Adobe XD if they didn’t already know, ideate, and design within a short span of time.</p><p><strong>This Year’s Jam</strong></p><p>This year, the event brought in the Chan Zuckerberg Initiative, or CZI, and provided participants with a project brief to address one of the crises caused by the COVID-19 pandemic: lack of resources for farmworkers. According to the brief, “farmworkers are the invisible frontline labor force of a country’s food supply. While many nations are reeling from the economic shocks of the pandemic, farmworkers — the vast majority being immigrants — make sure that we don’t go hungry. Many of them do not qualify for government stimulus packages, making it critical that they get access to safety net services like legal aid, healthcare, housing aid, counseling and/or food distribution.”</p><p>The goal was to create an app that would address the following criteria:</p><ul><li>sign up for services like legal aid, healthcare, <br> housing aid, counseling and/or food distribution</li><li>get access to timely and credible information</li></ul><p>And nice-to-haves for the app experience included:</p><ul><li>Showcasing crowdsourced content</li><li>Creating a community and connecting farmworkers</li><li>Engaging and mobilizing people to take action</li><li>Reaching people at local and national levels</li><li>Celebrating farm workers for their contributions to <br> our country</li></ul><p>As for the core UX requirements, the app must have:</p><ul><li>ID verification</li><li>An easy sign-up catered to a low-literacy audience with bilingual option</li><li>Access to safety net services</li><li>Access to relevant information and news</li></ul><p>Along with addressing the project brief, we also had to use the assets and branding guidelines of CZI’s mock organization, International Consortium of Farmworkers. The pre-established logos and branding allowed us to dedicate our time to brainstorming and considering what are the best ways to address the brief, as opposed to concentrating on the UI and visuals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d-gRgSDwkI0VzEJiSkzcLw.png" /></figure><p><strong>Day 1</strong></p><p>Adobe and CZI presented the Creative Jam on Thursday, May 14, where participants tuned into a live kickoff event that revealed the project brief. My partner <a href="https://alexandracarson.com/">Alexandra</a> and I spent the rest of Thursday coming up with questions, concerns, ideas, user flows, and paper sketches to share with each other in a FaceTime on Friday morning.</p><p>Initial questions we had from the project brief was how to ensure buy-in and safety for the farmworkers. Since many are likely undocumented, they may feel uncomfortable registering their information during the app’s sign-up process. Registering in-person at an office likely provides a stronger sense of trust than an app experience. I also wondered how might we design a tool for people who may not necessarily be familiar with mobile experiences in case they do not normally use smartphones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gJof26Tl5HyIXrsFMqMKPA.jpeg" /><figcaption>Initial sketching and user flow</figcaption></figure><p><strong>Day 2</strong></p><p>During our call, Alexandra, as a UX strategist and conversation designer, suggested the brilliant idea of incorporating a chatbot in the app. I thought this was such an innovative addition to an app experience that would essentially be a news feed and a list of resources that farmworkers need (legal aid, healthcare, housing aid, counseling and food distribution). The chatbot would help people navigate access to services by breaking down the information into simple questions to guide the user. A chatbot would better imitate an actual interaction that a farmworker would have in an office, and can connect them to a representative if they were to need further assistance.</p><p>We mapped out the beginning of a conversation with our chatbot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E4FlqI3JLLRIL_LtskQX9A.png" /><figcaption>Beginning of our chatbot’s scripted conversation</figcaption></figure><p>Our first iteration of our tab menu was also established on this day to ensure we addressed the brief:</p><ul><li>Chatbot</li><li>User Profile</li><li>Quick Access sheet to Organizations</li><li>Feed</li><li>Community</li></ul><p>It was also vital that we communicated what we expected of the other person. It helped that we were both open to feedback and welcomed each other to take initiative and use our best judgment. We checked in with each other on Slack throughout our work so that new designs in our shared Adobe XD file would not confuse the other.</p><p><strong>Day 3</strong></p><p>By Saturday, our original tab menu changed from “Services, Home, Community and Account” to “Services, Community, Chatbot, News, and Account.” We decided to make Services the default screen (it would otherwise be “Home”) because we assumed the farmworker would prioritize accessing safety net services over reading current events, even though the news would pertain to farming and aid services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vLegBSIkXVmkHYd02IIAaw.png" /><figcaption>The original intent for the chatbot button to stretch across the screen was to prioritize the action over the other options in the tab menu. With the second iteration, the same purpose is achieved with a more directCTA.</figcaption></figure><p>We continued with the workflow we established, with me establishing the visual language, including buttons, cards, and headers — so that Alexandra could populate them with the right content. I found out it was key to collaborate with my partner throughout the design process so that I could communicate blockers that needed a second perspective.</p><p>For example, one of the chatbot interactions presented three options, which didn’t look great if buttons were in two. My immediate thought was to change the buttons from two in a row to one option per row. As a solution, Alexandra came up with a fourth option, “Restart Chat,” which adapts to the UI while also adding another useful option for the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pLAkhi2S8d3TuM1mes4QuA.png" /></figure><p><strong>Day 4</strong></p><p>We spent the morning finalizing the UI and prototyping the remaining screens for Yuda, the name of our chatbot, inspired by the Spanish word for help <em>ayuda. </em>Because we started in high fidelity due to the time constraint, some UI elements had to be adjusted based on the screens for today. For example, we had to add a header element in our chat section as a way for older messages to disappear at the top once new messages were added.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d6lY_TXRUh8bvYaGHSofoA.png" /></figure><p><strong>Last Thoughts</strong></p><p>It was a welcome challenge to work within the constraints of the project and deadline, as it allowed us to come up with creative solutions such as a chatbot and adding icons when they could help clarify the function of a button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fB1ZdsJAhLk3-RM97WyR5g.png" /></figure><p>By designing for constraints — which is a low-literacy user in this case — we are also making designs more accessible for the rest of our users. Each card and tab couples an icon/image with text for maximum comprehension.</p><p>A second constraint we kept in mind were the farmworkers who migrate seasonally — even each month — to different states, and optimized for that lifestyle.</p><p>Many assumptions had to be made since we were not able to conduct user interviews or testing during the project. Besides assuming that farmworkers already trust this mock organization, we also assumed the ICFW app would be able to pull relevant information into the News section and the Community section (crowdsourced information from individual users and grassroots partners).</p><p>In the end, we ended up with a prototype that we are both proud of, and became better informed about migratory farmworkers and the increased challenges they face because of COVID-19. If you would like to learn more about farmworkers and the organizations that assist them, check out:</p><p><a href="https://www.nytimes.com/2020/04/02/us/coronavirus-undocumented-immigrant-farmworkers-agriculture.html">https://www.nytimes.com/2020/04/02/us/coronavirus-undocumented-immigrant-farmworkers-agriculture.html</a></p><p><a href="http://nfwm.org/">http://nfwm.org/</a></p><p><a href="https://equitablefood.org/">https://equitablefood.org/</a></p><p><a href="http://www.ufwfoundation.org/">http://www.ufwfoundation.org/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jy54YOYK04eivk1PbSpiTQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=710243fa3052" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-warp/adobe-and-czi-creative-jam-710243fa3052">Adobe and CZI Creative Jam</a> was originally published in <a href="https://medium.com/design-warp">Design Warp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>