<?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[John’s Reflections - Medium]]></title>
        <description><![CDATA[Thoughts &amp; reflections on technology, startups, and life - Medium]]></description>
        <link>https://medium.com/johnkchow?source=rss----4d81247b2525---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>John’s Reflections - Medium</title>
            <link>https://medium.com/johnkchow?source=rss----4d81247b2525---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:35:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/johnkchow" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Good Strategy Bad Strategy — Book Report]]></title>
            <link>https://medium.com/johnkchow/good-strategy-bad-strategy-book-report-c59fc56c2066?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/c59fc56c2066</guid>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Mon, 19 Oct 2020 04:27:00 GMT</pubDate>
            <atom:updated>2020-10-19T04:27:28.416Z</atom:updated>
            <content:encoded><![CDATA[<h3>Good Strategy, Bad Strategy — Book Report</h3><p>About a month ago I started working on a project where I had to help formulate a technical strategy for a very large project, so I thought this would be a good time to learn how to think about effective strategies. I found a lot of resources (particularly from Will Larson’s wonderful <a href="https://staffeng.com/guides/learning-materials">staffeng.com</a> website), but a few of the blog posts recommended the book <a href="https://www.amazon.com/gp/product/B004J4WKEC">Good Strategy Bad Strategy: The Difference and Why It Matters</a> so I decided to read it. Overall I enjoyed the book and learned a few things from it. I recently decided that I’m going to try and write book reports just to further help me internalize the key points.</p><p>There’s no particular structure to bullet points below, as I ossicilate between summarizing the key takeaways from the book and sharing my own personal commentary.</p><ul><li>The beginning of the book focuses on characteristics that make certain (in my opinion most) strategies ineffective. The author Richard Rumelt characterizes bad strategies having the following qualities: <em>fluff, failure to face the challenge, mistaking goals for strategy, </em>and<em> bad strategic objectives.</em></li><li><em>Fluff</em> is pretty straightforward, so I’m not going to spend much talking about this one. But if I were to define it, it’d be “words that make your eyes roll.”</li><li><em>Failure to face the challenge</em> means when the strategy doesn’t acknowledge the real underlying problem or obstacle that the organization faces. In one of his case studies, Rumelt describes International Harvester’s strategy as “high-sounding sentiments together with plans to spend more and somehow ‘get better.’” Another key quote that best captures this concept (bolded mine): “If you fail to identify and analyze the obstacles, you don’t have a strategy. Instead, you have either a <strong>stretch goal, a budget, or a list of things you wish would happen</strong>.”</li><li><em>Mistaking goals for strategy</em><strong><em> </em></strong>is something I see in a lot of my past companies (e.g. grow sales by X%) yet fortunately I don’t see too often here at Stripe (one of the major reasons I wanted to <a href="https://johnkchow.com/why-im-joining-stripe-and-going-back-to-an-ic-role-48795cc8cf62?source=collection_home---4------4-----------------------">join Stripe</a> was to see how effective organizations run, and I think I made the right decision here). I suspect that many startups sets high level goals, mistaking it for strategy.</li><li>Rumelt presents two categories that fall under<em> bad strategic objectives: </em>a) dog’s dinner objectives and b) blue-sky objectives. Dog’s dinner is something I’m guilty of committing in the past: simply presenting a todo list. Blue sky objectives simply mean setting impossible/vague tasks. This is common in the startup-world, since you don’t form startups without having <em>some </em>irrationality in you.</li><li>Rumelt presents some potential reasons why people choose bad strategy. One of them is the unwillingness/inability to make a tough decision. This manifests in trying to tackle too many things at once, stretching the organizatin thin and diluting the product quality or focus. I’ve also seen leaders punt making tough decisions because they’re afraid hurting others’ feelings.</li><li>Rumelt talks about the history behind “template-style strategy”, which was really fascinating. I won’t re-hash the history (it’s a long but good read), but template-style strategy is “a reduction of charismatic leadership to a formula: (1) develops or has a vision, (2) inspires people to sacrifice (change) for the good of the organization, and (3) empowers people to accomplish the vision.” It seems like many corporate strategies that are publicly available follow this formula (and in startups, this is pretty much the status quo).</li><li>While having a vision isn’t as valuable as having a solid strategy, I still think writing down a long term vision is useful. It’s helpful to know specifically what the ideal end-state <em>should</em> be. I use it as guiding posts as I’m thinking about what are the specific obstacles that are preventing the higher level goals and whether the problem I’m trying to solve actually aligns with that vision. If there’s no alignment, then perhaps the vision isn’t realistic or the right one. Adjust the vision, rinse and repeat.</li><li>Rumelt provided ~100 year historical context behind the New Thought movement, a major contributor to the current prevalent thinking that strong leadership is having immense self-confidence and having a “winning” attitude at all times (e.g. “We <em>will</em> defeat the enemy!”). I’ve seen many TED talks and self-help books talking about self-actualization and pushing away negative thoughts, and this is especially prevalant in the startup culture, so it’s fascinating to learn about the history behind the current leadership culture.</li><li>Chapter 5: The Kernel of Good Strategy. Finally, the good stuff! Good strategy has at the very minimum three elements: 1) a <em>diagnosis</em> of the challenge/opportunity, 2) a <em>guiding policy</em>, and 3) a set of <em>coherent actions </em>designed to carry out the guiding policy.</li><li>Rumelt makes the point that having the proper <em>diagnosis </em>is a critical (if not the most critical) piece of a good strategy. Identifying the problem enables one to look back in history (whether it’s from personal experience, blogs/books, or interviews with other people) to pattern match similar problems and apply a past solution that worked. In other words, how you frame the problem can quickly constrain the solution space. Effectively diagnosing the root problem is a hard challenge since there are many ways to interpret the underlying problem, and having an incorrect diagnosis can lead down a costly and wrong path.</li><li>The <em>diagnosis</em> element reminds me of the Situation/Complication elements from the <a href="https://strategyu.co/scqa-a-framework-for-defining-problems-hypotheses/">SCQA</a>, a tremendously valuable writing framework that I learned from Jeff Weinstein at Stripe. The biggest value I got from SCQA was to consciously think and write down the actual problem I’m trying to solve vs trying to prescribe a solution upfront. Many times when I write down what I think the problem is, I realize either a) I have a huge knowledge gap in the problem space (and I should talk to more people to better understand the problem) or b) I completely mis-diagnosed the actual underlying problem (and I should talk to some more people). If there’s one thing that has helped me in my career, it’s dedicating time to writing out my <em>perceived</em> understanding of the world.</li><li><em>Guiding policy</em> is a really nuanced but, in my opinion, really insightful concept. Rumelt best describes it as the following (bolded mine): “Good guiding principles are not goals or visions or images of deseriable end states. Rather, they define a <em>method</em> of grappling with the situation and <strong>ruling out a vast array of possible actions</strong>.” He then goes into examples of comparing visions to guiding policies e.g. Wells Fargo has the corporate vision of “satisfy all our customers’ financial needs [and] help them succeed financially”, but their guiding policy was to cross-sell their financial products as much as possible (although in retrospect this may had the unintended consequence of fostering a toxic culture, resulting in Wells Fargo’s illegal activities up until 2016).</li><li>The final element of a good strategy is defining what <em>actions</em> to take. They should be “consistent and coordinated” with one another, where coordination is not “ad hoc mutual adjustment” but rather “coherence imposed on a system by policy and design.” While coordination can be powerful, it can make the organization overall less efficient, and so the potential gain must be worth the cost.</li><li>Explicitly writing out goals (and non-goals) is somewhat similar to writing out the guiding principles. It helps reduce the solution space. However, the key difference is that goals/non-goals doesn’t necessarily suggest what general actions can be taken (although it can constrain the solution space so much that it’s obvious what the only path forward is).</li><li>In part 2 of his book, Rumelt focuses on “sources of power” for good strategies. There are some gems in this part and some that confirms existing beliefs (which is reassuring!). I won’t focus on all of them, but I’ll talk about the ones that I found insightful or resonating.</li><li>Rumelt talks about setting <em>proximate objectives</em>, which is basically setting an objective that you have high confidence in achieving. When the situation/environment is really complex and it’s hard to predict the future beyond a certain time horizon and can cause analysis-by-paralysis. By setting a proximate objective and committing to it, it unblocks the organization to come up with some near-term goals that directionally goes in the right way. This chapter resonated with me, and I recently went through an excercise at Stripe where proximate objectives was a really useful tool.</li><li><em>Chain-link systems </em>describe interlinked processes, organizations, or competitive strengths that collectively brings more value than the sum of the individual parts. Interestingly, sometimes investing in just the weakest link by itself can be more detrimental than doing nothing at all. This is something I had never considered deeply before, so I was really excited to learn about this.</li><li>Having intentional <em>design </em>when constructing a strategy is a “configuration of resources and actions that yields an advantage in a challenging situation.” The tradeoff, however, is that there’s an overhead cost with all the coordination. Additionally, if you had better resources (e.g. more engineers, people with specialized expertise, large streams of revenue, etc) then coordinating all your resources and actions may not be necessary. On the flip side, having better resources can make organizations become complacent and masks the need for a coherent strategy.</li><li>In chapter 11 “Dynamics”, Rumelt talks about an “attractor state”, which describes an ideal state where the buyers’ needs and demands are efficiently met with the lowest cost possible. He used IP addresses as an example. In the 1990s, many networking hardware companies created proprietary network protocols, which caused friction for ITs/businesses as they’re trying to integrate different networking solutions. The attractor state is a novel concept for me, and I’m storing this in my toolbox for future use.</li><li>Part 3 is more brief and less substantive than the first 2 parts, but in many ways it’s the most important section: tactics on how to actually form good strategy. The tl;dr? At the end of the day, forming strategy is no different than the scientific process: you’re making a highly educated guess based on data/observations that’s readily available (and your experiment is the execution of that strategy). So to think as objectively and clearly as possible, explicitly writing down your thoughts like the challenges, competitive advantages, goals/non-goals, guiding principles, etc. forces you to take a stance, which can then later be reviewed as you get more data/feedback on the strategy. Rumelt also suggests trying to actively tear down your strategy. One tactic he suggested was to think of different personas in your life (e.g. Steve Jobs, your manager from your last company, etc) and try to think about the problem/solution-space from their perspective.</li><li>In the last chapter, he finally ends with “Keeping Your Head,” which talks a about how to not not let your biases cloud your judgement. It reminded me of <a href="https://www.amazon.com/dp/B005MJFA2W/ref=dp-kindle-redirect?_encoding=UTF8&amp;btkr=1">Thinking, Fast and Slow</a>, another fantastic book.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c59fc56c2066" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/good-strategy-bad-strategy-book-report-c59fc56c2066">Good Strategy Bad Strategy — Book Report</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slowing Down]]></title>
            <link>https://medium.com/johnkchow/slowing-down-7eb2bdf97d35?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/7eb2bdf97d35</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[self-love]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Sun, 08 Dec 2019 01:38:08 GMT</pubDate>
            <atom:updated>2020-08-18T04:13:50.138Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W313oyy_qdjx3Flfzfm0Hw.jpeg" /><figcaption>The slow novice (eventually) wins the race.</figcaption></figure><p>In my last blog post, I wrote about <a href="https://johnkchow.com/small-startup-vs-big-company-39c76e9d5120">my experience so far at Stripe</a> (which has been great). I’ve been exposed to a lot of new and different ideas, both technically and organizationally, and I’ve learned more about how to build great software at a bigger scale. I’ve also settled into my role and finally feel like I have solid footing in the domain (Banking Platform and <a href="https://stripe.com/docs/api/payouts">Payouts</a>) that I’m working in.</p><p>However, it wasn’t a completely smooth journey, and I didn’t anticipate how long it’d take for me to feel settled in at Stripe (~6 months). It took me a while before I had a solid grasp of my team’s domain and its history, particularly when trying to understand both internal and external dependencies. Relatedly, because I wasn’t familiar with the opaque financial domain, it also took me longer to understand how Stripe organized and operated internally. There were times where I felt frustrated at my own learning process and my inability to contribute more than I had planned, and I was uncomfortable being in a position where I was dependent on others.</p><p>While there were certainly factors that contributed to my frustrations, looking back I realize that one of the biggest reasons was that I had set too high of expectations for myself, and instead of showing self-compassion I became incredibly hard on myself. I took on the <a href="https://www.amazon.com/Mindset-Psychology-Carol-S-Dweck-ebook/dp/B000FCKPHG">fixed mindset instead of the growth mindset</a>, and I became my own worst enemy.</p><p>I also didn’t realize that transitioning from being an engineering manager to IC (my first time going through this) would also be a process in of itself. I’ve forgotten how radically different the IC role is, especially as a newcomer to a company. As an EM, a lot of the work consists of communication both within the team and with other teams, and I didn’t realize how much I actually enjoyed the social aspect of that work, and I really got energized when I was able to help others. Stripe has a great engineering culture where there are fewer meetings in general, and while most engineers love less meetings to focus on their work, I actually initially craved more meetings just so I can get more face-to-face interactions with my coworkers! While I knew I was a social person, I didn’t realize how much of my intrinsic happiness was tightly coupled to socializing with and helping others at work until I joined Stripe.</p><p>The great news is now that I’ve settled in at Stripe, I frequently enter “the zone” and get lost in my work instead of getting hung up with unfamiliar concepts. Whenver I do encounter something that I’m unfamiliar with, I’ll take my time to read through the code and take great personal pride in learning something new along the way. Additionally, now that I’m knowledgeable(-ish), I’m able to not only collaborate with more people than before, but I’m able to give back and help share context to a new engineer that joined our team recently.</p><p>The biggest lesson I took away from all this is that in the future when I take on a new challenge, whether it’s joining a new company or changing to a new role, I should simply slow down and truly embrace being a curious novice again. Instead of prioritizing job performance and trying to build a name for myself, I should tell myself that it’s OK to slowly explore the landscape, lean on my coworkers more for questions and optimize for learning instead. Additionally, to maintain my self-compassion and motivation for learning, I should continuously remind myself that when I eventually become knowledgeable, there will be plenty of opportunities to work with others and contribute in ways beyond just my immediate responsibilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eb2bdf97d35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/slowing-down-7eb2bdf97d35">Slowing Down</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Small Startup vs Big Company]]></title>
            <link>https://medium.com/johnkchow/small-startup-vs-big-company-39c76e9d5120?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/39c76e9d5120</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 02:32:43 GMT</pubDate>
            <atom:updated>2019-11-04T02:49:38.760Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been over 6 months since <a href="https://johnkchow.com/why-im-joining-stripe-and-going-back-to-an-ic-role-48795cc8cf62">I’ve joined Stripe</a>, and it’s been a really wild journey. In our recent Stripe Sessions, we announced during the <a href="https://stripe.com/sessions/2019">keynote</a> the beta launch for the project that I’m working on, Cross Border Payouts (formerly known as Global Payouts). While I’m excited for the huge milestone (Github will be one of our first users for their <a href="https://github.blog/2019-05-23-announcing-github-sponsors-a-new-way-to-contribute-to-open-source/">Sponsors program</a>!), there’s still a ton more work to do to make it generally available for the public!</p><p>I’m finally settling into my role at Stripe, which has now given me the mental bandwidth to start reflecting my experience so far. One question that keeps popping in my head is whether I would have benefited from joining a “big” company earlier in my career. (Note: While Stripe in many ways still operate like a startup, given it’s size and code/business complexity I think it’s safe to categorize as “big”). While I have zero regrets of my personal journey, I think it’s worth reflecting my career path now with a different perspective.</p><p>I came up with 6 categories to assess whether startups or big companies would have been better in terms of my professional growth. The first 3 (systems architecture, building robust/correct systems, exposure to diverse technologies) revolve around becoming a better engineer, and the last 3 (organizational structure/processes, wearing different hats, learning from others) revolve around becoming a stronger professional/leader. Below are my assessments based on my past experiences the last 9 years.</p><h3><strong>Systems Architecture</strong></h3><p><strong>Winner: Startups</strong></p><p>Many people would argue that you’d learn more about systems architecture in a bigger company, and I don’t disagree. In order for Stripe to scale, we needed to introduce new technologies into our stack (e.g. Spark, Kafka, Kubernetes, Envoy, Java/Scala/JVM, etc), and even today we’re still evolving our architecture in anticipation of where Stripe will be 3–5 years from now.</p><p>On the team level, we’re still evolving our architecture. The broader team I’m currently part of (Payouts Experience and Banking Platform) historically confronted many major issues stemming from our architecture, and our team invested heavily in reliability, correctness, and observability in 2018. Given that Stripe has grown so much over the years (and with anticipated growth in the years to come), there will still be opportunities to improve the architecture.</p><p>Still, I think overall there’s less opportunities to change the architecture, and I learn best by actively working on a related problem vs abstractly thinking about it. As an engineer in a large organization, you don’t have to think about the tradeoffs between different data stores or message brokers; the tooling and patterns around existing system components have (mostly) matured, and there are a lot of (senior) engineers dedicated to solving these problems. The reality is that complex system components <strong>need</strong> to be abstracted away and moduralized. Engineering leverage can’t happen when engineers need to understand how all the different pieces work together, especially when those same engineers are trying to tackle very complex domain problems. While system modularity increases leverage, it does mean that there’s less opportunities to meaningfully change the architecture.</p><p>I was fortunate to have worked in high(-ish) traffic B2C startups alongside smart senior engineer mentors. I was lucky enough — or unlucky, depending on your viewpoint ;) — to be confronted with reliability issues that had real business consequence. In startups, it takes a village to tackle production incidents. This created opportunities for me to identify root causes, leverage new technologies and introduce changes across all layers of the stack. I learned the fundamental principles of scalability through my startup experiences, which are all still relevant even at Stripe’s scale. (Side note: this further reinforced my belief that <a href="https://johnkchow.com/when-does-having-a-cs-background-make-sense-2a2d7630b638">understanding the underlying theories</a> is tremendously valuable). Being confronted with scaling challenges first-hand gave me a deeper appreciation of the (sometimes nuanced) tradeoffs that different architectures present. This experience was critical in my growth as an engineer.</p><p>However, what was more crucial to my growth was having senior mentors that worked alongside me in those startups. They gave me feedback on my ideas, pointing out holes in my design, and course-corrected me when my viewpoint was too narrow or focused on the wrong things. They gave me perspective from the real world that couldn’t be captured in blogs or books. While I’m really grateful to have worked with some great people, I’m also very humbled and recognize that I’m somewhat lucky. I’ve heard of other people’s experiences where they were the most “senior” person in the small startups they worked for. It sounds like a frustrating experience, and I know that had I been in a situation like that early in my career, I would have felt like my growth was stunted.</p><h3>Building Correct, Robust Systems</h3><p><strong>Winner: Big Company</strong></p><p>I’ve been a first engineer hire for a startup and I’ve also been in startups where I helped the engineering org scale up to 50 engineers. All 4 startups I’ve worked at were either finding product-market-fit or levers for growth. In the first case where startups were looking for PMF, they didn’t have a viable business yet (or they did but it’s not looking like something that should be venture-backed). We were constantly building/experimenting in hopes of finding something that will stick; nothing built was considered “core” to the business (nor should it at that time!). In the second case where the startups were looking for levers of growth, they tended to de-prioritize investing in the core product for reasons ranging from lack of resourcing to overconfidence in their position in the market to a lack of strategic discipline. Regardless of the situation, building a correct/resilient system was rarely a priority (or if it was, it was very short lived) because they were all venture-backed startups searching for high growth at all costs, even if it means that the business will go down in flames if they miss on their bets.</p><p>In contrast, building a correct/resilient system is <strong>absolutely</strong> critical at Stripe. It makes sense: a good chunk of the internet’s GDP depends on our payments infrastructure, and our users rely on us to be highly available and reliable. So at Stripe you’ll see a lot of emphasis on correctness/resilience, starting with our <a href="https://firstround.com/review/to-grow-faster-hit-pause-and-ask-these-questions-from-stripes-coo/">operating principle</a> of <em>think rigourously</em>. This trickles down into our technical design docs, technical programs/processes (e.g. incident after-accident reviews) and in the various tooling that helps both developers implement and operators operate safely (e.g. <a href="https://sorbet.org/blog/2019/06/20/open-sourcing-sorbet">Sorbet</a>, which by the way is my favorite Ruby tool/library :). And our team, Banking Platform, is currently investing in ways to make development easier for our fellow engineers when it comes to building correct banking integrations, which I’m incredibly proud/humbled to be a part of!</p><p>So this isn’t really much of a debate: if you want to think more rigourously as an engineer, nothing beats working at a bigger company with other smart engineers and being exposed to the culture and tooling that emphasizes it.</p><p>However, I want to acknowledge that not all big companies will have a culture that emphasizes rigor within engineering. For example, companies that are either sales or product driven may not give the engineering org a voice when it comes to strategic decisions, which could result in a lack of engineering investments.</p><h3>Exposure to Diverse Technologies</h3><p><strong>Winner: Big Company</strong></p><p>In nearly all startups, a monolith service and a traditional relational DB (e.g. MySQL, PostgreSQL) gets you incredibly far. In my experience, technology choices in startups rarely matter as much as a having a simple architecture with simple code that’s easily readable/changeable. Nowadays, you can find a lot of PAAS services on the cloud (e.g. CircleCI for continuous integration, Heroku for managing applications and hosted OLTP databases, AWS Redshift/Athena for OLAP databases, etc), which frees engineers to focus on application development and building out the core product.</p><p>In my experience, rarely do startups have large enough data sets or traffic that require different technologies, and if they do, it’s not surprising that they re-purpose existing technologies and stretch them to their limits. There’s many reasons for this (and it’s not surprising): not enough engineers, lack of tenured<em> </em>senior engineers, lack of eng leadership experience, or pressures to find PMF/growth over stabilizing the system. The more a company is growing, the more likely that the company will invest in engineering. But the moment the company stops growing, the company will tighten its pockets, which typically leads to under-investment on the engineering side.</p><p>Historically Stripe was a Ruby shop working in a mono-repo, but we’re at a point where we need to use the right tools for each specific job. We have a good amount of Scala/Java in our overall codebase that’s geared towards data-intensive workloads (recently, we rewrote a critical piece of our infrastructure seeing 24–100x improvements in latency speeds). We have Kafka as our primary message broker. Our data pipelines are built on top of Spark/Flink (and we’re deprecating Scalding, Twitter’s map-reduce engine). We have large Splunk clusters for logs. We’re investing in Kubernetes to help with infrastructure orchestration. And we have a lot of in-house tools that are really incredible. I’ve already mentioned Sorbet. We also have an internal tool called Hubble that’s a great querying/visualization tool (think of Looker but much easier to use).</p><p>While it sounds like big companies are no brainers for getting exposure to different technologies, I don’t think getting exposure is as valuable as having mastery with a small number of technologies early in your career, and mastery takes a long time. For example, it took me 3 years to feel very confident in Ruby/JS, and it took me about 5 years to feel the same about relational DBs. One of the key benefits of attaining a level of mastery is you’ll have gained skills in learning <em>how</em> to learn, which makes it much easier to learn new technologies/paradigms.</p><h3>Wearing Different Hats</h3><p><strong>Winner: Startup</strong></p><p>When I was at Fundly, I wore a lot of different hats within engineering. I helped manage our EC2 infrastructure and our observability tooling, I owned both the mobile web and iOS experiences, and I helped improve site reliability. Near the end of my time at Fundly, I helped introduce new development processes such as code and design reviews. In addition to the engineering work, I also helped run lots of A/B experiments and optimized our critical funnel conversions. Given my knowledge about the product and the business, I was able to directionally influence the design/product.</p><p>When I first joined Teespring, there were a lot of opportunities to grow as a leader. I took on an EM role and oversaw a lot of projects that really challenged me professionally. In one project, I lead a team that built out a brand new revenue stream within Teespring (i.e. providing apparel fulfillment as a service within the Shopify ecosystem). I operated it like I was a cofounder of a mini startup, as I was involved with onboarding new users, prioritizing our backlog based on our users’ feedback and helped architect the app. I also worked closely with folks in customer success, data science and manufacturing.</p><p>Looking back, I feel incredibly lucky to have worked on so many different projects in such a relatively short period of time. At Fundly, I learned a diverse set of engineering skills, which I was able to critically leverage in Teespring/Reflektive (and now Stripe). Being exposed to so many different functions at Teespring helped shaped my viewpoint that building a great software business<em> </em>is a team effort ranging across many different areas of expertise. This greater appreciation also helped create a deeper empathy towards folks outside of engineering (e.g. marketing, ops, sales, etc), which helps me create stronger relationships when collaborating with other teams.</p><h3>Organizational Processes/Structure</h3><p><strong>Winner: Big company</strong></p><p>Early on in my career, I cared less about structure/processes and more on getting stuff done. And when you’re in a small startup, there’s no need for processes because everyone knows what everyone else is doing. Processes and structure aren’t necesary (and maybe even detrimental) for small startups.</p><p>However, about 4 years into my career, I started taking on tech lead responsibilities, and then a year later jumped into an <a href="https://johnkchow.com/why-i-m-becoming-an-engineering-manager-teespring-90704532f808">Engineering Manager role</a>. As an EM, I had to learn on the fly on how to prioritize backlogs, manage incidents and measure team health/performance. While I relished the new challenges I’ve never seen before, I have to admit that it was sometimes stressful to making decisions without any prior experiences to back it up. Still, I learned a lot through trials by fire (much like how I learned how to be a better engineer through production incidents!).</p><p>By the end of my time at Reflektive (which was about 2 years into my management career) I started to feel like I was <a href="https://johnkchow.com/why-im-joining-stripe-and-going-back-to-an-ic-role-48795cc8cf62">hitting my ceiling</a> as an EM. Had I worked in a company like Stripe many years ago, I feel I would have had more tools to lead effectively. For example, at Reflektive I felt our engineering culture didn’t emphasize enough on operational excellence. My strategy to change this was to create a program focusing on just my team (i.e. identify and monitor key operational metrics, have a giant TV running our operational dashboards, introduce design docs with an emphasis on capacity planning and rollout plans), prove it’s value and then help spread it across the engineering organization. Unfortunately, it didn’t spread beyond my team, and at times I felt like I wasn’t building enough momentum within even my team. At Stripe, I’ve seen first hand how technical programs around operational excellence have scaled across the org, and had I known what I know now, I would have done things a little differently.</p><h3>Learning from others</h3><p><strong>Winner: Big company</strong></p><p>There were a lot of very talented people that I’ve worked with over the years in startups, and I feel very fortunate (and humbled) that nearly every startup I’ve worked, I had at least one mentor whom I both admired and and learned a lot from. Startups provided me with role models that had a profound impact in my engineering career (as I’ve mentioned in the Systems Architecture section above).</p><p>However, when I reached a certain level in engineering leadership and wanted career advice from more senior leaders, I didn’t really have a network that I could reach out to. Most of my network were either non-managers or around my age who haven’t held engineering leadership positions for long. Here at Stripe, I’ve met many different people and got exposure to different behaviors/mindsets, which is pretty much what I wanted prior joining Stripe.</p><p>Looking back at my career so far, I don’t have any regrets. Working in startups have taught me a lot about engineering, business, leadership and — more importantly — about myself. I learned the importance of moving with urgency, aligning engineering with the user/business needs and maintaining focus/passion in every day’s work, even on days that are emotionally draining. I also made a lot of amazing memories and many good friends along the way.</p><p>However, if I’m going to be honest, I would have benefited greatly had I joined a big company instead of joining Reflektive. I joined Reflektive because I wanted to double down on the managerial path. While I learned a lot on how to build strong relationships with my reports, Reflektive was roughly similar to Teespring in size, which meant that many situations were also similar. My overall perspective didn’t broaden as much as I had hoped. If I had joined a bigger company instead, I would have seen first-hand how healthy engineering organizations scale and operate, and I would have developed an even deeper perspective around technical leadership. I feel I’ve learned some things in the last 6 months that would help me when I eventually get back on the management track.</p><p>So would I recommend starting your career in startups vs big companies? I think there’s a better question instead to ask: which sets of experiences are you lacking that would make you a more well-rounded professional? When looking at it from this lens, it matters less where you start but instead it matters more about your cumulutative experiences over a long period of time.</p><p>I like to compare our <a href="https://lethain.com/forty-year-career/">long careers</a> to having an investment portfolio. The most resilient investment portfolios are the ones with a diverse set of investments with a long time-horizon view. Similarly, we need to approach our careers by having a diverse set of experiences, and recognizing that not every job can provide it all (although it’s possible to get a wide range of experiences in a single company).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39c76e9d5120" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/small-startup-vs-big-company-39c76e9d5120">Small Startup vs Big Company</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working Agreement and Definition of Done]]></title>
            <link>https://medium.com/johnkchow/working-agreement-and-definition-of-done-73c5ed16145c?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/73c5ed16145c</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Sun, 01 Sep 2019 04:36:24 GMT</pubDate>
            <atom:updated>2019-09-06T16:26:34.729Z</atom:updated>
            <content:encoded><![CDATA[<h4>How defining your team’s values can foster psychological safety and improve team performance.</h4><p>There’s a saying that when teams are formed, they go through four stages: <a href="https://blog.trello.com/form-storm-norm-perform-stages-of-team-productivity">form, storm, norm, perform</a>. The general idea is that teams will inevitably go through some period of conflict, as it takes time for new teammates to understand each other’s working styles and core values. Through repeated conflicts, the team will eventually converge towards a shared understanding and mutual respect towards one another. In other words: the high performing stage can only be achieved once the team has built up trust with each other.</p><p>While I was at Reflektive, the whole Product-Engineering org went through Scrum training. One of the first exercises we did was to create the <a href="https://www.clearlyagileinc.com/agile-blog/how-working-agreements-help-scrum-teams">Working Agreement</a> and <a href="https://www.scrum.org/resources/blog/walking-through-definition-done">Definition of Done</a> documents for each of our teams. At first the exercise seemed kind of silly, since most teams have formed for a while now and we thought we knew each other well. However, as we went through listing the things that we each cared about and talked through people’s disagreements, we were able to uncover gaps of information and deeper rooted problems. It was through this process we converged towards shared understanding and mutual respect.</p><p>For example, at Reflektive the eng leadership decided that as an organization we’re going to commit to writing acceptance level (i.e. browser based) tests as part of our development process. Although there was general agreement within the eng org that we <em>should</em> do more acceptance level tests, there was tension between the embedded QEs and devs over who does what at what time of the development cycle. In both of my teams’ Definition of Done sessions, the topic of testing and ownership came up.</p><p>Those conversations became a little tense, and I could have easily stepped in as the manager and shut down the conversation, but I knew that it would rob people the opportunity to “storm” and learn more about their coworkers. Instead, I took on the facilitator role and made sure that everyone was heard (especially the quieter ones). Whenever the temperature dialed up, I’d jump in and de-escalate the situation by either rephrasing statements in a more neutral tone (which acknowledges the original sayer yet makes the content more receptive to the group) or listing the commonalities between differing view points.</p><p>As we talked more and more, people started revealing their deeper concerns. Some people were worried that since individual teams will be moving “slower” (because of less time spent on development and more on testing), they’ll be reprimanded for their performance. Concerns also came up around lack of tooling for both QEs and devs. And devs were worried that a majority of their time will be spent writing acceptance tests vs engineering work (i.e. building out the product or improving the system in some fashion).</p><p>Once we talked through these issues, we eventually converged to the shared understanding that a) as an organization we’re saying that it’s OK that teams will be going “slower” short-term (so that we can move faster in the long run), b) that when devs write at least one happy path acceptance test, not only does it prevent future regressions but it also helps QEs since they’re less familiar with our data models for setting up tests. We captured these into both our Working Agreement (“We believe in writing acceptance tests”) and our Definition of Done (“We will write one happy path acceptance test per User Story”).</p><p>Writing these documents didn’t magically solve all our problems. It took many more conversations, both private 1x1s and team retros, and little tweaks to the documents before people felt comfortable with the new agreements. Still, these conversations help set the precedent that as teammates we can be vulnerable with each other, which then eventually enabled the team to self-organize and hit the <a href="https://johnkchow.com/m2yl-measuring-team-performance-b9fbff5fed41">perform stage</a>.</p><p>The most important thing about these exercises is less about the resulting artifacts (i.e. the team documents for both Working Agreement and Definitions of Done) and more about having a real conversation — as a team — of what we value. Rarely do people get together to talk about their values, but it’s incredibly important for team members to not only understand each other’s viewpoints, but to then be able to honor and respect it. It’s this trust-building process that lays the foundation for how teammates work with each other, thus enabling teams to operate at a higher level.</p><p>In order to have these conversations, it requires an environment where psychological safety and genuine curiosity are emphasized. Playing the facilitator role by asking for people’s opinions, patiently going a <a href="https://en.wikipedia.org/wiki/Five_whys">few levels deeper with the whys</a> and helping people find common ground makes a big difference. Otherwise, people may withhold their real opinions or, worse, people will just shut down at the workplace altogether.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73c5ed16145c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/working-agreement-and-definition-of-done-73c5ed16145c">Working Agreement and Definition of Done</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Thing I’ve Learned @ Reflektive]]></title>
            <link>https://medium.com/johnkchow/one-thing-ive-learned-reflektive-d1942634dbc5?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/d1942634dbc5</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[empathy]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Sun, 14 Apr 2019 23:32:25 GMT</pubDate>
            <atom:updated>2019-04-14T23:42:06.469Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BYVUIYY7XFYNTEFVYqc2gg.jpeg" /></figure><p><em>I was talking to a coworker of mine at Reflektive before my last day, and she asked me what were the things that I’ve learned at Reflektive in the last 2.5 years. I thought it was a great question, and I want to share one profound lesson I’ve learned: the power of having empathy.</em></p><p>Prior to joining Reflektive, I’ve always wondered if being nice and being successful were mutually exclusive things. One question that I didn’t have a solid answer to was when push comes to shove, which choice would I make? However, I realize that this is a false dichotomy. It’s not about being <em>nice</em> but rather having <em>empathy</em> is what we’re really looking for. And once I’ve started approaching situations with empathy, it really then enabled me to achieve my goals and lead me to a happier, healthier life.</p><p>The distinction between being <em>nice</em> and having <em>empathy</em> is very nuanced. Being nice means that you don’t want to rock the boat with other people, which usually manifests in not confronting people when you don’t see eye-to-eye with them about how to make decisions, what behaviors are acceptable to you and what they can do more of to help you or the team more. Without those kinds of tough conversations, conflict will never be resolved, which then leads to a toxic environment. Having empathy, on other hand, is really trying to understand where the other person is coming from and trying to resolve conflict in a way that’s emotionally healthy for both sides. In some ways, avoiding confrontation could be considered a selfish act because it robs the other person of a better outcome.</p><p>I realized that, despite all our differences, everyone that I’ve ever worked with all want to achieve the same things: enjoy team/company success, be proud of the work that we do, master our craft and work with others that bring joy and energy into our lives. It’s this realization that has enabled me to approach conflict and confrontation differently than before. Whenever I’m in a situation where I disagree with someone (or vice versa), instead of getting defensive and coming off angry or blaming, I would instead be curious and apply actively listening to better understand the root cause of our disagreement and then working with the other person to identify whether there’s something I could have done more (i.e. maybe I misunderstood his intent or I didn’t communicate effectively enough), a misunderstanding on their part or whether there are certain circumstances that’s distorting our perspectives. Finally, I would then respectfully try and bridge the gap between us and steer the conversation so that we can reach an agreement that’s to the betterment of team/company.</p><p>In retrospect, I realized that having empathy really helped me in situations where I wanted to be proactive and have a greater impact within the company. By listening to others and being mindful of everyone’s intentions and circumstances — while constantly clarifying my own intentions — it was easier to bring people together to understand what large opportunities are out there and how we can achieve greater success. One story I’m incredibly proud of was the role I played in steering our company’s 2019 strategy. Near the end of 2018 was a really tense time for Reflektive because there was a lot of miscommunication between Sales, Product and Engineering about our overall strategy, and while there were a lot of people involved who helped steer the company to a strategy that is much more realistic and better aligned with our company mission, I truly believe that because I approached every tense conversation with empathy that I was able effectively work with fellow EM/PMs (with different personalities and beliefs) to identify the key initiatives and work estimates for what success would like had we continue our original strategy (the tl;dr is that it was way too much resources with few winning conditions). It’s through these tense experiences that reinforces my conviction that you absolutely don’t need to be an asshole to achieve success.</p><p>None of this would be possible if I wasn’t internally secure about my place in the world. It took many years of <a href="https://johnkchow.com/management-two-years-later-values-bae12cda8a2a">deeply reflecting</a> and learning to appreciate every single life experience, particularly my failures. I have utmost confidence in my own skills and abilities, but I also recognize that I’m a human being who has his own flaws, that I’ll probably make my fair share of mistakes and that every situation is an opportunity to learn and grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1942634dbc5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/one-thing-ive-learned-reflektive-d1942634dbc5">One Thing I’ve Learned @ Reflektive</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I’m Joining Stripe! — And Going Back to an IC Role]]></title>
            <link>https://medium.com/johnkchow/why-im-joining-stripe-and-going-back-to-an-ic-role-48795cc8cf62?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/48795cc8cf62</guid>
            <category><![CDATA[career-change]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Fri, 22 Mar 2019 20:21:21 GMT</pubDate>
            <atom:updated>2019-11-23T03:25:11.414Z</atom:updated>
            <content:encoded><![CDATA[<h3>I’m Joining Stripe! — And Why I’m Going Back to An IC Role</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PlOUBO-mRR3almG8LrCpsA.png" /></figure><p><em>Edit note: After 6 months at Stripe, I wrote a follow-up post </em><a href="https://johnkchow.com/small-startup-vs-big-company-39c76e9d5120"><em>Small Startup vs Big Company</em></a><em> where I reflected over my experience so far.</em></p><p>In 2015, I was in a startup, Fundly, that was going through an acquisition process. In the last 6 months I was there, I was playing the team lead role: doing ad-hoc project management, incorporating new development processes (e.g. conducting early design conversations and code reviews) and doing informal 1x1s with my fellow engineers, all the while still coding. As the acquisition process came near to a close, I started to think about my next step in my career. I arrived at a fork in the road: <em>I can either enter a new domain where I’d be challenged technically and continue deepening my engineering craft, or I can look for opportunities that can help launch me further into the management track.</em></p><p>Up until that point, I’ve always been a startup guy who had never worked at a company bigger than 60 people. (Technically the first company I worked at, O’ Grady Meyers, was bought by Meredith, a giant media conglomerate, a few months after I joined. Still, OGM never fully integrated into Meredith by the time I left so I still fondly look back at it as a startup experience). Because my network of friends were also mostly working in small startups themselves, I didn’t have as much exposure to different kinds of engineering (i.e. data, devops and infrastructure). I naively thought that application development was the only kind of work that really matters. While I definitely loved doing software engineering, I started feeling comfortable and plateauing as a full-stack application developer. Combined with my strong desires at the time to do my own startup in the future, I felt that career-wise it’d be best if I began focusing on leadership and management instead.</p><p>Thus, I joined Teespring because I saw a clear opportunity for me to eventually become a manager one day. Teespring ticked all the boxes that I was looking for: a “unicorn” company with well-known investors, huge hiring plans for its engineering org and an exciting startup environment that I knew I could make an impact in (I mean who <strong>doesn’t</strong> want to disrupt the t-shirt business?!). After 6 months of being a team lead, <a href="https://johnkchow.com/why-i-m-becoming-an-engineering-manager-teespring-90704532f808">I was promoted to an EM role</a>. The first 3 months as an EM were tough (I would come home <strong>exhausted</strong> every night because I was learning how to deal with spending most of my days talking to people instead of quietly coding), but every trying experience made me grow stronger as a leader. It was an amazing experience as I worked with some smart, driven people, and we built some amazing pieces of technology that solved interesting problems for our customers. My experience made me feel that as an EM I could make an even bigger impact for a business than if I was just an IC.</p><p>I decided to double down on the management track and joined Reflektive in 2016 because I felt I could get great mentorship to better my management and leadership skills. The head of engineering, Erick Tai, genuinely cared for his team, both on a personal and professional level, so I felt that I could learn a lot under his guidance. Additionally, I figured I’d learn all the best practices on being a manager since their HR software was all about helping companies foster a culture of constant feedback.</p><p>When I officially became a manager at Reflektive 18 months ago, I decided to focus 100% of my efforts in that role. That meant that I completely stopped coding and empowered the engineers with making all the technical decisions. I channeled my energy towards providing my team with as much business context and advocating on behalf of the engineers to the rest of the business. I looked for opportunities to grow my team, either through direct mentorship or finding projects that challenged them professionally. I partnered with fellow EMs and PMs to improve our development processes, ranging from contributing to the release process to facilitating the adoption of scrum to introducing a technical design document process to my team. Reflektive also had formal manager training, which helped me with how I construct and deliver feedback and conduct 1x1s.</p><p>By the end of 2018, I had groomed two team leads and delegated most of my day-to-day responsibilities to them. The two teams I oversaw were running smoothly with little intervention on my part, and many people in Reflektive said that’s a testament to the good work I’ve done as a leader. Additionally, because I contributed with Reflektive’s mini-pivot away from our primary 2018 strategy (a huge engineering cost with few winning conditions), there was even less challenging work on my plate as an engineering manager.</p><p>The feeling of being comfortable started settling in again. I tried looking for new opportunities to make an even bigger impact across engineering in Reflektive, but I felt like I couldn’t make big changes through just indirect influence alone. I felt uncertainty with where I can grow and what my next career step is.</p><p>Continuing down the management track was the logical option I considered, which meant becoming a director of engineering one day. Being in a director position at Reflektive would give me the authority to make sweeping changes within the engineering organization, which would enable me to have a greater strategic impact. However, it wasn’t very clear what exact path I needed to take to groom myself for that positional leap at Reflektive, nor was it clear how long that learning process would take. Even if the director path was concretely laid out for me at Reflektive, I felt like I’d do both myself and Reflektive a disservice if I pursued that role given my limited exposure to higher-level directors. (Both Teespring and Reflektive didn’t have director roles not including the heads of engineering, so I don’t have a strong sense of what’s considered being a “good” director versus a “bad” one.) Given that there’s much more at stake when you’re higher up, I didn’t want to operate through trial and error.</p><p>Last November, I started seeking advice from people about how I could go about my next step in my career, specifically how to prepare myself for a director role. Ironically, the feedback I got wound up pushing me to go back to an IC.</p><p>An experienced friend of mine bluntly told me that my work experience has been only limited to medium-sized companies (≤ 400 employees, ≤ 50 engineering teams) and web app technologies like Ruby on Rails and relational databases. As a director, I will probably have to oversee teams or work closely with other teams that operate in domains I have little familiarity with, and it’ll be harder to initially inspire confidence with the troops if you don’t have that “street cred.” There are two forms of managers, he argued: those who are hands-on with the team and continues giving architectural guidance, or those who completely get out of the way and just shields the team from organizational distractions. There’s no right or wrong way to be a manager, but he suggested that if I want to be the former type, I would benefit from broadening my technical perspective. There’s a whole slew of technical challenges that I haven’t experienced yet, whether it’s working with big data, working with alternative data stores or dealing with scaling challenges on a whole new level. Having that kind of exposure would enable me to make better strategic decisions down the road. He also mentioned that bigger companies operate at a much more mature scale, so joining a big company will give me a deeper perspective into what good engineering practices/processes really look like.</p><p>His feedback brought me back to the same exact fork in the road that I faced in 2015: <em>I can either enter a new domain where I’d be challenged technically and continue deepening my engineering craft, or I can look for opportunities that can help launch me further into the management track.</em></p><p>The red pill, or the blue pill.</p><p>For a split second, his feedback was a punch in the gut and I felt foolish for thinking I was ready to be a director. But after the initial sting went away, it suddenly hit me that this is an amazing opportunity to deepen what I still enjoy: the craft of software engineering. I continued to learn and grow as an engineer outside of work; in my spare time I would research deeply technical topics such as information retrieval, database internals, operating systems and scalable distributed systems just for fun. Several of my close friends worked at big companies like Twitch and Uber the last few years, and I realized that our conversations around the product/design problems they faced also involved talking about the interesting underlying technical challenges that had to be overcome.</p><p>Unlike in 2015, where I thought creating software was as trivial as rails generate scaffold User and storing data in some managed PostgreSQL, I have a deeper understanding and appreciation of how technology choices truly are sources of differentiation for many companies. For example, technologies like Apache Storm and Spark has enabled companies to process data at scales never seen before with near real-time capabilities. High-availability data stores like Apache Cassandra are powering global systems like Uber’s and Facebook’s. (Side note: If you peel away a few of the layers for these technologies, you’ll see the familiar data structures and algorithms that we’ve learned to loathe in university. It may sound corny to hear, but there’s a real beauty in seeing these complex systems built on top of basic building blocks that I’ve learned nearly 12 years ago.) I feel I understand the <em>theory </em>of building a scalable distributed system, but hearing his feedback triggered something deep within me and made me excited again: there’s still much more room to grow.</p><p>In addition to wanting to scratch the engineering itch in me, a part of me wanted more financial security, something that a bigger company could provide. If I went back in time 5 years ago and told my former self what I just said, I think he’d be absolutely shocked. But my situation and goals are a lot different at age 32 than age 27. Back then, I wanted to optimize for autonomy and growth, and I was in such a rush to accomplish my career goals. If it weren’t for the startups I’ve joined, I don’t think I would have grown as much as I did across all dimensions. But now I’m marrying the love of my life, and I’m starting to think about what it’d be like to start a family. Several of my good friends who have worked in big companies recently told me that they’re grateful for the opportunities their financial situations afford them (buying a house, taking on more creative projects, not worrying about their children’s tuitions). While having autonomy and making an impact is still really important to me, I realize that I’d be much happier providing for and spending more time with Steph, my family and friends.</p><p>Finally, I believe that deepening my engineering craft in a big company will make me a much better technical leader, which will enable me to be an even more effective manager down the road. I always tell engineers that regardless of role or title, leadership is leadership. As a manager, I tended to operate a bit more on the strategic level: given all the different priorities and data that we have about the business and our team, <em>what</em> do we want to focus our team’s efforts? However, when it came to the implementation phase I depend heavily on key engineers at Reflektive to define out <em>how</em> we intend on executing against our roadmap, and executing it in a way that not only solves the requirements in a timely manner but also somehow improves the system long-term. This creates a natural feedback loop where the <em>how</em> sometimes opens up doors for the <em>what </em>that was previously thought impossible to do. It was through this experience that further deepened my appreciation for strong technical engineers who can lead projects across the finish line. Leaders in general are hard to come by, which makes the technical ones even more crucial. By broadening and deepening my technical expertise, I believe that it will further enable me to define the technical vision that brings engineering value beyond solving the immediate requirements, which will then further enable me to understand and identify critical strategic opportunities for the business.</p><p>After interviewing with some of the bigger companies, I decided to join Stripe, specifically the Payouts Platform team. There were three criteria that I valued most: impact, learning, and great team culture. Stripe and the Payouts Platform team ticked all those boxes.</p><p>Payouts is a critical component to Stripe’s value proposition (I mean, nothing gets more critical than giving our customer’s money to them with accuracy and in a timely manner), and because Stripe has aggressive plans to penetrate even more countries in 2019 (essentially doubling their presence in total number of countries), Payouts will be crucial in the growth plans. One example that I learned recently: while Brazil has a population of 200 million, nearly 90% of the credit cards issued in Brazil cannot be used to purchase goods outside of Brazil. Payouts will play a huge role in reducing the barriers to accept payments for merchants. Additionally, because it’s Platform work, the team’s responsibility is to support multiple teams across the organization with a reliable and simple interface. I know that whatever work I’ll do in the team will have great impact within the company.</p><p>There will be tons to learn at Stripe. The problem space itself is extremely interesting: how do you make inherently unreliable 3rd-party integrations power a reliable capability for the rest of the company, how do you build out the platform in such a way that doubling or tripling the number integrations will require minimal effort, and how do you guarantee correctness of the amount to be paid out to the merchants when dealing with a messy world of archaic banks with wildly varying SLAs, fraudsters and customer disputes? On top of that, what is the right abstractions that we want to provide to our upstream clients that provides them the capability of transferring funds from one account to another while at the same time hiding the complexities of the complex domain?</p><p>While it’s a Ruby-first shop, I’ll be working with Sinatra, Kafka and the document store MongoDB, which I’ve never really worked with professionally (other than building out a prototype many years ago). Because the Payouts team owns their own reporting infrastructure, there’s currently talks of rebuilding it from scratch, which means there will be potential opportunities to work with newer big data technologies as well. Also, the Payouts team manages its own Kubernetes cluster, and while the hiring manager seems keen on handing that off to a centralized devops team, I’m excited to get my hands dirty with it!</p><p>Stripe will be the biggest company I’ve ever worked for. With over 400 engineers and 1600 employees, I’m excited to see not only how it’s organizationally structured (how priorities and goals are created and how different levels of leadership operate), but also how teams build their software in a way that enables efficient interfacing between teams as well as learning different ways of thinking from the sheer number of people I’ll be working with. I’d imagine there’s going to be a ton of learning just purely through osmosis; and since I’m a curious cat, I know I’ll be sticking my nose into things that will be new and exciting to me.</p><p>I really connected with individuals on the Payouts team on multiple levels. I can see their passion and desire to build not just immediate value for the company but also do it in a way that will long term scale with the engineering and business needs. There’s strong alignment between the Product Manager and the Engineering Manager about where Payouts directionally needs to go and how building a system with rigor and correctness is a strategic asset. The EM did a really good job articulating the architecture and the vision, and I have a feeling that I’m going to have a great relationship with her. And on a personal level, I felt genuinely welcomed and really comfortable around them.</p><p>While the team is crucial, since they will be the ones I’ll be spending up to 50% of my waking life with, what also compelled me to join Stripe was its company culture. I was skeptical at first, since you’ll hear people throw out the word “culture” like it’s candy in Halloween even though they don’t have the faintest clue what having a strong culture entails (or, on a basic level, even why it even matters). But everyone I talked to, including a friend of mine who works there, talks about how they really enjoy the culture there in a sense that a) people are empowered to make decisions on an individual level, b) product and engineering work very closely together to come up with the requirements, c) the leadership team holds bi-weekly all-hands and share meeting notes with the entire company, d) the culture is blameless when there are production issues (I’ve heard positive stories of the CEO cautiously messaging on-call engineers to better understand the issues) and e) everyone is so <em>nice</em>. Each of those points are rare by itself (at least from what I’ve seen in my 9 years in startups), so to see all of them in one company is really impressive. On top of that, Stripe does a 2 week onboarding process where they not only talk about different aspects of the business, but they also walk through the general architecture of the platform and hold a Q&amp;A with members of the executive team for the onboarding group. This just further reinforces their image that they’re really a people-driven organization.</p><p>Looking back, Reflektive was an incredible experience and I don’t regret a single moment. I grew a lot as an engineer, leader and, more important, as a human being. I’m grateful to have met so many passionate and smart people in this journey. While it’s tough to leave a place that gave so much to me the last 2.5 years, I’m excited for the opportunities, challenges and people that awaits at Stripe. I can’t wait to see where I’ll be 2.5 years from now!</p><p><em>If you enjoyed this post, I wrote a follow-up post </em><a href="https://johnkchow.com/small-startup-vs-big-company-39c76e9d5120"><em>Small Startup vs Big Company</em></a><em> where I reflected over my experience 6 months into the job.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48795cc8cf62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/why-im-joining-stripe-and-going-back-to-an-ic-role-48795cc8cf62">Why I’m Joining Stripe! — And Going Back to an IC Role</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[M2YL — Measuring Team Performance]]></title>
            <link>https://medium.com/johnkchow/m2yl-measuring-team-performance-b9fbff5fed41?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/b9fbff5fed41</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Fri, 01 Mar 2019 16:12:15 GMT</pubDate>
            <atom:updated>2019-03-01T16:15:42.390Z</atom:updated>
            <content:encoded><![CDATA[<h3>M2YL — Measuring Team Performance (Pt. 4)</h3><h4>High performing scrum teams can’t solely be measured by business metrics in startups</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ycWC6I9G8fEV7Y3mLhaaQ.jpeg" /></figure><p><em>Note: This is part of a series of posts talking about my experiences and learnings the last two years. You can find the rest of the series </em><a href="https://johnkchow.com/management-two-years-later/home"><em>here</em></a><em>.</em></p><p>I’ve worked in startups nearly my entire career, so I’m most familiar with <em>product</em> <em>scrum teams</em>, or engineering scrum teams that work closely with Product and Design. Traditionally, startups will measure a scrum team’s performance through either a) how much value they’ve brought to the company or b) how much work they’ve output over a period of time. However, when the team’s performance is <em>solely</em> based on either of these two dimensions, it can lead to good engineers burning out, a culture that incentivizes wrong behaviors or a combination of both. Instead, we need to take a step back and evaluate teams with a blend of metrics and behaviors that are better indicators of a product team’s performance. Much like everything in life, there’s no magical formula that can encapsulate our understanding of people into a single number.</p><p>Let’s explore the first measurement: <strong>business value created by the scrum team</strong>. This measurement is typically tied to something quantifiable and measurable, such as conversion rates for a checkout page or how many users have engaged with a feature over a time period. In the ideal world, whatever initiative the team works on will directly impact success metrics defined upfront during the planning stage.</p><p>But in startups, there <strong>will </strong>be times when the team’s work doesn’t move the needle. This is simply <a href="https://en.wikiquote.org/wiki/Murphy%27s_law">Murphy’s Law</a>. Let’s look at success rates of startups as a proxy of how often teams will fail with their plans. Out of all startups, on average 90% of startups completely run out of money and fold. And of those 10% that stay alive, only 10% of those startups actually have any kind of meaningful exit. So using those statistics as proxy, that suggests that 90% of <em>large </em>startup initiatives are destined to fail. If you have a high performing team — or you’re in a bigger company with more resources — the probability of failure isn’t going to be that high. But let’s say that instead of 90%, it’s really a 50% failure rate. That’s still incredibly high risk.</p><p>In my experience, there’s four reasons why failures happen. Either a) the team didn’t execute the plan correctly, b) the plan that the team executed was the wrong thing to work on, c) the metric was the wrong metric to measure or d) the measurements were captured incorrectly. If we assumed that these 4 outcomes happened equally, that means that at least 25% of the time a team’s “failure” isn’t about the team’s execution. But I’d argue that lack of execution makes up a <strong>significantly</strong> smaller portion of failures. Failures tend to happen not because of the team’s <em>execution </em>but rather that the planned work was not the <em>right thing</em> to work on. Whether it’s the market didn’t need whatever we built, we didn’t do enough customer research to validate our hypotheses or the research data were interpreted with major biases, there are many reasons that new features or initiatives are doomed before a single line of code is written.</p><p>When teams decide that they should be measured against some kind of business metric, the blame for failures <strong>should</strong> go towards the decision makers, which starts at the PM/EM for each team and up the management chain to the CEO. And in healthy cultures, companies <strong>should</strong> use failures to have an honest conversation and extract lessons that can be applied in future endeavors. However, in reality that doesn’t always happen. Blame is typically applied onto the <em>whole</em> team itself, and it can be incredibly demoralizing to the individuals who weren’t involved in the decision-making process at all. After repeated failures, engineers will feel burnt out and will either want out of the product work or just leave altogether. And if you’re in the Bay Area where the labor market is incredibly tight, losing a good engineer is incredibly expensive to the company from both a time and money perspective.</p><p>Let’s explore the second measurement: <strong>output of work over time</strong>. There are many ways to measure this, but the most obvious ones are to measure the number of story points or JIRA tickets completed by the team. Measuring output of work makes sense in that being able to quickly iterate on the product is extremely valuable to startups. As I’ve outlined above, assuming that there’s at least anywhere from 50–90% chance of failure for an initiative, it makes sense that the more work we can churn out in a short period of time, the higher our chances of having some kind of success.</p><p>The problem with using team output as the primary measurement of success is that it incentivizes engineers to purely execute and not at all participate in helping the PM brainstorm and identify what’s the right thing to build. So instead of the whole team participating in this process, we’re instead reducing our assessment capabilities to just one individual: the PM. That is a case of massive underutilization of smart engineers with great analytical skills. What’s worse is that it creates a culture where slowing the team down for reasons like paying down tech debt, stabilizing the platform or reducing production firefighting will be frowned upon. It’ll also encourage engineers to “game” the system by working on <em>expensive </em>(i.e. lengthy) projects instead of <em>valuable</em> projects. This goes against the idea of working smarter, not harder.</p><p>Also, a team’s ability to quickly build and iterate is only half of the equation for success. Another important factor is the research and analysis work that determines what work brings the greatest amount of value to the company. It’s this upfront legwork that can potentially minimize engineering costs, which is a lot of time and money to the company. So if we can optimize <strong>both</strong> our ability to assess and identify what’s the most impactful work as well our effectiveness to build out the product, then we’re maximizing our chances for success.</p><p>Some people — even engineers themselves — will argue that engineers should <strong>only </strong>focus on engineering (building high quality solutions using minimal time) and leave the analysis work to the PMs. Yes, separation of responsibilities and specialization is what makes companies run efficiently. But we shouldn’t try to create hard boundaries around that. While a PM has key skills in gathering, analyzing, and assessing data from various inputs, highly motivated engineers can effectively contribute on some — if not all — of those responsibilities. Additionally, engineers can be a rich source of data for new ideas. I’ve seen many engineers who knew the product better than the PMs responsible for it. Engineers know which business logic is confusing or inhibiting our users (probably because they see how confusing the damn code is in the first place!), exactly how our customers interact with the UI, where the usability gaps are and the bugs that are impacting our customers experience.</p><p>These two measurements, <strong>business metrics</strong> and <strong>output of work</strong>, focus on the outcomes of the team, but these indicators alone are not great indicators of how well the team operates. We also recognize that each initiative in a vacuum has a low success rate, so overall success requires maximizing both our confidence levels in our plans upfront as well as the maximizing the number of initiatives we can build for in a short period of time. So instead of trying to measure/maximize specific<em> outcomes</em>, which are lagging indicators of success at best, we should instead focus on identifying which <em>behaviors </em>are predicators of team success.</p><p>If we took a step back, I believe there are three qualities that high function teams exhibit in abundance:</p><ul><li>The ability to <strong>analyze, identify and prioritize </strong>the most impactful work so that we have higher confidence with our plans</li><li><strong>High development speed</strong> so that we can both quickly iterate on new features/products and respond to new market demands</li><li><strong>Focus on quality </strong>(aka maximum uptime, smooth performance, and minimal user-impacting bugs) so that our customers won’t get frustrated and churn to another solution</li></ul><p>There are many ways that can help measure development speed and quality of work (e.g. story points, bugs, customer support tickets, number of paged alerts, etc), but how can we measure a team’s ability to analyze, identify and prioritize? This one is tough because it’s like assessing a baseball player’s ability to hit the ball: you need a lot of data points over a long period of time. Instead, we should measure certain <em>behaviors </em>that are indicators that the team is helping identify the most impactful work:</p><ol><li><strong>Do individuals in the team put the customer and team first? </strong>A related question is: do people put egos aside? This seems like an obvious thing. Of course we don’t want egotistical people in our teams! Who wants someone that’s all about themselves! But in my experience ego is a very subtle thing. While having some ego is powerful (and maybe even necessary) in motivating people to do amazing work, it can also slowly poison a team if not managed properly. There’s a reason San Antonio Spurs and the New England Patriots have been so successful the last few decades: it’s because their team culture does not allow me-first attitudes. <br><br>It’s easy to spot if the team is focused on the customer through the questions and concerns raised by the team. For example, if during backlog grooming you see people pushing back on value to customer or advocating that we don’t take shortcuts and conversations aren’t being shut down by anyone, then you have a healthy team dynamic. However, when the team dynamic isn’t healthy it’s much harder to pinpoint the root cause. This is because you’ll instead see a <em>lack</em> of activity/conversations, which can be harder to identify, let alone dig into.</li><li><strong>Is the entire team collectively and constantly striving for a deep understanding of the problem and the parameters for success?</strong> If the PM isn’t doing a good job effectively communicating and reaffirming the team about why they’re working on the things that they’re working, then engineers won’t even have the opportunity to poke holes into the plan. Relatedly, if the team isn’t engaged and playing devil’s advocate about the feature during team conversations, then the solution will only reach a local maxima. <br><br>A signal that I typically look for is whether teams are asking clarifying questions for a user story, especially if it’s a forward looking question e.g. “So user story says we’re building for just customer X, but we intend on signing N new customers in the next 12 months, which doesn’t it mean we should invest heavily in scalability upfront?”</li><li><strong>Will individuals in the team raise their hand when they see an issue, and does the team then take action on that?</strong> Let’s suppose that the business demands that we deliver something by the end of the quarter. Let’s also suppose the engineering team agrees that there’s no way we can deliver the project in time without either cutting scope or taking on huge technical debt. In this situation, engineers need to a) feel comfortable raising their hands, b) effectively communicate what the tradeoffs are to the appropriate stakeholders, and c) advocate for what’s best <strong>long-term</strong> for customer/team. In turn, the PMs need to respectfully listen to the concerns and then partner with the engineers to come up with a plan that works for both sides. It’s a delicate dance that needs to happen between Engineering and Product, but if done well I’ve seen great solutions come out of it.</li></ol><p>It’s harder to quantify those 3 points above because it takes time and experience to develop perspective and intuition of what specific actions contributes (or detracts) from the team’s ability to make better decisions. (In many situations it’s the <em>lack</em> of certain actions that’s the problem, and that is much harder to learn from just reading books or talking to mentors).</p><p>There are many books out there that outline what behaviors are most important to look for. A few books that have impacted me greatly are:</p><ol><li><a href="https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884/ref=sr_1_1?keywords=high+output+management&amp;qid=1551455172&amp;s=gateway&amp;sr=8-1">High Output Management</a> by Andy Grove. It’s about the Andy’s decades of management experience as the Founder and former CEO of Intel. His approach is full of logic (he compares running a business to a factory line) yet it comes from a place of empathy and respect.</li><li><a href="https://www.amazon.com/Turn-Ship-Around-Turning-Followers/dp/1591846404/ref=sr_1_1?keywords=turn+ship+around&amp;qid=1551455156&amp;s=gateway&amp;sr=8-1">Turn the Ship Around!</a> by L. David Marquet. It’s about a former captain of a nuclear submarine who helped create a culture of bottoms-up empowerment. What’s great about his story is that he also talks about his failures in his first stint as captain.</li><li><a href="https://www.amazon.com/Extreme-Ownership-U-S-Navy-SEALs/dp/1250183863/ref=sr_1_1?crid=34CV83CRSWQMY&amp;keywords=extreme+ownership&amp;qid=1551455118&amp;s=gateway&amp;sprefix=extreme+ownership%2Caps%2C196&amp;sr=8-1">Extreme Ownership: How U.S. Navy SEALs Lead and Win</a> by Jocko Willink and Leif Babin. It’s about two former US Navy SEALs officers’ views on how effective leadership leads to mission success in life-or-death situations. Their stories definitely puts perspective about the situations that we in the workforce go through, but at the same time it also highlights that leadership is leadership, regardless of the situation.</li><li><a href="https://www.amazon.com/Five-Dysfunctions-Team-Leadership-Fable/dp/0787960756/ref=sr_1_1?crid=2LHWFJNVHZWJ0&amp;keywords=five+dysfunctions+of+a+team&amp;qid=1551455274&amp;s=gateway&amp;sprefix=five+dys%2Caps%2C194&amp;sr=8-1">The Five Dysfunctions of a Team</a> by Patrick Lencioni. An extremely entertaining book about how a fictional CEO helps a dysfunctional executive see a better way in working and collaborating. It’s great not because of the story telling, but I think Patrick did a great job capturing the common archetypes we see in the workforce and thus what specific actions they do that are both good and bad.</li></ol><p>While reading these books have been extremely helpful in helping me identify the key behaviors that I want in my teams, that said though, management is <em>tough</em>. You can read all the books upfront and have the best mentors in the world, but you can’t really <em>know</em> until you’ve been through the ringer a few times. I’ve made a few mistakes in my past, whether it’s pushing my team members too hard or not pushing them hard enough. But that’s the circle of (management) life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9fbff5fed41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/m2yl-measuring-team-performance-b9fbff5fed41">M2YL — Measuring Team Performance</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[M2YL— Objective, Critical Thinking of People (Pt. 3)]]></title>
            <link>https://medium.com/johnkchow/m2yl-critical-thoughts-pt-3-7d846f8f025d?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/7d846f8f025d</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Sun, 04 Nov 2018 22:18:26 GMT</pubDate>
            <atom:updated>2018-11-13T14:34:34.956Z</atom:updated>
            <content:encoded><![CDATA[<h3>M2YL — Objective, Critical Thinking of People (Pt. 3)</h3><h4>How I started thinking critically of other people in an objective, productive and healthy way</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rVkRvtHAzloXx_7ysQ9awg.jpeg" /></figure><p><em>Note: This is part 3 of a series of posts talking about my experiences and learnings the last two years. You can find the rest of the series </em><a href="https://johnkchow.com/management-two-years-later/home"><em>here</em></a><em>.</em></p><p>One of the hardest things I had to overcome was my fear of stepping out of bounds or making someone feel bad. I was raised to respect authority and to always do what you can to help the family. As I grew older in life, “family” included my friends, teams and coworkers. That desire to put the team/company first helped me in my career; I was able to develop meaningful relationships with my coworkers which enabled me to make impact beyond just writing code.</p><p>However, this is also a weakness in that I have a hard time having critical thoughts towards other people, even in private settings. Once I transitioned into management, I was put in a lot more situations where problems weren’t binary and technical but they involved other people, whether it’s another engineer, a fellow peer in another department, my direct manager or the CEO. For these kinds of problems, the solution isn’t something that I have full control over but instead requires some kind of behavioral change in others.</p><p>As a manager, one of the primary responsibilities is to remove blockers for the team. That meant that I was responsible for identifying the root cause and dealing with organizational problems within my sphere of influence. In most situations, problems occur because there’s a gap in resources. That’s a easy problem to solve because it’s binary: more resources means more bandwidth for productivity and less resources means more unhappy people across the company (especially the engineers who became the whipping boys/girls). However, the other category of organizational problems revolve around gaps within a person or a group of people, whether it’s with technical knowledge, communication or soft skills. In my first year being a manager, the values I was brought up with unconsciously clashed with my responsibility of giving feedback to others — especially to people higher up in the organizational ladder.</p><p>One day I was venting to a mentor of mine about a certain problem I was brushing up against at Teespring, and she said that it sounded like there was poor leadership at the top. I was quiet for a moment, and then my first response was to defend my company and dismiss the idea that somehow I was working under poor leadership. She then objectively laid out her case that the conflict I was facing was a result of the leadership team saying one thing but their actions saying something completely different. Once I absorbed what she was said, she then asked me,</p><blockquote>“John, do you realize that you had trouble having critical thoughts towards your leadership team?”</blockquote><p>That was an eye-opening experience for me. I was unaware I had a hard time having critical thoughts towards others, even in a private conversation with a person I trusted. My desire to defend the leaders of my company blinded me from seeing that they had areas they could improve upon. I realized that as a manager I could play a role in influencing my superiors to do better.</p><p>Over time, that same mentor coached me into understanding that there’s a difference between <em>having</em> critical thoughts towards others and <em>being</em> <em>critical</em> to others. Having <em>objective </em>critical thoughts towards people is important in not just for your own emotional well-being, but — when applied appropriately — it will help solve organizational problems in a more effective way. <em>Being</em> <em>critical</em> to others, on the other hand, is something that’s shunned not because we as a society want to avoid sharing feedback but because historically people deliver critical feedback poorly, which makes the other party quietly feel marginalized or humiliated. I think we can all agree that <a href="https://www.reflektive.com/">receiving constructive feedback</a>[1] is something we all seek. But even if we all had the ability to <em>deliver</em> that feedback effectively, it wouldn’t matter if we didn’t have any critical thoughts to begin with. Having <em>objective</em> critical thoughts is the foundation for any kind of meaningful change.</p><p>So what does it mean to have <em>objective</em> critical thoughts? You can make an argument that no thoughts are truly objective, since thoughts are formed through our own personal lens of prior experiences and upbringing. However, there is a process where we can ground our critical thoughts to facts so that they’re as objective as possible. As with many other things, having good judgement isn’t an inherent ability but a skill that can be developed over time.</p><p>As an engineer, I naturally gravitate towards math and science, so the way I see this process of forming objective critical thoughts is very similar to the <a href="https://en.wikipedia.org/wiki/Scientific_method">Scientific Method</a>: we first must observe the situation, create a hypothesis, gather data (i.e. email/Slack, JIRA, interviewing key individuals), analyze the facts and finally decide on next action steps. The most important thing in this process is to hold off casting any judgement until the very end. As humans, we have many kind of <a href="https://corporatefinanceinstitute.com/resources/knowledge/trading-investing/list-top-10-types-cognitive-bias/">cognitive biases</a> where our brain can quickly draw conclusions even though it may not be true. When dealing with other people, drawing a wrong conclusion too early can lead to devastating consequences i.e. ruined working relationships or personal credibility.</p><p>Additionally, I’ve found it useful to share my findings with someone I trust (like having scientific research peer reviewed). Even if I did my due diligence in my fact gathering, it’s possible that my analysis was based off of a wrong perspective or I missed some key information. That said, make sure to do your due diligence first and gather all the facts. Everyone will have their own cognitive biases, so it’s important to ground ourselves to the facts.</p><p>It’s important to ask yourself throughout this process: could I have done something different to make the situation better? In Jocko Willink’s and Leif Basin’s book <a href="https://www.amazon.com/Extreme-Ownership-U-S-Navy-SEALs-ebook/dp/B00VE4Y0Z2">Extreme Ownership: How U.S. Navy SEALs Lead and Win</a>, they talked about how that in order to create a culture where people take full ownership of their actions, the leaders must take full ownership of failures, even if it’s directly caused by someone else. When drawing conclusions and thinking of next steps in this process, it’s important to also think of things <strong>you</strong> could have done. Maybe you could have been clearer with your expectations much earlier, or maybe you can make the work environment less stressful so morale can improve or maybe you can work with the right teams to develop additional tools or training to prevent certain bugs in the code. Reflecting on how you could have done more for the other person will not only be appreciated by the other person, since it shows you’re genuinely interested in improving the situation and not wanting to blame others, but more important it also will help ground you so that during the stressful moments of delivering feedback you’re coming from a place of compassion and not from anger.</p><p>There are still times when even after going through this process to develop objective criticism, I would still feel that knot in my stomach knowing that I have to deliver constructive feedback. But every time I notice that I’m hesitating in giving that feedback, regardless of whether it’s to someone on my team or one of my superiors, I try to remind myself of these key principles:</p><ul><li>Constructive feedback will not only help the team/company, but more importantly it will help this individual grow in his/her career for the future.</li><li>If you frame the feedback so that it’s coming from a place of growth and support and less about blaming and attacking one’s character, the person will always be more grateful in the long run than if you had said nothing.</li><li>As leaders, it’s our duty to take ownership and try to improve the situation instead of letting it fester. If you see a bug in the code, you don’t just say “Ah I’ll let our customer report it first before I’ll fix it.” So why would you act differently when you see a “bug” in other people?</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d846f8f025d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/m2yl-critical-thoughts-pt-3-7d846f8f025d">M2YL— Objective, Critical Thinking of People (Pt. 3)</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When does having a CS background make sense?]]></title>
            <link>https://medium.com/johnkchow/when-does-having-a-cs-background-make-sense-2a2d7630b638?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/2a2d7630b638</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Sat, 15 Sep 2018 18:35:41 GMT</pubDate>
            <atom:updated>2018-09-15T18:43:15.483Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bLQ43HLQRp1r6KGs2G7PsA.jpeg" /></figure><p>In the end of a recent interview with a junior-level candidate for Reflektive, the dev bootcamp grad asked me:</p><blockquote>“I’m trying really hard to better my computer science fundamentals [i.e. data structures, algorithms], but I don’t see when I’d actually use it in my job, and I feel like I’m struggling to learn it. Do you think it matters to <strong>really</strong> know the CS fundamentals?”</blockquote><p>This is a common question for most software engineers starting in their career (I know I asked this myself a million times after UCLA). The growth of dev bootcamps is yet another data point that software engineering doesn’t require CS fundamentals. Most day-to-day application work requires a foundation of solid software engineering principles: writing simple/testable code that reflects the business domain, leveraging the right technologies based on different tradeoffs to address the business requirements and making sure our applications are operationally sound. I’ve seen many successful senior engineers who were either self taught or went to some dev bootcamp. If you were to ask me 3 years ago this question, I’d flat out say that you wouldn’t need any kind of formal CS education (unless you’re trying into something that needs it, like machine learning or embedded systems).</p><p>However, I’ve now grown to really appreciate computer science. I’ve worked on many scaling problems throughout my career, and they all required me to understand on a deeper level how different technologies really worked. Understanding read/write performance characteristics for data stores (e.g. Redis, PostgreSQL, ElasticSearch, Kafka) required knowledge of data structures and basic operating system principles. Relatedly, having a strong understanding of data structures and networking have helped me in both understanding and designing large systems along with communicating those designs with other engineers. Even when optimizing SQL queries using EXPLAIN ANALYZE, you’ll see many artifacts of algorithms, data structures and operating system principles. The deeper my knowledge goes, the simpler the problems seem to become. (Side nerd note: there’s a sense of beauty in seeing how some of the most impressive pieces of technologies today are built on the data structures you first learn about like hash tables and trees).</p><p>Despite how beneficial CS has been later in my career, I don’t think going to a 4-year university for a bachelors in CS is the best choice for everyone (although I absolutely loved my time at UCLA for the friends and new experiences). Computer science is <strong>different</strong> than software engineering. Traditional universities can still fail preparing students for the real world because a majority of the coursework leans theoretical; software engineering isn’t emphasized as much (although I think that’s starting to change). Also, colleges are <strong>expensive</strong>.</p><p>It’s hard to have a general recommendation because every person’s situation and personality is different. If you have the resources and desire for having a wide breadth of knowledge, attending 4-year universities first can be absolutely amazing. However, if you’re looking to get into the workforce ASAP or make an impact in the real world, going through the dev bootcamp route will prepare you for an awesome career. The one bonus side effect about working first is that having real world experience will actually make learning computer science concepts <em>much</em> easier. By grounding computer science to real world problems that you’ve encountered, the abstract concepts will more likely stick.</p><p>Regardless of your decision, software engineering is a <strong>craft</strong>, and to be considered good, one requires a lifelong commitment to learning. Learning requires dedication and discipline, so make sure to carve out time in your life to learn as much as you can.</p><p>There are a few things I do to continually deepen my CS knowledge. One is to read white papers about new technologies like Raft, Kafka and Google Spanner. (You’ll be surprised how easy of a read these white papers are, since they’re written by engineers for engineers). Additionally, I’ve taken <a href="https://www.coursera.org/learn/machine-learning">Andrew Ng’s Machine Learning</a> course on Coursera, which was an absolute blast. Finally, I read textbooks that’s listed on Stanford’s CS course websites. I know, I know; this sounds super nerdy. But like white papers they’re actually pretty approachable to read, and I supplement the readings with the course slides (they’re usually posted on the website). A couple of my favorites that have really impacted my day-to-day work are <a href="https://www.amazon.com/Database-Systems-Complete-Book-2nd/dp/0131873253">Database Systems: The Complete Book</a> and <a href="http://codex.cs.yale.edu/avi/os-book/OS10/index.html">Operating Systems Concepts</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a2d7630b638" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/when-does-having-a-cs-background-make-sense-2a2d7630b638">When does having a CS background make sense?</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Management, Two Years Later — Values (Pt. 2)]]></title>
            <link>https://medium.com/johnkchow/management-two-years-later-values-bae12cda8a2a?source=rss----4d81247b2525---4</link>
            <guid isPermaLink="false">https://medium.com/p/bae12cda8a2a</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[John Chow]]></dc:creator>
            <pubDate>Sun, 15 Jul 2018 23:09:26 GMT</pubDate>
            <atom:updated>2018-07-22T01:36:03.948Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Note: This is part 2 of a series of posts talking about my experiences and learnings the last two years. You can find the rest of the series </em><a href="https://johnkchow.com/management-two-years-later/home"><em>here</em></a><em>.</em></p><p>Early in my management career, I remember being in a planning meeting with another person and that person started raising his voice at me. I remember feeling upset but also really torn. Looking back my mind was torn between two competing thoughts. On one hand, I wanted to tell that person that yelling is unacceptable and that if it ever happened again I’d walk straight out of the room. On the other hand, I also believed in team success above all else. We couldn’t afford to lose that person at that time and I felt I should somehow figure out how to work with this person first. Also, the general perception in Silicon Valley is that sometimes it’s OK to deal with difficult people, especially when you see companies succeed despite difficult leaders (Apple with Steve Jobs, Uber with TK).</p><p>I talked with a lot of people in my company to try and get perspective. There were some people who had similar experiences. Still, some wanted to give the person a benefit of the doubt and see if the person can improve. It took me long, long time before I refined my personal values: team success is entirely dependent on having a safe environment first and any kind of hostility is unacceptable under all circumstances. With a better understanding of my values, I decided that not only will I refuse to work with people like that in the future, but that I’d also snuff out that kind of behavior in any team I’m responsible for.</p><p>This situation was a pivotal moment in my career. Before, I thought there were at least two truths: 1) that when people join your company they will immediately share your values and 2) that all values are created equal. This situation, however, actually pitted two values I held against each other. This experience forced me to further clarify my values which ultimately gave me clarity on what next action to take.</p><p>Defining your personal values is extremely valuable in both the business world and personal life. Values enable you to make quicker decisions when faced with huge uncertainty. As a technical leader, you’ll encounter many situations where it’s unclear which course of action will lead to the optimal result. How do you ensure a project is delivered on time: do you jump in and write code yourself or do avoid playing hero for the team? If the project does go behind schedule, do you tell the PMs that it’s their fault for introducing too much scope or do you tell your scrum team that they should have pushed back? When mistakes are made, do you deliver feedback sternly to get your point across, or do you go with the gentler way to make people feel supported? Knowing your own values will help you navigate through these situations.</p><p>Additionally, defining your personal values helps create richer relationships with other people. It sets expectations with other people, especially with direct reports. In the manager-to-direct-report relationship, there is a power dynamic such that the manager is looked upon for measuring employee’s performance (Side note: I hate using the word “performance” because it makes it sound like people can be tuned like machines! But I’m going to continue using this since it’s a common term in the management/HR space). Because of this power dynamic, it’s imperative that clear expectations are set between the manager and direct report so that a strong foundation is established and the working relationship can be genuine and mutually beneficial. This can have the profound impact of influencing how people behave when you’re not around.</p><p>Defining your personal values is a tough task because it’s entirely a personal journey. Your experiences, your upbringing, your friends and family all collectively shape who you are today and will continue influencing you in the future. However, there is a process to understanding your own values, and I hope that sharing my process can enable you to refine your values so that you can make better, faster decisions and build richer relationships with others.</p><h4>1. Start off by putting your values into words.</h4><p>It’s simple, but writing down your values forces you to break down complex thoughts and feelings and condense it into a set of concrete words. To start off, think about the most critical situations that you’ll face as a technical leader and what you believe is best course of action. Drawing common themes will lead you to your values.</p><p>For example, here’s a series of questions that revolves around operational excellence. Note that each question ties values relating to ownership, communication, and teamwork.</p><ul><li>Should everyone be on-call for production site issues, only the team leads, or just be the managers (aka just you)?</li><li>Do you believe that every person on the team should be empowered to have direct production access, or do you believe that security policies are absolutely critical?</li><li>Do you believe that every app should have an SLA (e.g. availability, response times, etc)? If so, what kind of SLA do you think is appropriate for the application? Also, what kind of additional effects you hope to create by defining an SLA?</li><li>Who should be responsible for deployments?</li></ul><p>Here’s a set of topics that you can use to help jump start additional situational questions:</p><ul><li>Code quality (relatedly, tech debt)</li><li>Team dynamics and culture</li><li>Ownership for an individual/team/organization</li><li>Employee happiness</li><li>Giving/receiving feedback</li><li>Engineering/Product prioritization</li><li>Learning/development</li><li>Inter/intra-team communication</li></ul><p>(Side note: doing this exercise is also super helpful in preparing you for interviews as a team lead or manager!)</p><h4>2. Recognize that nearly all your values define are simply guiding principles…</h4><p>If you tried answering the questions I posed above, your answers probably start with “Well, it depends...” To be rigid with ALL your values means that you can’t adapt to new, ambiguous situations. If you were dropped in a different team where the software’s business requirements and the tools are completely different with different people and you bring in strong opinions, the team will quickly tune you out. You also run the risk of potentially making suboptimal decisions. For example, let’s suppose that you believe high availability and performance trumps everything else when it comes to prioritizing technical tasks. But let’s suppose your project is to build a simple internal tool with a minimal feature set, and it’s only used by a very small number of people at any given time. It probably makes more sense to optimize for simplicity and ease of maintenance (e.g. Heroku, Postgres, Ruby/JS/Python) and not over engineer it (e.g. AWS/Kubernetes, Cassandra, C). Obviously, this doesn’t preclude you from tackling some low-hanging fruit scalability, but being flexible when it makes sense leads to the optimal solution.</p><p>There’s a saying that applies here: have <strong>strong opinions, but weakly held. </strong>It’s important to recognize that the world does not operate in black and white and neither should you. If you only operate in black and white, then you’re going to be consistently disappointed for the rest of your life.</p><h4>3. … But sometimes, you’ll realize “absolute truths” and that’s OK too.</h4><p>While 99.9% of the time you should be flexible with your values, if you do enough introspection and reflection you’re going to realize some “absolute truths”, or values that will you’ll never compromise on. Drawing clear lines in the sand for what’s acceptable (and inversely what is unacceptable) is key to something that’s so crucial and basic when dealing through uncertainty and adversity: confidence and self-respect.</p><p>Some of you may ask, “Well you just said that I shouldn’t operate in black and white, so aren’t you contradicting yourself?!” So to clarify, nearly all your values <em>should </em>be guiding principles so that you can adapt in a multitude of situations, but(!) as human beings it’s imperative to have a solid moral foundation. For example, you may believe in fundamental truths through your religion, or you may believe in ideas like free speech and equal rights are unequivocal. As human beings, it’s in our very nature to hold absolute truths dear to our hearts; to completely reject that is to deny our very nature. (Side note: I feel like I’m just re-packaging ideas from Westworld like <em>core drive</em> and <em>reveries</em>. I swear this blog post didn’t come from just watching Westworld all day long!). Having zero absolute truths can be perceived as not having a backbone, which undermines anyone’s ability to lead. So to conclude: we should be as flexible as possible, but it’s OK to hold <em>some</em> absolute truths as long as we’re open to re-assessing them when presented with new data points. Which leads to my last point…</p><h4>4. ABR — Always Be Reflecting</h4><p>Everyday is a gift because you will receive additional data points about what works well and what doesn’t. To never reflect is a missed opportunity to refine think about the things that you have learned and apply them in refining your values (which, if I haven’t made clear, will impact your ability to make optimal decisions and build meaningful relationships). Create a habit of asking yourself the question, “What did I learn today, and does this change how I view the world?”</p><p>While introspection is critical, this entire process isn’t done in isolation. It’s also crucial to find a group of people that you really trust in sharing your thoughts and exposing yourself to different perspectives. Reflection in isolation is worst case an extremely frustrating/lonely experience and best case leads you to sub-optimal or incomplete conclusions of the world. Data points to validate (or disprove) your values aren’t just pushed to you in life; you should also <em>pull</em> data points from other sources. Reading many different blogs and books is another source to help widen your perspective. All this follows the same principles as machine learning: the more data points you have to feed into your mental model of the world, the more accurate your mental model will be.</p><h4>Another personal story</h4><p>At the core of it all is that this process is really about exploring and learning about yourself. So I’d like to to end this post with a personal story about some of my absolute truths and what I’ve learned through my experience.</p><p>So near the end of my tenure at Teespring, the company wasn’t hitting its numbers and there were legitimate concerns throughout the company about its financial viability. In a meeting with all the managers, we were asked to not only work more hours ourselves, but that we need to demand the same from our direct reports. There’s a lot I didn’t like about the message, but the thing that bothered me the most was that directive that I had to demand my team to work more hours.</p><p>This pitted me against two of my absolute truths. The first is that I only ask people to do something if it’s something I’m willing to do myself. I believe that as leaders, our biggest vehicle to inspire is through action, not words. For example, when I ask my team members to participate in an on-call schedule, I make sure I’m the first person in that schedule. This helps highlight to my team that they’re not alone in this. I don’t do this because I’m trying to manipulate people to do what I want them to do; I do this because I believe that being on-call is critical to the health of the business, and I believe that people will follow if you lead by example.</p><p>Throughout my time at Teespring, I put in a ton of extra hours because I believed in the startup. But in that meeting with all the managers, I was already feeling burnt out and I knew I myself just couldn’t give anymore to the company. And it also broke my heart imagining delivering that message to my teams. Some people had families, and they didn’t have much skin in the game (i.e. equity). Most people joined Teespring because they thought working with t-shirts was going to be cool and fun; but the reward for working more was not something that they would (nor should) make huge personal sacrifices for.</p><p>The second absolute truth is that I believe people can only be motivated through inspiration and togetherness, not through fear and competition. In this situation, I totally understand why we were being asked to put in extra hours. Everyone knew this was a precarious time. A lot of people really, really still believed in the company’s mission. However, in that meeting with all the managers the message was delivered with an defiant, dismissive tone. Some people brought up morale concerns. The response was that people who wanted to work extra hours are the true believers. Those who didn’t are irredeemable and should simply leave the company.</p><p>These absolute truths are core to who I was (and still am). That night, I asked myself if there’s anything I can do to help steer the company to a better place. I had already been through a startup’s downturn before (Fundly), so I felt that our teams had already tried everything. The next day I put in my notice. But before my last day, I learned that Teespring wouldn’t institute the longer work hours policy.</p><p>I never regretted my decision to leave Teespring. It was a liberating experience; it felt like I honored something deep within myself and freed me to pursue my next opportunity that was going to rejuvenate me. I recognize that there were probably a lot of factors that went into Teespring not instituting the longer work hour policy. But I’d like to think that my leaving had some impact in that decision. And while I may not know full truth of what could have happened with Teespring had I stayed, I feel reassured knowing my absolute truths that I live my life by.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bae12cda8a2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/johnkchow/management-two-years-later-values-bae12cda8a2a">Management, Two Years Later — Values (Pt. 2)</a> was originally published in <a href="https://medium.com/johnkchow">John’s Reflections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>