<?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 Sewook Wee on Medium]]></title>
        <description><![CDATA[Stories by Sewook Wee on Medium]]></description>
        <link>https://medium.com/@sewook?source=rss-77be7038fb92------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FyX-40D8Uys_SkYhU8ZqkQ.jpeg</url>
            <title>Stories by Sewook Wee on Medium</title>
            <link>https://medium.com/@sewook?source=rss-77be7038fb92------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:42:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sewook/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[Receiving candid feedbacks from your direct reports]]></title>
            <link>https://sewook.medium.com/receiving-candid-feedbacks-from-your-direct-reports-5583dc51d8f0?source=rss-77be7038fb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/5583dc51d8f0</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Sewook Wee]]></dc:creator>
            <pubDate>Sat, 13 Jul 2024 22:57:53 GMT</pubDate>
            <atom:updated>2024-07-13T22:57:53.948Z</atom:updated>
            <content:encoded><![CDATA[<p>Providing feedback can be intimidating, especially when the recipient is your boss. It requires courage, and when the person on the receiving end isn’t mature enough, it can backfire and cause various degrees of harm. I learned this lesson the hard way.</p><p>Years ago, I had a manager who solicited feedback about his performance. Trusting him, I mustered the courage to be honest. I told him that while I generally enjoyed working with him, there was one trait of his that drove me crazy — a sentiment echoed by others. Unfortunately, he repeatedly brought up my feedback defensively, saying things like, “Well, you said this, but you didn’t understand the context.” He even made jokes about it. These incidents made me uncomfortable, and most importantly, he didn’t change. So, what was the point of taking a risk and giving him my feedback?</p><p>For years after that experience, I avoided giving candid feedback to my superiors. That changed when I met another manager who invested significantly in our relationship. His efforts gave me the confidence to share my feedback. When I did, he took it seriously and constructively. I was amazed to see my feedback reflected in his yearly personal improvement goals.</p><p>These experiences taught me crucial leadership lessons about receiving feedback:</p><ul><li>You won’t receive enough open and honest feedback from your direct reports. Silence doesn’t mean you’re doing fine.</li><li>Appreciate any feedback you receive. My team is taking a risk by being honest. Making that risk worthwhile encourages more openness.</li><li>Invest in your relationships with my team at every touchpoint.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5583dc51d8f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Strong Performer]]></title>
            <link>https://sewook.medium.com/strong-performer-71d5cce6d5b4?source=rss-77be7038fb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/71d5cce6d5b4</guid>
            <category><![CDATA[high-performance]]></category>
            <dc:creator><![CDATA[Sewook Wee]]></dc:creator>
            <pubDate>Fri, 01 Sep 2023 16:04:51 GMT</pubDate>
            <atom:updated>2023-09-01T16:05:21.664Z</atom:updated>
            <content:encoded><![CDATA[<p>Who’s a strong performer? How to become one? As a manager and a mentor, people often ask me this question. I have a mental model that focuses on three aspects that I want to share with you. I believe this model applies to all job functions and all levels.</p><h3>Fundamentals (“Know How”)</h3><p>This is about knowledge, experience, and skill sets. Both soft and hard skills. Strong performers continue to develop themselves. They deliberately allocate their time (both work time and personal time) to sharpen up your fundamentals. They take online courses, go to conferences and trainings, participate in meet-ups, execute personal projects, etc. As a result, they tend to make better technical decisions for their work, and be efficient and productive in executing their work.</p><h3>Business Acumen (“Know Why”)</h3><p>This is about orientation and alignment. Strong performers understand the customer problems, company’s mission, strategy, products and services, business model, and priority. By having this big picture view, they know their team’s role and what’s important and how much. As a result, they tend to produce the outcome that fits the original need (“why”).</p><h3>Execution (“Get There”)</h3><p>This is about rigorous execution. Strong performers produce results. They are disciplined and consistently deliver. They anticipate the obstacles and mitigate them in advance. They communicate the status and risk to the stakeholders. As a result, they contribute to the business and their words are trusted.</p><p>Continuously assessing and developing yourself on all three of these makes you a strong performer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71d5cce6d5b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is a management track for me?]]></title>
            <link>https://sewook.medium.com/is-a-management-track-for-me-cec77b01ccc0?source=rss-77be7038fb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/cec77b01ccc0</guid>
            <dc:creator><![CDATA[Sewook Wee]]></dc:creator>
            <pubDate>Tue, 29 Dec 2020 05:35:15 GMT</pubDate>
            <atom:updated>2020-12-29T05:35:15.161Z</atom:updated>
            <content:encoded><![CDATA[<p><em>[Disclaimer: All views expressed on this post are my own and do not represents of any entity whatsoever with which I have been, am now, or will be affiliated.</em></p><p><em>This post is a recap from Career Story event organized by SNU in SF Bay Area group on 12/3/2020.</em></p><p>Manager가 될 것인가? 아니면, Technical track에서 더 깊이 팔 것인가?</p><p>이 고민은 회사생활 5~10년사이에 많은 사람이 하게 됩니다. 일을 잘한다고 인정받는 사람일수록 더욱 그렇습니다. 고민하는 패턴도 비슷합니다. 고민의 중심에는 Management track에 대한 막연한 두려움이 있습니다. 두려움은 크게 두가지, 첫째는 내가 지금 가장 잘하는 일에서 감을 잃어버리고 도태될 지 모른다는 두려움, 두번째는 내가 사람 상대하는 일을, 특히 의사소통을 잘 할지에 대한 두려움입니다.</p><p>이런 고민을 하는 후배들에게 제 일관된 조언은 “management track을 도전해보라&quot; 입니다.</p><p>좋은 메니져가 된다는 것은 본질적으로 좋은 사람이 되는 것입니다. 그래서 좋은 매니져, 좋은 리더가 되는 것은 여러모로 쓸 일이 많이 있습니다. 나중에 좀더 자세히 다루겠지만, 좋은 메니져는 정직해야하고, 관계에 있어서 신뢰를 쌓고 지킬 줄 알아야 하고, 자신의 의사를 효과적으로 전달해야 하고, 남의 의견을 잘 경청할 수 있어야 하고, 올바른 판단을 내릴 수 있어야 하고, 시작한 일을 마무리할 줄 알아야합니다. 이런 것들은 리더로서 뿐만 아니라 부모로서, 남편과 아내로서, 신뢰할만한 친구로서, 심지어는 Technical track에서 일하는 individual contributor로서 너무나 중요한 Quality 들입니다. 리더를 키우는데 많은 투자를 하는 회사에서 체계적인 리더쉽 교육을 받는 것은 돈을 벌면서, 하루종일 실습을 하면서, 좋은 사람이 되어가는 엄청난 기회입니다.</p><p>둘째로, 매니져가 되면 시야가 넓어집니다. 회사생활에서 시야가 넓어진다는 것은 “이 일을 왜하는지&quot;에 대한 이해도가 높아진다는 것입니다. 매니져가 되고 그 직급이 올라갈수록, 이 일이 회사의 매출, 이윤, 고객확보 등에 어떤 방향으로 어느 정도 영향을 미치는지 더 폭넓게 알게 됩니다. 일에 대한 이해도가 높을 수록 꼭 필요한 일을 꼭 필요한만큼 할 수 있습니다. 이런 이해도는 매니져로서뿐만 아니라, 나중에 혹시 technical track으로 전환했을 때 엄청난 힘이 됩니다. 매니져 입장에서, 이런 경험과 식견을 가진 technical track의 senior는 “내 맘 알아주는 고마운 동지”입니다. 괜히 떡하나 더 주고 싶을 만큼 감사한 팀원이 됩니다.</p><p>셋째로, 매니져가 되는 기회는 항상 있지 않습니다. 팀에 매니져는 1명입니다. 새로 팀이 만들어지거나, 기존의 팀에 팀장이 없어지거나 (퇴사 또는 그 위로 승진) 하는 등의 이벤트가 있어야 기회가 열립니다. 그리고 그 기회가 열리길 기다리고 있는 사람은 많이 있습니다.</p><p>결론적으로, 항상 있는 기회가 아니고, 매니져가 되어서 배우는 건 평생 써먹을 life skill이며, 아니다 싶으면 technical track으로 돌아올 수 있고, 돌아왔을 때 오히려 사랑받는 individual contributor가 될 수 있기 때문입니다. Nothing to lose!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cec77b01ccc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A friend of mine asked: I have an academic focused team member who works on problems interesting to…]]></title>
            <link>https://sewook.medium.com/a-friend-of-mine-asked-i-have-an-academic-focused-team-member-who-works-on-problems-interesting-to-9654d019e138?source=rss-77be7038fb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/9654d019e138</guid>
            <dc:creator><![CDATA[Sewook Wee]]></dc:creator>
            <pubDate>Fri, 27 Sep 2019 01:40:33 GMT</pubDate>
            <atom:updated>2019-09-27T01:40:33.308Z</atom:updated>
            <content:encoded><![CDATA[<p>A friend of mine asked: I have an academic focused team member who works on problems interesting to him, but not delivering products. How can I turn him around?</p><p>This is one of the common questions I get, and I also suffered myself. So, I think it’s worth to share my thoughts here.</p><p>Let’s call him James for now.</p><p>I assume that</p><ul><li>your company needs to deliver values to customers,</li><li>There are a lot of great ideas and works to be done than your team size.</li><li>It’s important to prioritize, focus, and be pragmatic.</li></ul><p>First of all, you cannot change what others want. If James couldn’t care less about your company making money and paying the bill, he doesn’t belong. So, don’t sweat on him.</p><p>Otherwise, if he likes to deliver values, but what he values are not what you value, it’s time for alignment discussion. You should share how your team is measured for success, and translate it to how you measure his success. It’s basically saying that what you value is not by your own preference or style, but by the expectation on your team. That means he should choose to align or to move on.</p><p>Lastly, think about whether there’s a way to maximize his value add while him being himself as is. You may want someone in your team who’s constantly exploring and is good at that. If you can afford, keep him explore. Don’t forget to periodically remind him what jewel you’re waiting for. Then, pair him up with someone else who’s good at delivering more defined work — something James defines out from the exploration. There are many people who enjoy it more than open exploration.</p><p>Again, there’s no wrong person. There’s only misalignment and unspoken expectation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9654d019e138" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership roles in the engineering team project]]></title>
            <link>https://sewook.medium.com/leadership-roles-in-the-engineering-team-project-814cb606f4c2?source=rss-77be7038fb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/814cb606f4c2</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Sewook Wee]]></dc:creator>
            <pubDate>Sun, 25 Nov 2018 19:05:26 GMT</pubDate>
            <atom:updated>2018-11-25T19:05:26.275Z</atom:updated>
            <content:encoded><![CDATA[<p>Leadership roles in the engineering team project</p><p>For an engineering team project to be successful, it needs four different leadership roles: Product manager, project manager, technical lead, and people manager.</p><p><strong>Product manager</strong> owns direction, definition, and goals of a project.</p><p><strong>Technical lead</strong> owns the designs, architecture, and implimentation details.</p><p><strong>Project manager</strong> owns the execution of the plan.</p><p><strong>People manager</strong> owns each individual member’s career development, performance evaluation, hiring and retention.</p><p>With that, there are two takeaways in designing your team.</p><ol><li>The need of four different roles doesn’t mean you need 4 different leaders. In real world, you see a leader plays 2 out of 4 roles with the help of (or partnership with) 1 or 2 people filling the gap.</li><li>Each role requires different strength. You need to understand what’s your strength and which roles you can play the best. Then, more importantly, you need to find your complimentary partner to fill the gap. Try not to play all four roles yourself, because it doesn’t scale.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=814cb606f4c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>