<?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 Zhiyu Xue on Medium]]></title>
        <description><![CDATA[Stories by Zhiyu Xue on Medium]]></description>
        <link>https://medium.com/@zxue?source=rss-c4900cfbe405------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BO3VKCpf_tUe5nXgrpcv-Q.png</url>
            <title>Stories by Zhiyu Xue on Medium</title>
            <link>https://medium.com/@zxue?source=rss-c4900cfbe405------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:50:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zxue/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[5 things to consider when designing a peer-to-peer product]]></title>
            <link>https://uxdesign.cc/5-things-to-consider-when-designing-a-peer-to-peer-product-224f8ba76d03?source=rss-c4900cfbe405------2</link>
            <guid isPermaLink="false">https://medium.com/p/224f8ba76d03</guid>
            <category><![CDATA[p2p]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Zhiyu Xue]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 12:21:53 GMT</pubDate>
            <atom:updated>2020-11-25T12:21:53.352Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BK3IkO4eKaw2Xl3sSE92A.jpeg" /><figcaption>Peer to peer</figcaption></figure><p>I <strong>recently had some challenges designing </strong>a shift trading feature for conference staff members to exchange their shifts. The conference has over 40,000 attendees and more than 3,000 workers who host and staff the event. To maximize the conference experience, we want every employee to be happy with their assigned shifts. We already had a system in place to assign shifts based on employees’ preferences of time and locations, but the system can’t always guarantee that people would get the time slot or area they would want to work. We want to design a system to allow employees to trade their shifts to ensure “maximum happiness” that employees bring to the conference.</p><blockquote>When we talk about ‘<a href="https://en.wikipedia.org/wiki/Social_peer-to-peer_processes">P2P (peer to peer)</a>’ here, we are talking about services that assist two types of users. For example, Uber and Lyft serve both drivers and passengers. They offer the platform for drivers to take passengers to a destination.</blockquote><p>When we worked on this feature, there were so many good points that came out of the conversations. I want to share them with you. I also wrote down the <a href="https://medium.com/@zxue/be-open-to-innovate-even-its-late-in-the-process-25a5ebc05adf">story of when we designed this feature</a>.</p><h3>Don’t let the typical interaction model limit your design.</h3><p>Think outside of the box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Lum8F9C83wcT8IARJnrxA.jpeg" /><figcaption>Don’t let the typical interaction model limit your design.</figcaption></figure><p>When I started designing our shift trading service, I didn’t realize I mentally limited myself to a traditional trading model, where one person offers their stuff to trade, and others bid on it. Like Craigslist or eBay, when both sides agree on a deal, the trade is completed. There’s nothing wrong with this model. However, it wasn’t the best solution under our circumstances because it requires employees to spend too much time manually posting their trade and bidding on a list of open trades. That will cause employees to spend too much unnecessary time on the system while doing their job. More importantly, employees may miss their best chance of trading a shift in this manual process because it functions as first come, first serve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvI7R1WY7KpmsgvVdCmw2g.jpeg" /><figcaption>Trading Board Model</figcaption></figure><p>When we finally broke outside of the box, we came up with a new model. Jokingly, I called it a dating (matchmaking) app model because much like a dating app, we let employees set their shift preferences, and the system would match them with other employees who have shifts that “matched” to that preferences (not like Tinder). This whole process is automated. Once employees put their shifts up to trade, the only thing they need to do is wait for the desirable shifts to show up in their schedule. There’s no need to look for what they want and go back and forth with bidding and accepting/rejecting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UEYtQHL3MISV4JWH7SmfKQ.jpeg" /><figcaption>Match Making Model</figcaption></figure><p>Did we reinvent the wheel? In a way, yes, because matchmaking has been done before. However, to our team in the context of shift-trading, this was a novel idea that came about only because we were willing to think outside the box.</p><h3>Think beyond the front end</h3><p>Good UX may lie beyond UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xFhedlWgCk-blzYzaJXgTA.jpeg" /><figcaption>Think beyond the front end</figcaption></figure><p>With the new trading model we created, the system beyond the UI was where the magic happened. As the designer on a P2P project, you should think about the flow and process more than the UI you design because there are hidden opportunities.</p><p>A well-designed back-end system helps simplify the process and increase the chance of successfully serving our users’ needs. Let’s say if we present all the tradable shifts on the UI and let users initiate the trade on a first-come-first-serve cadence. Users will need to browse through many shifts, and they may need to come back often to check newly posted shifts if what they wanted is not there. That can cause users to spend too much time on tasks and nervousness of missing what they want. The back-end system can review tons of users’ requests in a second and find accurate matches or wait until what the user wants is posted, simplifying the user’s tasks on the interface.</p><p>When designing this, I was worried that I would add a burden to the development team because I don’t want to blow the project&#39;s scope with limited time. However, talking to engineers, I found that my “matchmaking” model is way easier to build than the “Craigslist” model, even though “matchmaking” requires a lot of backend system support. Still, as designers, we should always check with engineers to figure out the time and complexity of implementing a design. If it is an intricate design to build, you can run an Event Storm with engineers to sort out the details.</p><p><a href="https://uxdesign.cc/5-rules-for-designer-engineer-collaboration-182fd74bd09f">5 Rules for Designer-Engineer Collaboration</a></p><h3>Think about the Edge Cases’ effect on all stakeholders</h3><p>Design to encounter user errors and users’ unexpected needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RSt8wjXHEul2J1X5BPpq4A.jpeg" /><figcaption>Think about the Edge Cases’ effect on all stakeholders</figcaption></figure><p>When I refer to “edge cases,” I refer to extreme use cases and hidden use cases that designers or development teams missed.</p><p>Looking for <a href="https://en.wikipedia.org/wiki/Edge_case">edge cases</a> is very painful, but we all spend time digging them out. Just like engineers always try to test out bugs and debug them. The impact of edge cases on P2P products can be more potent than other products because users’ behavior depends on each other. When one user makes an unusual decision, other users may get impacted. If you want to make sure both users have their best experience, there are edge cases from both sides. The tasks users want to complete are their shared goals. If one side can’t finish their tasks, the shared goal can’t be accomplished even if the other side completed their tasks. For example, if A wants to trade with B, A did all the steps, but B couldn’t complete the process. A and B won’t be able to deal eventually.</p><p>In our case, A may trade with many other people depending on who has the piece that A wants. To dig out those Edge Cases, we set up a “Breakfast,” a set time that all our department members get on the system and try to trade as many times as they can. (Breakfast, Break-fast, Break it fast, get it?) “Let’s see who breaks it first,” is what we tell people. In that “Breakfast” session, we found so many bugs and logic flows we didn’t think through. Once we fixed those bugs and designs, we tested it again with our department, and we found more bugs and design improvements. We ended up doing five “breakfasts” before releasing the product to be sure we encountered most edge cases.</p><h3>Take advantage of the network.</h3><p>Don&#39;t limit yourself to one person with another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJfE6OFhkpJjF3N1fi6bIQ.jpeg" /><figcaption>Take advantage of the network.</figcaption></figure><p>When we were brainstorming our shift trading tools, we start thinking, what if user A has what B wants, but B has what C wants, and A wants what C has? In the system, we can identify those needs and trade in a chain that might be very complicated to achieve from a UI perspective. However, this could increase the chance of successfully trading and help match as many people as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T33H_hSj24-N7EhxHjl59g.jpeg" /></figure><p>We originally designed it for just one person trade with another one. However, in our “breakfasts,” we discovered the chance of matching might not be high enough to support most users. It is possible some users may not get a trade because a match depends on both users wanting each other’s shift. To maximize the chance of successful trading, we came up with the idea of chain trading. In chain trading, we can let A trade with B, B with C, and C with D. All four users will get what they want. The more users in a chain trading, the higher the success chance is. With this system, we can make sure more employees are happy with the shifts they get.</p><p>In some other cases, it can be three people or a group of people. Think about the Uber pool or Lyft line; they match more passengers to one driver to help passengers save money. <strong>When designing a peer to peer product, we should also think about peers to peers or peer to peers cases.</strong></p><p><em>Credits to </em><a href="https://www.linkedin.com/in/kevin-klein-703848113"><em>Kevin</em></a><em> for coming up with this idea at our brainstorming sessions.</em></p><h3>Understand user might have biases</h3><p>Should users pick the match?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fgYF2QY-iUbUDH-PXjzo-Q.jpeg" /><figcaption>Understand user might have biases</figcaption></figure><p>If we allow our users to choose which shift they want to trade with, what would happen when there is more than one shift with the same time slot and working area? How would users pick one over another? The same question could be asked if users can pick drivers when they call an Uber or Lyft. How would passengers choose one driver over another if they get the same rating, car model, and it takes the same amount of time to pick up the passenger?</p><p>What if employees get more shift trades in these situations, or some drivers may get more customers than others? It may create an unknown impact on the product and how people interact with the product.</p><p>However, in some situations, the system should let users pick what they want. For example, if the tool connects doctors to patients. It would be a plus that patients can pick doctors based on their expertise because patients may have specific needs that only individual doctors can fulfill.</p><p>When we design a peer to peer platform, we should think about whether or not the product should allow peers to make selections and what criteria we let users choose. <strong>Once we understand the needs behind choices, we can design accordingly to accommodate them and minimize biases.</strong></p><p><a href="https://medium.com/dose/airbnb-uber-and-lyft-all-have-this-one-disturbing-problem-4c75fede4d6d">Airbnb, Uber And Lyft All Have This One Disturbing Problem</a></p><p><em>I want to thank </em><a href="https://www.linkedin.com/in/nicole-hayashida-a6a54754?trk=people-guest_people_search-card"><em>Nicole Hayashida</em></a><em> and </em><a href="https://www.linkedin.com/in/chadcamara"><em>Chad Camara</em></a><em> for reviewing and giving me feedback on this article.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*3w-dHWO4PbCIgW4S" /><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=224f8ba76d03" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-things-to-consider-when-designing-a-peer-to-peer-product-224f8ba76d03">5 things to consider when designing a peer-to-peer product</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[Be Open to Innovate Even It’s Late in the Process]]></title>
            <link>https://medium.com/@zxue/be-open-to-innovate-even-its-late-in-the-process-25a5ebc05adf?source=rss-c4900cfbe405------2</link>
            <guid isPermaLink="false">https://medium.com/p/25a5ebc05adf</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Zhiyu Xue]]></dc:creator>
            <pubDate>Thu, 17 Oct 2019 06:15:04 GMT</pubDate>
            <atom:updated>2020-11-06T03:49:02.655Z</atom:updated>
            <content:encoded><![CDATA[<h4>And why it’s important</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7JhgsROmaAB1BaNX_8Q9Bw@2x.jpeg" /><figcaption>Image from Unsplash: <a href="https://unsplash.com/photos/tZc3vjPCk-Q">https://unsplash.com/photos/tZc3vjPCk-Q</a></figcaption></figure><p>In the innovation process, we often prototype something as quickly as possible, to learn from the prototype, and to throw it away. It takes thousands of “No” ideas to find one “Yes” idea. These methods and mindsets are applied at the early stage of designing a product. However, it’s still possible to find better solutions later in progress. What would you do when you see something much better later in the process？</p><p>In July, I had a project to design a feature that allows conference staff to trade their shifts on our events management platform. As UX Designer, I started by pulling engineers and product managers in the same room to sketch out initial ideas because I want to put pencils before pixels instead of limiting ourselves to a certain idea. We came up with 3–4 ideas in the meeting, but all ideas had the same base as a traditional market where one person offers their shifts to trade and others bid on it. Like Craigslist, when both sides agree on a trade, the trade will be completed. The only difference between the ideas is just simplifying the process. However, we didn’t notice our ideas were limited to the traditional trade model. I went back to my desk to figure out the actual UX to make it work.</p><p>The thing is, no matter how much we simplify the trading process. If a complete trade process needs to wait for someone to post, others to bid on the one they want, and both sides need to agree on it. It is already a very long journey. Needless to say, that requires users to check back on the market all the time and be the first person to bid to get what they want. It adds a lot of unnecessary workload to the employees. I started seeing those inconveniences and struggles in the process. Yet, it still didn’t catch my attention to think about a different solution because the idea of a traditional market makes me think it is just the necessary steps for a trade to happen. I never questioned that the traditional trading method is probably not the right solution for this feature.</p><p>We carried on with the design and finished it. Meanwhile, I have communicated with the team on how I feel about this project is more complicated than we expected. We put the design in front of our users and tested it. The result was good but not great because we can only test how users navigate through the UI, but we can’t test how users will behave in the real market. With the deadline approaching and us in a meeting, an engineer proposed to rethink from the start point. Taking the use case as an employee looking into getting a shift they want, we can let them put in a ‘want,’ and if the system finds a matching want from two users, the trade will happen automatically. Others started to contribute to this idea, saying “we can now let users trade open shifts that haven’t been filled,” and “we can make three or more people trade together if two people don’t make a match.” We sketched a whole new plan at the meeting. Everyone was excited.</p><p>Now the hard question is, with the time we have left, engineers have to start working on it immediately in order to make it on time but we don’t even have a design for the new concept yet. We followed our core value, “every voice matters.” Everyone expressed their feelings and concerns. Together we decided to make the change. Because everyone agreed to the change, we all tied together to work towards the new goal. The trust and collaboration we built within the team helped us to work through this tough change.</p><p>One thing I learned from this process is that the innovation process can be applied in every step of the way. I remember when we decided to pivot, everyone was concerned about my feelings because the design was so far into the process. We had designed out the entire UI and tested it with users by then. They were worried that I would be unhappy to throw all that work into a trash can. However, I believe without learning from the design we have done, we couldn’t land on this new idea. So I don’t feel bad at all, instead, I think any ideas or feedback that will make the product better. I am always open to listening to it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25a5ebc05adf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to present to get the feedback you want]]></title>
            <link>https://uxdesign.cc/how-to-present-to-get-the-feedback-you-want-aff0704c47a9?source=rss-c4900cfbe405------2</link>
            <guid isPermaLink="false">https://medium.com/p/aff0704c47a9</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Zhiyu Xue]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 05:12:24 GMT</pubDate>
            <atom:updated>2019-08-18T22:56:33.607Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YGX1VGjJoXjT2-NQcwblkw@2x.jpeg" /></figure><p>Getting feedback can be challenging, especially for fresh designers. It can be hard to think through the consequences of implementing the feedback on the spot, and we can feel obligated to implement feedback from seniors and above. To get myself comfortable with such situations, I read through some Medium articles (linked at the end of the post) and discussed my findings with my mentor to help me during our weekly one-on-ones. I have come up with some tips that helped me present in front of people, and I’m sharing them to help you as well.</p><p>Feedback is important for designers because we need to be open to hearing everybody’s voice and catch flaws before shipping a product. The ability to present is equally important — due to the fact that we make such professional work, we don’t want to lose credibility due to getting our tongues tied when responding to feedback or answering clarifying questions on the spot.</p><h3>1, Explain your problems and intent</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*cE0FnWqupNwcLpbZg7U2Pg@2x.jpeg" /></figure><p>No one else in the room knows more about your work than you, including your manager, peers, and directors because you are the creator of that piece. When you present your work, people are trying to understand where you are coming from and why you made some design decisions. As junior designers, we tend to only explain how to get to “this” page and what happens if users click “that” button; we are helping our audiences navigate through our designs. Knowing the previous and next step in the flow is helpful, but it is not enough to understand your design decision.</p><p>My mentor, Jessi, once gave me a tip after noticing that I seemed anxious when I tried to get feedback from Engineers. After I explained my concerns, she recommended that I start sharing my design work by answering two questions:</p><blockquote>What is the problem I am trying to solve?</blockquote><blockquote>What is my intent to solve the problem in the design?</blockquote><p>This will help bring people to the same level of understanding as you because the problem will have been brought to their attention. When you only present a solution, no matter how good your solution is, your audience’s interpretation of the problem can be different from your own. Explaining your intent can give people a quick braindump of what directions you have tried. Knowing what you have thought through can help them filter out repeated ideas and give you fresh ones.</p><h3>2, Know what feedback you want</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Xn5cCeKEKJNZF2j6TXp7eA@2x.jpeg" /></figure><p>There are many different types of feedback. Sometimes you don’t know what to do next so you want a direction with which to move forward. Sometimes you have a solid design but you want an extra pair of eyes to catch missing points. Sometimes you don’t feel right about a design decision and you just want to talk about it.</p><p>During a critique or collaboration with your team, we tend to just welcome any kind of feedback, which is very open and you can get a lot of information. However, the feedback is not always helpful for you. For instance, if you are already stuck on something and the feedback you receive is about a point you have missed, you can feel more lost at the end of the session, but your issues are still not solved and you get more questions to think through.</p><blockquote>What’s your goal and scope?</blockquote><p>Before you go to a feedback session, ask yourself: what is your goal? What are you trying to achieve? Share it with your team when you present, so that everyone knows the direction to help you.</p><p>What is your scope? How much work needs to be done before the deadline? Be communicative with your team so everyone knows what step you’re heading into so they can offer proper support. Achieve what you can within your scope.</p><h3>3, Ask until you truly understand the feedback</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*5beXemOEBbatJWt5eu7mCg@2x.jpeg" /><figcaption>Based on <a href="http://www.dubberly.com/models/conversational_alignment_4.html">http://www.dubberly.com/models/conversational_alignment_4.html</a></figcaption></figure><p>When two people have a conversation, they are both building a mental model in their heads to help them understand. Our language can help us create an outline of the content we are talking about, and our brains will fill in the blanks. Our interpretation can cause us to talk about different things, meanwhile, we think we are talking about the same thing as it falls under the same outline.</p><p>One day, I was talking about the design of showing results with an engineer. However, we grew more and more confused about the conversation until another designer, who had been listening to us this whole time, pointed out that I was talking about showing the users’ preview result before a user takes an action, and he was talking about showing users’ report result after the action had been taken. It is the same piece of information we have been talking about, but the use case of the information we are thinking about is very different. In my mind, I was hoping the information could help users make a decision but in his head, he was hoping to let users reflect on what they had decided. Our trains of thought started in the same station but ended up going in very different directions. There are ways to engage in a conversation when this situation happens; for example, you can reiterate what you heard to let the other side tell you if it is what they expressed. One trick that works for me is:</p><blockquote>Use your <a href="https://www.interaction-design.org/literature/article/personas-why-and-how-you-should-use-them">personas</a> to make a scenario of how the user would use a product. Provide your understanding of the feedback using a new user journey in order to validate with your audience that you understand their thoughts.</blockquote><p>Stories, for designers, provide a journey to help reset some of our assumptions. They offer a platform for you and your conversational partner to work with and give you users and flows to think through instead of listening to a piece of feedback just based off of a suggestion.</p><h3>4, Don’t be defensive, but validate</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*njwYJ5R57EZrR5lc4lbxCA@2x.jpeg" /></figure><p>Often when you receive feedback, you might hear debatable ideas. By debatable, I mean some feedback that doesn’t align with your vision. For example, an icon is not clear or a piece of UX copy is confusing to some people but not to others. When you encounter a situation like this, don’t be defensive or too open because you and your peers are not the users of your product. As designers, we are supposed to be the representation of our users’ voices.</p><blockquote>When there’s conflict on opinions. Rather than fight for which one you think is better, we should be open to listening to the feedback and validate with users.</blockquote><p>Use your research resource to test out different versions. If you have limited resources and scope, you can also guerrilla test with someone who has never worked on your product to get a sense of what works better. No matter what, don’t be defensive when you receive feedback that doesn’t align with your vision.</p><blockquote>Being open allows you to ask questions and look at the project objectively.</blockquote><h3>5, Redirect bad feedback to get good feedback</h3><blockquote>“I am not a big fan of models”</blockquote><blockquote>“I don’t like this color</blockquote><blockquote>“Can you just add a button here?”</blockquote><p>You will inevitably get bad feedback that can be personal, subjective, and direct to solutions. People don’t always know how to give constructive feedback. It is frustrating to hear bad feedback, but instead of panic or ignore the suggestion, you can help them come up with good feedback.</p><p>Sometimes, your teammates just express their concerns, but they are not sure how to share it with you. For example, an engineer tells you he/she doesn’t like side panels. It may sound like a very subjective feeling, but if you ask more about why they don’t like it and what’s not working for them, then you will find out more things that you as a designer might never think about. For the side panel example, it could be that side panels mess up the scrolling on your page, or the platform your product lives on works better with models than side panels. When you hear bad feedback, don’t get frustrated. Instead, try to ask questions to understand the thoughts behind them.</p><blockquote>Ask for your audience’s concerns that you don’t see.</blockquote><p>When your audience gives subjective feedback or immediately offers solutions, ask what the problem is that they notice — if they respond with “that’s just my personal feeling,” then the struggle to understand the feedback isn’t worth the time and effort and you should move on with your life.</p><p>As I mentioned before, I’m still working to improve my skills in getting feedback. Some of what I’ve said are things I am actively practicing; when I grow more comfortable, though, I may have a different opinion. What do you think of my recommendations? Leave a comment so we can learn from you too!</p><blockquote>Feedback is a gift. — Jim Trinka and Les Wallace</blockquote><p>References:</p><ul><li><a href="https://link.medium.com/iwvrKbFTDW">Confidence As A Designer: How To Build It</a></li><li><a href="https://uxdesign.cc/dont-take-design-critique-as-an-insult-6cf187ca6308">Don’t take design critique as an insult</a></li></ul><p><a href="http://www.dubberly.com/articles/conversational-alignment.html">http://www.dubberly.com/articles/conversational-alignment.htm</a>l</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aff0704c47a9" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-present-to-get-the-feedback-you-want-aff0704c47a9">How to present to get the feedback you want</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[5 things to be mindful of when you design filters]]></title>
            <link>https://uxdesign.cc/5-things-to-be-mindful-of-when-you-design-filters-fc1ca83e157c?source=rss-c4900cfbe405------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc1ca83e157c</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Zhiyu Xue]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 12:31:00 GMT</pubDate>
            <atom:updated>2019-05-06T12:02:26.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2UAxvJEm0lLVnV9A74bnMg.jpeg" /></figure><p>As a newly graduated designer, I recall when I worked on any school project, I just threw a search box on design to meet the needs for filtering. Thanks to Google, I was so used to the magic of just putting in what I was looking for and the system would most likely return what I wanted within 1 or 2 pages, and even offered related info that I didn’t think of. When I started my design career, filter and search were not an easy task to design. I had to recognize how much work Google had to put into designing a web page with just a search bar in the center. After working on a couple of projects and hitting walls when I didn’t comprehensively think about how filters function, I want to share my experience with you.</p><p>We will only go through designs about filters. I want you to keep in mind that not all item arrays need filters. Ultimately, it depends on how manageable the volume of content is, you might not need to provide any filter, or you can categorize the content into small enough groups so that users can navigate through the content.</p><h3>1, No filter state</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4_v0YMsr3LgauaEl1dIG2A.jpeg" /></figure><p>Same as most empty-state design principles, you can add instructions or informative calls to action to lead people to use the filter. Don’t feel that it is necessary to display all items when there’s no filter applied. Depending on users’ needs, when there’s no filter applied, loading all content up front is not always the best for users. If the content is extensive, loading it before the user applied a filter can cause the system problems (e.g. overload). If there are plenty of irrelevant content, loading it before the user applied a filter can confuse our users.</p><p>In this case, you can either load featured content or bring attention to your filter design so users will look at the content you want to present, or lead them to filter down to the content they need. If your product is going to be heavily used in a user-filtered custom view, you can also design an onboarding experience to collect users’ preferences up front so users will be directed to relevant information when they log in for the second time. There are apps that collect users’ preferences when they onboard their users, they may have different intent but it is a good strategy you can borrow to help your users to set up a filtered custom view.</p><h3>2, Define your filter logic and be clear about it</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8UJvKzoYHV4eZuYqDiJIZA.png" /></figure><p>Usually, a filter’s purpose is to help users narrow down the number of items that display in front of them. If a user input 1 search query but there are still too many items to look through, the user can input more queries until the information is digestible. In this case, the logic in design is that the content needs to contain all queries users put in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7SlY-NiQXW4E8nChjxdX3g.png" /></figure><p>However, it is NOT the only logic that can apply to filters. For instance, a filter design for a scheduling app; the user, a store manager, needs to see when he or she assigned shifts to a sales associate and a technical support person. Depending on the use case, if the manager only wants to modify a shift that both of them were assigned to, he or she needs the type of filter logic I mentioned above. On the contrary, the manager might need to see shifts that either of them was scheduled to make sure they won’t work overtime. In this case, the filtered content contains schedules of both employees. It is no longer narrowing down the number of items that users filter, instead it opens up to more content about the second query the users put in.</p><p>Both of the situations are possible. As designers, we should think through the users’ journey and fully understand what they need to do with the filter to determine the search logic behind the filter. I also recommend always communicating with your developer team about the logic of this design and have them help you make the decision.</p><p>No matter what ways support your users’ needs; make sure you give a clear visual clue of how to narrow down and open up your filtered content.</p><h3>3, What are the users’ next steps after filtering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ikiaUxbGWlUtup0YiKBjLw.png" /></figure><p>Think a step ahead. What do your users need to do with the content they filter? What’s important for them to see? Are there links to click? How does that affect your filter? Reflect on the intent and why users filter your content, does your filter effectively support their use case?</p><p>There are many ways to display filtered content: you can hide irrelevant content and only show filtered items, highlight the filtered items among all content, and sort the content and have filtered items on top of the list. Be mindful of how your users will interact with the content and use that to determine how to display filtered content. For example, if the filter is for a tool where users can drag and drop items to change the hierarchy of the items, then you shouldn’t hide irrelevant items or sort the filtered content to the top of the list because users wouldn’t be able to drag and drop the content in the right order.</p><p>Some filters are shortcuts to help users achieve their goal. Don’t allow the filter behavior to be abrupt. Sometimes that logic might hide behind a designer’s blind spot. That’s when you should always try to test out your filter design.</p><h3>4, Always try to test out your filter design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-kbSNOYqKOdMj33bu3lpA.png" /><figcaption>Search phrase from a mother on <a href="https://www.imdb.com/title/tt4955480/">Great News</a></figcaption></figure><p>Filter behavior is very unpredictable, it is different from a flow that you designed for your users in which you know where they will go next. Users can input anything and get returned content based on what they search. We need to test if the returned content matches what the user expects. For example, if a user searches “Big bang,” should the system return content about the scientific big bang theory, the comedy TV show, or the Korean pop band?</p><p>On the other hand, when you give users a result to look for, the query they input to the system is also unpredictable. Power users might input the exact name of the result, but users who are not familiar with the result might input all kinds of descriptions to try to look for the result. Some of the queries might be keywords that directly relate to the result and some of them might be filling words. User testing can help you study those user behaviors. By understanding how your users search, you can make the filter experience more accurate and smooth.</p><h3>5, Let users share their filter result by URL</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o8t2kP0IJJMeerlM24Rm6g.png" /></figure><p>This is another expected user behavior but we might forget when we design filters. If you are designing a web app, users are used to sharing things by just copying the link and sending out. It is a nice touch to your product. Also if users click the back button on the browser they expect to go back to the filtered page.</p><p>Developing a filter is not easy. When you are designing one, please try to collaborate with your developer team as often as possible. It is very easy for designers to blow up the scope of building the filter.</p><p><strong>TL;DR</strong></p><blockquote>Help your users understand how to use the filter before they start. Think about users’ needs and design the filter logic that fits their need. Display the filter result in a way that supports how the users want to use the results. Test your design and allow users to share their search results.</blockquote><p>Check out more of my work: <a href="https://medium.com/@reajixue/why-you-should-document-your-ux-product-specs-afc98e6b4271">Why You Should Document Your UX Product Specs.</a></p><p>Thanks to my Manager <a href="http://www.linkedin.com/in/brandonmaraia">Brandon Maraia</a> who helped review my writing and gave me feedback.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%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/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc1ca83e157c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-things-to-be-mindful-of-when-you-design-filters-fc1ca83e157c">5 things to be mindful of when you design filters</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 you should document your UX product specs.]]></title>
            <link>https://uxdesign.cc/why-you-should-document-your-ux-product-specs-afc98e6b4271?source=rss-c4900cfbe405------2</link>
            <guid isPermaLink="false">https://medium.com/p/afc98e6b4271</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Zhiyu Xue]]></dc:creator>
            <pubDate>Mon, 25 Feb 2019 07:37:40 GMT</pubDate>
            <atom:updated>2019-05-12T22:43:04.988Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why you should document your UX product specs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OrkumBypna_YTpKtGSld1A.jpeg" /></figure><p>Last month, I was working on redesigning an annual benefit statement that will be sent to the whole company at the end of the year. Considering the fact that design was done five years ago, we decided to give it a UX touch before we turned it to visual designers to redesign the look and feel of the statement. Therefore, I started to research and design information architecture for our benefit statement.</p><p>From a user perspective, the project merely seems like just a statement of what benefits you received that year. However, it is way more significant than it looks. As I mentioned, this benefit statement would be sent to the whole company, that means we have nine different countries for whom to design. Every country has an entirely different set of benefits — not to mention different languages, currency system, and legal requirements that may apply.</p><p>With so many different regions, one universal design might not apply to all the areas. Because some countries give a couple hundred units in their currency and some countries give millions of units; some countries are required to display every single detail and policy in the benefit calculation, and some countries present a total number of benefits.</p><p>My original plan was to design nine different versions for every region, but after I finished the first region, I died a little bit inside. I was afraid of adding or removing content without checking with HR considering it can be legally required. With that said, I started to look into a better way to work on this project (once was enough, really). The “lazy” way of thinking is to consider what’s out there that can automatically finish this for me. I don’t remember what my thought process was, but Google Material Design Library inspired me. Design different UI elements to display different benefits and make a guide for Dev to build them. Basically, a guide says in this situation use this table in this way.</p><p>I analyzed the content in every region and designed tables that can fit different materials. Creating this guide ended up taking more effort than designing nine versions. However, I learned so much by developing a design guide than actually designing a product, and I would love to share it with you:</p><h3>What UX Product Specs I built and Why</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XKPTcJxeT85Rc7M3.png" /><figcaption>image from <a href="http://atomicdesign.bradfrost.com/chapter-2/">http://atomicdesign.bradfrost.com/chapter-2/</a></figcaption></figure><p>From my mentor, I learned that what I built is called UX product specifications. Similar to the visual design style guide, UX product specs should document the reasons behind your UI element to an <a href="http://atomicdesign.bradfrost.com/">atomic</a> level (Atoms are the smallest UI element such as labels or buttons) by describing its usage. In general, UX product specs include all your UX design work documents, such as problem statements, the sitemap, workflows, and annotated wireframes. Depending on your audience (dev team or stakeholders) you might want to include extra information designated for them. There’s no standard way to convey this information because it is all dependent on how you want to communicate your design.</p><p>In my case, I was inspired by Google Material design. I found it beneficial for adding “dos” and “don’ts” because we might set some UI elements to behave a certain way, but it might mislead developers (or designers) to use it differently. For instance the<a href="https://material.io/design/components/cards.html#behavior"> Material Card Design Spec</a>: When you look at the “don’ts” example, the product specs have defined the element and its behavior. However, when you look at the “dos” example, it is a better design behavior because it doesn’t break the context from the content. When your product specs have a lot of UI elements defined, there are many possibilities to create a molecule that obeys the product specs but not necessarily work well with the content. Therefore, understanding “dos” and “don’ts” is very beneficial for helping your audience develop based on your product specs.</p><p>If you are interested in reading more about how to write general UX product specs, I found <a href="http://chriskiess.net/a-practical-guide-to-ux-specifications/">Chris Kiess’s guide</a> very helpful.</p><h3>Better understanding, validating, and showing your design</h3><p>As a designer, you are often asked to present your design in front of a group of people. They can be engineers, stakeholders, product managers, or your fellow designs. At those presentations, people will always ask you why you designed it a certain way. As a young designer, like me, you can be too panicked to justify your reasoning behind those design decision. In that moment, you will lose trust from your clients or stakeholders.</p><p>I am not going to say writing product specs are the way to solve those problems, but it helps me rethink my design decisions and memorize them by writing them down. Honestly, sometimes we are so comfortable with our design work and decide without having a second thought. Enough so that we might miss opportunities or not think about the reason behind them. When writing down the anatomy of the UI element, it is time for you to slow down and rethink every single detail. So hopefully, when you are asked to justify your design decision, you will answer the question the way you want.</p><h3>Help Engineers know why you designed this way</h3><p>Think about the situation above. Designers don’t always get a chance to present their design work in front of the dev team. Sometimes, the dev team might even be offsite or across the ocean. Now, other than giving them wireframes to build off of, how can you clarify the design decisions or help engineers understand your vision? The UX product specs now become an honest blueprint from you to the engineers.</p><p>Often when engineers receive design comps, they don’t agree with them. I was surprised when I heard that idea from one of our dev teams, but it’s actually not that surprising. I remember there was a dev team from overseas who didn’t want to “waste” their time to build the design work when I was interning at a design consultancy firm. I am not saying design specs can fix those problems but at least it gives designers a way to articulate their reasoning. You might think an intuitive design doesn’t need explanation, I would agree if the audience consists of users, but an intuitive product is not necessarily a design for engineers to build. A product specs should give them the insight of why the designers made the choices they made, and if engineers/stakeholders want to validate the choices, we should include the research in UX product specs.</p><h3>Help other designers if they will pick up this project in the future</h3><p>I asked my mentor how to measure good product specs. He said, “if you get hit by a bus tomorrow, I would expect developers and designers can continue the project without you.” I am so sad that no one cares if I get hit by a bus but I agree that a good product specs should have enough information to carry on the project without my presence.</p><p>To be honest, I wish the previous designer who worked on that benefit statement left a UX specs for me (maybe they did but the specs were lost over time). So I could feel more confident working with statements that need to meet legal requirements in other countries.</p><p>However, I hope my UX specs are good enough for other designers to redesign the product in the future if they need. At least, I think they won’t struggle as much as I had to.</p><h3>Unify the design language</h3><p>There was one time we received email feedback from one of our stakeholders. She used a word — backsplash — in the feedback. So our team was guessing what she meant by backsplash, whether it was the landing (splash) page or something else. We messaged her, called her, emailed her and even had a couple internal meeting to talk about what the feedback meant. A week later, we found out that backsplash page was the page behind a pop-up model. The conversation would have been so much easier if we set a unified language between us. And I think the missed opportunity is the product specs, because when you annotate your screens, you will name every UI element within the screen. That way, when people who don’t speak the same design language are trying to communicate with you, they can refer to the names in your product specs so it causes less confusion.</p><p>The current design industry is still very messy. There are so many different creative ways. People use so many different words to name something similar depending on where you learned design. So product specs can help communicate even within the design team. It helps to set up a “bible” for a product.</p><h3>What can I do better next time?</h3><p>Just a couple of things I wish I did and will try to do next time.</p><ul><li>Start documenting product specs at the beginning of the project</li><li>Use product specs to communicate within the team</li><li>Keep product specs up to date and follow it as the “bible” for the product.</li></ul><p>I know some companies require designers to document product specs. We don’t require it because we work very closely with our dev team. However, I still think it is very valuable to document product specs, and it is not just something you do because of work. It effectively facilitates your design communication.</p><p>Citations:</p><ul><li>“Google Material Design.” Material Design, Oct. 2017, <a href="https://material.io/design/.">https://material.io/design/.</a></li><li>Frost, Brad. <em>Atomic Design</em>. Brad Frost, 2016.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afc98e6b4271" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-you-should-document-your-ux-product-specs-afc98e6b4271">Why you should document your UX product specs.</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>