<?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 Tianyuan on Medium]]></title>
        <description><![CDATA[Stories by Tianyuan on Medium]]></description>
        <link>https://medium.com/@chentianyuan?source=rss-2b3ebcdcdf21------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kErB0TrQEwKqWj0zU3D41Q.jpeg</url>
            <title>Stories by Tianyuan on Medium</title>
            <link>https://medium.com/@chentianyuan?source=rss-2b3ebcdcdf21------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:08:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chentianyuan/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[For the first time, how to lead a team in a UI/UX design challenge?]]></title>
            <link>https://medium.com/@chentianyuan/for-the-first-time-how-to-lead-a-team-in-a-ux-design-challenge-4315598fc21c?source=rss-2b3ebcdcdf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/4315598fc21c</guid>
            <dc:creator><![CDATA[Tianyuan]]></dc:creator>
            <pubDate>Wed, 26 Oct 2022 07:40:51 GMT</pubDate>
            <atom:updated>2022-10-27T00:54:48.913Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TOaBS8LTbb1fplkKUpLzXQ.png" /></figure><p>Seriously, how to build a team and lead the team in a UI/UX design challenge for the first time?</p><p>It’s the question going around my head when I was a self-claimed designer with no degree in design, limited network and recourses, and only a yearning heart for a real project to prove my ability. I spotted an opportunity that a prominent tech company in the city I stayed would hold a design challenge. Then I started to think about this question.</p><p>I did team up with two people and joined the challenge this September. My team did not make it to the second round. But we had great cooperation, and we brought out the best of us at that time. I hope this outcome will not affect the credibility of this article. As a self-learner and a person aspiring to win a place in the UI/UX field, I want to share my experience with people who may face the same circumstance. The following are the things that I’ve learned in the process as a first-time design team leader. These are mindsets and behaviours that I find essential to a team leader at different stages of a UI/UX design challenge.</p><h4><strong>Being the leader does not mean being the best</strong></h4><p>Imagine two scenes. In the first scene, you are a team leader, and your team makes a revenue of $2,000. You take 50% of the revenue and earn $1,000. In the second scene, you are also a team leader. Your teammates all have splendid abilities, and you only take 10% of the revenue for fairness. Since your teammates are so good, the total revenue is $50,000 and you’ll earn $5,000. If your target is to make money and you’re not the kind of person with a greedy ego to feed, which leader do you want to be?</p><p>I want to be the leader in the second scene. I want to learn about my teammates’ strengths, potential, and personalities, and the appropriate ways for me to cooperate with them, give them suitable tasks, and inspire them. I did three things to ensure I did my best to reach this goal.</p><p>First, <strong>I held a meeting with my teammates before the design challenge</strong>. It was a session to do self-introductions and guess about possible problem statements of the challenge together. I did not know about my teammates before we teamed up. Listening to how they introduced themselves allowed me to see their personalities. I also got a sense of their skills and strengths by hearing about how they thought of the problems that the company might want teams to solve in the challenge.</p><p>Second, <strong>I took notes on every workshop and shared them with my teammates</strong>. The company provided all the teams with virtual training workshops teaching UI/UX and product management knowledge. I encouraged my teammates to share about which session they would attend and the knowledge and information they learned in workshops that would benefit us. I also held a sharing session after the workshops were finished. We went through all the key takeaways of the workshops and shared our thoughts on the incoming challenge.</p><p>Third, <strong>I asked for feedback and gave feedback actively</strong>. Exchanging feedback is an effective way to find a better way to cooperate. When my team was brainstorming for the solutions after the problem statements were released, I found one teammate good at business analysis and another with good UI skills and experience. I gave them this feedback and encouraged them to give play to their strengths. Since we just had one week to work on our design solutions and everyone did not have a long time to ponder, they accepted my suggestions and took responsibility for the parts I thought they would be good at. What’s more, though we do not get the chance to compete for the finalist, we’ve made a deal to have a meeting and give feedback to each other when the finalists’ works are revealed. Reflection and feedback will help us to do better in the future.</p><h4><strong>Be responsive and responsible</strong></h4><p>After I built the team, my first task was to win my teammates’ trust. I had two teammates. I found one on social media. She commented on a post and asked whether she should attend a UI/UX design challenge if she aimed to seek a product manager role after she graduated. Then I reached out to her since she needed a teammate with UI/UX design skills, and I needed her product management knowledge. My second teammate was introduced by my friend. His original teammate dropped out and was looking for a new team. In short, our team barely knew each other before we teamed up. And I had to do something to let them trust me.</p><p>Before every meeting,<strong> I informed them of the meeting topic and duration</strong>. <strong>I also pinned important messages in our chatting group since I did not assume that others knew what were the important things in my messages. Besides,</strong> <strong>I gave my reasons every time I gave a suggestion and raised a proposal</strong>.</p><h4><strong>Make full use of a limited amount of time</strong></h4><p>Including the registration period and virtual training workshops, the challenge takes about one month for the first round. The actual time for teams to provide design solutions according to the company’s problem statement was just one week. The time was very limited for writing a complete report that was well-constructed and included background research, user research, competitor analysis, design solutions with high-fidelity mock-ups and an interactive prototype.</p><p>I want to talk about how to handle user research in a short time first. One week is too short to be split for detailed user research, which includes defining problems, targeting users, designing surveys and interviews, analysing the data, providing design solutions or modifying designs based on the user research. It’s easy for teams to skip user research when they face a tight schedule in a design challenge. Or teams may choose to do some user interviews and abandon the idea of doing surveys, considering the difficulty of reaching enough participants in a limited time. So was my team. But after experiencing the real project, I highly recommend all team leaders take user research seriously and plan for it at the beginning of a UI/UX design challenge. And <strong>I want to share some tips to save time during user research and defend user surveys.</strong></p><p><strong>The first tip to save time is to let you and your teammates be the users and give full use of empathy. </strong>When a company asks to improve their product, if there’s a problem that you and your teammates all encounter while using the product, there’s a high possibility that this problem is common in real user journeys. And your team shall put the problem to good use, try setting your analysis around it, and hopefully come up with design solutions to the problem.</p><p><strong>The second tip is to make use of the app reviews.</strong> It works well when you’re in a UI/UX challenge held by a tech company. If you take a look at the reviews of their products on the App Store and Google Drive, you’ll be surprised by the large number of valuable complaints. From them, you can analyse these reviews with your team and purify the essential problems to solve.</p><p>Your team probably already has an idea of what kinds of problems your team will solve after the two steps. One or two days may have passed, and you may consider doing a few user interviews and finishing the user research stage as soon as possible. But please reconsider. User interviews appear as time-saving to do, but it takes time, skills, and effort to unscramble them. It’s not easy to extract concrete guidance for your designs and translate user interviews into straightforward and conviving arguments to present to the judges. But you can achieve them with user surveys more easily. So <strong>l highly recommend starting composing questionnaires on the first day of the challenge</strong>. The questions you design for the users can help you understand the product better and inspire you. And when you’ve decided on the structure of your report, you can happily publicise your questionnaires, and it will be an appropriate timing based on the overall schedule.</p><p>Problems may come after the user survey is publicised and you’ve shared it on your social media accounts. There may not be enough participants, and your teammates may stay silent. <strong>As a leader, you should be responsible for user research and its performance. </strong>Whether you choose to do an interview, a survey, or both, you should urge your teammates to take part and ensure that they will do things on time. If they remain silent and let you be the only one sending the questionnaire, you can inform them of the progress and remind them that the sample size is insufficient to draw robust conclusions. Even if they still respond nothing and you also don’t have the energy to push them to send the questionnaire to more people, at least you’ve made a statement and reached an agreement with your teammates in advance. When one of my teammates asked me to delete the number of people that had done our questionnaire since he thought the number was too small, I wished I had drawn their attention to the sample size when they stayed silent after I composed the questionnaire.</p><p>In the final part of this article, I’d like to talk about <strong>how to allocate work in a team and stick to the work division to collaborate efficiently and come out with a report that fulfils the original expectations.</strong></p><p><strong>My first suggestion is to make sure everyone is clear about what the team is doing now and what they should do. Set the metrics first and let everyone be responsible for their part. </strong>Or you will end up tidying up the report and not having time to do the critical work. The sudden change of work division will cause imbalance. If you suddenly shift your work to another person to help someone with their work, the person taking over your work may do something according to their taste. And you won’t have the time and effort to review their work by then.</p><p><strong>The second suggestion is to be cautious of being a people pleaser and praising your teammates too much.</strong> It’s nice to cheer for your teammate’s accomplishments, and you should do that. But you may also want to say Bravo to every work your teammates do near the end of the challenge because you feel so exhausted and don’t want to give any advice. Cheering up for others will boost their confidence. It’s good that people will come up with brilliant ideas when they feel confident. But if you say yes to everything, your teammates may get very excited and want to overturn everything, even if you’re just one day before the deadline. So it’s vital that you keep calm, protect your plan, and avoid giving praises overly out of tiredness. And you should stay confident. Otherwise, it’s easy to lose trust immediately. After all, people don’t team up in a competition only to make friends that will understand each other and give hugs when someone feels tired. When the report is submitted, that’s when you celebrate your friendship.</p><p><strong>Last but not least, please go through the design challenge guideline with your teammates on the challenge’s first and last day.</strong> The former helps decide the structure of the team’s report together, and the latter is to ensure there are no omissions and inconsistencies in the final report.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4315598fc21c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>