<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vincent Tsao on Medium]]></title>
        <description><![CDATA[Stories by Vincent Tsao on Medium]]></description>
        <link>https://medium.com/@vincenttsao14?source=rss-9436a6b4aacb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YPJ8URCueVRq2kLdFw_jKQ.jpeg</url>
            <title>Stories by Vincent Tsao on Medium</title>
            <link>https://medium.com/@vincenttsao14?source=rss-9436a6b4aacb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:39:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vincenttsao14/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My 2025 Review]]></title>
            <link>https://vincenttsao14.medium.com/my-2025-review-a790c1890218?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/a790c1890218</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[yearly-review]]></category>
            <category><![CDATA[self-reflection]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 22:27:22 GMT</pubDate>
            <atom:updated>2026-01-02T02:08:43.485Z</atom:updated>
            <content:encoded><![CDATA[<p>I peaked in the <a href="https://vincenttsao14.medium.com/my-2024-review-67c4fef421d0">2024 review</a>. It was a 21-minute read. A novel.</p><p>At this rate, I can’t expect anyone, including myself, to keep reading these or even to keep writing them.</p><p>There’s a lot of AI slop on the internet right now, so I’m making an effort to contribute slightly less of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OdoSJ3nJkHMcR90-ejVYAw.png" /></figure><p>2025 is shorter, more visual, still very personal, and after reading <a href="https://www.goodreads.com/book/show/102146148-what-s-our-problem"><em>What’s Our Problem?</em></a> filled with one too many hand-drawn visuals.</p><h3>Table of contents</h3><ul><li>On celebrations</li><li>On renewed momentum</li><li>On hype to habit</li><li>On growing fast but feeling small</li><li>Memorable moments</li></ul><h3>On celebrations</h3><p>This year’s big event was our wedding, which we split into two celebrations.</p><p>In June, we rented out a restaurant in San Jose and invited all our extended family and family friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GhmquRHXdlzq_Xa92n7KCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7pdytQpT1RZazaTgP0kWA.png" /></figure><p>And in September, we had an intimate wedding in France with our immediate family and closest friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dpxn29qcL8_WuLaTVHnV4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ctBKtANE6QPpVrPIGKBH-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N8Ql6j-DMVaGNVEdzgPQ8w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pd1qxI7XFIkUss4BqpXSpQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojcS9EpJad81tqp4p7d1yQ.png" /></figure><p>Not that we needed an excuse to celebrate twice, but we gladly took one.</p><p>We wanted to actually see and talk to everyone, not just say “hi, thanks for coming,” and create different experiences for different communities in our lives.</p><p>Both celebrations were perfect on their own, but as an added bonus, the first became a family reunion across both our families and the second a vacation with our favorite people.</p><p>Earlier in the year, I hosted a much smaller celebration I’m also proud of.</p><p>A simple affair.</p><p>I invited a small group of coworkers over for dinner to mark a recent company milestone, complete with food that not-so-subtly referenced it.</p><p>While the scale of a dinner and a wedding differ greatly, both reinforced the same lessons about celebrating milestones.</p><p><strong>You can have meaningful celebrations without spending a lot of money, but you can’t do it without effort, intentionality, and people.</strong></p><blockquote>Effort (the work to show up) + Intentionality (deliberate choices about the experience) + People (who’s there and why) = Meaning</blockquote><p>Even though we were already courthouse married, celebrating created an emotional knot that made our union feel not just real, but stronger.</p><p>The same applied to the low-key dinner. Showing people you care matters, and simply finding a time that works for busy coworkers and parents is half the battle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iALlC9lF2Us0C3hJLSc6Hg.png" /><figcaption>* The wedding was a forcing function to get in better shape- I started lifting again and roped Bridget into it.</figcaption></figure><p><strong>Hosting a great celebration is a real craft.</strong></p><p>You hear a lot about the pain of wedding planning, but it’s hard to fully appreciate until you’ve lived it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*tIS5qtyeoUERMuXoRFVjeQ.jpeg" /></figure><p>Admittedly, I didn’t care much about things like table settings, but I did appreciate how small details contributed to the overall atmosphere.</p><p>What I really loved was crafting the social experience and predicting how guests would engage and mix. We had all kinds of fun with:</p><ul><li>Bingo designed to surface shared interests</li><li>Seating that intentionally mixed groups</li><li>Handwritten notes for every guest</li><li>A video guestbook with short prompts</li><li>A relaxed day-after pool party and field day</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4trxxyB4vms4ylRk12fPgQ.png" /><figcaption>The magic is in the middle between the boring familiar and the awkward unfamiliar.</figcaption></figure><p>Once you treat hosting like a craft, the details stop feeling optional and start feeling meaningful.</p><h3>On renewed momentum</h3><p><a href="https://vincenttsao14.medium.com/my-2022-review-5aadf7f6580c#ae3a">On marathons</a> in 2022, I said I felt closer to the end of my time at Persona than the beginning.</p><p>That wasn’t true this year.</p><p>It was the first year since then that I didn’t think about leaving, for a few reasons.</p><h4>People</h4><p>A lot of new talent joined this year (more on that later), particularly early-career folks.</p><p>Seeing how talented and hard-working many of them are has been inspiring and brought out a more nurturing side of me, which isn’t exactly one of my stronger instincts 😅.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cB9aFRhYMaEzBx6yRRgoiQ.png" /><figcaption>The early-career hiring boom, combined with a high retention, has created a bimodal distribution.</figcaption></figure><p>More personally, several close friends joined. I referred five people this year, which unintentionally turned our wedding into a Persona offsite.</p><p>I’m really proud of how my referrals have worked out and I’d like to keep it that way. That means being deeply invested in their success and keeping expectations high, sometimes unreasonably so. Lucky for me, I get to work with most of them directly.</p><p>Whether it’s early-career teammates or friends I’ve known since elementary school, I’m spending more time and energy trying to build the next generation of leaders.</p><p>That’s been energizing in a way I didn’t anticipate.</p><h4>Scope</h4><p>Once I was able to get off a couple of major customer escalations and focus more on strategic initiatives, my work started to feel leverage-driven and long-term again, rather than constant firefighting.</p><p>Looking back <a href="https://vincenttsao14.medium.com/my-2022-review-5aadf7f6580c#f59e">on roles</a>, one thing I got right was prioritizing breadth. My scope has shifted in ways that feel both broader and more sustainable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*__Wp7t1MOVnO6R1nbGV8lw.png" /></figure><p>The areas I’ve been driving are each meaningful and interesting to me for different reasons:</p><ul><li><strong>New product and business development</strong>- a return to the early-stage problems I find most energizing.</li><li><strong>International expansion</strong>- a chance to apply a global lens shaped by time spent working, studying, and backpacking abroad.</li><li><strong>Leveraging AI for company productivity</strong>- as an optimization nerd, the most exciting new lever since… spreadsheets.</li><li><strong>Experimenting with new roles</strong>- creating and testing roles for others amid a fluid jigsaw of priorities, teams, and fit, informed by my experience wearing many different hats.</li></ul><h4>Winning</h4><p>The identity industry feels delicately balanced right now, with:</p><ul><li>Increased consolidation and acquisitions as customers favor platform plays over point solutions</li><li>Regulation becoming more prominent (e.g. age assurance, digital IDs)- I never thought we’d be attending meetings with the White House</li><li>Identity increasingly viewed as “<a href="https://www.investopedia.com/terms/p/pick-and-shovel-play.asp">picks and shovels</a>” for AI, creating massive opportunity amid an unsettled landscape</li></ul><p>There are also clear signs that Persona can win:</p><ul><li><strong>Market leadership</strong>- being named a leader in <a href="https://www.gartner.com/en/documents/6875366">Gartner’s 2025 Magic Quadrant</a> was meaningful validation of years of focused execution across product, go-to-market, and strategy, especially after the crushing disappointment of not being named a leader last year.</li><li><strong>Public validation</strong>- seeing our verification flow for Roblox featured on <em>Good Morning America</em> was surreal. What we do matters enough to be on the news, and we handle so much real-world traffic that most people have used Persona, whether they realize it or not.</li></ul><p><a href="https://www.goodmorningamerica.com/family/story/roblox-announces-new-safety-measure-amid-spate-lawsuits-127626071">Roblox announces new safety measure amid spate of lawsuits</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XaTQQulYZZvB0aFyJamsgg.png" /></figure><ul><li><strong>Capital:</strong> raising a Series D from a position of financial strength means we can play offense, not defense, and invest ahead of the market rather than react to it.</li></ul><p>We can see a path to winning, but we’re not there yet. The best product doesn’t always win.</p><p>I’m a competitive person, and I want to win.</p><p>Being relied on to help close a lot more candidates this year forced me to articulate the belief that we can win and, in the process, believe it more myself.</p><h3>On hype to habit</h3><p>AI hype is still going strong. But personally, I’m past being impressed by <em>claims</em> of AI adoption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Onc9xwoaha1zlKLcEyA3dw.png" /></figure><p>I care about what actually changes how work gets done.</p><p>This year, I focused less on dramatic breakthroughs and more on quiet saturation. I’m using ChatGPT and Notion AI hundreds of times a day, putting a very literal spin on the idea of a <a href="https://vincenttsao14.medium.com/second-brain-c3574a3394cc">second brain</a>. The impact is real even if it’s not flashy.</p><p>That said, the hype is exhausting. The clearest illustration is the parade of AI billboards on Highway 101.</p><p>The technologist in me enjoys the dopamine hit from parsing esoteric billboards like this one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HhtGhSaIuXtsm7h9whENA.png" /><figcaption>Don’t worry about it.</figcaption></figure><p>But broad statements like “we’re adding AI into our product” aren’t innovation.</p><p>They read more like FOMO or attempts to stay relevant and capitalize (literally) on the fervor through fundraising.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*-avz_BhZO8-qQiuNPCK3ow.png" /><figcaption>It’s the unsettling robot eyes…</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtzG7theSQfDfHFXIRJexg.jpeg" /><figcaption>Utopia or dystopia?</figcaption></figure><p>It’s gotten to the point that I find myself appreciating the <em>non-AI</em> billboards that just slap a logo on and call it a day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*guB72ik4_BkL3z0C1uaTZg.jpeg" /></figure><p>At Persona, AI adoption has been steady.</p><p>We’ve done the obvious things: stood up an agent-building platform, ran an AI hackathon, invested in trainings and all-hands deep dives, created Slack channels and office hours, and encouraged usage from the top.</p><p>But the real inflection was hiring a dedicated AI operations /program manager.</p><p>Builders are the domain experts (e.g. AEs, PMs, Finance, etc) who best understand the problems and what AI solutions <em>should </em>look like. AI ops sits between enabling builders to move faster and building enough themselves to know where the current friction is.</p><p>What surprised me was how much <em>infrastructure</em> this role had to own. We want builders to be distributed across teams and functions, but without centralized support they quickly hit the same walls.</p><p>I think of this as <strong>AI systems strategy:</strong></p><ul><li>Centralizing the boring but critical setup</li><li>Reducing hours spent debugging, tweaking, and trying to cross the threshold of usefulness</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*33Yif_RFQK7IJZENvvu0QQ.png" /></figure><p>Without this layer, adoption stalls. Not from lack of interest, but from friction. Most people don’t have the patience or skills to do the plumbing.</p><p>For example, “just connect Slack” quickly turns into hidden rate limits, missing fields, public vs private access issues, security reviews, incomplete channel coverage, and context window constraints.</p><p>And the moment you want to <em>write</em> rather than just read, say an AI-generated weekly Slack post on high-priority deals, complexity compounds.</p><p>We’re in the messy middle of AI adoption, the unglamorous slog between hype and habit, where impact is visible but hard to measure.</p><p>We see plenty of strong upstream indicators.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ldnAI7xWDDH48jzLiadXQ.png" /><figcaption>More code/PR output doesn’t necessarily mean more impact.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SaNQmyB4aoqNbWix33tJtA.png" /><figcaption>PRs from non-engineers are still largely “quality of life” as opposed to net new features.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5hijgxLPuv1CrnRGtT1RNw.png" /><figcaption>Increased MAUs should enable us to do more with less headcount.</figcaption></figure><p>But we can’t cleanly map these to downstream outcomes like higher customer satisfaction, cost savings, and increased revenue.</p><p>What’s been most valuable right now is sharing specific workflows and learnings, especially across companies, to calibrate where we are on the adoption curve.</p><p>To that end, I presented during a webinar about how we used AI to start automating two of our most time-consuming workflows (starts 4:21, ends around 23:46).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0HgOglUHcaM%3Fstart%3D261%26feature%3Doembed%26start%3D261&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0HgOglUHcaM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0HgOglUHcaM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/429fc878f1e3fc93aaf05d9cd54bdbf5/href">https://medium.com/media/429fc878f1e3fc93aaf05d9cd54bdbf5/href</a></iframe><p>We’re still early. Still learning everyday. Still optimistic, just more selective about what we pay attention to.</p><h3>On growing fast and feeling small</h3><p>In 2025, Persona doubled in headcount.</p><p>Much of that growth was backfilling for 2024, when we were significantly understaffed.</p><p>Within the product function, we exceeded that pace, growing from 13 to 29 people, even as the first three PMs left the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wwg6w7jrYugT-jsZgUffXQ.png" /><figcaption>Half the company joined in the past year.</figcaption></figure><p>After such an explosive growth period, the challenge is ingestion: absorbing that many new teammates without losing too much of the culture.</p><p>Even as the company gets larger, we’re intentionally trying to make it <em>feel</em> small, optimizing for <a href="https://vincenttsao14.medium.com/speed-process-c064ed283360">speed over process</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eC26ulgsb8UXQzZVyFUXAA.png" /></figure><h3>Memorable moments</h3><p>Since I’m still terrible at writing conclusions for these reviews, here’s a collage of more great memories from 2025 instead.</p><ul><li>The “With Persona” customer conference @ the Chase Center</li><li>Oversharing the anime version of Bridget and Miso</li><li>Watching the <a href="https://en.wikipedia.org/wiki/Giro_d%27Italia">Giro d’Italia</a>, bucket list item checked (bucket hat optional)</li><li>👰 Congrats Morgan &amp; Jeremy, Kush &amp; Alicia, Shiv &amp; Raghav, Peter &amp; Hannah!</li><li>Bachelor parties</li><li>Visiting TAMS and the TX state fair after 15+ years</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EO2X95aIw9xfMNIGlwgzDA.jpeg" /></figure><p>Wishing you and yours a happy and healthy 2026!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a790c1890218" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 2024 Review]]></title>
            <link>https://vincenttsao14.medium.com/my-2024-review-67c4fef421d0?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/67c4fef421d0</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[self-reflection]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[yearly-review]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Thu, 02 Jan 2025 06:54:03 GMT</pubDate>
            <atom:updated>2025-12-31T22:28:04.338Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gOaCDkRHc3kAqVLL" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is my seventh end-of-year blog, but it’s the first infused with AI.</p><p>Let me know if my writing has been taken over by the “professional but approachable” tone of ChatGPT. And if you prefer listening over reading, here’s an AI-generated <a href="https://notebooklm.google.com/notebook/e960f980-ad8e-4023-b005-e6641242f2d1/audio">podcast</a>!</p><p>Each year there’s one big change.</p><p><a href="https://vincenttsao14.medium.com/my-2023-review-9ab991288ba7">2023 was about the dog</a>- we’ve now fully settled into life with Miso, trained him more, and resolved his icky stomach issues. Happy two years to the best short-legged companion anyone could have!</p><p>2024 was about getting engaged and married- more on that later.</p><p>However, the arguably bigger change as a married couple was Bridget leaving her job of nearly six years. She’s currently exploring operations-focused roles at small to mid-sized companies after spending a decade in client services at marketing agencies.</p><p>If you have leads, please reach out!</p><h3>Table of contents</h3><ul><li>On AI</li><li>On community</li><li>On code -&gt; culture</li><li>On morale</li><li>On families</li><li>On marriage</li><li>Memorable moments</li></ul><h3>On AI</h3><p>I came out firing with the densest material first. I was close to breaking away from written form and creating slides instead, but I tried to provide plenty of visuals here!</p><p>As a self-diagnosed technophile, it’s obvious that AI is the next major platform shift in how we build and interact with technology. I never said this about VR/AR, blockchain, or autonomous transportation, so I probably <em>mean it</em>? Or I’ve just been reading too many posts about AI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YY1YY6_xGV4vkmyx4SJGgQ.png" /><figcaption>“AI eats the world” — ben-evans.com</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UM5AlLhSXYkiTvT0QFwbig.jpeg" /><figcaption>WIMP = windows-icons-menus-pointer interaction; “Gen AI Bridge to the Future” — stratechery.com</figcaption></figure><p>Like with any technology, I try to apply a <a href="https://vincenttsao14.medium.com/technorealism-43470fe430ed">technorealist</a> lens to AI:</p><h4><strong>Technologies aren’t neutral</strong></h4><p>Every dataset has bias, these biases compound exponentially at scale, and they’re a black box to us.</p><p>AI: Long-term differentiation in AI comes from proprietary training datasets that are going to be inherently biased- LLM model improvements are already <a href="https://www.theinformation.com/articles/openai-shifts-strategy-as-rate-of-gpt-ai-improvements-slows?rc=ph0xqt">plateauing</a> and the major models are converging on the same performance benchmarks.</p><h4><strong>The internet is revolutionary but not utopian</strong></h4><p>We can’t look to the internet to solve all our problems.</p><p>AI: While AI will improve productivity, create new jobs, and spur economic growth, it’ll also displace workers, amplify biases, and further widen socio-economic gaps.</p><h4><strong>Government has an important role to play</strong></h4><p>Innovation shouldn’t be stifled, but power also can’t be left unchecked.</p><p>AI: We’re still in the early days, but OpenAI’s conversion to a for-profit entity is about to be a litmus test for regulatory involvement.</p><h4>Information isn’t knowledge</h4><p>We don’t need more information; we need to reason and make sense of what we already have.</p><p>AI: With the proliferation of genAI tools, <a href="https://www.cnn.com/2024/09/03/tech/facebook-spam-ai-meta/index.html">“AI slop”</a> is already rampant online. And it’s getting much harder to determine whether content is generated by humans or not.</p><h4><strong>Wiring the schools won’t save them.</strong></h4><p>Technology in the classroom hasn’t meaningfully improved learning outcomes.</p><p>AI: <a href="https://www.vice.com/en/article/grade-school-ai-only-classes-no-teachers/">AI-only classes</a> don’t strike me as the best way to teach what students may increasingly lack: problem solving, adaptability, how to learn, resilience, and collaboration.</p><h4><strong>Information wants to be protected.</strong></h4><p>There’s a growing awareness and legal resistance to the fragmentation and exploitation of personal data.</p><p>AI: <a href="https://www.cnbc.com/2024/04/30/eight-newspaper-publishers-sue-openai-over-copyright-infringement.html">Eight major news publishers</a> already sued for copyright infringement- the same fight will inevitably widen to include individuals’ sensitive data.</p><p>I have three big questions about what’s next:</p><h4><strong>1. When does the bubble pop?</strong></h4><p>Investment in AI has significantly outpaced the actual revenue being generated.</p><p>Revenue multiple = valuation / revenue. So a company generating $10 million revenue with a $100 million valuation has a 10x multiple.</p><p>Revenue multiples for AI startups are <strong>4–5x higher</strong> than other SaaS startups. The last time revenue multiple were this high, the bubble burst after interest rates started going up and COVID subsided in early 2022.</p><p>According to an analysis from Sequoia Capital, <a href="https://www.sequoiacap.com/article/ais-600b-question/"><strong>$600 billion</strong> in annual revenue</a> is needed to justify the amount of money that’s been invested in AI. At <strong>$4–5 billion</strong> in annual revenue, OpenAI leads the industry by a wide margin.</p><p>That’s quite the revenue shortfall to cover... I’m bullish on AI but those numbers don’t make sense to me.</p><h4>2. How does a product find a problem?</h4><p>Normally, you see a juicy problem and you create a product. We call this <a href="https://productschool.com/resources/glossary/product-market-fit">product-market fit</a>.</p><p>AI is the opposite. It’s a solution looking for a problem.</p><p>There’s a long list of factors but I think the more important ones are: 1) the pace of model improvement exceeds our ability to identify and implement practical applications, combined with 2) the immense market hype and our innate curiosity (FOMO) about what generalized artificial intelligence looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U4DWmwteFHLBmk-1Tm07dg.png" /><figcaption>“AI eats the world” — ben-evans.com</figcaption></figure><p>In other words, we’re riding the early wave of the Gartner hype cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*KiIgOUzFniQpVAyu6KYn1w.png" /></figure><h4>3. What gets disrupted first?</h4><p>Up to this point, I’ve laid out a somewhat bearish case on the current state of AI, but it doesn’t change the fact that AI is still a major platform shift <em>long-term</em>.</p><p>As I see it, there’s three general markets to shift:</p><ol><li><strong>Personal</strong>- how AI changes the way we go about daily life</li><li><strong>Processes- </strong>how AI changes the way we build products internally</li><li><strong>Products- </strong>incorporating AI into external-facing products</li></ol><p>All markets are already getting impacted, but my bet is AI truly <em>disrupts</em> 2→3→1 in that order.</p><p>I’ll also acknowledge two massive biases: 1) I work at a B2B software company that’s small enough to quickly experiment with AI, and 2) outside of writing a couple blogs each year, I don’t have any creative pursuits, which is where I think genAI is poised to disrupt the personal market.</p><p>While many applications of AI (e.g. generating high quality video based off a couple sentences) captivate our imagination, the reality is that the highest-leverage near-term applications of AI are far more mundane… helping businesses run better day-to-day 🙄.</p><p>In other words, OpenAI has a clearer path to being the next <a href="https://sherwood.news/tech/openai-is-salesforce/">Salesforce</a> than the next consumer-facing brand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-YdLC4e01Lz5BaWRTmN8A.png" /></figure><p>Okay- enough armchair prognostication! It’s not as fun as getting hands-on with the shiny new AI tools myself.</p><p>The best summary of my experience so far has been <em>tempered excitement</em>, which seems to be slightly above the baseline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wW4Zzqk0WR5algstAuSepg.png" /><figcaption>“AI eats the world” — ben-evans.com</figcaption></figure><p>There’s an ever-growing list of AI tools to try- many of which undoubtedly won’t exist in a couple years time. They range from <a href="https://www.dashworks.ai/">cross-application search</a>, <a href="https://deepmind.google/technologies/project-mariner/">AI controlling my browser</a>, <a href="https://apollo-lmms.github.io/">analyzing videos</a>, <a href="https://www.granola.ai/">summarizing meetings</a>, <a href="https://www.napkin.ai/">generating diagrams</a>, <a href="https://flux1.ai/">creating images</a> / <a href="https://openai.com/index/sora/">videos</a>, <a href="https://www.chatprd.ai/">writing product requirements</a>, and even <a href="https://www.delphi.ai/">cloning myself</a> 👯‍♂️.</p><p>Unfortunately, I stop using half of them after an hour.</p><p>I’d get more use out of them if I invested way more time, but it’s not time I want to spend when I don’t have a clear problem to solve.</p><p>And if you’re wondering where all the social/fun/non-productivity use cases are- don’t bother asking me about those! Remember- I’m a <a href="https://vincenttsao14.medium.com/2018-review-f6aed94c531e#3d4b">productivity nut</a>.</p><p>My experimentation has mostly been in the context of being more efficient at work (i.e. <strong>Processes</strong> market). I’m still looking for the 10x improvement, but there’s already a lot of small optimizations that have shaved off minutes here and there.</p><p>At Persona, we leverage AI in the product itself (i.e. <strong>Products</strong> market), but the bar has to be <em>much</em> higher. If a customer can touch it, not only does it have to be accurate, but if it <em>is</em> inaccurate, we have to be able to explain why.</p><p>The development of <a href="https://getstream.io/blog/reasoning-llms/">reasoning models</a> and <a href="https://www.linkedin.com/pulse/184-explainability-interpretability-rishi-yadav-vzinc/">interpretability</a> will help, but I think there’s still a fundamental bottleneck to scaled adoption. I want to understand how something works as opposed to blindly trusting it- maybe that’s just me?</p><p>Outside of experimenting with different use cases, I’m trying to spend more time with each of the major LLMs instead of defaulting to ChatGPT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*1FHBGNkFgn_fJgcX1QwpOw.png" /><figcaption>Generated by Gemini 2.0. It was real nice to export into a Google Sheet with one click.</figcaption></figure><p><strong>Note:</strong> Perplexity isn’t a LLM but it’s become my starting point for any research, and I’m experimenting with it as my default search engine.</p><h3>On community</h3><p>Lately, I’ve been thinking more about the communities I’m a part of.</p><p>From a <strong>personal</strong> standpoint, we started planning a wedding and we definitely want to celebrate with our friends and family. The idea of bringing our communities together is thrilling- there’s only so many times (1?) we’ll have the energy and excuse to rope everyone in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ad7Dik3oy_sNIt7MJS24tQ.png" /></figure><p>As we’ve embarked on this journey, I’ve realized that my community is wide. Heck, I have a <a href="https://vincenttsao14.medium.com/2018-review-f6aed94c531e#39dc">Personal CRM</a> I maintain monthly.</p><p>But Bridget’s community is deeper.</p><p>Why?</p><ul><li>The primary communities that shaped us are: family, childhood, high school, college, work, and extracurricular. I think the latter two account for the main difference between us. When I joined a small tech startup, I decided that my coworkers would be my friends. Stripe had a <strong>Sunday test- </strong>if a candidate were alone in the office on a Sunday, would that make you more likely to come in and want to work with them? For startups, colleagues have to genuinely enjoy each other’s company and share a common drive. And with extracurriculars like playing organized sports or joining a (community service) fraternity, I’ve also been more embedded in larger communities with shared interests.</li><li>I’m naturally introverted but I’ve always been a social chameleon. A close friend calls me the “normal guy” from high school. That’s a mild insult at best. But at a math and science boarding school, it enabled me to move between social circles in a way that my hyper-intelligent but eccentric peers couldn’t.</li><li>I like to actively stay in touch and catch up with folks I haven’t seen in a while. I’m quick to reconnect, but I’m not as inclined to regularly talk with those closest to me. Sorry mom and dad! Bridget is infinitely better at continually keeping in touch with smaller, close groups.</li></ul><p>From a <strong>professional</strong> standpoint, there’s been two times in my product management career where I’ve felt like I had a community to really push me:</p><ol><li><strong>Persona’s Head of Product joining in 2021</strong>- working with the CEO is invaluable for aligning on product vision, but there were many more topics (e.g. how to scale up the product functions) we didn’t have the experience — or in the CEO’s case, time — to unpack together. So when the Head of Product joined, we built rapport quickly because we were able to navigate way more ambiguity by not only bouncing more ideas off each other but also having deeper discussions.</li><li><strong>Joining the </strong><a href="https://skip.community/"><strong>Skip Community</strong></a><strong> in 2023- </strong>after every one of our monthly meetups this year I’ve thought to myself, “these aren’t everyday conversations I can have at work.” In one meetup, we advised startups on their product challenges- something I’d love to do more of. It was eye-opening to see how a dozen different product leaders answered questions about hiring. There were starkly different answers but they were all well-reasoned and insightful.</li></ol><p>Meanwhile, the Persona community continues to grow too- we’re almost 300 strong now. There’s so many new faces and this was the first year where I legitimately felt anxious about introducing myself, compounded by what I call the <strong>Cumulative Awkwardness dilemma</strong>- you pass by someone everyday which only makes it harder to introduce yourself the next time.</p><p>There’s two small ways I’ve tried to fight the awkwardness:</p><ol><li><strong>Move desks</strong>- the 14th floor of our office is primarily engineers/PMs/designers; while the 13th floor is primarily sales/post-sales/marketing. I relocated to the 13th floor to break out of the bubble and interact with coworkers I normally wouldn’t, with a goal of meeting one new person each week.</li><li><strong>Support early career folks</strong>- this year we ramped up heavily on entry-level hiring across the business functions. I wanted to make a concerted effort to bridge <a href="https://vincenttsao14.medium.com/my-2021-review-93cba15e4ce9#94b1">generations</a> by getting to know the new hires and acting as a mentor to set an example that anyone at Persona is accessible.</li></ol><p>When I reflect on my personal and professional communities, I wonder <em>how can I make these communities more effective and closer</em>?</p><p>I read a book called <a href="https://www.goodreads.com/book/show/37424706-the-art-of-gathering">“The Art of Gathering”</a> that inspired the above question and a host of ideas I’m excited to experiment with.</p><p>Personally, I want to use our wedding as an opportunity to not only spend time with ones we love, but also for fostering stronger connections between our guests.</p><p>Professionally, the age-old question is how to get more out of meetings. Running effective meetings is arguably my most important skill, and I’d love to keep up-leveling.</p><h3>On code -&gt; culture</h3><p>For the past couple years, the main challenge of building Persona has shifted from product (i.e. code) to process and people (i.e. culture).</p><p><em>How do we operate, communicate, and grow?</em></p><h4>Product</h4><p>The biggest challenge is not whether we’re building the right things and winning in the market anymore.</p><p>Over six grueling years in a rapidly changing market, we’ve proven that we deeply understand the market and know how to build great products.</p><p>Rather, the challenge now is playing defense. When we were small and irrelevant, we could just play all-out offense.</p><blockquote>This year, I felt the first tug of playing it safe — not to lose.</blockquote><p>As we’ve established ourselves as a <a href="https://withpersona.com/gartner-magic-quadrant">market leader</a> in identity verification by prominent industry voices, we’ve needed to start playing defense.</p><p>Being recognized as the leading product was a massive accomplishment, but competitors have subsequently ramped up their efforts to attack us by cherry-picking examples and blasting us on public forums.</p><p>Compliance and stability are other great, more silent examples.</p><p>As we work with larger companies, geographical scale, industry variance, and legal implications ramp up exponentially. We could be staying on top of 99% of relevant regulations, but missing the 1% at scale is the difference between winning and continuing to work with enterprise customers or not.</p><p>Similarly, the baseline expectation for selling to any enterprise is that your service will be <em>available. </em>Any downtime of critical-path software could mean hundreds of millions of dollars lost.</p><h4>Process</h4><p>I’ve talked about <a href="https://vincenttsao14.medium.com/speed-process-c064ed283360">embracing speed and chaos</a>, which I still believe and practice.</p><p>However, I’m also increasingly aware of and compelled to address the tradeoffs of that mentality.</p><p>Over time you see two trends:</p><ol><li>The speed of shipping goes down as you constantly revisit products that were shipped too fast.</li><li>The quality of the product declines and becomes increasingly inconsistent across teams.</li></ol><p>I’ll share some unique factors at play and what we’re doing about it.</p><p><strong>Factors</strong></p><ul><li><strong>Remote</strong>- on the whole, we’re not much different from other tech startups. We’re neither fully remote nor in-person, and our engineering team is more distributed than other functions. But the specific teams I work with daily are primarily remote, and being able to quickly tap folks on the shoulder significantly lowers the barrier for seemingly less urgent conversations, which is exactly what product polish tends to be.</li><li><strong>Tenure</strong>- an absurd number of early hires are still at the company (<a href="https://vincenttsao14.medium.com/my-2023-review-9ab991288ba7#5a3d">which I love</a>), but it’s triggered many second and third order effects. As it relates to process, many managers and leaders — myself included — who are supposed to be focused on establishing process and scaling teams are often overloaded doing individual contributor work because: 1) that’s how they started at Persona, and 2) now they have too much context to <em>not</em> chip in.</li></ul><p><strong>What we’re doing about it</strong></p><p>Over the past year, we’ve pushed a “Unify” narrative. Instead of pursuing different business and product goals at all costs as startups within a startup, we want the different products to be consistent and work together as a seamless platform.</p><p>I always perceived the narrative as focusing on <em>outputs</em> (i.e. what product we build), but I’ve realized it’s actually about <em>inputs (</em>i.e how we build and do the hard things).</p><p>One example is <strong>product polish</strong>. It’s impossible to prioritize small improvements when your biggest customers are banging on the door for features they wanted months ago.</p><p>Another example is <strong>cross-product implications</strong>. It’s easier to blindly ship your own feature than to put yourselves in other teams’ shoes, gather context on product surface areas you’re unfamiliar with, and chase down stakeholders, only to have seemingly created more work for yourself when there’s inevitably push back.</p><p>But that’s the crux! It <em>should</em> feel ever harder to glue everything together as we evolve from a startup to an established company. The most impactful Personerds constantly embrace rather than shy away from the hard things.</p><p>On the less fuzzy, more tactical side:</p><ul><li><strong>Leverage AI</strong>- see <a href="https://vincenttsao14.medium.com/my-2024-review-67c4fef421d0#8599">On AI</a> <strong>🙂</strong></li><li><strong>Invest in supporting functions</strong>- while we started building a revenue ops team (e.g. set up our Salesforce instance) a couple years ago, we just started building out dedicated ops teams for other functions like marketing and product management.</li><li><strong>Systematize documentation</strong>- we have a strong culture of documenting, but we need to do a better job building systems that can accurately point to the relevant documentation.</li><li><strong>Establish key metrics with robust monitoring</strong>- one of my regrets is relying too long on excuses like “<em>we don’t have statistically significant data” </em>and “<em>we’re data-informed, not data-driven.”</em></li><li><strong>Train launching as opposed to just building</strong>- we now spend more time rolling out and launching products than actually building them, yet most of our training and discussions still revolve around how to build faster.</li></ul><h4>People</h4><p>2024 was the first year we had true performance reviews.</p><p>Besides reminding us that each individual is unique and we should put them in environments that accentuate their strengths, it also reminded me of the many challenges and learnings that come with evaluating performance, including my own.</p><ul><li>The more people, the <strong>more variance</strong> in expectations and performance (e.g. junior vs senior, role specialization, low vs high tenure, organizational structure, career aspirations, management styles). Regardless, the golden rule is to <strong>err on the side of too high</strong> versus too low expectations.</li><li><strong>Prioritization is as much about people and performance</strong> as it is about product. We’re just as likely to work on a feature because a high performer is at risk of burning out and needs to work on a passion project, as we are to work on the most requested feature from customers. The former can still be what’s best for the business, but it’s less obvious or explicit.</li><li>Every day, I get further from the product details. And when I do have to dive into details, it’s usually because something’s wrong. How am I supposed to evaluate my team’s performance if I don’t understand the details? One of the most important tactics to combat this paradox is to <a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food"><strong>dogfood</strong></a><strong> the product whenever I can</strong>.</li><li>High tenure is again both a blessing and a curse- many of the highest performers are folks who’ve been at Persona a long time. But <strong>past success isn’t a guarantee of future success</strong>. Similarly, expectations for new hires shouldn’t be capped by their previous work experience or even their previous month at the company- different environments call for different expectations.</li><li>How about my own performance? A coworker once told me that my receptiveness to feedback and bias for corrective action was a superpower. However, in my position, <strong>I so willingly give feedback to others but receive so little of it myself</strong>. Yet, to advance in my career, I’m supposed to get 360° feedback to identify and shore up my weaknesses.</li><li>My personal conundrum is that I sometimes wish people would <strong>expect <em>less </em>of me to counterbalance my own relentless drive to expect <em>more </em>of myself</strong>. It’s a tactic I’ve developed over the years — alongside more common ones like setting boundaries — to mitigate <a href="https://vincenttsao14.medium.com/my-2023-review-9ab991288ba7#c435">repeated burnout</a>, which is ultimately <a href="https://theskip.substack.com/p/the-burnout-paradox-in-tech">fueled by one’s own expectations</a>.</li></ul><h3>On morale</h3><p>👍 On one hand, Persona is doing really well. We exceeded our revenue goals again, and we’re about to hit milestones only <em>1% of venture-backed startups ever hit</em>.</p><p>And at a macro level, the rise of AI undoubtedly amplifies the importance of identity- <em>are you really who you say you are</em>? We feel the tailwinds already, and I expect those winds to grow stronger in coming years.</p><p>👎 On the other hand, morale isn’t as high as one would expect given our success. Every year is harder than the last, but this year felt <em>especially hard</em>.</p><p>Why?</p><p>This paradox has been the source of countless conversations and sleepless nights, but I’ll summarize:</p><ul><li><strong>Powerlessness</strong>- many of the company’s biggest challenges affecting everyone can only be realistically solved by a much smaller subset of people.</li><li><strong>Scale</strong>- we’re processing tens of millions of verifications every day and working with companies many orders of magnitude bigger than we are.</li><li><strong>People</strong>- there’s more churn and attrition compared to years past, and the core of the company is aging (e.g. the difference in energy between tenured and newer folks widens, important people are out on parental leave).</li><li><strong>Political environment</strong>- highly polarized and sensitive events silently but heavily weigh on us mentally (e.g. Israel/Palestine, US elections).</li><li><strong>Fraud</strong>- as much as AI is a tailwind, it’s also accelerated fraud at enormous scale. Creating fake IDs or deepfakes of stolen identities is 10x easier and cheaper than it was before.</li></ul><p>I don’t have many clear cut solutions, hence why this is the problem of 2024.</p><p>But I’m optimistic that the problem is fueled by a potent mix of short-term factors and that the underlying strength of the business will ultimately win out.</p><p>😟 My biggest worry is actually that low morale becomes a self-fulfilling prophecy.</p><p>Because it’s the topic we talk about most, I sense my mood dampened by default and an over-sensitivity to related problems. Combined with my already unreasonably high bar, it’s easy to feel like the company is crumbling.</p><p>I continually try to remind myself and other leaders at the company that our negativity or positivity is infectious and amplified. And I’m uniquely bad at being positive- just ask my dog!</p><p>💪 We shouldn’t act like everything is fine and be tone deaf by over-celebrating success- these are really difficult problems to solve. But we also shouldn’t ignore that it’s inherently hard to build meaningful and successful companies. If it was easy, everyone would do it.</p><h3>On families</h3><p>Since Bridget’s parents live in San Jose, I’ve been able to spend a lot of time with them over the years. Not to mention, they’re unequivocally our first choice dog-sitters!</p><p>One experience we hadn’t shared together yet was going on a family vacation; we’d already traveled to Hawaii with my family back in 2021.</p><p>This year her parents celebrated their 45th<strong>👏</strong> wedding anniversary with a family Rhine River cruise in Europe over the summer.</p><p><strong>Fun fact:</strong> it ran right through where I had studied abroad just over a decade ago!</p><p>Needless to say it was a blast and I’m grateful we were able to celebrate together.</p><p>Plus, spending a highly concentrated period of time with them always affords interesting insights about family and cultural dynamics (see <a href="https://vincenttsao14.medium.com/great-big-christmas-746f0554fd09">Great Big Christmas</a> 🎄).</p><p>And this year was particularly interesting because we also traveled with my parents in Asia to attend my cousin’s wedding at the end of the year, so we had recent family vacations to compare and contrast.</p><h4>McAnany(s)</h4><ul><li>At the dinner table, it’s common for multiple conversations to happen simultaneously. I often see one group talking about topic A suddenly, yet seamlessly, pivot to another group’s topic B. Which brings me to a related observation- <strong>interruptions are practically a family sport</strong>. Whether it’s a comment, quip, or probing question, don’t expect to finish your story in one go. You may get asked the exact or a variant of the same question, or hear the same story repeatedly because another conversation was happening or someone just sat down.</li><li>On a broader level, it’s clear to me that the McAnanys are simply curious and love to talk- traits I admire deeply because they know so much more about each other. Bridget knows every detail about how her parents met, while I just learned some basic details of my parent’s courtship last week- because Bridget asked, of course!</li><li>Each McAnany has a strong personality, wildly different preferences, and isn’t afraid to express their opinions. There’s always some debate or disagreement but you’ll also always know where each person stands- nothing is hidden or silent.</li></ul><h4>Tsao(s)</h4><ul><li>Instead of communicating with words, we communicate with food- a whole lot of it. When you look closely, food tells a story about our values. Chinese food is incredibly time intensive to prepare- you mince, chop, slice, and marinate everything. We don’t just <em>eat</em> food- we take pride in preparing intricate dishes for hours, comprised of dozens of ingredients. Cooking requires <strong>patience</strong> and <strong>discipline</strong>. We eat <strong>communally</strong> as a group- dishes are shared on lazy susans and the elders are served by others and eat first. At a table of 12 adults, there’s only one real conversation happening and some folks may <strong>largely be silent</strong> during dinner. We get three orders of a dish we didn’t want simply because we <strong>can’t miss a deal</strong><em>. </em>Even the fight for the bill, which can get hilariously contentious, is an act of <strong>contributing</strong> back to the wider group.</li><li>In general, gifting is a major part of the culture. We brought back way too many snacks from Asia gifted to us from family and friends. I’m admittedly not the best role model- I’m terrible at both giving and receiving gifts. The one thing I’m any good at is paying for the bill, which I thankfully learned from my mom.</li><li>After we eat, we like to go on meandering walks to help with digestion. Bridget despises any sort of physical activity after eating, while I’m happy to go for a jog. In Asia, we walked through dozens of malls because they were all over the place- and since that’s also where all the food was, we naturally wandered through the megaplexes after meals.</li></ul><p>While Bridget and I occasionally find ourselves annoyed by some of these cultural differences, both of us agree that discovering and bridging the gap between our families is an incredibly rewarding and meaningful process.</p><h3>On marriage</h3><p>Bridget doesn’t like surprises.</p><p>Don’t talk to her about the time I made her trudge up Mount Tallac in Tahoe but woefully underestimated how long and hard the hike would be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SnokV-0KmGU8Z7-CG1j5YQ.jpeg" /><figcaption>She’s smiling for the selfie but absolutely seething inside.</figcaption></figure><p>So when I planned to propose on an August weekend, I needed to give her enough signal that it was happening so she could do her nails, pack the right outfits, and just be mentally prepared for the big moment. But I wanted to sprinkle in spontaneity too: where and when I would pull out the ring, how I might incorporate the dog, only making a dinner reservation.</p><p>I ended up picking Mendocino, a three hour drive north, and a place that holds special meaning for us since it was one of our first real weekend getaways after COVID lockdown. Despite the predicable coastal fog and one nerve-wracking hour where I was desperately searching for the imaginary perfect cliff to propose, it went swimmingly!</p><p>We got some beautiful photos to cherish the memory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3a70GUXxA4V9oGFY3EdlQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xE-HYQ36VuK4PxcweziKpw.jpeg" /></figure><p>I assumed that getting engaged fulfilled my 2024 duties as a good partner, but it wasn’t to be.</p><p>We also got legally married so Bridget could get healthcare, and secondarily because I hated the idea of signing and submitting paperwork as another to-do of an actual wedding.</p><p>I’m happy we got that out of the way because I was getting seriously confused about what it meant exactly to “get married within 90 days”.</p><p>Thankfully for us, it just meant getting a marriage license, asking Bridget’s mom (in her case, a religious officiant) and dad (i.e. a witness) to sign said license at our kitchen table, and then submit it to City Hall which is conveniently 300 feet from our front door.</p><p>We ended up being <em>extra</em> happy we got married though, because we’re saving a bunch of money on taxes too.</p><p>Honestly, it hasn’t fully sunk in yet that I have a whole other side of the family now, even though I’ve already psychoanalyzed the crap out of them.</p><p>Or for that matter, that I have a <em>wife. </em>Feels weird to even write it, even though I had no problems yelling at the TSA agents last year that my <em>wife</em> had been stuck at security for ten minutes and we were going to miss our flight.</p><p>Now that we’re both engaged and married, we’d really like to actually celebrate with more than just Bridget’s parents!</p><p>Fortunately, Bridget has made wedding planning her full-time job and we’re way further ahead than I thought possible after three months. It’s quite a luxury to skip all the hours of research and simply be presented with the best three options, leaving only the choice to be made.</p><p>Additionally, after attending almost two dozen weddings together, we’ve already pre-decided many aspects of our own by identifying the elements we liked most from others.</p><p>From my perspective, decisions are being made lightning fast!</p><p>Again, I’m just incredibly appreciative of the disproportionate share of planning Bridget’s taken on. That’s on top of everything else she’s already taken on more of — like making dinner and walking the dog — while being incredibly accommodating of my schedule during her break from work.</p><h3>Conclusion</h3><p>I haven’t written pithy conclusions in previous posts because it’s hard to pull out a top-level theme from a wide range of topics.</p><p>But there was a actually a bit of a theme this year— duality.</p><ul><li><strong>On AI</strong>: excitement vs skepticism</li><li><strong>On community</strong>: wide vs deep</li><li><strong>On morale</strong>: optimism vs pessimism</li><li><strong>On code-&gt; culture</strong>: speed vs quality</li><li><strong>On families</strong>: loud vs quiet</li><li><strong>On marriage</strong>: spontaneity vs planning</li><li><strong>Bonus</strong>: Progressive vs conservative (<strong>Note:</strong> politics isn’t really my thing and this wasn’t a section, but I highly recommended <a href="https://www.goodreads.com/book/show/102146148-what-s-our-problem">What’s our Problem?: A Self-Help Book for Societies</a> from one of my favorite bloggers)</li></ul><p>After all, it’s very me to balance the tradeoffs and embrace the gray area.</p><h3>Memorable moments</h3><p>As is tradition, here’s an overly simplistic collage of more highlights from 2024 to wrap up.</p><ul><li>EDC for the first and last time</li><li>Family cruise down the Rhine</li><li>Cousin’s wedding in China</li><li>Cabo and Oaxaca for a wedding (plus making mole)</li><li>My dad’s 69th birthday (<strong>Note:</strong> in Chinese culture, birthdays ending in 9 are auspicious and celebrated with more fanfare)</li><li>Dominican Republic with the high school crew</li><li>Money2020 conference in Vegas</li><li>Hans Zimmer Live concert</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vVGpZYxf_sl3JDF3Lk3I9Q.jpeg" /></figure><p>Wishing you and yours a happy and healthy 2025!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67c4fef421d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 2023 Review]]></title>
            <link>https://vincenttsao14.medium.com/my-2023-review-9ab991288ba7?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ab991288ba7</guid>
            <category><![CDATA[yearly-review]]></category>
            <category><![CDATA[self-reflection]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Sun, 31 Dec 2023 04:55:48 GMT</pubDate>
            <atom:updated>2024-01-02T23:50:08.083Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vjX73jJbZ76cyBrb" /><figcaption>Photo by <a href="https://unsplash.com/@okeykat?utm_source=medium&amp;utm_medium=referral">okeykat</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>According to the Chinese zodiac, 2023 was the Year of 🐰. But for us, it was the Year of the 🐶.</p><p>We picked up our new pup, Miso, at the end of <a href="https://vincenttsao14.medium.com/my-2022-review-5aadf7f6580c#8ad2">My 2022 Review</a>, and spent the first part of the year potty training him and taking photos of every nap.</p><p>Once Miso settled into a steady schedule, so did we. I started going back to the office 4x a week (which magically solved my neck cricks), committed to early morning cycling classes, and walked the dog at least once a day.</p><p>Then the rest of the year just flew by.</p><p>Now that we successfully absorbed the shock of inviting another living creature into our home, we’re ready for another change in 2024. Is it time to start ring shopping?</p><h3>Table of contents</h3><ul><li>On being a dog dad</li><li>On burnout</li><li>On culture, care, and craft</li><li>On teams</li><li>Quick hits</li><li>Memorable moments</li></ul><h3>On being a dog dad</h3><p>I didn’t grow up with pets. To paraphrase my parents, “Another mouth to feed? NO THANKS!”</p><p>Raising a puppy was a big commitment and a steep learning curve. And while we taught Miso a lot, Miso taught us more:</p><ul><li><strong>Patience</strong>- I’ve always had a short temper, which reared its ugly head during potty training. Each time Miso peed on the floor, I honestly felt <em>betrayed</em>. He once peed indoors three times in a row and I lost it. I sat him on the couch, seething, and stared at him for fifteen minutes as if he’d internalize my disappointment. He didn’t 😆. Bridget rightly pointed out how my anger was unproductive, and I focused instead on what I could control: systematically tracking his schedule, praising his progress, and resetting my own expectations that accidents happen! Miso was progressing, but the curve was spiky rather than linear, and I had unreasonably high expectations for him and myself. Don’t take progress for granted. Be patient with the process.</li><li><strong>Positive reinforcement</strong>- 99% of dog training methodology is based on positive reinforcement. Dogs don’t feel guilt or regret, so shaming or yelling at them doesn’t work. Anybody who knows me knows I’m not exactly a fountain of praise, so dog training brought out a side of me I wasn’t sure existed.</li><li><strong>Manners</strong>- I believe our pets reflect our values. The rules and manners we impart on Miso indicate how we interact with those around us. No dogs allowed in the bedroom or bathroom. No jumping on the table. Wait for the “OK” before going through doors or eating. Greet other dogs and hoomans calmly. Go to the crate when asked.</li><li><strong>Parenting</strong>- our favorite question to ask our couple friends is, “Who’ll be the stricter parent?”. It often stirs up interesting debate, but in our case there’s no debate — it’s me! It’s fascinating to see Bridget, who would’ve otherwise been more strict, take a good cop approach to balance my strictness. I want Miso to be well-trained, well-mannered, and well-socialized. Maybe too much so. Strict parenting often leverages negative reinforcement, which doesn’t work with dogs, so I’m mindful of not turning into a tiger dad.</li><li><strong>Love</strong>- I love my furry friend more than I thought I could. He puts a big, priceless smile on my face every day. As DINKWADs (dual income, no kids, with a dog), we have an overflow of love to shower upon our dog. I honestly have to catch myself when I get home and greet the dog before Bridget 😬.</li></ul><p>I’ve always wanted a family, and after our first year with Miso, our small family is starting to feel very real. Nothing brings me more joy than bear-hugging Bridget and Miso.</p><p>And beyond our household, my sister is having her second child next year. So we’re excited to welcome the little one and spend more time with my three-year old niece, Iris. It’s surreal to see the next generation of my family emerge.</p><p>As much as I hate to be the obnoxious pet owner shoving photos in your face, how about just a couple..?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R6RTMbCrAMg9yGoAOV33fQ.jpeg" /></figure><h3>On burnout</h3><p>Burnout is <em>physical or mental collapse caused by overwork or stress.</em></p><p>During my time at Persona, I’ve had countless conversations about my own and others’ burnout. After going through another round this year, I wanted to reflect on what I’ve learned.</p><p>First, I asked myself a couple questions about each time I’ve felt burned out. What were the circumstances? How did I handle it? How did I recover?</p><p>I count at least four instances:</p><ol><li><strong>December 2018</strong>- the full story’s <a href="https://medium.com/@vincenttsao14/vendor-management-3ae381293317#13dc">here</a>, but the short version is I had two weeks to find, sign, and integrate two vendors to launch our first major customer in a space I knew nothing about. I ignored everything outside work for the month. And while I frantically cobbled together a plan, the co-founders shipped an absurd amount of code. It was as tense a time as it was invigorating, but we got it done! To this day, still one of my proudest Persona moments. But after already grinding 24/7 for months leading up to this pressure-packed sprint, I was exhausted. The holidays were a much-needed break.</li><li><strong>March 2022</strong>- our most important gig economy customer escalated a big conversion drop in their sign-ups. It was the most challenging, intense incident I’ve ever been apart of. For weeks, we pored through every possible change and data point, going back and forth with what seemed like their entire company. We never nailed down the exact root causes, but we pushed out a slew of improvements and conversion recovered. I remember being unreasonably frustrated and short-tempered with everyone.<em> If you weren’t directly involved, why were you slacking off and not working on this incident? If you were helping, why weren’t we able to solve the problem?</em> It was a classic lose-lose situation.</li><li><strong>October 2022</strong>- our biggest customer was at risk of not renewing their contract, and I was asked to work closely with the customer team to get things back on track. I was indignant because I was already slammed trying to ramp up new team members, and I wasn’t excited to work with people I perceived to be struggling. After a series of conversations in which we talked through the pros/cons, what I’d have to take off my plate, and planned different scenarios to transition off smoothly after renewal, I <em>very</em> reluctantly agreed. Looking back, I overreacted. Frankly, I was scared of causing another customer incident and in a deeply introspective mood about work after <a href="https://vincenttsao14.medium.com/my-2022-review-5aadf7f6580c#ae3a">reaching the four year mark</a>.</li><li><strong>March 2023</strong>- I was convinced it was time to quit. It wasn’t any one thing, but rather a slow build of many irritants: potty training the pup, dealing with organizational issues, running into scaling problems, recovering from annual planning, jumping on complex sales deals. It was a real existential crisis. I felt disconnected and nothing excited me. I’d look at my calendar in the morning and be filled with dread. And a discussion about upcoming time off was the straw that broke the camel’s back. <em>I put so much into this company, why should I feel bad about taking time off?</em> Ultimately, through a series of convos with those I trust most, they helped me hit the reset button and redefine my <em>why</em>.</li></ol><p>Next, I looked for trends.</p><ul><li><strong>Conditions:</strong> urgent customer escalations, not seeing others put in care and effort which is exacerbated when I have even more on my plate, not working closely with people I admire and respect, not taking care of my body, not having a break to look forward to.</li><li><strong>Signs:</strong> less engaged in meetings, low energy, less sociable, everything gets under my skin, easily distracted, difficulty focusing, Monday blues but everyday.</li></ul><p>Each time I felt burnt out, I realized there was at least one <strong>stack</strong>.</p><p>We can sprint for weeks or even months when we need to get something done. But at some point we’re tapping into our reserves, and periods of intensity are balanced by periods of recovery.</p><p>When you stack multiple intense periods on top of each other, you hit the limit exponentially faster. I’ve seen folks with unbelievable limits (easily 10x my own), but they ultimately have limits as well.</p><p>In both 2022 and 2023, we had just had wrapped up an intense month of planning culminating in high-pressure presentations at our annual kickoff. I realize now that I was already in a precarious state after kickoff, and it didn’t take much to tip into a downward spiral.</p><p>Each burnout was seemingly worse than the previous, so how do I mitigate it?</p><p>For the past three months, our Head of Product has been on maternity leave and I’ve been covering for her. I’ve been as busy as I can remember, but not nearly as stressed. Why?</p><ul><li><strong>Set boundaries</strong>- I’ve been intentional about setting boundaries over the years, treating it as a gradual process and balancing the tradeoffs (e.g. turning off certain notifications, being more comfortable about not knowing every detail).</li><li><strong>Separate work from personal identity</strong>- make sure I always have an answer to this question.. <em>who am I if I’m not working at Persona?</em></li><li><strong>Relieve stress</strong>- establishing a consistent, rigorous cycling schedule and playing a couple video games I was excited about were tremendously helpful in releasing stress.</li><li><strong>Avoid stacks</strong>- just like an exercise regimen, you have to balance intensity and recovery.</li><li><strong>Talk about it</strong>- burnout is worse when you feel isolated and alone. My tendency is to bottle up negative emotions, and I’m constantly surprised at how much better I feel after a conversation.</li><li><strong>Find the <em>why</em></strong><em>-</em> when the existential crisis hit me earlier this year, rediscovering <em>why</em> I was still grinding after all these years was the key to getting out of the rut: 1) I’m intensely loyal to the early team, 2) there’s things I still want to learn/do that can contribute to Persona’s success, and 3) this may very well be the most important work I ever do.</li><li><strong>Create meaningful breaks</strong>- taking any less than three consecutive days off isn’t a meaningful break, it’s just piling on for later. We started counting down to our December vacation when we booked it in July. We created a surprisingly powerful anchor for our tired minds to look forward to. My most productive weeks are the ones leading up to breaks- that’s how powerful the effect is!</li></ul><p>I’m incredibly lucky to have passed 5️⃣ years at Persona. But if there’s anything I’ve learned about burnout, it’s not about luck. Burnout can be managed and mitigated. And it doesn’t go away if ignored. Identify the trigger conditions, look for the signs in behavior change, talk openly about it, and make the change.</p><h3>On culture, care, and craft</h3><p>These three related concepts came up seemingly every day at Persona.</p><h4><strong>Culture</strong> — the values and principles that guide how we operate</h4><p>Having a shared set of beliefs is powerful — they’re the superpowers of any company. But <a href="https://theskip.substack.com/p/open-doors-in-your-career-by-unlocking">superpowers mask hidden weaknesses</a>. These shadow superpowers are not only counterintuitive, they often only surface during times of crisis. This year, we’ve had to grapple with shadows of our culture.</p><ul><li>The shadow of a considerate and friendly culture results in avoiding necessary conflict and not taking charge for fear of stepping on others’ toes.</li><li>The shadow of high bias for action results in a small group of individuals who consistently end up driving complex decisions and stunt growth opportunities for others.</li></ul><p>Incidents are a great example of the above. When the product breaks, we’re scrambling to figure out what’s wrong and how to fix it. During this time, we need folks to jump in with ideas, debate, and take decisive action.</p><p>But what happens when there are a lot of people deferring because they think someone else knows better? How do we spread knowledge and empathy if it’s the same people making the critical decisions?</p><p>The bigger a company gets, the more important it becomes to understand the shadows. More people, processes, and products create cultural cracks that need to be glued back together.</p><p>As a professional glue guy, and in the unique position of being the first hire but not an executive (i.e. I understand the historical context but not necessarily mandating from a position of power), I started pushing myself <a href="https://vincenttsao14.medium.com/my-2022-review-5aadf7f6580c#2e73">last year</a> to find more explicit ways to share aspects of our company culture.</p><p>I want to encourage conversations <em>at scale</em> about our culture, both good and bad. I want to talk more openly and often in meetings, write more, create podcast episodes, and start a working group to mobilize folks across the company with different perspectives. Culture is set by example, but that shouldn’t be mistaken for being top-down.</p><h4><strong>Care</strong> — committing to shared success and giving it your all</h4><p>Arguably the most important part of our culture, but also the hardest to scale.</p><p>Back in 2021, I wrote about <a href="https://medium.com/@vincenttsao14/my-2021-review-93cba15e4ce9#94b1">different generations of employees</a>. I’ve come to realize that the perceived divide is driven not by differences in skills or context, but about how much one <em>cares</em>.</p><p>The easy answer is that some employees — particularly early ones — just care more. Maybe they feel more ownership, figuratively and literally. Maybe they have less commitments and can put in more hours. Maybe they have more innate bias for action or intrinsic motivation. All can be true, but I refuse to believe we can’t also nurture care.</p><p>We’ve tried a lot of different tactics, many of them having to do with getting closer to customers and those we serve, and we’ll continue to do so because our long-term success depends on it.</p><p>Instead of asking what’s best for me, ask what’s best for customers, the company, and those around me?</p><h4><strong>Craft — </strong>the skill in carrying out your work</h4><p>There’s an adage in startups that “people don’t grow as fast as the company does.” While there’s truth to it, outside of picking the line of work you focus on, mastering your chosen line of work is the next best way to scale yourself as the company grows.</p><p>Craft means holding yourself to a high standard.</p><p>Craft means constantly improving your product and yourself.</p><p>Craft means being proud of what you put out into the world.</p><p>Craft means loving the tiniest details.</p><p>Even when the company is rapidly growing or changing around you, being great at what you do naturally leads to growth opportunities.</p><p>One of my favorite indicators of high craftsmanship is diligent bug reporting. No matter how good the software is, there’s always bugs. Users run into bugs all the time but often don’t report them. In a rational sense, reproducing the bug in different scenarios and filing a report isn’t worth the effort. But that’s a slippery slope. <em>What bugs are worth filing and why? When the next person runs into the same bug, will they have that same understanding?</em></p><p>This year I’ve been thinking about craft on our product management team. We have an incredibly talented group of individuals, but we’ve relied too much on talent and done a poor job systematically raising the bar on craft. The good news, though, is that craft is teachable, learnable, and has a clear feedback loop with higher quality products.</p><h3>On teams</h3><p>The basic structural unit of a company is a team, so I’ve been thinking about how to make teams more effective<em> </em>and what role I have to play.</p><p>This is not meant to be a comprehensive list but I <em>have</em> applied every one of these bullets this year.</p><p><strong>Purpose</strong></p><ul><li>Define what the team does, who they serve, and why.</li><li>Have a clear set of goals for a given period, evaluate the team against it, and iterate.</li><li>Consider how the team’s behavior is influenced by incentives — whether it’s the above goals or at the level of wider company strategy. At Persona, our product teams became siloed over time because they were rightfully following the mandate to build standalone products.</li><li>Let teams self-organize as opposed to rigidly defining areas of ownership. The team that feels the most pain has the most incentive to invest in a solution. In this way, I’ve seen many teams take on more than their immediate scope and clarify existing purpose or even discover new ones.</li></ul><p><strong>Structure</strong></p><ul><li>Organize the team by function (e.g. sales, engineering) or mission (e.g. SMB customers).</li><li>Make sure the team is the right size to serve its purpose. Better too small than too big, but effectiveness suffers in extremes of both scarcity and excess. I personally do my best work in small teams. In a couple months, with a couple engineers and a designer, we laid the foundation to go after a new market and launched the first iteration of the product this year.</li><li>Split out new teams when new purposes arise. Teams naturally try to coalesce, but new ideas need space to break out of the status quo.</li><li>Put the right leaders in place. Teams take on the personalities of their leaders and need different types of management to be successful.</li></ul><p><strong>Culture</strong></p><ul><li>If people don’t weigh in, they don’t buy in. High-performing teams have to be comfortable disagreeing and debating.</li><li>Stay connected to the front-lines. As teams get bigger, it’s easy for leaders to make too many assumptions about details. Similarly, it’s easy to treat people as nameless faces or resources on a gantt chart instead of understanding how each individual fits the team.</li><li>Experiment! High growth teams are constantly changing. If you don’t feel like anything needs to change, that’s a clear signal something needs to change. The more you experiment, the more you learn about the natural cycle of change. I’ve seen multiple product teams start without standups, introduce live standups, move to async standups, and go back to no standups. On and on as the team evolves.</li></ul><p><strong>Process</strong></p><ul><li>Get the right people in the room — how do we arrive at informed decisions as quickly as possible? As Persona has grown, trying to engage entire teams has become less effective. Making decisions within or across teams is ultimately about creating champions out of key individuals.</li><li>Invest in tools like AI. I’m no AI fanatic, but it’s clear that it’s a game-changer for internal process. We’re implementing AI into our products, but there’s challenges like processing time, vendor roulette, and rate limits (i.e. how much data we can throw at the AI in a given time period) that make customer-facing applications risky. No doubt these will be solved in due time, but I’m more excited about internal applications like summarizing Zoom meetings and code editing via Copilot in the near term.</li><li>Beware of <a href="http://here/">too much process</a>.</li></ul><p>I’m actively applying the above to the product management team. We’re going through another inflection point as a company, and we haven’t put enough emphasis this year on resetting the team to scale for the next stage. As a group, and over many weeks, we unpacked what was wrong about PM’ing at Persona and brainstormed dozens of initiatives I aim to empower folks to drive in the new year.</p><p>More broadly, the PM function went through a reset after <a href="https://www.mindtheproduct.com/airbnbs-product-management-shift-the-viewpoint-of-product-leaders/">Airbnb dropped their PM titles</a>. I’m indifferent about the title itself — I’ve long believed that PMs are too often glorified — but the responsibilities needed to build great products haven’t disappeared. Airbnb bifurcated the primary responsibilities of PMs into business outcomes (i.e. product marketing managers) and product delivery (i.e. program/project managers). That was their hypothesis to improve their teams’ effectiveness and I admire their willingness to change!</p><p>Separately, I’ve been mulling over my role on teams, specifically on management. This year, I donned the manager hat again and spent more than three months stepping in for our Head of Product, which was a valuable opportunity to re-evaluate my capacity and desire to manage.</p><p>Many of these observations aren’t new but bear repeating:</p><ul><li>Management often doesn’t feel like <em>real</em> work. I’m further away from the execution and how the actual work happens is more opaque. If you “manage” to achieve your desired outcomes, it’s genuinely the most rewarding feeling. But when you don’t, you have to dig way deeper to find out what went wrong.</li><li>I felt more prepared and comfortable managing the second time around after: 1) taking a half-year break from it, 2) having more experience under my belt, 3) observing and partnering closely with other team leads.</li><li>I still prefer a player-coach role. Having a project I can fall back on when dealing with draining organizational or people issues is a great stabilizer.</li><li>Don’t conflate management with career progress- it’s just a different path. There’s so many ways to grow outside of management. If you’re interested in management, ask yourself if you’re more energized by solving people problems or product problems?</li><li>I prefer coaching and mentoring over management. In other words, I like to teach and facilitate more than direct. Fun fact: I’d love to coach my kid’s sports team one day, but I also know I’ll struggle with the kids that aren’t exactly excelling on the field 😅.</li><li>Steve Jobs said, “You know who the best managers are? They’re the great individual contributors who never, ever want to be a manager, but decide they want to be a manager, because no one else is going to be able to do as good a job as them.” This resonates with me more than ever.</li></ul><h3>Quick hits</h3><p>A new, experimental section- thoughts that don’t warrant separate sections but are still personally interesting.</p><ul><li>Big decisions need time to <strong>bake</strong>, so start the conversation early. I dipped my toes for half a year before committing to buying a condo or getting a dog. It happens at work too. Our most important decisions were on again, off again discussions over many months or even years. People need space to digest complex topics for themselves, understand the ramifications, and feel enough ownership of the idea to buy in.</li><li>At work, I pride myself on replying to messages quickly and directly. A sentence sent fifteen minutes later is often more helpful than three-paragraphs sent a week later. If only I could do the same with my texts!</li><li>One monthly reminder I’ve had for the past couple years is to stop comparing myself to others, which has always been a major driver of imposter syndrome. I can’t point to any one thing that made me feel comfortable removing the reminder this year, but I’ve just learned more over time about what truly brings me joy.</li><li>It’s no secret why Persona has been successful- 23 of the first 25 employees are still here. There’s fewer opportunities to work closely with that group as the company has surpassed 230+ employees, but I cherish the moments we get to solve problems together.</li><li>I only posted one <a href="https://vincenttsao14.medium.com/five-lessons-from-my-first-three-months-at-a-startup-2121307dc5f8">article</a> this year 😕. I like to daydream about taking a break from an operating role and writing full time for a bit. Bridget can attest to how many banal dream jobs I have, but this piece about <a href="https://lethain.com/writers-who-operate">writers who operate</a> reminded me that the grass isn’t always greener on the other side.</li><li>I watched more cycling this year, and it’s been fascinating to learn the dynamics of a team sport that crowns individual winners. Every team has a lead rider and everyone else rides in support of that leader. But team and individual ambitions constantly butt heads, as exemplified by the <a href="https://www.npr.org/2023/09/15/1199761154/cycling-sepp-kuss-spain-la-vuelta">Vuelta de España controversy</a>.</li><li>When hiring, if you‘re not desperately trying to convince everyone else why a candidate should be hired, you don’t feel strongly enough about them. Objectivity is an illusion when you’re the hiring manager.</li><li>Pedestrians and cyclists in San Francisco are so dangerously entitled. They always think they have the right of way. And whatever you do, don’t <strong>honk</strong> at them. Even when they’re clearly at fault, nothing brings out the irrational anger and colorful swearing like honking. Myself included.</li></ul><h3>Memorable moments</h3><p>As is tradition, it was painfully difficult to condense the year into a single collage.</p><ul><li>Miso’s first camping trip</li><li>California Pizza Kitchen nostalgia</li><li>Hosting Spark SC at the office</li><li>Oyster shucking on the beach</li><li>Visiting Greece and Turkey for an over-the-top Indian/Kazakh wedding</li><li>Long weekend in Tomales with the fam</li><li>Bridget’s first cruise</li><li>Christmas in Albuquerque</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ewr7ZfuTIWWEY-RPJ1PAg.jpeg" /></figure><p>Wishing you and your loved ones a happy and healthy 2024!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ab991288ba7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Lessons From my First Three Months at a Startup]]></title>
            <link>https://vincenttsao14.medium.com/five-lessons-from-my-first-three-months-at-a-startup-2121307dc5f8?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/2121307dc5f8</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Mon, 19 Jun 2023 22:32:19 GMT</pubDate>
            <atom:updated>2023-06-20T21:32:33.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hgkDbCuS-UYfRl4F" /><figcaption>Photo by <a href="https://unsplash.com/@sickhews?utm_source=medium&amp;utm_medium=referral">Wes Hicks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I started this draft over four years ago.</p><p>It was to be the first entry in a series of monthly posts in which I’d share learnings from working at a startup as the first hire. Future employees would read the posts and get a firsthand look at the company’s evolution.</p><p>Though the draft ballooned to thousands of words, I never hit publish. Thankfully over the years, I’ve written about many would-be topics in other posts (e.g. <a href="https://medium.com/@vincenttsao14/speed-process-c064ed283360">Speed &gt; Process</a>) and year-end reviews (e.g. <a href="https://medium.com/@vincenttsao14/my-2022-review-5aadf7f6580c">My 2022 Review</a>). And just last year, I started an internal company podcast for the same purpose.</p><p>But I finally decided to cull through the draft and share the learnings that’ve been fermenting — this time without the monthly commitment 😅.</p><h4><strong>Table of Contents</strong></h4><ul><li>Spend money to make money</li><li>Tools are for fools</li><li>Sell vs build</li><li>B2B basics</li><li>Roles don’t matter; titles do</li></ul><h3>Spend money to make money</h3><p>I tend to be too <a href="https://medium.com/@vincenttsao14/the-life-changing-magic-of-saving-up-67819fa43f4d">frugal</a>, which is a mentality I’ve had to fight against at Persona. In business, you spend money to move faster — startups live or die based on their ability to run uphill faster than incumbents.</p><p>In fact, investors actually prefer their startups spend money and collect signal as fast as possible on the potential trajectory.</p><p>Most startups aren’t swimming in cash, but follow a simple rule to maximize what’s in the bank:</p><p><strong>Spend your <em>time</em> on core competencies — spend <em>money</em> on everything else.</strong></p><p>Core competencies are customers, product, and people. You’ll spend money on these too, but more importantly, you’ll need to invest time.</p><p>Money often affords access to opportunities you wouldn’t have otherwise. On the never-ending list of problems, many can be solved or sped up by calculated spending. Pay for top talent, hire consultants, find contractors for specialized projects, and upgrade to better tooling. Expertise and efficiency are worth paying for.</p><p>We worked with a well-referred design agency to build the first iterations of our product. One of our core hypotheses was that a thoughtfully designed UX would be a key differentiator in a market historically dominated by API-first solutions. But we didn’t have the network to hire experienced designers or time to train less experienced designers. While it wasn’t cheap, the agency helped launch our first flows and website that confirmed our hypothesis and gave us confidence to invest in designers.</p><p>As a company handling identity sensitive data, we knew we had to get a <a href="https://admincontrol.com/security/soc-2-report">SOC 2 report</a> to close deals, but had no experience in the world of InfoSec certifications. After countless hours of confusing online research, I reached out to a friend who was an IT consultant and auditor. We flew her out to SF for a weekend and paid $2k to pepper her with all our questions. She reviewed our tool stack and provided insights that saved us time and money we would’ve otherwise spent working with a less transparent, costlier auditing agency.</p><p>That said, there’s ways to spend <em>smarter:</em> do it yourself so you know what to look for in a solution, try before you buy, and spend within your means.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBtzUo6vL3Iw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBtzUo6vL3Iw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBtzUo6vL3Iw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d24cc0ed17fc043d4472a029b61488a/href">https://medium.com/media/0d24cc0ed17fc043d4472a029b61488a/href</a></iframe><p>Don’t use money as a crutch, use it as a lever!</p><h3>Tools are for fools</h3><p>The header is purposely hyperbolic — tools are critical for any company. But they command a disproportionate amount of attention.</p><p>My spidey senses tingle whenever someone recommends a new tool!</p><p>Sometimes it’s the right decision, but oftentimes it’s not. It’s easier to recommend a new tool than to unpack and solve underlying problems of how the team functions.</p><p>In fact, the process of deeply understanding the problem before choosing one tool or another ends up being more valuable in the long run.</p><p>When properly wielded, tools make a team faster, but they’ll never inherently make the team <em>better.</em></p><p>As a PM, I’ve had my share of thoughts like these:</p><p><em>It’s always a struggle to understand how far along projects are.. do we use a different issue tracking tool?</em></p><p><em>The business team doesn’t know what the product teams are working on next quarter.. do we use a different roadmapping tool?</em></p><p>I researched the gamut of PM tools but decided not to use them. They can calculate prioritization scores for the backlog or automatically ping stakeholders with status updates on feature requests, but they can’t replace intuition.</p><p>Different tools make sense at different stages. But as a company grows, the stack needs to handle an ever-widening range of use cases. So the most flexible tools ultimately win — it’s why many Fortune 500 companies run off GSuite.</p><p>I find this quote from <a href="https://www.bringthedonuts.com/essays/the-tools-dont-matter/">Ken Norton</a> spot-on:</p><blockquote>If you want to be a better tennis player, you could ask Serena Williams what kind of racket she uses. What brand? Grip type? Swing weight? <strong>Rackets are undoubtedly important in tennis, but there’s a lot of other shit you need to learn before they even begin to matter.</strong></blockquote><p>Compounding on the pitfall of new tools, there’s also so many of them!</p><p>Ironic that while building a B2B company, my key learning is that there are too many B2B companies.</p><p>Over my first three months, I created a doc of all the competing identity verification solutions. To my surprise, the list was in the hundreds. There were all kinds of solutions that specialized across regions, verification types (e.g. scanning ID cards, database records), and use cases (e.g. fintech, age-restricted goods).</p><p>It takes time to understand how the solutions are different. And for B2B, it’s extra confusing. Nine times out of ten, you have no idea what a company does even after combing through the entire website. Personally, I like to skip the marketing pages and read the API docs instead!</p><h3>Sell vs build</h3><p>Start selling as soon as possible. You don’t need a functioning product. Sell ideas. Sell yourself. Build trust.</p><p>In the early stages, product discovery is the priority. Validate problems (even if they weren’t the ones you set out to solve), test different pitches, ask questions, get feedback, and ask for intros. Set goals for the number of conversations you have per week.</p><p>There are definitely scenarios in which it makes sense to build before you sell. One example is products that have life or death implications. Another is products that fall under specific regulations. But overall, the above is widely-accepted advice for startups.</p><p>There’s a corollary, however, that’s harder to master and less intuitive — <strong>sell faster than you build.</strong></p><p>Many early sales conversations hopefully go something like, <em>“Your product looks great. Can you do X and Y too?”</em></p><p>And regardless whether you can do X, Y, or neither, you should say yes.</p><p>It’s uncomfortable, risky, and undoubtedly backfires periodically. But it’s worth it. If we sold what we’d built in the first three months, we’d never have sold a thing.</p><p>In a matter of seconds, often while still actively listening or participating in the conversation, you decide 1) whether you can build what’s being asked for, and 2) in a timeframe and way that makes it seem like you had it all along.</p><p>Technical or product-minded folks are best equipped to make these decisions, so make sure they’re on the call!</p><p>I still marvel how one of our early engineers would immediately say yes with such confidence anytime a customer asked about a feature. And he always delivered in a matter of days.</p><h3>B2B basics</h3><p>I worked in B2B SaaS at Amazon, but it was at a drastically different scale. Working at zero scale was eye-opening to say the least.</p><p>There’s some advice above around early stage sales, but here’s a couple more learnings worth sharing:</p><ul><li><strong>Build qualitative intuition</strong> from your conversations. It’s more important than gathering quantitative validation. You don’t have customers, so you don’t have data. And even when you do have customers, it’ll be a while before you have enough data to drive meaningful decisions.</li><li><strong>Get comfortable operating in gray areas.</strong> Due to the historical opaqueness of the identity industry, rapidly-changing data privacy landscape, and emergence of biometric technologies, we had to embrace making risky decisions with incomplete information. We imperfectly juggled the interests of end users, customers, vendors, and legal counsel, but we did it as quickly as possible.</li><li><strong>Work your network. </strong>Everyone you talk to has the potential to become a mentor, investor, co-worker, or customer. Case in point, Rick, our CEO, was introduced to Parker Conrad through YC. Parker was trying to sell Rick on joining the upcoming YC batch, but he ended up giving us the best sales advice we’ve ever received, invested in Persona, and ultimately became a customer. Not every interaction is as fruitful, but it’s incredible how much help you can get from your extended networks. Arguably the biggest advantage for older founders compared to their younger counterparts is their network.</li><li><strong>Find your champions.</strong> Working your network is one thing, but knowing <em>how</em> is another. Referrals are key, but they work differently for B2B vs B2C. In B2C, you’d never refer a product you don’t use yourself. But in B2B, that’s not true. Even if you’re not talking to the end user, they pass on messages to their colleagues. In every outbound sales email, always include a line like, “Let me know if there’s someone else we should be reaching out to!”. The B2B goal is to find the internal champion who can influence their teammates. The champion may also be the decision maker, but you need both to close the deal. We’ve lost deals when our champion couldn’t convince the decision maker, but we’ve also won deals with the reverse.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*orOD_T8CKkftAo0mSSXC7Q.png" /><figcaption>Hunting for B2B champions is less direct than B2C</figcaption></figure><h3>Roles don’t matter; titles do</h3><p>I didn’t have a title when I joined Persona — I barely had a role. Since the two co-founders were engineers, I just did everything else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*PLSYhnHF61jLswLiq4QosA.jpeg" /><figcaption>Is “business” a role?</figcaption></figure><p>A snapshot of my first two weeks:</p><ul><li>Set up payroll on Gusto</li><li>Wrote and committed new copy for the website</li><li>Set up Hubspot and then Zoho as a CRM</li><li>Run pitch practice with the co-founders for seed funding</li><li>Set up Outreach for outbound campaigns and sent cold emails</li><li>Wrote an onboarding doc</li></ul><p>The prevailing advice is to have a clearly defined role and title before you join a company. While I was nervous about the ambiguity, we made it work because Rick and I have been friends since high school, so we already had an established level of trust.</p><p>My title has never changed, but my responsibilities change monthly. We’ve always had open and honest conversations about my future and where I want to have an impact. And as a generalist, that’s ultimately what matters to me. I decided a long time ago that I’ll worry about titles when I leave Persona.</p><p>That said, titles matter in external contexts like sales or customer relationships:</p><ul><li>When I set up the first outbound campaigns, I sent and replied to sales emails via a fake CEO email account for rick.song@withpersona.com to increase our hit rate. I A/B tested a campaign using my email vs the fake email and saw a 2.5x higher response rate with the latter.</li><li>In customer meetings, we often bring in “big titles” to make sure we signal the importance of our relationship or simply balance the table. If there’s a senior leader on the customer’s side, there’s a senior leader on our side too. So at this point, I’ve unofficially held every title at Persona 😃.</li></ul><p>I have the advantage of hindsight as I write this four years later than intended. But time has only helped me realize that these lessons are truer than ever.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2121307dc5f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 2022 Review]]></title>
            <link>https://vincenttsao14.medium.com/my-2022-review-5aadf7f6580c?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/5aadf7f6580c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[yearly-review]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[self-reflection]]></category>
            <category><![CDATA[introspection]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Sat, 31 Dec 2022 23:52:29 GMT</pubDate>
            <atom:updated>2023-01-01T23:41:34.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Introspection" src="https://cdn-images-1.medium.com/max/1024/0*A_MLurs-cBRq7XZG" /><figcaption>Photo by <a href="https://unsplash.com/@tingeyinjurylawfirm?utm_source=medium&amp;utm_medium=referral">Tingey Injury Law Firm</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I turned thirty this year, and for a hot second considered writing a review of the past decade. These annual reviews, however, are thoughtful enough and getting longer every year anyway (<a href="https://vincenttsao14.medium.com/my-2021-review-93cba15e4ce9">My 2021 Review</a>).</p><p>I even forced a year-end relationship retro on Bridget while we were on vacation, which wouldn’t have gone so well if I hadn’t caved in to her blue bubble demands and bought an iPhone in February.</p><p>Staying on brand with these reviews, 2022 was a very <strong>introspective</strong> year for me. I’m grateful for many conversations with friends, family, and co-workers about the next decade both personally and professionally.</p><h3><strong>Table of contents</strong></h3><ul><li>On life stages</li><li>On cycling</li><li>On marathons</li><li>On people</li><li>On roles</li><li>On startup mentality</li><li>On reading and writing</li><li>Memorable moments</li></ul><h3>On life stages</h3><p>Not to be overly dramatic, but 2022 marked another inflection point in terms of planning my life in longer horizons. As a student, I merely had to think about next semester. As a young adult, I considered the next two years at most. But now, I need to think in five year increments. I’m no better at predicting the future, but now I know more about what I do and don’t want.</p><p>Our closest friends are getting married and starting to have kids. We attended seven weddings this year alone! Besides being memorable opportunities to reflect and to celebrate loved ones, we also learned plenty about each of our wedding preferences. If I had my way, we’d have a casual backyard BBQ with a smattering of toasts. Skip the verbose ceremonies, plated dinners, best man / maid of honor, and bridal parties. But got to have the late night snack!</p><p>On a more serious note, the weddings also served as natural opportunities to reflect on my own relationship with Bridget and what the future holds in store for us. We had important discussions about our own timelines in the next five to ten years, and I’m excited and grateful to embark on that journey together.</p><p>But the most immediate change in our lives is the corgi puppy we picked up on New Year’s Eve. Apologies in advance to our friends and family for the late replies and ragged appearance in early 2023! Bridget and I had joked about getting a dog starting last year, but I knew it was inevitable when we started watching videos of other people’s corgis on Instagram before bed.</p><p><a href="https://www.instagram.com/p/CiMkjjrJVfx/">Willow &amp; Mango 🌻🥭 on Instagram: &quot;Oh... Hey 👋🥭 * * * * #corgi #corgilove #corgipuppy #corgilife #corgifeed #corgioftheday #corgis_of_instagram #corginstagram #corgipuppies #corgidaily #corgismile #corgidog #corgilovers #corgisofig #corgilicious #corgithings #corgithecutie #corgisdaily #corgiloaf #corgis #corgistagram #corgiaddict #corgigram&quot;</a></p><p>We can’t wait to introduce you to our pup soon, but no guarantees on an Instagram account.</p><p>And if I wasn’t already hyperaware about getting older, I also continued the trend from my late twenties of discovering how eerily similar I am to my dad:</p><ul><li>My rapidly receding hairline 🧑‍🦲, sigh.</li><li>My leadership style — I’m not the most vocal or motivating, preferring instead to lead by example behind-the-scenes.</li><li>My tendency to binge — whether reading a book, watching a show, or playing a game. I’ll stay up way past bedtime.</li></ul><h3>On cycling</h3><p>In what I hope is a continuing trend, 2022 was the best year of cycling yet. I hit my goals:</p><ol><li>climbed Hawk Hill in under nine minutes</li><li>completed the right of passage in cycling known as a century (a 100 mile ride)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nthsbvntXEzEK38RkePI_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mi09ofnWx1PEJY3ZHgosmg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1lBFiV7WLw9aHyF7P8TcCg.jpeg" /><figcaption>Stats that no one cares about but me</figcaption></figure><p>But more important than hitting arbitrary numbers, I started riding with a group of fellow cyclists that call themselves the <em>SF Cyclomaniacs</em>, a fitting name that captures their enthusiasm for the sport. I was introduced when I reconnected with a college classmate, and it’s been humbling to discover how little I actually know about cycling — and especially bikes, as I was fortunate enough to have obtained my bikes from a high school friend who also moonlights as my mechanic.</p><p>The primary group activity is a 6:30 AM meetup at the entrance to the Golden Gate Bridge to haul our butts up Hawk Hill every Wednesday. It’s a great way to push through the mid-week slump, and doubles as an outstanding opportunity to enjoy the San Francisco sunrise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oZIwLcAbNNgkjrtrRKAqeQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6EjegPOAru1OnXMOIY1B8w.png" /><figcaption>SF Cyclomaniacs take over Hawk Hill</figcaption></figure><p>I really found my groove with cycling this year. I have a great group to ride with, a mental map of all the routes in the north bay (which continues to amaze me as one of the best places to cycle in the world), and a new level of fitness to tackle even more challenging but rewarding rides.</p><p>I even squeezed in some mountain biking in Mammoth!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dN8FipOm60s6JKaTB04tFw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0Qc7hqEQCzQC3PDJcvgHA.png" /><figcaption>Rides on rides</figcaption></figure><p>While it was a great experience riding my century solo, now that I’ve gotten a taste of group riding, I set my sights next year on completing a group event like a double century or a multi-day trip.</p><h3>On marathons</h3><p>To be clear, I’d never run an actual marathon! My poor knees would crumble. But I did surpass four years at Persona in October, and as the saying goes:</p><blockquote>Startups are a marathon, not a sprint.</blockquote><p>So I wanted to reflect on the marathon so far and what else is in store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Su14rsiy2MPSzDeymhjOzw.jpeg" /><figcaption>Celebrating four years of eating all the food at Persona</figcaption></figure><p>The four year mark is a major milestone in startup land. It tells a rich story, including, but not limited to:</p><ol><li>Against the odds, the business is still ALIVE</li><li>You’ve been around long enough to make an impact</li><li>You have a rolodex of fun stories to tell new employees</li><li>You fully vested your initial stock grant</li></ol><p>The last point is the least important to me, but much to my surprise, was the one that forced me to think most critically about my future at Persona.</p><p>Why?</p><p>It came down to one question- <em>do I want a new four-year stock grant or a one-year grant</em>? I won’t get into pros/cons here, but this seemingly innocuous question triggered a more important question- <em>how long do I realistically see myself at the company</em>?</p><p>Which then triggered more questions:</p><ul><li>How has the company changed in the past four years? How will it change in the next four?</li><li>Why am I still at the company? Am I still having fun?</li><li>What else do I want to accomplish before my time is up?</li></ul><p>I spent months contemplating, ultimately arriving at the conclusion that I still have miles to run in the Persona marathon, but also acknowledging that:</p><ol><li><strong>I don’t know what I’ll do after crossing the finish line. </strong>One thing I realized early on was that I don’t want to be CEO of a venture-backed company. Other than that, I know more about what work excites me but less about how to build a career out of it. I care less about titles and climbing the ladder than I ever thought I would. And I don’t see an obvious “next play” professionally (to borrow some LinkedIn lingo). This both scares the part of me that’s always envisioned myself as a high-powered exec and excites the part of me that’s always sought and embraced risk.</li><li><strong>I’m not running as fast as I was at the start. </strong>I’d been wanting to take a three month break to rest and recharge, and I was finally able to squeeze in five weeks off this past summer. I <em>actually</em> avoided the emails and Slacks this time, and the break contributed significantly to staying sane this year. A longer chunk of time off served as a valuable reminder to create intentional points of change for myself — to have something to look forward to in the never-ending marathon. Better yet, it provided an opportunity for other talented folks that can run much faster than me to step up in my absence.</li><li><strong>I’m likely closer to the end than I am to the beginning. </strong>There’s a lot of different reasons to unpack here, but the takeaway is ultimately the same. I don’t feel the same levels of excitement as I did in the earliest days. The company has evolved so much over time, and I’m in a different stage of life now than when I started. It was initially frightening to internalize this, but putting it into perspective was also freeing and helped me prioritize how to best spend my remaining time, however long it may be.</li></ol><h3>On people</h3><p>The first two years at Persona was heads down building the product, last year was building the company, and this year was all about people.</p><p>When asked what kept me up at night, I consistently found myself answering with some variation of <em>“the product isn’t the hard part, it’s the people”, </em>or “<em>I spend most of my time on people problems”.</em></p><p>People problems are a different breed of problem. They’re emotional, messy, and personal. They trigger countless rounds of investigation, questioning, and listening. They require copious amounts of tact and deep thought about potential second/third order effects. And they have an unfortunate knack for backfiring spectacularly.</p><p>We’re constantly moving people from team to team. Experimenting with different roles and responsibilities to spark increased performance. Meticulously putting folks on projects that have complementary strengths and weaknesses. Rigorously debating who can or should lead initiatives. Intervening when there’s too much friction between groups. The org chart is an ever-changing jigsaw puzzle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*ZjvWLKNWCknBOPJDBan0og.jpeg" /><figcaption>We’re constantly forced to pick between two tough options</figcaption></figure><p>We go to extraordinary lengths to put folks in different positions to succeed when conventional wisdom suggests we let them go. It’s astonishing how often it’s worked out, but it doesn’t change the fact that we invest a lot of blood, sweat, and tears to make it happen and increase the odds of success. <strong>People-first</strong> is our number one value at Persona and I’m proud we’ve stayed true to it despite the tradeoffs.</p><p>I find myself surprisingly adept at identifying and diagnosing people problems, although resolving them is a different skill entirely. I’ve always had strong intuition on how well groups are working together and can build trust quickly across different personality types- these are the type of generalist skills that allow me to tackle all sorts of problems with all kinds of people.</p><p>The irony is, I don’t even directly manage anyone anymore! There are number of factors related to the organization and my role, but I don’t think I’m a great manager either; I hate dealing with poor performance, I’m not politically savvy, and I’m conflict avoidant. But I do care deeply that everyone is able to do their best work because a company is only as good as its people. I’m more mentor than manager, more dotted line than solid line.</p><h3>On roles</h3><p>Breadth, depth, and prestige. Every role optimizes for different combinations of the three. At Persona, I started with breadth and depth, believing prestige was the next step. Over time, I traded off breadth and prestige for depth. And in the inevitable next iteration of my role, I want to prioritize breadth again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrPYenN76zQfde1dFlr_gw.png" /><figcaption>Different role iterations and possibilities</figcaption></figure><p>The closest thing to an interview I had to do for Persona in 2018 was a phone call with an investor. I don’t remember much about the call, but one thought shared after the conversation always stuck with me:</p><blockquote>Generalists wake up one day at a startup and realize they don’t have a role at the company anymore.</blockquote><p>There’s different flavors of this statement, another one being:</p><blockquote>The people that you got here aren’t the same who’ll get you to the next stage.</blockquote><p>These statements ring true as startups grow, but they paint too binary a picture. There’s opportunity to create value regardless of role:</p><ol><li>There are <strong>so many holes of different shapes and sizes </strong>in the company as we try to accelerate through the growth stage, which generalists and folks who’ve been around longer are acutely aware of and are constantly plugging in the background. There’s more to do than ever, and having an extreme bias for action and a can-do attitude never goes out of fashion. Yes, we need more specialists now, but that merely changes the expectation for generalists. You need folks who can operate in the rapidly increasing number of seams between teams and specialists, creating cross-functional systems that scale.</li><li>Arguably the most important aspect of my role these days is not doing the work and leading by example in the trenches, but rather being a <strong>culture</strong> <strong>bearer and historian</strong>. I kickstarted an internal company podcast to capture the stories that have shaped the company (inspired by a similar effort at <a href="https://sirupsen.com/podcast">Shopify</a>), which had been on my backlog for the better part of two years. And on a recent intro call with a new hire who had worked at GitLab, a leader of the <a href="https://about.gitlab.com/company/culture/all-remote/guide/">remote-first movement</a>, she dropped so many great suggestions to improve remote work that I immediately pointed her to our ops team. I assured her we didn’t have a tedious process and we value feedback and bias for action whether you’re in week one or the CEO. So I was ecstatic to see us implementing her suggestions by end of week!<strong> </strong>Sharing context about the past and how we work is critical to perpetuating core behaviors that have driven our success.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*AARjbZc3-XFCJZ9LDJJQUg.png" /></figure><p>The key is <strong>embracing change.</strong> I don’t necessarily know how to solve problems any better than others, but I’m not afraid to make change. And if there’s one thing I’ve learned as the company doubled again this year, it’s that much of scaling successfully is mental. There are no silver bullet processes that magically make everything easy. Prioritize the right fires, invest the time and effort to listen to problems, collaborate on solutions, and communicate that you’ve thought deeply about the consequences, and progress will come. The act of making a change is often more important than the change itself.</p><h3>On startup mentality</h3><p>After years of free capital being plowed into every startup with a passable pitch deck, 2022 was a reality check for startups. Inflation and the Ukraine war were <a href="https://en.wikipedia.org/wiki/Black_swan_theory">black swans</a> that burst the grow-at-any-cost bubble — a much needed reset of expectations.</p><p>The startup mentality that <em>building a successful startup is insanely hard</em> was forgotten amidst the tailwinds of the last couple years, and I have some 🌶️ takes unpacking it:</p><ul><li>Folks in tech, including myself, have gotten entitled and soft. Take remote work as an example. I shared why I prefer in person work in <a href="https://vincenttsao14.medium.com/my-2020-review-d7d7c36e719c#53ec">My 2020 Review</a>. And after two more years of hybrid, I think remote work spoiled us. We expect increased flexibility, comfort, and productivity. Call me a pessimist, but I don’t believe you get more of one without trading off others. I’m the first to admit that I’ve traded productivity for increased flexibility and comfort over the years, but it was a conscious and communicated decision.</li><li>The odds are always stacked against you as a startup. You have to fight for survival and seize every possible advantage, all of which require some level of personal sacrifice. You need an edge and mental fortitude to withstand the ups and downs. If that’s unbearable, think carefully about whether you’re in the right situation instead of complaining!</li><li>Tech employees are undoubtedly some of the best paid and privileged personnel, and we’ve been able to demand more from employers because of recent market dynamics and COVID. Historically, the pendulum has swung too favorably for employers to get away with equating real people as mere “resources”, and it’s a good thing work will never be the same — change is progress. The pendulum now shifts back in favor of employers as we enter an economic downturn, and after swinging wildly in favor of employees, that’s also a good thing.</li><li>Some of my co-workers are also my closest friends, and work would be far less enjoyable without them. I’m careful to distinguish, however, that Persona is not my family. At the end of the day, we’re trying to build a business. And too much emotional attachment blurs the line between professional and personal. I have a reputation for being very serious at work. Not only is it just my style, but it’s also a tradeoff I’m willing to make to funnel the bulk of my energy into building the company.</li></ul><p>Success is highly correlated with effort and sacrifice. Everyone has different priorities that dictate what they can put in to the startup, but the startup mentality never changes, so we should make those tradeoffs intentionally.</p><h3>On reading and writing</h3><p>While I didn’t read many books this year, I still read plenty and managed to write a bit:</p><ul><li><a href="https://technically.substack.com/">Technically</a>- the author writes simple explanations of tricky technical concepts. What’s a data lake? What does GitLab do? What are microservices? I’m so impressed by the crisp writing and whiteboard visuals. Communicating complicated concepts simply is one of the best indicators of clear thinking, and I try to emulate the author’s style as much as possible!</li><li><a href="https://www.notion.so/withpersona/a9f358038b374670b39978fffc011a03?v=1c4fd31aeab34c4f99a5e1a10089a710">Tim’s monthly retros</a>- these are unfortunately gated to Persona folks. Tim is an engineering leader I’ve worked closely with over the years, and he started writing a monthly retro that spans a range of topics on process, culture, and people. It’s quickly become one of the share-outs I most look forward to each month. His writing is a key reason why he’s able to drive complex decisions to quick resolutions, and the retros are a great way for the team to get into the head of someone they respect and admire. Periodically look back on what’s happened in order to chart a clearer path forward.</li><li><a href="https://www.allinpodcast.co/">The All-In Podcast</a>- during the course of five weeks over the summer, I cranked through dozens of these hour+ long episodes and gained a wealth of insights on the economy, tech, and politics. I’m not the biggest fan of venture capitalist personalities, and there are plenty of cringeworthy moments that remind the listener they’re listening to the fireside chatter of a highly privileged group. But <em>all in</em>, I find the debate and <a href="https://en.wikipedia.org/wiki/Straw_man#:~:text=A%20steel%20man%20argument%20(or,not%20the%20one%20they%20presented%22.">steelmanning</a> to be rigorous and comprehensive in unpacking the nuance of the issues.</li><li><a href="https://vincenttsao14.medium.com/technorealism-43470fe430ed">Technorealism</a>- the first article I wrote this year was also one of my favorites. I’d never stopped to challenge my own rose-colored lens on technology. We too readily paint tech progress and leaders as unequivocally positive for society. That’s changing now, and THAT is unequivocally a good thing.</li><li><a href="https://medium.com/@vincenttsao14/speed-process-c064ed283360">Speed &gt; process</a>- letting go of the need to layer process on top of everything I touch is one of the biggest mental shifts I’ve noticed over the years. Startups have but a few powerful advantages, and moving fast is the most important one of all.</li><li><a href="https://vincenttsao14.medium.com/abstractions-and-models-29cba9b2a95f">Abstractions vs models</a>- as we work more remotely and rely on written documentation to communicate, word choice becomes increasingly important. These particular words had bothered me at work for so long, I decided to write about them.</li></ul><h3>Memorable moments</h3><p>As is tradition, I’ll end with collages of 2022: highlights, weddings, and home-cooked meals!</p><ul><li>Scavenger hunt offsite</li><li>Our first international vacation in Mexico</li><li>My niece Iris’s 1st bday</li><li>USC-Stanford football game</li><li>My dream of catered lunches at work finally realized</li><li>Stagecoach country music festival</li><li>Resuming our annual July 4th Vegas trip</li><li>Babysitting Iris</li><li>Laser tagging on my 30th birthday</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gPqaXDusb7SnpItckBOVw.jpeg" /></figure><p>Weddings 💜</p><ul><li>Alexis + Clay</li><li>Becky + Kenden</li><li>Stan + Kathy</li><li>Kirsten + Ryan</li><li>Alyssa + Doug</li><li>Karen + Mike</li><li>Payal + Harsh</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_8vCWVsTdpPfco1exnA2A.jpeg" /></figure><p>Homemade Food 😋</p><ul><li>Beef noodle soup</li><li>The fluffiest pancakes</li><li>Friendsgiving</li><li>Barbeque</li><li>Chicken enchiladas</li><li>Pork and cabbage dumplings</li><li>Chicken sloppy joes</li><li>Birthday cake for Bridget’s 31st (I tried with the candles)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FgKUKzJ_u3EPnPJO4P4IIQ.jpeg" /></figure><p><strong>From our new family of three to you and your loved ones, happy 2023!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGvcqlIl0m8c6Q59Tg3PfQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9P0i7gQmeuNUIfsd6p93MA.jpeg" /><figcaption>His name is Miso!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5aadf7f6580c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Abstractions and Models]]></title>
            <link>https://vincenttsao14.medium.com/abstractions-and-models-29cba9b2a95f?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/29cba9b2a95f</guid>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Tue, 02 Aug 2022 01:39:06 GMT</pubDate>
            <atom:updated>2022-08-17T01:50:45.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F98kFSyUFFmBu249" /><figcaption>Photo by <a href="https://unsplash.com/@kvalifik?utm_source=medium&amp;utm_medium=referral">Kvalifik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Two common words we use in software development are abstractions and models<em>.</em></p><p>A search of the company Slack returns countless matches:</p><blockquote>“It turns out that our <strong>abstraction</strong> for verification checks was right and consistent regardless of what verification type it is.”</blockquote><blockquote>“Doesn’t matter to me as long as we’re settled on polling state as the right <strong>abstraction</strong>.”</blockquote><blockquote>“Are we missing a <strong>model</strong> between inquiries/verifications/cases and accounts?”</blockquote><p>Abstraction has a specific definition within software engineering. In object-oriented programming, <a href="https://stackify.com/oop-concept-abstraction/">abstraction</a> is one of three central principles (along with <a href="https://stackify.com/oop-concept-for-beginners-what-is-encapsulation/">encapsulation</a> and <a href="https://stackify.com/oop-concept-inheritance/">inheritance</a>). Its main goal is to handle complexity by hiding unnecessary details from the user — a tool I as a product manager quickly adopted.</p><p>When you’re building something, you start with the big picture and fill in the details. Abstractions and models allow us to represent important parts of the software as more general ideas and illustrate ambiguous parts of software in other ways that we already understand. Put simply, they help us understand the big picture and reduce the complexity of details.</p><p><strong>When used correctly, abstractions and models help us align and build faster. But when used incorrectly, it slows us down and creates confusion.</strong></p><p>As an aside, the two terms are used interchangeably even though they shouldn’t be. We’ll unpack those nuances another time!</p><p>To illustrate how we use abstractions and models, let’s build some software that allows customers to create online surveys.</p><p><em>The following diagrams are NOT meant to be actual mockups of what a user sees — they’re illustrations of how the sum of the parts make up the product.</em></p><p>To start, we know nothing about how our product works, which we represent as a literal black box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7uTvdOwPM7H7EIyErg_sKA.png" /></figure><p>First, we realize the need for some “thing” where users can fill out the survey, and another “thing” where customers can see all the survey results. Let’s call them interface A and B, respectively. We don’t know what each interface will look like or how it works, but we have a general understanding of these interfaces and can start filling in details from these abstractions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vxv8vSwgf8fb3Hx9Y8PoNQ.png" /></figure><p>Next, we break down the two interfaces.</p><p>For interface A, we know a survey is made up of a variable number of <strong>questions</strong>. We’ve also heard from customers that the customizability of the survey’s appearance is important to increase survey completion rates, so the interface also needs to reflect the visual design choices of our customers as a <strong>theme</strong>.</p><p>For interface B, we know customers want a <strong>view</strong> that shows each users’ responses to each question. We also know that some customers will want to filter the responses in different ways that we can’t support in our MVP, so we’ll have an export that dumps all the response data into a <strong>CSV</strong> file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Im6ejXj0TZJ0l2ii0GUjxw.png" /></figure><p>There’s almost a recognizable product here — just have a couple more things to flesh out!</p><p>Our surveys need to collect all kinds of information, so customers need to add different <strong>types</strong> of questions (e.g. multiple choice, short answer, file upload).</p><p>There are also a lot of different ways customers could potentially customize the appearance of the survey, but let’s start with <strong>text color</strong> and <strong>font family</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rUXTzvQ4FKmmM5K1yx67Ig.png" /></figure><p>Now that we know more about how our product works, we can revisit the abstractions known as interfaces A and B.</p><p>Interface A collects information from users through a set of questions, which models a similar pattern of how we fill out physical documents, so we call it <strong>forms</strong>.</p><p>Interface B displays all the information that was collected by the above forms, so we call it <strong>responses</strong>. Another option is “answers”, but that more closely models questions rather than forms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/1*mggr9zF-U7KKJ5n5UZAZsQ.png" /></figure><p>We excitedly start building the new product, but soon realize there’s a missing abstraction. Customers need another builder interface where they can actually create the surveys!</p><p>The <strong>builder</strong> interacts with questions and themes of the form, but also introduces potential new abstractions like <strong>templates</strong> that enable customers to pick pre-built surveys (e.g. event registration) instead of creating them from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7k-1AWFBVMldWC3pcHp5g.png" /></figure><p>As we see in this example, the use of abstractions represents new ideas that are loosely defined. We can talk about these concepts in generalities without getting bogged down in specifics that aren’t helpful until we’re aligned on the higher-level assumptions.</p><p>So where does it go wrong? Unsurprisingly, we tend to get in trouble when we’re not specific enough.</p><h4>More general = more open to interpretation</h4><p>Words and phrases have multiple definitions that also depend on the context in which they’re used and who’s doing the interpreting (e.g. a product manager should understand the nuances of their product better than a salesperson).</p><p>When we hear the same word used in a sentence, I may use one definition while you use another. And when we specifically use the words “abstraction” or “model”, we need to perform two transformations:</p><ol><li>What is the concrete concept that’s being referred to as the abstraction?</li><li>Are there multiple definitions? If so, which one is it?</li></ol><p>Hopefully in most cases, we ask each other and confirm our understanding is the same, but that’s not always the case. Deviations in our understanding of complex ideas lead to very different outcomes over the course of many months of back-and-forth.</p><p>To avoid this problem, I’m constantly asking for clarification of concepts in conversations with engineers, designers, and other product managers!</p><h4>The audience needs the details</h4><p>While it’s common for technical folks to get way too in the weeds with non-technical audiences, it’s just as easy for non-technical folks to talk in extreme generalities with technical folks.</p><p>Most developers I’ve worked with prefer a bottoms-up approach, in which they explore something in a lot of detail before they start to understand the higher-level abstraction. It makes sense when I think about how code has to handle every explicit detail — the computer doesn’t infer anything.</p><h4>A placeholder that never gets defined</h4><p>Abstractions can end up as placeholders to be updated at a later time but never do. The developer has enough context to understand the intent of the placeholder, but the user doesn’t. There’s always a next layer to the abstraction that you can peel back to make the product easier to understand.</p><p>When I write product specs, I specifically avoid using the words abstraction or model, and include as many examples and different explanations/analogies for core concepts as possible. I want to make sure everyone who reads the spec has the same understanding of the problem and solution afterwards.</p><p>Whenever I hear the actual words abstractions or models — sometimes from yours truly — my spidey senses tingle. If I don’t interject immediately for clarification then, I’ll write a note to follow-up later.</p><p>More often, we generalize concepts with different terms and we should ask ourselves:</p><p><em>Is there a more specific description we can use here? If not now, when do we revisit it?</em></p><p><em>Who’s the audience? Do they need more or less detail?</em></p><p>Using abstractions and models is an extremely powerful tool in software development, but we need to be mindful about how we wield it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29cba9b2a95f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Speed > Process]]></title>
            <link>https://vincenttsao14.medium.com/speed-process-c064ed283360?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c064ed283360</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Sat, 23 Jul 2022 00:36:30 GMT</pubDate>
            <atom:updated>2023-06-19T00:35:54.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z2OgIDWZSlI5mlZ4" /><figcaption>Photo by <a href="https://unsplash.com/@claytonrobbins?utm_source=medium&amp;utm_medium=referral">Clayton Robbins</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>A process is a series of actions or steps taken in order to achieve a particular end.</blockquote><p>All companies have processes — there’d be no sane employees left otherwise — but not all processes are the same:</p><ol><li><strong>Implicit</strong> processes mirror general systems or values e.g. collaborating closely with co-workers when building a new feature.</li><li><strong>Required</strong> processes keep the lights on e.g. setting up payroll to pay employees or collecting payments from customers.</li><li><strong>Explicit</strong> processes solve with precision e.g. asking specific stakeholders to give written approval before launching a feature.</li></ol><p>This article is about the last type so please make sure employees keep getting paid!</p><p>Friends and coworkers always tell me I’m a process-oriented person, so this article may come as a surprise.</p><p>I do love writing up and rolling out SOPs (standard operating procedures). But after spending time at Amazon, a process-laden behemoth, then jumping to Persona, a startup with no product or customers and founders who were seemingly allergic to process, I have a more discerning view on when to throw down process.</p><p>Processes inevitably grow as a company grows, but startups should err on the side of too little rather than too much. <strong>When you have no idea what you’re doing,</strong> <strong>moving fast is more important than doing things right</strong>.</p><p>Some pitfalls I’ve experienced at Persona:</p><h4><strong>Too early</strong></h4><p>It’s human nature to bring order to chaos, but chaos can also be the optimal path to experiment and learn quickly. Experiencing the pain in different ways over time unlocks a deeper understanding of why and how that pain is solved. And oftentimes, that particular pain wasn’t the highest priority to solve anyway.</p><p>As we closed our first couple customers, we started debating whether to create a sales playbook. But conversations with prospects at the time were more different than similar. We customized our pitch for each prospect (e.g. creating personalized demo videos based on the job function of the decision maker and their use case), and creating a playbook that early would’ve impacted our flexibility and creativity to close a deal by any means possible.</p><h4><strong>Conflating WHY and HOW</strong></h4><p>In other words, focusing on a solution instead of understanding the problem. As a PM, this is one of the biggest challenges in multi-month product development. We get distracted and grasp onto specific solutions too tightly while slowly losing sight of the original problem over time.</p><p>Every couple months, we have a conversation with the product marketing team about whether it’s time to set up an internal <a href="https://en.wikipedia.org/wiki/Changelog#:~:text=A%20changelog%20is%20a%20log,level%20files%20in%20their%20distribution.">changelog</a> for product launches. It’s an enticing feature but doesn’t address the more fundamental and unanswered question of “how deeply do we expect different internal teams to understand what’s being launched?”.</p><h4><strong>Maintenance cost</strong></h4><p>Startups are constantly changing, and maintaining heavy process is a cost startups can’t afford to pay. As every experienced developer knows, “the best code is no code at all”. The cost of maintaining code is always more than planned. So instead, let’s keep learning and collecting information that builds stronger conviction that we’ll solve the right problem in the right way.</p><p>Last year, I tried writing a “how-to” guide for a new version of our product. I spent a week fleshing it out, only to spend many more weeks re-writing it when we decided to descope some features we initially committed to. At one point, I realized I was spending <em>more</em> time updating the guide than saving the time of those who were working with the product! Not to mention the added communication tax of constantly announcing new updates to the guide.</p><p>Worse, we’re naturally reluctant to abandon existing processes due to <a href="https://en.wikipedia.org/wiki/Loss_aversion">loss aversion</a> and <a href="https://en.wikipedia.org/wiki/Sunk_cost">sunk cost</a>, opting instead to spend even more precious time trying to fix them. Similarly, newer hires at the startup may assume that the current process exists for a reason and stop questioning whether it truly solves the problem.</p><h4><strong>Overextending</strong></h4><p>This one is the real killer! Just because one process works in one company or scenario doesn’t mean it works in another. Don’t just “trust the process”. Be careful when new hires, advisors, investors, and others who may not have insight into the nuances of the company start recommending processes. Every process we have at Persona is heavily inspired by successful previous iterations we’ve seen, but with our unique twists.</p><p>We’ve adopted a decentralized roadmap planning process for each product team because they’re in different stages of development. While some products have millions of users, others are looking for their first paying customer. Rather than dictating how each team sets their roadmap, we define the expected outcome of roadmap planning and empower each team to figure out how to get there. Why spend multiple weeks planning a detailed version of the next year’s roadmap when there’s not even a demo-able product? Use that time to build a demo and start selling.</p><p>So how might we avoid such pitfalls?</p><h4>Define the problem</h4><ul><li>What’s the problem? A process usually solves for one of either quantity (i.e. scaling efficiently) or quality (i.e. making sure things don’t break). If the former, figure out how much time or money is currently lost. If the latter, figure out why things keep breaking.</li><li>How important is that problem? As an extreme example, the military relies on heavy process because people’s lives are literally on the line. One kink in the system could be catastrophic.</li><li>Are there alternatives? First talk to relevant stakeholders about the problem to develop a shared understanding. Recognizing that there’s a problem is often just as important as trying to implement a solution.</li><li>How likely is the problem to change, and how drastically? If the first customer hasn’t signed yet, don’t create an integration playbook. Once the tenth fintech customer has signed, the overall integration process won’t change much.</li></ul><h4>Start small</h4><p>If the problem is worth solving, what’s the lightest-weight process that can be put in place? Expect to iterate constantly and keep those sneaky maintenance costs as low as possible. An old startup adage is relevant here — invest in scale only after finding product market fit.</p><h4>Revisit the WHY, not just the HOW</h4><p>When it’s time to update the process, it’s also time to revisit the problem anew. Is it still important to solve? How’s it changed over time? Don’t assume what worked before works now.</p><p>To sum up, <strong>explicit process is often implemented too early and aggressively, stifling a startup’s most important advantage — speed.</strong></p><p>Reflecting on my time at Amazon, I was blinded by the personal satisfaction of creating order but didn’t think critically about the tradeoffs. Now, I’m one of the crazy early hires at Persona who pushes everyone to be more comfortable with ambiguity and embrace the speed of chaos 🤷.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c064ed283360" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technorealism]]></title>
            <link>https://vincenttsao14.medium.com/technorealism-43470fe430ed?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/43470fe430ed</guid>
            <category><![CDATA[metaverse]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Tue, 08 Feb 2022 04:52:11 GMT</pubDate>
            <atom:updated>2022-03-28T18:19:58.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rCWZ4_QamXpqH1IV" /><figcaption>Photo by <a href="https://unsplash.com/@ciabattespugnose?utm_source=medium&amp;utm_medium=referral">Lucrezia Carnelos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One of the most memorable conversations of 2021 arose from unexpected circumstances. During a dinner over Thanksgiving break, my partner’s brother, Austin, needed to grab something from the local market. I’d been sedentary and gorging myself all weekend, so I volunteered to walk with him. We’d never interacted in a 1:1 setting before so I was curious what we’d talk about.</p><p>To my pleasant surprise, we hit the ground running as soon as we set off. No pleasantries or idle comments about the weather. We quickly covered artificial intelligence, remote teaching (he’s a teacher), and a smattering of other topics. But one in particular dominated the discussion — the pros and cons of technology.</p><p>For brevity, I’ll paraphrase our respective stances. Austin argued that technology is net negative to humanity. While I, as the tech startup employee, argued that technology is net positive. In hindsight, as with most things, we were both right.</p><p>We had such an engaging conversation, and I knew I’d need to process it later especially since I instinctively knew that technology brings changes both good and bad, and therefore got the sinking feeling we may have missed something as we each laid out our arguments and counterarguments.</p><p>After stumbling upon a twenty year old website, I realize what I’d missed. It’s not about <em>what </em>technology, but rather <em>how </em>it’s being applied. The site refers to this concept as <a href="https://www.technorealism.org/">technorealism</a> — a bridge between techno-utopianism and neo-Luddism.</p><p>Over two decades and many technological advances later, the principles of technorealism still speak to me loud and clear.</p><ol><li><strong>Technologies are not neutral.</strong> The greatest challenge with machine learning is bias. No data set that powers an algorithm is ever fully representative. Equally worrying is that these biases compound exponentially at scale. But most concerning is that these biases are a black box to us. A human may not have made the right decision because of their own biases, but at least we can get to the why. We can’t blindly assume that more decisions driven by algorithms is better.</li><li><strong>The internet is revolutionary, but not utopian.</strong> Virtual reality is undeniably one of the most revolutionary technologies today, but that doesn’t make it utopian. Over a decade ago, <em>Ready Player One</em> suggested as much. The metaverse may eventually change how we experience the internet but it first needs to solve a much more pressing problem — <a href="https://www.nytimes.com/2021/12/30/technology/metaverse-harassment-assaults.html">rampant harassment and assault</a>. We can’t look to the internet to solve all our problems.</li><li><strong>Government has an important role to play on the electronic frontier. </strong>Tech companies had decades to consolidate their position and dominate markets before the government finally decided to step in. Just because tech companies have loftier mission statements than the oil and finance companies of old doesn’t mean that unchecked power won’t stifle innovation and create negative ramifications. Even tech companies themselves recognize this! <a href="https://www.washingtonpost.com/technology/2018/07/13/microsoft-calls-regulation-facial-recognition-saying-its-too-risky-leave-tech-industry-alone/">Microsoft has repeatedly called for regulation of facial recognition software</a>, and the government needs to step up before it’s too late.</li><li><strong>Information is not knowledge. </strong>We live in an echo chamber, constantly getting spammed by and consuming an overwhelming amount of messages, articles, and ads. Everyone has a voice and it’s amplified with technology. We find ourselves getting yelled at — unable to turn off all the voices — while our attention flits from one stimulant to the next. Information is plentiful, yet knowledge is harder than ever to come by. We don’t need more information; we need to reason and make sense of what we already have.</li><li><strong>Wiring the schools will not save them. </strong>COVID was the ultimate experiment. It’s still too early to make any sweeping conclusions, but it sure seems like not all learning can be replicated or accelerated by technology. Even pre-COVID, technology in the classroom had not meaningfully improved learning outcomes. We teach more of the same things (e.g. math, history, english), but not necessarily the right things (e.g. problem solving, adaptability, how to learn, resilience, collaboration).</li><li><strong>Information wants to be protected. </strong>Identity and privacy has finally drawn our attention in the past five to ten years. While it’s still a largely one-sided battle in favor of the tech companies who provide services in favor of collecting and selling your data, there’s a slowly growing awareness and resistance to the fragmentation and exploitation of our personal data.</li></ol><p>When considering how technology is applied, it’s worth pointing out that technology is merely a means to an end. That end, in this case, is the continuation of the human race. So with that in mind, I propose one additional principle.</p><p><strong>The survival of humanity is increasingly volatile. </strong>We can talk to friends and family all over the world, research life-extending medicines, and build spaceships to explore potentially habitable planets. But we also build weapons that can wipe us off the face of the planet, are more distracted than ever from existential issues like climate change, and continue to widen the inequality gap between those who have and those who don’t. Simply put, the highs are higher and the lows are lower.<strong> </strong>Technology creates many more paths to survival, but at what cost? Are we destined to survive in the metaverse like the Fermi paradox suggests, existing solely in a digital world?</p><p>I’m grateful for the conversation that night with Austin. It prompted me to evaluate my own views on technology with a more critical lens. From a bright-eyed technologist to now a technorealist, I expect my views to continue evolving as technology inevitably progresses. I, for one, still believe we can find ways to apply technology in the right ways that will best serve humanity, and am as energized as ever to play my small part in doing so.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43470fe430ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 2021 Review]]></title>
            <link>https://vincenttsao14.medium.com/my-2021-review-93cba15e4ce9?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/93cba15e4ce9</guid>
            <category><![CDATA[self-reflection]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[yearly-review]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Thu, 30 Dec 2021 20:58:50 GMT</pubDate>
            <atom:updated>2022-01-04T04:00:50.563Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l4iWQIE98rJ0bEBz" /><figcaption>Photo by <a href="https://unsplash.com/@srosinger3997?utm_source=medium&amp;utm_medium=referral">Samantha Gades</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>2021 was a breath of fresh air compared to <a href="https://vincenttsao14.medium.com/my-2020-review-d7d7c36e719c">My 2020 Review</a>.</p><p>Quality time with friends, family, and co-workers lifted my spirits as I rejoiced at the return of trips with friends, birthday celebrations, family vacations, eating out, live concerts, and that unmistakable office buzz. We enjoyed being physically together, even if six feet separated us at times.</p><p>In January, I hopped on a one way flight to Dallas. My lease in San Francisco was up, my roommate had moved out, and I wanted a change. Going home presented an opportunity to reconnect with my parents and rediscover my focus. It ended up being one of the most productive months in recent memory, and the perfect way to kickstart the year.</p><p>But most importantly, I also wrapped up the year on a high note by publishing this review on December 30th so I can finally relax on New Year’s Eve!</p><h3>Table of contents</h3><ul><li>On home</li><li>On cycling</li><li>On merging minds</li><li>On startup growth</li><li>On traveling</li><li>On writing and reading</li><li>Memorable moments</li></ul><h3>On home</h3><p>As only one definitively past the peak of youth would say, buying a home in San Francisco was a big move. I explained why I wanted to mortgage away my future in a <a href="https://vincenttsao14.medium.com/settler-9ed9f1bb42de">previous article</a>, but suffice to say it was a calculated choice.</p><p>I snuck in at the end of the much-needed market correction (downturn) triggered by COVID, buying a new condo right in the center of the city. But of all the things I should be grateful for — like continuing the wonderfully convenient trend of being able to walk to work — I’m still endlessly amused that the address 555 Golden Gate Avenue is as SF as it gets. I hadn’t considered whether it was a factor in the buying decision — probably best not to think about it too much!</p><p>Finding a home was a challenge, but ultimately nothing like furnishing it. Without any expiring lease agreements in my near future, I could finally invest in quality furniture and quite a lot of it indeed. For months, life was summed up as working during the day and furniture hunting at night. We’ve slowly but surely whittled down our “(FUN)iture” doc, but new items keep sprouting up in the doc like weeds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GADAMvrJWz7nlwZDSH6vDg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vfJfGoPe8CjwyHEgG5exBw.jpeg" /><figcaption>Learning the little joys about furniture: 1) seeing friends cozy up on the couch, 2) taming footwear sprawl with a shoe bench</figcaption></figure><p>For anyone who’s stepped into my primitive dwellings of the past decade versus the new home, they’ll quickly recognize a changed man. There’s an alarming number of furniture photos from different angles on my phone, I have this growing desire to fill every empty space with houseplants, and Architectural Digest videos dominate my YouTube history. Ah, the joys of a home.</p><h3>On cycling</h3><p>Instead of titling the section “fitness”, I thought it better to be specific, since cycling has become my primary source of exercise and competition as well as the only sport my battered joints can survive.</p><p>2021 was the year I unlocked the true secret to cycling faster.</p><p>It wasn’t the oatmeal and homemade energy balls, interval training, heart rate monitor, aero tuck, or drafting. Although these, amongst others I’ve learned, are all great strategies to pick up the pace.</p><p>No — the best way to get up that hill faster is…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OnXEpt_sOijwMUSLlS0Ctg.jpeg" /><figcaption>The only picture I’ve taken of this bike, I swear</figcaption></figure><p>… getting a significantly lighter bike.</p><p>I jest! Mostly. Everybody knows there’s no real shortcuts to consistently increasing your speed outside of deliberate training. But the first time I took the new carbon fiber frame for a spin, I really did feel like I was pedaling on a cloud.</p><p>How obnoxious I must sound when I painstakingly differentiate between my old “city bike” and my “real road bike”. The new bike also signals the start of the slippery slope that ends in a garage full of expensive bikes collecting dust, otherwise known as the n+1 principle:</p><blockquote>While the minimum number of bikes one should own is three, the correct number is n+1, where n is the number of bikes currently owned. This equation may also be re-written as s-1, where s is the number of bikes owned that would result in separation from your partner.</blockquote><p>With a lighter bike in tow, I picked up the intensity in the second half of the year and hope to ride, so to say, that momentum going into 2022 . I didn’t finish a century (100 mile ride) or break 9 minutes on the hill sprint, but I did enjoy a beautiful 60 mile ride to and from Half Moon Bay and hauled my butt up Hawk Hill dozens of times. Good progress for next year’s goals!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*tMk0DFANK3aENANDm37FAQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZkP2GO1vgy_VbQovNJQIQ.png" /></figure><h3>On merging minds</h3><p>Bridget, my partner, asked me if she’d show up in the review. She’ll either be irked or flattered when she realizes she gets an entire section instead. For as big a part she’s played in making 2021 a fantastic year, it was actually unfair to set aside just one section.</p><p>We passed some important milestones in our relationship. We spent time long distance, survived an extended vacation with my parents, moved in together, and even started texting each other’s mom directly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*pB_EDu0kM8nb9dr_W7Scxg.jpeg" /><figcaption>Candid photos- a real benefit of having a direct line of communication with Bridget’s mom</figcaption></figure><p>I relied on her more than ever this year as a thought partner, confidante, and home design consultant. And we’re thoroughly convinced that our minds have merged, with some <a href="https://www.nytimes.com/2021/05/25/science/optogenetics-brain-social-behavior.html">exciting science</a> lending credence to our claims. So in what can only be described as “stupid things couples do”, we make it a game to shout out the thoughts the other one might be thinking a split second before they can say it aloud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*8zdwq_f1_NILdLeOdCNzqg.gif" /></figure><h3>On startup growth</h3><p>Persona’s year can be summarized in one word — growth.</p><p>Growth is a double-edged sword. On one hand, you get revenue, recognition, funding, and opportunities. We tend to tout and fixate on these. On the other hand, you have more pressure, competition, onboarding, communication, and knowledge transfer. We tend to ignore these and let them fester.</p><p>We’ve grown quickly every year, but year three felt markedly different. I summarize my time at the startup as a series of key inflection points, and this year brought the biggest one yet.</p><p>For the first two years, I knew all my co-workers in a meaningful capacity, many as friends. The cross-team collaboration required of my functional role combined with incumbent knowledge as an early employee meant I had the privilege to work closely with everybody. As we’ve raced past the hundred-person mark this year, I don’t know everybody anymore. There’s people I’ve never even introduced myself to! I’m the first to admit that I should make more of an effort to reach out proactively, but it’s no easy task to build and maintain so many relationships.</p><p>This hundred-person inflection point is scary for two reasons:</p><ol><li><strong>More complexity, less control- </strong>I like to get things done and do them well. Generally, the more factors I control, the better the results. This likely demonstrates poor/unscalable leadership or control freak tendencies, but I can own up to that. As the number of people and processes increases linearly, any given individual’s control decreases and communication needed to get anything done increases exponentially. In short, getting things done becomes much harder much faster. While these challenges are inevitable and expected, the real challenge is adapting my own behavior from when the entire company fit on a small couch to now a hundred-plus organization. We try hard to keep teams small and de-coupled, as popularized by <a href="https://www.theguardian.com/technology/2018/apr/24/the-two-pizza-rule-and-the-secret-of-amazons-success">Amazon’s two-pizza teams</a>, to combat this complexity.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*3fze4m07-em0V0LT4p3jAQ.jpeg" /><figcaption>Lines of communication increase exponentially as people increase linearly</figcaption></figure><ol><li><strong>Stratification- </strong>This one scares me more because it often goes unnoticed. I see people falling into this trap all the time, myself included. As more people join the company, implicit “generations” form based on when you started. The human need for connection and storytelling is strong — you bond with those whom you share the most in common. This often manifests as innocuous statements like “Remember that time we…” or “It was so much better before…”. In private, it spurs camaraderie. In public, it stratifies and slowly pushes apart groups that know and don’t know what you’re talking about. It’s incredibly difficult to fight, but well worth it since it’s a primary way that the startup’s culture stays cohesive over time.</li></ol><p>Navigating the growth stage comes down to finding new and clever ways to operate as if you were still that ragtag bunch on the couch, all while optimizing the transfer of knowledge across the company.</p><p>I like to draw upon some simple adages.</p><h4>Repeat, repeat, repeat</h4><p>One thing we product managers love to commiserate about is how no one seems to absorb what we tell them about the product. Why?</p><ol><li>There’s so much going on that nobody is absorbing 100% of what you’re saying at any given time.</li><li>Our product surface area is expanding rapidly as we build multiple standalone products on top of the platform.</li><li>New people join every week and the knowledge gap between them and existing folks widens. We need to communicate at the lowest common denominator.</li></ol><p>I still find myself getting annoyed at repeating myself over and over again, but I also continue to marvel at how critical it is to keep doing.</p><h4>Teach while you do</h4><p>I recently joked with one of our early engineers that we’re just professional teachers these days. Truly, the most powerful way to scale ourselves is to teach others. I originally wrote that “Teaching is more important than doing”, but realized that’s not quite right. The reality and more difficult duty is that we need to teach and do at the same time. At this stage of the company, our ability to tackle the most complex problems from the front is as valuable as ever, but we also need to guide and empower others to be able to accomplish at least the same if not better. The earlier and more senior you are, the more important it is to internalize.</p><h3>On traveling</h3><p>One of the great pleasures of 2021 was being able to travel.</p><p>While we didn’t leave the US, it was rejuvenating to resume the annual trips with friends that I looked forward to like the seasons of the year and escape the daily monotony of being cooped up in a small space. There’s simply nothing I love more than exploring new places with old friends. So I’m happy to now share this cringey rhyme.</p><p>Our first time in Hawaii, but certainly not our last.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h5Doq6HMpzu_Yo7tFY3wsw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W6CDXqVUlyvketOxChmcSg.jpeg" /></figure><p>We relaxed in LA and Vegas over July 4th, golfing as the fireworks blast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*nKUiOBRfQWCDmoQmfVMeug.gif" /></figure><p>A cloudless sky in Minneapolis<strong>, </strong>with a jaunt to the Renaissance Fair.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7FDstWMgcUSMAun1k-8wpA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*gXzs30890XUoN48lX-GubQ.jpeg" /></figure><p>Walking and eating our way around Seattle, whose summers are beyond compare.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZRVvv_Mcd8DEEp79MmFiLg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pWzPCFlFILUDkAClq1dzxg.jpeg" /></figure><p>Long weekends in Santa Cruz, Mendocino, and Monterey kept us near.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JZ3R0g2dFB0c9hI7gaPlQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cplW_Bo5wZdqg87eM5meYw.jpeg" /></figure><p>And now we’re old enough now to look forward to many a wedding next year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQBTjdguOzVXIRfLTA7CfQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uu3P6wPC_AKXCdyrcrG-4A.jpeg" /><figcaption>Congrats, ya’ll!</figcaption></figure><h3>On writing and reading</h3><p>In January, I challenged myself to <a href="https://vincenttsao14.medium.com/my-2020-review-d7d7c36e719c#a7c6">write and publish an article on Medium every day</a> of the month. I’m proud of what I accomplished and learned a great deal about recreational writing and my distinct style within it, which I dutifully summarized in a follow-up <a href="https://vincenttsao14.medium.com/what-i-learned-from-writing-24-articles-in-one-month-70ef320b15f8">article</a>.</p><p>Though I failed to consistently write publicly in the following months, I constantly reference and revisit the thoughts that had finally been organized into coherent write-ups. I was recently collaborating with a co-worker on a how-to guide for working with third-party vendors that power our product, and got the ball rolling on our discussion by drawing upon tips I’d laid out in my <a href="https://vincenttsao14.medium.com/vendor-management-3ae381293317">Vendor Management</a> article.</p><p>Yet the best part is not what I gain, but hopefully what I in some small way can inspire. As unexpected as it was gratifying, after Bridget’s dad, Emile, heard about my writing, he starting blogging about the memories of his own life. He’s lived a rich nine decades, not to mention written many books as a professor, so I’m ecstatic to be a part of an exclusive group who get a glimpse into his journey. As is much of starting to write, Emile fittingly started the blog with this:</p><blockquote>I am making a start on a path that has no immediate destination.</blockquote><p>Now we’re waiting for the ninth entry!</p><p>Inspiration to write often comes from what I’ve read, and I managed to read a book or two. While I still challenge myself to read a certain number of books, I primarily use it as a reminder to find interesting reads as opposed to worrying about quantity, especially as the selection of books I actually want to read shrinks. I’ve eased up on the <em>Outliers</em>-type self-help and behavioral economics books for two reasons:</p><ol><li>I’ve read so many books in the genre that I recognize the same core message repackaged across different examples.</li><li>Now that I’m old enough to have some actual life experiences, they teach deeper and longer-lasting lessons than learnings from a book.</li></ol><p>Therefore, I’ve taken an interest in biographies, history, and societal commentary (with a scattering of sci-fi as always).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XoDTWs6giyahfuf7wydYPA.png" /><figcaption>See <a href="https://www.goodreads.com/user/show/43537565-vincent-tsao&#39;">Goodreads </a>for all my reads</figcaption></figure><p>My non-fiction highlights:</p><ul><li><a href="https://www.goodreads.com/book/show/41721428-can-t-hurt-me?from_search=true&amp;from_srp=true&amp;qid=EWd4uGKb0I&amp;rank=1"><em>Can’t Hurt Me</em></a>- Few books have had a bigger impact on me. In hindsight, I had been in a rut when I read this but hadn’t yet grasped the cause-and-effect. It was a wake-up call that helped me refocus on goals I’d unknowingly put off. <em>Can’t Hurt Me</em> is an easy-to-read autobiography written by “the toughest man alive” who embodies mental resilience and does us a favor by sharing his story. But more importantly, it was exactly what I needed at the time. A blurb won’t do it justice — I plan on writing more later.</li><li><a href="https://www.goodreads.com/book/show/29890867-world-after-capital?from_search=true&amp;from_srp=true&amp;qid=vpNMc1gEJD&amp;rank=1"><em>World After Capital</em></a>- A thought-provoking read about technology and society. If there’s one thing I appreciate about venture capitalists, it’s that they tend to share interesting insights into trends and the future. Whether or not the author’s predictions come true, it’s worth understanding why and how technology is pushing us from the Industrial Age to the proposed Knowledge Age, in which the scarcest resource to optimize for shifts from capital to our attention.</li><li><a href="https://www.goodreads.com/book/show/21.A_Short_History_of_Nearly_Everything?from_search=true&amp;from_srp=true&amp;qid=CdirdKPOVq&amp;rank=1"><em>A Short History of Nearly Everything</em></a>- This is a brilliantly-written and well-researched book on an ambitious premise. It’s <em>Homo Sapiens</em>, one of my favorite books of all time, but with a deeper dive into the science and copious amounts of wit. Not every page or historical figure is riveting. After all, the great challenge of science is that it’s largely uninteresting until suddenly it isn’t! But if I had read this in lieu of science textbooks in school, I may have chosen a different career.</li></ul><h3>Memorable Moments</h3><p>As is tradition, I’ll end with some additional 2021 highlights and a gratuitous collage of our home-cooked meals so people think we’re good cooks:</p><ul><li>Birth of my niece, Iris 💮</li><li>Camping in Bothe</li><li>Our first caricature</li><li>Bridget’s 30th birthday party</li><li>LANY and Brett Young concerts</li><li>First TAMS trip with +1s</li><li>Persona’s holiday party</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j-hrusCQhOaAY8YuN5-GZA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OI89wOxoGaJDGQzVm9akxA.jpeg" /></figure><p><strong>Best wishes for a happy and healthy new year!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93cba15e4ce9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned From Writing 24 Articles in One Month]]></title>
            <link>https://vincenttsao14.medium.com/what-i-learned-from-writing-24-articles-in-one-month-70ef320b15f8?source=rss-9436a6b4aacb------2</link>
            <guid isPermaLink="false">https://medium.com/p/70ef320b15f8</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[writing-challenge]]></category>
            <dc:creator><![CDATA[Vincent Tsao]]></dc:creator>
            <pubDate>Mon, 15 Feb 2021 23:38:45 GMT</pubDate>
            <atom:updated>2021-12-28T15:48:07.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IPs4nzQCh-kARzfw" /><figcaption>Photo by <a href="https://unsplash.com/@ryansnaadt?utm_source=medium&amp;utm_medium=referral">Ryan Snaadt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>While I didn’t publish 31 articles for each day in January, I consider the pledge in <a href="https://vincenttsao14.medium.com/my-2020-review-d7d7c36e719c">my 2020 review</a> fulfilled.</p><p>My goal wasn’t to start a daily journal or jot down my stream of consciousness, although many folks I know find the practice to be meditative and useful in comprehending, processing, and focusing. Instead, I wanted to put down well-formed thoughts on interesting subjects and stories that had either been floating in my head or were particularly topical.</p><p>Over the course of 24 articles that took up to two hours each on average — not including doggedly searching for the <em>perfect</em> photo or meme — I observed a thing or two about how I write and the art of writing itself:</p><ul><li><strong>Inspiration</strong>: I’ve never been one to be struck by inspiration. The way I generate ideas is far more mundane. I dedicate a tab in my <a href="https://vincenttsao14.medium.com/second-brain-c3574a3394cc">to-do list</a> to jot down problems, inefficiencies, or interesting topics along with a couple bullets of what’s on my mind at the time. Over time, I revisit and refine those thoughts. So being forced to write about a new idea almost every day taught me how to shift the system into overdrive.</li><li><strong>Transitions</strong>: I struggle with transitions. Seamlessly connecting two oft-related but disparate ideas is one of my biggest growth opportunities as a writer. Bullet points are my crutch, and I’m not afraid to use them.</li></ul><blockquote>There appear to be only three principles of connections among ideas, namely Resemblance, Contiguity in time or place, and Cause or Effect.</blockquote><ul><li><strong>Critical reading</strong>: I started paying attention to stylistic and even grammatical nuances of the content I was reading. This author used occasional short sentences to drive emphasis — that author used the <a href="https://www.thesaurus.com/e/grammar/em-dash/">em dash</a> instead of a colon. Reading is one of the best ways to become a better writer, but you don’t just improve by osmosis.</li><li><strong>Writing style</strong>: When folks ask me about my experience working at Amazon, I always describe the working environment as <em>brutally efficient</em>. Now I describe my writing style with those same words. While I do enjoy throwing in a flourish, synonyms (at least a dozen Thesaurus tabs are open at any given time), or a bad joke here and there, I always try to get to the point.</li><li><strong>Endings</strong>: In my opinion, writing an ending that both summarizes and stimulates is the ultimate skill. The ending is the most important transition of them all. Does it feel like a natural stopping point? What are the key takeaways? Do you sign off with a flurry or take it slow?</li><li><strong>Deep thinking</strong>: Writing allows me to think deeply and organize my thoughts in ways that back-and-forth verbal interactions do not. I call myself a “processor”, in that I need time to consider and synthesize new information. My brain tends to forge connections in a series of small steps, not large leaps. Writing helps me structure my thoughts as such.</li><li><strong>Anecdotes</strong>: Once I started brainstorming topics, I discovered there was no shortage of content. What wasn’t always so easy, however, was finding the right story to pair them with. Writing from personal experience amplifies your voice and credibility, and digging deep into the well of my own experience was one of the highlights throughout the month. One friend told me that reading my articles revealed a lot more about who I am as a person. I can’t think of a higher complement for anecdotes than that.</li></ul><blockquote>Narrative is the oldest and most compelling method of holding someone’s attention; everybody wants to be told a story. Always look for ways to convey your information in narrative form.</blockquote><p>Finding the mental energy and discipline to write after a full day of work was ultimately the biggest obstacle to writing daily. Most days, it was the last thing I wanted to do after dinner. But when I sat down at my computer and forced myself to just start typing, I quickly found myself in a flow state as the hours flew by.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Cjew4YHcLgwAG2TFtFiJGg.gif" /><figcaption>Gettin’ ready to write</figcaption></figure><p>I love writing. It’s a medium that complements how I think: methodical, linear, iterative. One of my favorite parts of being a product manager is producing a compelling document over many drafts that can lay out a clear picture of what we need to build. More than anything, I enjoy creating order from chaos.</p><p>Although I enjoyed publishing daily, <strong>two articles a month</strong> is a more sustainable and reasonable goal. I’m proud of what I wrote but I’d prefer to dive a couple layers deeper and add more polish. After all, putting time between your re-reads and relentlessly editing are two of a writer’s best tools.</p><p><em>For those who read this article or any others throughout January, I want to say thank you! I hope you enjoyed the journey as much as I did.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70ef320b15f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>