<?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 Kevin L on Medium]]></title>
        <description><![CDATA[Stories by Kevin L on Medium]]></description>
        <link>https://medium.com/@jaewon604?source=rss-e85db783cfe1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*T_sJ_uzHfXTp38VZ.jpeg</url>
            <title>Stories by Kevin L on Medium</title>
            <link>https://medium.com/@jaewon604?source=rss-e85db783cfe1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:24:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaewon604/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[Learnings from my first year as a design lead]]></title>
            <link>https://medium.com/@jaewon604/learnings-from-my-first-year-as-a-design-lead-ba35eb603fc9?source=rss-e85db783cfe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba35eb603fc9</guid>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Kevin L]]></dc:creator>
            <pubDate>Wed, 02 Jan 2019 16:37:55 GMT</pubDate>
            <atom:updated>2019-01-02T16:37:55.252Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ggLQfiQ4hIuBdQFsUPJQrg.png" /></figure><p>I’m writing this as I fly 30,000 feet somewhere above the Canadian prairies on Christmas. I guess there’s nothing quite like a 5-hour flight to make you reflect. These are my musings on lessons that I have learnt over the past year being in a leadership role and mistakes that I have made. I hope you find a point or two that resonates with you.</p><h4><strong>Be Vulnerable.</strong></h4><p>I was in a weekly product team update meeting. We were giving a demo and update of our ongoing projects. As soon as I finished my update, my manager called me out for not doing something that I committed to a few weeks prior. I could hear the laughter and chuckles in the room. My initial reaction was one of embarrassment and annoyance. My mind immediately ran to think of excuses. But I knew he was in the right. I swallowed my ego and agreed that I would do what I said I would.</p><p>It took me a few days to un-package that in my head. It upset me that I was put on the spot like that, but it dawned on me that allowing myself to be vulnerable and accepting of criticism was an invitation for others to be honest with me. And by being vulnerable and accepting of criticism, I was also encouraging others to do the same as well. People relate better with others’ weaknesses than their strengths. Ego and self-pride have no place in being an effective leader. As a leader, you can take that first step and set an example.</p><h4><strong>Shut up and listen.</strong></h4><p>When I started doing 1 on 1’s with my direct reports, I did most of the talking. I felt I had a lot of knowledge to share that would be useful for them to learn. However, by dominating the conversation, I was robbing my direct-reports of having the opportunity to learn for themselves. Instead of leading in with “teachable moments”, I stopped talking as much and started asking more questions. What were they looking forward to this week? What was the thought process in their design decisions? What design assumptions were they making? By leading in with questions, it created a learning opportunity for both sides. It allowed me to understand where they needed support and guidance, and it allowed them to uncover insights and connect the dots for themselves.</p><p>To clarify, this isn’t an invitation to interrogate your direct reports. People can pick up on bullshit and disingenuousness. I was genuinely curious and invested in my direct-reports’ career journey. If you have that mindset and heart, you will be more curious about what they have to say rather than what you have to say. One of the rewarding moments is when your direct report can share with you something that they learned on their own. Even if you knew the answer already, it’s going to be more impactful coming from themselves than from what you could have said. Keep the “I told you so” to yourself.</p><h4><strong>People will rise (or fall) to your expectations.</strong></h4><p>Joining a startup at such an early stage, I was the “lone-ranger” designer during the initial years at Chalk. I had to wear multiple hats as a designer. And I loved it. It was so rewarding to have an immense impact from the daily work I was doing. I took great pride in that I had the various design skills to provide value to the company on different levels.</p><p>Fast forward a few years, we hired a communication and a product designer. Now we had folks that could do what I used to do. I knew the design process inside out. I knew our products like the back of my hand. I had deep industry knowledge. It was difficult for me to entrust someone else to do a job that I knew I could execute on.</p><p>One day I heard a saying that people are going to do as well as you expect them to. And it became apparent to me there was a major flaw in my old thinking. If you don’t trust your teammates to get the job done, how will you be able to view them as people with immense potential? This limiting mindset is going to trickle down into your daily interactions with them. You are going to be dismissive of any work or idea that they bring if you don’t believe they are valuable. Trust your teammates, empower them, and set clear expectations. You will find more often than not that people will step up to the challenge.</p><p>Shout out to (the other) <a href="https://medium.com/u/4cff1676113b">Kevin Lee</a> for writing feedback &amp; polishes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba35eb603fc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Forward thinking UX that your users will love]]></title>
            <link>https://medium.com/chalk-talk/forward-thinking-ux-that-your-users-will-love-9491b4d4aaae?source=rss-e85db783cfe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9491b4d4aaae</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kevin L]]></dc:creator>
            <pubDate>Mon, 27 Jul 2015 17:52:42 GMT</pubDate>
            <atom:updated>2016-01-11T16:07:31.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gfCUua15NLrICLZL.jpg" /></figure><p>There’s something quite exciting about turning an idea into a real thing. That’s a role many UX designers fill working in early-stage startups. To accomplish this, one of the first things we as designers do is to conduct early user interviews and look at what other products in the market are already doing. This process helps identify required use cases that we need to design for.</p><p>This user study process was very helpful when our team designed the first iteration of <a href="http://www.markboard.com/">Markboard</a>, a web application that helps teachers capture and assess their students’ learning. In the spirit of lean UX, we launched a MVP (minimum viable product) that would be validated and adopted by our users at a basic level. The app was not fundamentally ground-breaking from what the rest of the market was already doing. It simply helped our users get their job done.</p><p>Following the launch of Markboard, I was approached by one of our ed-tech specialists to envision the next iteration of the app. He had been in talks with various Canadian and American school districts and was excited about the discussions he’d been having. He had identified some of the latest teaching best-practices that Markboard needed to adopt in order for it to become a leader in the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*ZaQCuD0mM_7X0HsE.jpg" /></figure><p>The only problem? We were uncertain how that would look in conjunction with our pre-existing app. How do you integrate best-practice use cases without creating an idealistic or unrealistic user experience? Just because you think the user should adopt a best practice, doesn’t mean that they will. It was vital that these best-practices were implemented in a way that would become a natural extension of the user’s current workflow.</p><p>In order to do this, I needed to better understand how a teacher actually works. Fortunately for me, our ed-tech specialist happens to be a former high-school teacher. I asked him questions and clarification on terminology and concepts that gave me insight into a teacher’s world. Through this, I was able to gain valuable insight into our users. I came to understand their workflow and the pain-points that they face.</p><p>With this insight, I established a framework of constraints and guidelines that reflected a realistic user experience. Instead of going in the deep end of designing complex and idealistic solutions, I set myself a boundary to work with. This became a great way to validate whether or not these best-practice solutions were intuitive and relevant to our users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sjXWhN2K2VsfQsud.jpeg" /></figure><p>With this said, there will always be a learning curve that comes with new product features. A practical strategy to address this is to provide users with accessible avenues (help page, info tooltips, walkthroughs, etc..) to learn how to use new features and understand why they would use them. Enticing your users by providing actionable benefits is also a great strategy. For instance, if the user is required to input data that will be used later, let them know about its benefit and purpose early on.</p><p>Introducing new innovative ideas and best practice can be a challenge. The last thing you want to do is create naïve design solutions that users don’t buy into. Get into your user’s head- understand how they perceive and work through the problems that they face. Your users will thank you for it.</p><p><em>Originally published on July 27, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9491b4d4aaae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chalk-talk/forward-thinking-ux-that-your-users-will-love-9491b4d4aaae">Forward thinking UX that your users will love</a> was originally published in <a href="https://medium.com/chalk-talk">Chalk Talk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>