<?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 Jing Huang on Medium]]></title>
        <description><![CDATA[Stories by Jing Huang on Medium]]></description>
        <link>https://medium.com/@jingooo?source=rss-536ed63e9a70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yTGu3MjE_8VWvqmm.jpeg</url>
            <title>Stories by Jing Huang on Medium</title>
            <link>https://medium.com/@jingooo?source=rss-536ed63e9a70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:52:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jingooo/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[Some of my learnings from Stanford’s AAEP]]></title>
            <link>https://medium.com/@jingooo/some-of-my-learnings-from-stanfords-aaep-d72876d85b25?source=rss-536ed63e9a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/d72876d85b25</guid>
            <category><![CDATA[asian-american]]></category>
            <category><![CDATA[ascend]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[stanford-gsb]]></category>
            <dc:creator><![CDATA[Jing Huang]]></dc:creator>
            <pubDate>Sun, 18 Aug 2019 03:55:44 GMT</pubDate>
            <atom:updated>2019-08-18T03:55:44.360Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week, I attended Stanford’s Asian American Executive Program. This is a week-long program that focuses on U.S. Corporate culture and how Asian Americans can better adapt to it. I’m writing this post to share my learnings from the program since I enjoyed every component of it and truly learned a lot.</p><p>Some of you may ask why does Stanford create an executive program just focusing on one ethnic group? In this case, shouldn’t there be a program for African Americans, for Latin Americans, etc? I had the same doubt, and here is what I learned.</p><p>In the U.S. corporate world, Asian Americans are the most likely to be hired to a white-collar job, but least likely to be promoted to management level. Asian men are least likely men and Asian women are the least likely women to be promoted to executive levels. This may or may not be news to some of you, but it is quite eye-opening for me. At the opening session of this program, Mr. Buck Gee introduced to us the Executive Parity Index (EPI). EPI is the ratio of one group’s representation at the executive level versus its representation at the professional level. So if one company has a total of 10 Executives, including 2 Asian, and the same company has a total of 100 Professionals, including 40 Asian. Hence, Asian are 20% of Executives and 40% of Professionals. In this example, the EPI for Asian is 20% / 40% = 0.50, significantly below parity. You can read more details about the index here: <a href="https://www.ascendleadership.org/page/EPI.">https://www.ascendleadership.org/page/EPI.</a>As you can see from the EPI graph below, Asian men hold the lowest ratio among men, Asian women hold the lowest ratio among all groups! As I thought about this, all my doubts of why Stanford hosts an executive program focused on Asian Americans went away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wCs8_MvrnBA68oXJ9kyFBw.png" /><figcaption>Executive Parity Index 2017</figcaption></figure><p>Now that we know why such an executive program is especially beneficial to Asian Americans, the second step is trying to understand why and how it can be improved. Among all the reasons, culture difference is one of the top ones we mostly tend to give. But what is culture, how can we identify the key differences? Also, culture is not unique to Asians. Even though this program caters to Asian American, it’s really about decoding American culture and essential skills that will help everyone to be more successful. There are a couple of courses in this program that touched on different aspects of corporate culture. Prof. Charles O’Reilly walked us through the examples of big corporates failing to adapt to change, name a few: Kodak, Blockbuster, GM, Sports Authority, etc. He also deep dived into a couple of successful turn-around stories, ie. Fujifilm, IBM, Ford. The key take away for me is “culture can be a double-sided sword for any transformation a corporate hopes to perform”. Culture could be your competitive advantage, it also could eat strategy for breakfast.</p><p>If we didn’t understand what culture really is, there is no way we can lead any organization successfully. So what is culture? I love the definition Prof. Charles O’Reilly gave: Culture is a social control system that already operates within your organization. Culture is the pattern of behavior that is reinforced by people &amp; system over time. In other words, culture is not the words you put on your office wall; culture is not what you say in all hands. Culture is what people do with or without enforcement. Culture equals to social norms! As a leader leading a transformation, you must find ways to change the social norms within your organization. For the past year and a half, my work requires me to be a leader that can drive transformation effectively. This simple yet profound wisdom enlightened me! After this class, I feel more prepared than before.</p><p>Now, we understand that culture is just norms in values and behaviors. This program also designed multiple lectures to help us understand behaviors that can help management development. For example: asking, acting with power, motivating others, negotiation, etc. And the aim is to improve awareness of different behaviors but are not asking anyone to question their values.</p><p>My primary work focus for the past year has been scaling: scaling in terms of team, scaling in terms of technology. This is why I believed Prof. Huggy Rao’s lecture on “Scaling management team” to be especially beneficial. One of my favorite quotes is “Scaling is renovation. “ This quote is given by Prof. Huggy Rao on the 2nd day of the program. How I interpret this: you cannot gain the ability to write “100” by writing “1” a hundred times! Even though the focus of the course is on hiring and scaling leadership team, I found many tactics can be applied to scaling any team in the corporate setting. My focus is on scaling the machine learning capability in my company. It feels like a completely technical challenge at first glance. While it’s true that there are many technical challenges on the way, but the real challenge is how to form the team. Who do I recruit to the team can be a deciding factor for future success. Prof. Huggy introduced concepts like “pre-mortem” and “DEFT”. I found DEFT very interesting. DEFT refers to: Diversity within the team; Expertise of the team members; Fault lines within the team; Timing of the team expansion. So, here are a couple of steps to help avoid some of the blind spots while expanding the team. First, carefully assessing the timing of fresh hires. Second, understand the current team’s DEFT. Third, map out the desired D and E of the new team composition. Identify gaps. Ideally, the new team should maximize knowledge diversity and technical skills while minimizing fault lines introduced by new members.</p><p>And among all the great things, the most invaluable thing to me is this: the program deliberately invited many successful senior Asian American executives as guest speakers. They are the best role models! They showed me how it could be done with our proud identity. I want to thank @Buck Gee and @Wes Hom especially! Because of their work on EPI, we started to gain more awareness of the issues the Asian community is facing. And they didn’t stop there, they devoted their time and energy, tirelessly trying to help the community. All of their research work can be found here: <a href="https://www.ascendleadership.org/page/Research">https://www.ascendleadership.org/page/Research</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d72876d85b25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things I learned from hiking — part 2]]></title>
            <link>https://medium.com/@jingooo/things-i-learned-from-hiking-part-2-f116ce0f349c?source=rss-536ed63e9a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/f116ce0f349c</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Jing Huang]]></dc:creator>
            <pubDate>Mon, 27 May 2019 05:25:27 GMT</pubDate>
            <atom:updated>2019-05-27T05:25:27.351Z</atom:updated>
            <content:encoded><![CDATA[<h3>Things I learned from hiking — part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i3QXnLwyqPQ-TwXSrVoaiA.jpeg" /><figcaption>Hiking to Everest Base Camp</figcaption></figure><h4># Acclimatization</h4><p>If you have ever traveled to high altitude region, you’d understand the concept of acclimatizing. In short, the higher we climb, the lesser oxygen available for us to consume. Our body needs time to adapt to the thinner air. Each body adjusts differently, so it’s crucial to figure out your limit and give yourself ample time to acclimatize. I have done a couple of hikes that have an average altitude higher than 14000ft. It took a couple of try-fail-adjust to figure out my range of limit. I learned 2300m increase a day is out of my limit through hiking Iztaccihuatl trail. I learned from hiking in Daocheng, I can comfortably climbing 800m each day. Over time I became more knowledgable about my physical limitation. This knowledge became my guideline for later planning.</p><p>I started to draw interesting analogies from high altitude acclimatization to our work life. For example, the process of figure out one’s speed to acclimatize is very similar to the process a software development team takes to figure out its velocity. The better I understand my physical limit, the better I can plan for future trips. The better a team understands its velocity, the better it can plan for future projects. Like how I figured out my speed to acclimatize, a team would need to take many iterations of try-fail-adjust to understand its velocity. These iterations are also important training processes. It not only tests your velocity but also builds it. Before planning for longer, more challenging trails, you need to build your stamina to allow a larger margin for error. Before it can be trusted with larger, riskier projects, a team needs to build consistency in delivering velocity.</p><p>Thinking from a different angle, the journey of acclimating to higher altitude is similar to adjusting to the increasing responsibilities and higher expectation in your career. For hiking, the higher you climb, the heavier your backpack makes you feel. For your career, the higher you climb, the heavier your responsibilities make you feel. Just like the thinner air keeps testing my physical limits, the increasing level of stress keeps testing my mental limits. So maybe I can apply the same lessons learned from hiking to my career: Keep improving my knowledge about myself, set the right expectations, and give myself enough time to acclimatize.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f116ce0f349c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things I learned from hiking — part 1]]></title>
            <link>https://medium.com/@jingooo/things-i-learned-from-hiking-part-1-ab7398727976?source=rss-536ed63e9a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab7398727976</guid>
            <category><![CDATA[hiking]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Jing Huang]]></dc:creator>
            <pubDate>Mon, 13 May 2019 06:52:36 GMT</pubDate>
            <atom:updated>2019-05-13T06:52:36.581Z</atom:updated>
            <content:encoded><![CDATA[<h3>Things I learned from hiking — part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OeDWe3_AsqL3N7omfy6s1A.jpeg" /><figcaption>Yangmaiyong, Yading</figcaption></figure><p>I caught in a very bad cold last week. There was a day or two, I couldn’t talk at all. My productivity went low, so did my mood. I opened my journal of past travel trips, trying to ease my anxiety and feel better. While reading my own journal, I realized how much I have learned from my past hiking trips. I also realized these learnings are just as useful for everyday life as they are for hiking.</p><p>#1 Setting up small milestones. My journal first brought me back to my backpack trip to Daocheng, Sichuan, China. The physical and psychological crux of the whole trip was the grueling hike up to Songdu pass, the highest point for the route(4750m). I felt agonizingly slow. I wanted to take rest with every step, I wished for a miracle that something or someone would carry me to the top. But I knew the only miracle I could count on is myself. I started to manage my breaths and steps carefully. “Inhale, exhale.” I started to count my steps against each breath. I set a goal to hike at least 20 steps before I could take a short break. With that rhythm, the endless hike became manageable since I only focused on getting 20 steps every time. It took me half an hour to up climb the last 200 meters. I stood at the pass, looking back on my footsteps, that feeling of accomplishment was indescribable. Here comes my first lesson from hiking: setting up small milestones. Steer your direction based on your bigger goal, but maintain your focus on the next immediate milestone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*es8akLO7GQvJqOi85-dINQ.jpeg" /><figcaption>Hiking up to Songdu pass</figcaption></figure><p>To be continued ……</p><p>I am writing this post on Mother’s day weekend. While reflecting on critical moments in my life, I always feel so fortunate. I am fortunate that I could be my Mom’s daughter. I am fortunate that my Mom planted the seeds of seeking excellence in me while I was little. I am fortunate that my Mom taught me to be strong, to be independent, and do not limit myself because of my gender. Happy mother’s day, Mom! I love you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab7398727976" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts on technology transformation]]></title>
            <link>https://medium.com/@jingooo/thoughts-on-technology-transformation-7b289e058be3?source=rss-536ed63e9a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b289e058be3</guid>
            <category><![CDATA[technology-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Jing Huang]]></dc:creator>
            <pubDate>Sun, 05 May 2019 05:33:16 GMT</pubDate>
            <atom:updated>2019-05-05T05:33:16.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P6iK9erw91Ycvz6cRrsMkQ.jpeg" /><figcaption>Grey Glacier, Patagonia, Chile</figcaption></figure><p>Thoughts on technology transformation</p><p>“Transformation” seems to be one of the common themes among most tech companies nowadays, regardless of its size and stage. In the software arena, the ability to transform quickly has been one of the deciding factors for many companies in the past two decades. The PC transformation, the web transformation, the mobile transformation, the cloud transformation, to list a few. Software companies that lived long enough must have managed to go through these transformations successfully.</p><p>We took the result of these transformations for granted when we look backward. However, it’s full of uncertainty when we stand in front of a big change that yet to happen. Just imagine if we place ourselves back to 2012, that’s the year Facebook started its journey of mobile transformation. That year, mobile revenue was negligible for Facebook. It takes vision and bold execution strategy to say “no more new features till we become mobile first.”. This probably is the fastest way a company can ever steer and execute on a tech transformation. For most established companies, tech transformation usually takes place with a more long term and phased approach. It takes longer, but less disruptive. It requires a company-level strategic analysis to decide on how fast a particular transformation needs to be completed. What I am interested though, is what are the tactics we can use to manage these transformation phases, so that it can be effectively executed and more enjoyable at the same time. Here are a couple of my thoughts around this, leave me a comment if you like to share your thoughts.</p><p><strong># translate the technical decisions to the business outcomes.</strong> Most Engineers are hands down to get things done every day. It’s the management’s job to communicate the business value. It is important to help engineers work with a purpose especially when a project doesn’t involve developing new features or generate immediate revenue.</p><p><strong># Skill sets upgrade. </strong>Tech transformations require engineers to upgrade their skillsets. Make sure learning resources are provided to engineers early throughout the process. Tech transformations can be a much more fulfilled journey if it can help engineers to acquire new skill sets.</p><p><strong># Be Mindful with task assignments. </strong>It may seem most productive to ask engineers to contribute according to their domain expertise. During a prolonged transformation project, repetitive work may introduce stagnation, boredness and affecting morale. When it comes to planning and task assignments, there are a couple of things to consider: periodically change the area of responsibilities for engineers who showed signs of fatigue; give engineers opportunities to learn and work on different parts of the product. If appropriately managed, technology transformation can also be an excellent opportunity to solve some historical issues. For example, reduce the single point of failure, foster knowledge sharing, etc.</p><p>On an unrelated note, I’m witnessing my two years old son undergo his transformation every day. It is fascinating to see him transform from infancy to toddlerhood, from immobility to mobility, from cooing to talkative. Isn’t every one of us consistently going through some transformation in our lives?</p><p>I want to end this post with a belief I think can be applied to both transformations happening in our life and work: transformation is a journey, not a destination. What shaped us is the journey, not the destination.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b289e058be3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Things I wish I knew when starting my first job]]></title>
            <link>https://medium.com/@jingooo/3-things-i-wish-i-knew-when-starting-my-first-job-fb227786b250?source=rss-536ed63e9a70------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb227786b250</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Jing Huang]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 03:41:44 GMT</pubDate>
            <atom:updated>2019-04-29T03:41:44.235Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sGxWghUY3jsEd2tUMgmtcA.jpeg" /><figcaption>Life is a long hike, every step counts</figcaption></figure><p>When I graduated from graduate school more than a decade ago, I found myself lucky enough to start a career as a software engineer in one of the biggest tech companies in Silicon Valley. As a new grad, securing a good job offer should have made me feel more relaxed and confident. However, it made me feel more anxious than ever. Just like many international students, my learning and understanding of the American work culture was very scattered and limited. Many things played in my head constantly, and I was so unsure about how will I perform or even survive. English is not my native language, would I be able to express myself effectively? I had never worked in the United States, how would I read people’s reactions correctly? No one in my extended family circle could provide me any practical advice, who would I talk to if I needed help? Now, many years have passed by, and I have long grown and passed that initial stage. I’m writing this post to note down my learnings from that period and hopefully, it will be a useful resource for younger generations who are facing a similar situation as they start their career.</p><p>I still remember my first big assignment. It was a project potentially impacting 14 Million revenue, and I was just 3 months into the job as a new grad. It felt unreal, stressful and extremely honored all at the same time. I was 120% pumped to get this opportunity even though my back head voice consistently whispering “Are you sure?”.</p><p>I was confident I could deliver it, as long as I had enough time. But that enough time was vague. At that phase of my career, I wasn’t very good at scoping my work; I hadn’t mastered the complicated software architecture of that product; I didn’t quite understand the up and downstream interdependencies this project has. All of these needs time to figure out. But I was not sure how much time that would be, could be less or more …… When my manager told me the expected timeline of delivery, I didn’t feel confident to raise my concerns. Instead, I took this assignment as a test for my skill and ability to deliver. There was that fear of being judged and I would lose the opportunity. For a couple of months, I often stayed in the office till midnight. Nuts and potato chips were my companions. Luckily, I had great senior mentors who were guiding me through the journey, some of them even stayed late in the office debugging with me. Sadly, even with me putting many extra nights and weekends. I still slipped the asked delivery date. I felt like a failure, incapable of keeping one’s promise. I took it all on me. Without a second of hesitant, I pushed myself even further. Eventually, I delivered the project one month after the initially assigned deadline. Everyone on the team was praising me. Management was very happy, even give me a merit bonus reward despite the fact I was late on the initial timeline. However, I was not happy, not as I’d expected. Simply because I knew I couldn’t work like that for any longer, I was at a breaking point. I even started doubting my ability to do my job well without breaking myself.</p><p>While writing this down, I wish I had the opportunity to go back in time to tell my younger self how do handle this better.</p><h4>#1. Don’t assume.</h4><p>Don’t assume you should know the answer. For any question and doubt you have, ask! If you are not confident in your verbal communication, write the questions down, send a follow-up email to clarify.</p><h4>#2. Managing expectations.</h4><p>It was one of the most valuable mindset changes from being a student to a professional worker. The goal of managing expectation is to build trust. “Trust is consistency over time!” Managed expectations over time will give you that consistency and people will trust you.</p><p>For a student, you are expected to get as high marks as you can, it’s all about you. But in the professional world, it’s no longer about you, it’s about the team, the product, the company. The ability to manage expectations is mutually beneficial for you and everyone works with you. If I could manage to get my first manager to understand the right level to expect from me, then I would not need to work to a level to almost break myself. My manager, my mentor, my team wouldn’t need to risk slipping an unrealistic timeline that potentially might impact millions of dollars of revenue.</p><h4>#3. It’s all about learning. Don’t take work feedback personally.</h4><p>You might be an introvert who grew up in Asian culture. It’s natural for you to observe and self-correct. The fear of being judged might push you away from speaking up. When all these fear haunted you, just remember, it’s ok to be wrong and it’s all about learning. You might stop carrying the title as a student, but your learning ever stop. You will find all your courage when you feel safe to be wrong.</p><p>Now, many years passed by, these bumps are my treasure boxes collected along the way. Just like <a href="https://medium.com/@joulee">Julie Zhuo</a> (Product design VP @ Facebook) who inspired me to start writing more, I’d like to pass on my treasure boxes to whom might be benefitted.</p><p>Lastly, my special thanks to my co-worker Shubhi and Jessica who encouraged me to start this journey of writing with them. As part of a challenge three of us committed, also as one of my personal goals this year, I am committed to writing something every week. I look forward to the next treasure box I will collect along this new exciting journey!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb227786b250" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>