<?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 Charlotte Tao on Medium]]></title>
        <description><![CDATA[Stories by Charlotte Tao on Medium]]></description>
        <link>https://medium.com/@charlottetao?source=rss-5a658beec450------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ssCywxcFhRecP8GFPfHQ_w.png</url>
            <title>Stories by Charlotte Tao on Medium</title>
            <link>https://medium.com/@charlottetao?source=rss-5a658beec450------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:38:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@charlottetao/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[How ChatGPT is Quietly Rewiring Our Brains]]></title>
            <link>https://charlottetao.medium.com/how-chatgpt-is-quietly-rewiring-our-brains-71f31694f724?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/71f31694f724</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Thu, 26 Jun 2025 13:06:01 GMT</pubDate>
            <atom:updated>2025-06-26T13:06:01.757Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>How to Use Generative AI Tools While Staying Human</strong></h4><p>Since ChatGPT, one of the most widely used generative AI tools, came out in <a href="https://en.wikipedia.org/wiki/ChatGPT">2022</a>, I have noticed a subtle shift in my way of thinking. Whether I’m researching at work, learning about AI, planning a trip, or just catching up on news, my first move is almost always: “Let me ChatGPT it.” It’s like muscle memory now.</p><p>One day it hit me. Why did I even use ChatGPT for this? Was it really necessary? Why didn’t I try thinking on my own first?</p><p>That little moment got me wondering: As AI becomes my go-to for work and life, have I started over-relying on it? Turns out, I’m not alone. <a href="https://educationaltechnologyjournal.springeropen.com/articles/10.1186/s41239-024-00444-7">Studies</a> show that over-relying on AI and generative AI tools links to memory loss and procrastination. Sure, AI saves time and effort, at least on the surface. But it’s easy to lose track of just how much we are handling over to the machines.</p><p>So, I decided to run a little experiment on myself. For two weeks, before turning to ChatGPT, I made myself pause and ask: “<em>Do I really need ChatGPT for this? What would I be thinking if I had to do this myself?</em>”</p><p>Soon, some interesting patterns emerged. Honestly, a few of them made me uncomfortable. My way of thinking was changing, and I hadn’t even noticed.</p><h3>How AI tools like ChatGPT are shaping our minds</h3><h4><strong>From asking better questions… to not thinking at all</strong></h4><p>One of the biggest changes I found was that I started focusing more on how to ask the perfect question to ChatGPT, instead of actually thinking about solutions myself. I once spent 30 minutes polishing a question for AI tools like ChatGPT, but not even three minutes trying to future things out on my own.</p><p>Prompt engineering (the process of crafting the right question for generative AI) is a fun challenge, but let’s be honest: <strong>today’s AI doesn’t truly “think”.</strong> It’s just very good at generating what sounds right. The more I noticed this, the more I saw it creeping into my life. I started letting ChatGPT weigh in on what to eat, what to buy, and even big decisions like career moves. The more I delegated, the less I trusted my own instincts.</p><h4><strong>Trusting AI a little too much</strong></h4><p>Unfortunately, today’s generative AI still hallucinates. Even when it doesn’t, it’s trained to give answers you probably want to hear. Sometimes, that means AI may reinforce your own biases, especially on tricky topics like social issues and career moves. This is one of the subtle but real effects of AI on thinking and social perception.</p><p>And let’s be real: humans like those who flatter us, and AI is pretty good at that. The more we use it, the more we trust it, even when it gives less-than-ideal advice. I have noticed some people even start to prefer AI’s easy answers over their human friends’ honest opinions. But honesty, even when it’s hard to accept, is what we actually need as humans.</p><h4><strong>Fear for chaos</strong></h4><p>If you use ChatGPT a lot, you willl notice: every answer is well-structured, full of bullet points, headers, pros and cons, and step-by-step solutions. Over time, anything unstructured or a little chaotic can start to feel uncomfortable.</p><p>However, <strong>chaos is where real learning and real innovation happen</strong>. When life gets messy, that’s when we grow. AI makes everything look clean and simple, but sometimes that order is just a façade. Most of us remembered the life lessons we struggled with, not the ones where the answers were handed to us. It’s still true now. Knowledge sticks when you wrestle with it, not when it’s served on a silver platter.</p><h4><strong>You don’t know what you don’t know</strong></h4><p>We tend to believe that the answer AI gives us must be the best one, especially when we work hard to craft the “perfect” prompt. But AI is actually very prompt-sensitive. The depth of the answer depends almost entirely on the depth of your question. This is why human vs AI thinking remains so different. And this isn’t just about prompt engineering as a technical skill. It’s about your own thought process, your wisdom, and your self-awareness.</p><p>If you simply ask, “How do I find a good product manager job?” you will get a very shallow answer. But if you ask, “How can I get a PM job at Company Z because it’s the right time for me to gain experience in X, thanks to my skills in Y”, you will get a much more meaningful response.</p><p>That’s because you have already done some of the important thinking on your own. You have realized what you have, what you lack, and why that self-awareness matters in job hunting. That’s how AI tools can actually help you, instead of just filling in the blanks.</p><h3><strong>How to get your brain back</strong></h3><h4><strong>Use AI — a lot, but pay attention</strong></h4><p>Use AI — a lot. Even for things you don’t actually need help with, like what to eat or what to buy. It might sound counterintuitive, but the point is to really get to know what AI is good at and where it falls short. Don’t avoid it.</p><p>Then, notice when you would have done a better job on your own. Jot down those moments. Think of AI like your teammate: the best partnerships come when you know your own strengths and let AI fill in the gaps. After a while, you will get a better sense of when to trust yourself, and when it makes sense to lean on the machine.</p><p>On the flip side, <strong>pay attention to the times when AI surprises you with a better idea or a new perspective</strong>. Sure, AI knows more trivia than any one of us, but sometimes it will also spark thoughts you might never have had on your own. When that happens, ask yourself: Why didn’t I think of that? Is it because of a gap in my critical thinking, or just lack of experience? Use those moments to figure out how AI can best assist you, rather than just take over.</p><h4><strong>Break the AI pattern</strong></h4><p>Leverage AI for ideas, but don’t let AI define how you think. Generative AI, by nature, tends to organize everything into structured, step-by-step, linear responses. It’s easy to fall into that same linear way of thinking, even when you are not using AI. But real creativity often happens when you connect unexpected ideas, jump between topics, or let your mind wander beyond what seems logical on the surface.</p><p>So, challenge yourself to think differently. Don’t be afraid to take nonlinear paths or approach a problem from a completely new angle. Sometimes the most valuable insights come from the “messy” parts that AI would never suggest.</p><h4><strong>Learn AI basics</strong></h4><p>Take a little time to understand the basics of how AI models actually work. Even if you are not a tech person, it’s worth spending a few minutes on this. AI models aren’t gods, and they are definitely not omniscient. <strong>I firmly believe today’s generative AI won’t be the end game.</strong> Much better versions are on the horizon. But knowing the basics now will help you use AI wisely instead of worshipping it.</p><h4><strong>Gain more real-world experience</strong></h4><p>If you want to get really good at prompting, step away from the keyboard for a bit. Get more real-world experience. The richer your background, the sharper your questions, and the smarter your AI answers will sound. Strong real-world experience can sharpen your prompts and make your use of AI tools even more effective.</p><h4><strong>Stay human</strong></h4><p>Finally, don’t forget your human side. Go have real conversations. Build real relationships. We are not here just to get the fastest answes. We are here to actually live, love, and learn. I know someone who once asked ChatGPT for advice on negotiating her rent. AI gave her a very thorough answer. But in the end, she simply picked up the phone and talked honestly with her landlord, and they actually lowered the rate, no script required.</p><p>Sometimes, your own instincts and a genuine conversation work better than any AI-generated plan. Just like we learned to put our phones down sometimes, try giving yourself <strong>“AI-free” time</strong>. You will be fine without it for a bit, maybe even better.</p><h3><strong>Final thought</strong></h3><p>At the end of the day, AI is here to assist us, not to run the show. Don’t hand over the keys to your brain just yet. Ask questions, make mistakes, and enjoy figuring things out for yourself, even if it’s a little messy.</p><p>So go ahead, use AI to spark ideas and save time. But save some room for your own questions and your own struggles. That’s where the real learning happens.</p><figure><img alt="Are We Forgetting How to Think?" src="https://cdn-images-1.medium.com/max/1024/1*qmaMX2_XCY4XQd9-4VzQDg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71f31694f724" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Missing Skill in the Age of AI: Why Today’s Engineers Must Learn Sales]]></title>
            <link>https://charlottetao.medium.com/the-missing-skill-in-the-age-of-ai-why-todays-engineers-must-learn-sales-31683ee2c820?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/31683ee2c820</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 15:11:01 GMT</pubDate>
            <atom:updated>2025-02-04T15:11:01.417Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sales and Programming are More Similar Than You Think</h4><p>I used to think sales had nothing to do with me. As an engineer and product manager, my job was to build. I believed that if I created something great, people would naturally recognize its value. But after spending the last few years in startups, both as a technical founder and working closely with sales, I realized how wrong I was.</p><h3>The “Build First, Sell Later” Mindset</h3><p>Time and time again, I saw brilliant engineers build incredible solutions. They had the most advanced machine learning models, the sleekest platforms, and the cleanest codebases. Yet when I asked, “Do you have customers?” the answer was often, “Not yet.”</p><p>That’s when it clicked: Sales is just as important as building the product itself. No matter how powerful your technology is, if no one sees its value, it doesn’t matter. This realization forced me to shift my thinking. Instead of seeing sales as someone else’s job, I started seeing it as an essential skill for engineers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3g8TfS3-et9s1sZ2Q5ks0Q.png" /><figcaption>Sales and Programming are More Similar Than You Think</figcaption></figure><h3>Myths About Sales That Hold Engineers Back</h3><p>I used to see sales as something reserved for a different kind of person. But the more I engaged with sales, the more I realized I had been holding onto myths that actually limited my growth.</p><blockquote>1. “Sales Is Just for Extroverts”</blockquote><p>I used to believe that sales was all about being charismatic and persuasive, neither of which I considered my strengths. The idea of networking events, pitching to strangers, and initiating small talks felt exhausting.</p><p>Then I started actually selling. What I learned surprised me: sales isn’t about talking. It’s about listening.</p><p>The best salespeople aren’t the ones with the flashiest presentations. They are the ones who ask the right questions and pay attention to what customers actually need. In fact, introverts often make great salespeople because they naturally focus on deeper, more thoughtful conversations.</p><p>I once spoke with a skeptical enterprise customer who dismissed AI automation right away. “We’ve tried it before,” they said. “It didn’t work.” Instead of pushing back, I got curious. “Tell me more. What didn’t work?” That one question changed everything. They started sharing their frustrations and disappointments. Thirty minutes later, they weren’t just open to AI; they were asking how soon they could implement it.</p><blockquote>2. “Sales Is Manipulative”</blockquote><p>Many engineers distrust sales because they associate it with overpromising or tricking customers into buying something they don’t need. But real sales isn’t about manipulation. It’s about alignment.</p><p>A strong salesperson deeply understands the product and communicates its true value to the right customers. Rather than pushing customers, they work closely with customers to set realistic expectations.</p><p>Once I reframed sales as a process of helping customers make the right decisions, it no longer felt manipulative. Instead, it felt like an extension of what I already did as an engineer — solving real problems with the right solutions.</p><blockquote>3. “Sales is Hard to Learn”</blockquote><p>I used to think that sales was an art that required years of experience in negotiation and persuasion. But the more I did it, the more I realized that sales is a skill just like programming. It has lots of patterns that can be learned and practiced.</p><p>Here are some surprising parallels I found.</p><h4>a. Both Sales and Programming Require Systematic Problem-Solving</h4><p>When debugging a program, you don’t just try random fixes — you follow a structured approach: reproduce the issue, analyze logs, identify the root cause, test hypotheses, and refine your solution.</p><p>Sales follows a similar process. If a deal isn’t progressing, a good salesperson doesn’t just push harder; they analyze where the friction is, adjust their strategy, and test different approaches until they find what works.</p><h4>b. Sales Requires Multiple Paths to Success, Just Like How Engineers Handle System Failures</h4><p>In large-scale systems, engineers design redundancies and fallback mechanisms to ensure reliability. If one component fails, another can take over.</p><p>Similarly, in sales, a deal rarely depends on just one champion from the customer. To close a big contract, you need multiple internal champions (finance, tech, and other executive sponsors). If one sponsor drops out, the deal shouldn’t collapse. A great salesperson, like a great engineer, builds fault tolerance into their process.</p><h4>c. Sales Relies on Playbooks, Just Like Software Relies on Design Patterns</h4><p>Good software engineers follow design patterns that have been proven to work. Similarly, top sales follow structured playbooks to close deals efficiently.</p><p>Just like a reusable user authentication module speeds up development, a well-crafted objection-handling response helps sales teams navigate customer concerns. This structured approach makes sales processes repeatable and scalable.</p><h3>Why Tech People Need Sales Skills</h3><h4>1. Sales Validates Ideas Before You Build</h4><p>Talking to customers early prevents you from wasting time on features no one wants. Don’t try to guess what might be useful. Test your ideas in real conversations and prioritize what actually matters.</p><h4>2. Sales Makes You a Better Leader</h4><p>Whether you are pitching an idea to your team or influencing company direction, leadership is about selling ideas. The ability to communicate persuasively is one of the most valuable leadership skills you can develop.</p><h4>3. Sales Is Essential for Technical Founders</h4><p>Think sales is your sales manager’s job? If you are a founder, you are always selling — to customers, investors, and even your own team. No matter how strong your technical skills are, your ability to sell your vision will determine the success of your startup.</p><h4>4. Sales Keeps You Agile</h4><p>Customer feedback helps you iterate quickly and adapt to market changes and shifting customer needs. This ensures that what you are building remains valuable and relevant.</p><h3>How Engineers Can Develop Sales Skills</h3><h4>1. Start by Listening</h4><p>Sales begins with curiosity. Instead of jumping into explaining your product, ask potential customers, “What’s your biggest challenge?” Listen to their pain points before offering solutions.</p><h4>2. Tell Stories, Not Features</h4><p>Which would you remember more — a list of AI model specifications or a story about how it helped a company cut costs by 50%? Avoid just explaining what your product does. Focus on how it solved a real problem for someone.</p><h4>3. Shadow Sales Teams</h4><p>If your company has a sales team, spend time with them. Observe how they handle objections, negotiate, and close deals. Understanding their approach can help you learn what real sales is about.</p><h4>4. Practice and Iterate</h4><p>Like any skill, sales improves with practice. Have more conversations with stakeholders, potential customers, or even colleagues, and refine your approach based on their feedback.</p><h3>Final Thoughts</h3><p>If you are an engineer who thinks sales isn’t for you, I challenge you to reconsider. With AI already automating many coding tasks, engineers need to expand beyond just technical skills. Learning sales will help you sell your ideas, grow your influence, and future-proof your career. Start small. You will be surprised how much it changes the way you build — and the way you succeed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31683ee2c820" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your New Year’s Career Upgrade]]></title>
            <link>https://charlottetao.medium.com/your-new-years-career-upgrade-8a4eff6a0226?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a4eff6a0226</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Thu, 02 Jan 2025 19:17:58 GMT</pubDate>
            <atom:updated>2025-01-02T19:17:58.175Z</atom:updated>
            <content:encoded><![CDATA[<h3>Your New Year’s Career Upgrade: Build People, Not Just Products</h3><h4>Why Everyone Should Consider Becoming a People Manager</h4><p>For years, I focused on building great products. Whether it was delivering a high-performing system or leading innovative projects, I measured my success by what I created. But as I grew in my career, I realized something profound: products come and go, especially in the fast-changing age of generative AI. There is an endless list of technologies to learn and build, but the most enduring impact you can have is through the people you grow and inspire.</p><p>Transitioning from an individual contributor (IC) to a people manager wasn’t just a shift in my role; it was a transformation of purpose.<strong> It became clear that building people, not just products, was the ultimate career upgrade.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GwgW64wTNlDL6kDQBGKhvg.png" /><figcaption>Career Upgrade: From Individual Contributor to People Manager</figcaption></figure><h3>Why Fewer People Are Opting for Management (And Why That Needs to Change)</h3><p>I always ask my direct reports this question during their first week: “Do you want to take the IC route or the manager route?” I always hope to hear “manager,” but unsurprisingly, I get “IC” most of the time. The younger generation today no longer sees being a people manager as an attractive career path. But I hope you’ll give it another thought, especially as we enter a new year and reflect on meaningful resolutions.</p><p>It’s no secret: fewer professionals aspire to become managers today, particularly younger generations. Recent surveys consistently show low interest in management roles. (<a href="https://www.entrepreneur.com/leadership/young-workers-dont-want-to-become-managers-and-this/462273">Source</a>) While the reasons are understandable, this trend is troubling, not just for organizations but for individuals who may be limiting their own potential.</p><h3>IC vs Manager: Why IC Roles Are More Popular Today</h3><p>The IC route has never been more appealing. These roles now come with clear growth paths, such as Staff Engineer or Principal Designer, which offer strong earning potential and significant recognition. ICs get to stay deeply involved in technical work, avoiding what many see as the burdens of management, such as morale issues and office politics. For those who love their craft, the IC path feels like a way to focus on what they enjoy most.</p><p>But while IC roles may seem like the better choice, they have their limits. From my own experience, being an IC can only take you so far. Early in your career, it’s an excellent way to build expertise. Over time, though, you may find yourself hitting a glass ceiling — not necessarily in terms of salary, but in your ability to grow and make a lasting impact.</p><h3>Common Myths About People Management</h3><blockquote>“It’s just supervision.”</blockquote><p>People management is not about overseeing others. It’s about amplifying your impact by empowering a team. There’s only so much you can accomplish on your own. To grow your product and your business, you must have a team that you can guide toward shared goals. Even as a senior IC, you might design a brilliant system, but the success of that system often depends on having a manager to align the team’s efforts with larger organizational priorities.</p><blockquote>“It’s all about politics.”</blockquote><p>It’s true that office politics exist, but avoiding management won’t shield you from them. As you grow in your career, whether as an IC or a manager, you’ll encounter organizational dynamics. The difference is that managers are better positioned to influence and navigate these dynamics, using them to create opportunities for their teams. Learning to face politics directly is part of leadership, and strong managers do this effectively.</p><blockquote>“You lose sight of product building, which is the fun part.”</blockquote><p>While managers may not code or design as much as ICs, the best managers never lose their connection to the product. They shape its success by fostering collaboration, providing strategic direction, and ensuring the team’s work delivers value. Management isn’t about stepping away from the work you love. It’s about scaling your expertise and enabling others to excel.</p><blockquote>“The career ladder isn’t worth it.”</blockquote><p>The IC and management ladders may seem comparable at first glance, but management equips you with skills that can open doors you might not even realize exist. People skills and strategic thinking are highly transferable skills that set you apart for leadership roles, cross-functional opportunities, and entrepreneurship. Many successful entrepreneurs credit their management experience for preparing them to lead organizations and tackle complex challenges.</p><h3>Why Building People is the Ultimate Career Growth Strategy</h3><h4>1. Products Come and Go, But People Endure</h4><p>In today’s world, products and technologies can become obsolete in a matter of months. What you create today might not matter tomorrow. The people you mentor, though, carry your influence far beyond the lifespan of any product. When you invest in others, the impact ripples through their lives and careers, shaping the teams they lead and the ideas they bring to life.</p><h4>2. You Grow as a Person, Not Just an Employee</h4><p>IC roles focus on technical expertise, but management challenges you to grow emotionally, socially, and intellectually. Leadership forces you to develop empathy, self-awareness, and resilience — qualities that make you a better professional and a more fulfilled person. Growth isn’t just about skills; it’s about becoming someone who inspires and uplifts others.</p><h4>3. Build Deep Connections That Truly Matter</h4><p><strong>At the end of your career, you’re unlikely to remember every product you shipped, but you’ll always remember the people whose lives you impacted. </strong>Building relationships through mentorship and leadership gives you purpose and fulfillment that no deliverable can match.</p><h4>4. Create a Legacy</h4><p>ICs are remembered for the products they build. Managers are remembered for the people they grow. Mentoring and developing others creates a legacy that lives on through their successes. Watching a former mentee thrive is one of the most rewarding aspects of leadership.</p><h4>5. Prepare for Bigger Opportunities</h4><p>Management equips you with critical skills for future roles like executive leadership or entrepreneurship. By aligning team goals with broader priorities and mastering people leadership, you prepare yourself for roles that demand strategic vision and cross-functional influence.</p><h3>How to Transition from IC Into People Management</h3><h4>Start Small</h4><p>Take on leadership-like responsibilities, such as mentoring a junior colleague, leading a project, or organizing a team initiative. These experiences give you a feel for guiding others without the full responsibility of managing a team.</p><h4>Seek Support and Training</h4><p>Leadership is a skill, not something you’re born with. Look for training programs or workshops that can help you develop the tools you’ll need. Shadowing an experienced manager or seeking feedback from mentors can also accelerate your growth.</p><h4>Shift Your Mindset</h4><p>Management isn’t about stepping away from the work you love. It’s about helping others thrive. Success as a manager is measured by your team’s achievements, not just your own.</p><h4>Embrace Mistakes</h4><p>No one is a perfect manager on day one. Mistakes are part of the journey and provide valuable learning opportunities. Take time to reflect and recharge if needed. Leadership is a marathon, not a sprint.</p><h3>Build People, Not Just Products</h3><p>This New Year, challenge yourself to think beyond deliverables. Build teams, mentor others, and create a culture where people can thrive. By investing in people, you’ll amplify your impact, grow as a person, and leave a legacy that lasts far longer than any product you build.</p><p>If you enjoyed this blog post and found it valuable, I’d be incredibly grateful if you <strong>shared it within your network</strong>. It will only take you a few seconds, but it will mean the absolute world to me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a4eff6a0226" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surprisingly Wrong Ways to Motivate Your Team]]></title>
            <link>https://charlottetao.medium.com/surprisingly-wrong-ways-to-motivate-your-team-82f9deef999e?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/82f9deef999e</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Wed, 23 Oct 2024 12:27:42 GMT</pubDate>
            <atom:updated>2024-12-31T13:12:10.404Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>What Great Leaders Do to Recognize Their Employees</strong></h4><p>Managers often assume that giving plenty of praise is always beneficial for employee motivation. However, there are many ways this can go wrong, and your employees may not receive your praise as intended. To improve employee performance and team productivity, it’s important to <strong>tailor your praise</strong> based on the unique needs of each individual. Let’s explore some common mistakes managers make with recognition and how to avoid them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*P6jLK9cw7k3wno4_UT6S-g.gif" /></figure><h3><strong>Recognition without criticism</strong></h3><p>It may sound counterintuitive, but some employees aren’t looking for endless praise. Instead, they always prefer constructive feedback. They aren’t focused on protecting their ego; they want to grow. Even when their performance is top-tier, you still need to put in the effort to offer thoughtful, constructive feedback. If you skip that step, employees might feel you’re not paying close attention to their work — or worse, that you’re not skilled enough to coach them.</p><h4><strong>Bad examples:</strong></h4><blockquote>“Your analysis is perfect. No changes needed.”</blockquote><blockquote>“You’re the ideal person for this presentation. No need to prep.”</blockquote><h4><strong>Good examples:</strong></h4><blockquote>“Your analysis is already very thoughtful. One thing to consider would be how you can turn this into a repeatable process so future analyses can be done quicker and easier.”</blockquote><blockquote>“Your presentation is great as is. To take it a step further, I’d recommend adding a section for non-technical stakeholders to make it even more accessible.”</blockquote><h3><strong>Not recognizing the larger impact</strong></h3><p>Sometimes, managers get so caught up in the details that they forget to highlight how an employee’s work contributes to the broader company goals. Try to avoid surface-level praise like presentation skills without connecting it to the bigger picture. Employees want to know that their efforts are moving the needle, not just checking boxes.</p><h4>Bad examples:</h4><blockquote>“Your slides looked really professional.”</blockquote><blockquote>“You fixed the bug so quickly.”</blockquote><h4>Good examples:</h4><blockquote>“Your presentation really helped the leadership team make an informed business decision.”</blockquote><blockquote>“The way you identified the bug was really efficient. It should become a method for other teams to adopt.”</blockquote><h3><strong>Extravagant recognition</strong></h3><p>Exaggerated praise might seem like an easy way to motivate someone, but it often comes across as insincere, especially to more experienced employees. Statements like “You built the best software in the world!” may sound enthusiastic, but they risk either inflating egos or making the employee doubt the authenticity of the praise. Genuine, specific recognition is always far more impactful.</p><h4>Bad examples:</h4><blockquote>“You are a true genius!”</blockquote><blockquote>“You built the best software in the world!”</blockquote><h4>Good examples:</h4><blockquote>“Your contribution was crucial to winning this project, especially with your attention to detail and timely delivery.”</blockquote><blockquote>“The solution you developed was highly effective and addressed a major client need. Your hard work made a significant impact.”</blockquote><h3><strong>Overusing comparisons</strong></h3><p>Some employees thrive on competition, especially in environments like sales teams, but overusing comparisons in praise can do more harm than good. Saying things like “You did much better than [another employee]” may boost motivation temporarily, but it can lead to unhealthy rivalries. It may also make the praised employee feel uncomfortable knowing their success is being compared to someone else’s shortcomings. Instead, focus on how they can help the rest of the team to improve.</p><h4>Bad examples:</h4><blockquote>“I’m glad I had you work on this instead of [Employee B]. I can always count on you to deliver!”</blockquote><blockquote>“You are much better than [Employee B] at this.”</blockquote><h4>Good examples:</h4><blockquote>“Your expertise really helped. Make sure to help the rest of the team to get similar result.”</blockquote><blockquote>“I’m glad you were the first one on the team to deliver results. This sets a good example for the rest of the team.”</blockquote><h3><strong>Wrong setting</strong></h3><p>Not all employees enjoy being praised in public. For some, receiving recognition in front of others can be uncomfortable or even embarrassing. It’s a good idea to give them a heads-up if you plan to praise them publicly. On the flip side, some employees thrive on public acknowledgment — being recognized in front of the company can be sometimes more motivating for them than a raise. Understanding these differences is key to delivering praise in a way that resonates.</p><h4>Bad examples:</h4><blockquote>(In front of a group) “We had such a success all because of [your name]!”</blockquote><blockquote>“Let’s all give [Employee’s Name] a round of applause for carrying this project to success!”</blockquote><h4>Good examples:</h4><blockquote>(In front of a group) “It’s clear that your guidance brought everyone together, and I want to make sure we all recognize that.”</blockquote><blockquote>(Privately) “Your contribution was key to the project’s success. I want to personally thank you for going above and beyond.”</blockquote><h3><strong>Praising personal traits instead of effort</strong></h3><p>Praising personal traits like intelligence may sound like a good idea, but it doesn’t necessarily encourage growth or improved performance. Compliments like “You’re so smart” can feel superficial, and they don’t acknowledge the hard work or effort an employee put into the task. Instead, focus on recognizing the actions and strategies they used to achieve success. This promotes a growth mindset and motivates them to continue improving.</p><h4>Bad examples:</h4><blockquote>“You’re so smart, no wonder you solved that problem.”</blockquote><blockquote>“You’re naturally talented, that’s why everything you do turns out great.”</blockquote><h4>Good examples:</h4><blockquote>“Your hard work and attention to detail really paid off.”</blockquote><blockquote>“The effort and creative approach you took made a big difference.”</blockquote><h3><strong>Praising for things that are expected</strong></h3><p>Avoid praising employees for merely doing what is expected of them. For example, don’t just thank someone for showing up on time or completing routine tasks. Employees want to be recognized for going above and beyond, not for doing the bare minimum. Acknowledging their contributions at a deeper level is what makes praise meaningful.</p><h4><strong>Bad examples:</strong></h4><blockquote>“You always get work done on time.”</blockquote><blockquote>“You are never late to our morning meetings.”</blockquote><h4><strong>Good examples:</strong></h4><blockquote>“Your commitment is always appreciated, especially when we’re on tight deadlines.”</blockquote><blockquote>“I really like how you consistently keep our meetings organized and manage time so effectively.”</blockquote><p>Ultimately, praise is about more than just boosting morale — it’s about creating lasting motivation for individual team members. When you take the time to offer meaningful recognition, you show employees that their work is truly valued. So, take some time to reflect on your recent praise strategies. The key is knowing when and how to deliver praise in a way that resonates with them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82f9deef999e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 Ways to Fail a Startup]]></title>
            <link>https://charlottetao.medium.com/100-ways-to-fail-a-startup-the-hidden-pitfalls-for-founders-and-entrepreneurs-efb244aadeea?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/efb244aadeea</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Fri, 13 Sep 2024 18:41:30 GMT</pubDate>
            <atom:updated>2024-12-31T13:13:02.385Z</atom:updated>
            <content:encoded><![CDATA[<h3>100 Ways to Fail a Startup — the Hidden Pitfalls for Founders and Entrepreneurs</h3><h4>The Hidden Reasons Why Startups Fail and How to Avoid Common Mistakes</h4><p>We’re all familiar with the classic reasons why startups fail: lack of funding, bad business ideas, and the like. But the truth is, <strong>most startups collapse for less obvious reasons.</strong></p><p>Sure, failure is a subjective term, and it’s tempting to pin it on one clear issue without diving deeper. In my opinion, though, the real insights lie beneath the surface. The real reasons behind startup failure are far more valuable than the convenient excuses.</p><p>After four years as a startup founder and countless chats with fellow entrepreneurs, I’ve compiled a list of 100 real reasons startups fail. Take these with a pinch of salt (and a dash of sarcasm) — these are biased by my own understanding, but I hope they spark some ideas to help improve your startup’s odds of success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibbNO5PN4yKhY6qV1N-JQA.png" /><figcaption>100 Reasons Why Startups Fail</figcaption></figure><h3>I. Fundraising problems</h3><h4>1. Bad macro-environment</h4><p>Timing is everything. When the economy tanks, investors and customers alike get cold feet. It’s not your fault, but it sure doesn’t help.</p><h4>2. Rejecting a VC because they didn’t love your favorite product feature</h4><p>Look, finding an investor you like is important, but don’t be too picky when you do need to raise quickly. Being overly idealistic about your product can lead you to reject perfectly good money. Better to have one investor than none at all.</p><h4>3. Bad mood</h4><p>Do not show up in a pitch looking like you just got dumped because another investor just rejected you. Investors can sense your mood, and suddenly, your startup seems less like the next big thing — even when it is.</p><h4>4. Going radio silent on investors</h4><p>Even if an investor seemed disinterested after your initial pitch, keep in touch. You never know when they might circle back.</p><h4>5. Unprepared pitches</h4><p>First impressions matter. If you don’t have enough time to properly prepare, delay the pitch. Rushing through it will only make you look sloppy.</p><h4>6. Typos in your pitch deck</h4><p>Tiny typos may not seem like a big deal, but for some investors, they scream “lack of attention to detail.” Always double-check before you hit “send.”</p><h4>7. Skipping investor events</h4><p>Investor-organized social events may seem like fluff, but they’re actually golden opportunities. Investors like to see your commitment — and they might introduce you to others in their network.</p><h4>8. Overvaluation</h4><p>Getting overvalued early on is like being the high school superstar — great until the real world catches up. When you can’t justify your expectations in the next round, your business may take a nosedive.</p><h4>9. Aiming too high</h4><p>Never ask for a mountain of cash when a hill will do. Bridge rounds exist for a reason — don’t go broke waiting for the perfect deal.</p><h4>10. Aiming too low</h4><p>On the flip side, asking for too little seems easy at first, but you’ll be back at the table raising money again before you know it. And that’s exhausting.</p><h4>11. No clear milestones</h4><p>You should be able to point to specific goals with the money you raise. If you can’t show consistent customer acquisition or revenue growth, investors won’t know what they’re really funding.</p><h4>12. Too many features</h4><p>More product features may delight your users, but they can confuse investors. If they can’t figure out your core focus, they’ll hesitate to invest.</p><h4>13. Complex legal terms</h4><p>If you’re early-stage, keep your terms simple and flexible. Too much legalese will scare investors away. Some only accept SAFE agreements, so make it easy for them to say yes.</p><h4>14. Signing unfair terms</h4><p>Flexibility is important, but do not allow bad terms which can lead to disastrous consequences — including losing control of your company. Hire a good lawyer to work with you.</p><h4>15. Inexperienced lead investor</h4><p>A first-time investor might sound exciting, but if they lack the resources or connections to support you when things get tough (or when you’re ready for the next round), it could hurt more than help. Aim for a seasoned lead investor if possible.</p><h4>16. Not aligning with key customers in advance</h4><p>Investors often want to hear from your top customers. Make sure you’ve got a few loyal supporters lined up, ready to provide strong references.</p><h3>II. Strategy problems</h3><h4>17. Ignoring partnerships</h4><p>Thinking your team can do it all alone? Think again. Often, it’s easier and more effective to partner with the right companies than to build an internal team from scratch. Be open to collaborations.</p><h4>18. Single customer dependence</h4><p>Relying too much on one key customer or niche market is risky without a backup plan. Diversify your customers to ensure stability. After celebrating that big customer win, immediately focus on landing the next one.</p><h4>19. Declining a promising acquisition</h4><p>Sometimes the smartest move is to sell and leverage bigger resources to bring your vision to life. Selling your company isn’t necessarily a failure — it can be a great way to continue your product’s journey and ensure your team thrives, as long as the acquiring company shares the right vision.</p><h4>20. Uncommunicated pivot</h4><p>Pivoting without telling your investors/board because you’re afraid they might disapprove? That’s a recipe for broken trust. Transparency is key — keeping your stakeholders informed keeps them on your side.</p><h4>21. Fear of negotiation</h4><p>Feeling awkward about negotiating with investors or partners? Don’t. Negotiating can save your business a significant amount of money.</p><h4>22. Overlooking big tech</h4><p>Do not just focus on competitors of your size and assume the big tech companies will never copy your idea. The moment they do, your startup could be in trouble. Try to get market intelligence from big tech if possible.</p><h4>23. Expensive vendors</h4><p>Avoid signing too many costly vendor contracts. Avoid large upfront payments. Review your budget weekly, and cut those low-value vendors immediately.</p><h4>24. Wrong forecasts</h4><p>Overestimating or underestimating revenue can lead to poor hiring and fundraising decisions. Avoid simplistic forecasting; consider as many risk factors as possible for a more accurate picture.</p><h4>25. Supply chain costs</h4><p>If your supply chain is getting more expensive, don’t ignore it. Regularly review and optimize your supply chain to control costs — never assume it will just work itself out.</p><h4>26. Overlooking big tech</h4><p>Do not just focus on competitors of your size and assume the big tech companies will never bother to copy your idea. The moment they do, your startup could be in trouble. Try to get market intelligence from big tech if possible.</p><h4>27. Greedy pricing</h4><p>Do not price your product too high out of the gate, hoping to cash in quickly. Trust and value come first; you can always raise prices later to new customers once you’ve proven yourself.</p><h4>28. Complex pricing structure</h4><p>A complicated pricing model can confuse potential customers. Keep it simple — clear pricing makes decisions easier. You don’t need five pricing tiers when you only have ten customers.</p><h4>29. Over-expanding geographically</h4><p>Opening offices in other countries just for the sake of calling yourself a global company is a costly move, especially from a legal and HR perspective.</p><h4>30. Declining a promising acquisition</h4><p>Sometimes the smartest move is to sell and leverage bigger resources to bring your vision to life. Selling your company isn’t necessarily a failure — it can be a great way to continue your product’s journey and ensure your team thrives, as long as the acquiring company shares the right vision.</p><h3>III. Engineering problems</h3><h4>31. Tech debt</h4><p>Technical debt can quickly snowball into a serious problem. Address them early before they become blockers.</p><h4>32. Treating your product as an R&amp;D project</h4><p>Transitioning from R&amp;D to a production-level product can be tricky, especially for high-tech products. Sometimes it even requires a complete reorganization of your engineering team to make it work.</p><h4>33. Over-relying on contractors</h4><p>Relying solely on low-cost contractors without an in-house engineering lead compromises quality and consistency. You need someone with a strong technical background to guide development and maintain standards.</p><h4>34. Patent oversights</h4><p>Do not ignore patents just to save some cost. Protecting your intellectual property not only gives you a competitive edge but can also increase your value in the event of an acquisition.</p><h4>35. Security holes</h4><p>Getting hacked due to poor security practices can be detrimental, especially when customer data is involved. Prioritize data security from day one.</p><h4>36. No security compliance</h4><p>Related to the above, achieving security certifications like ISO 27001 or SOC2 early on shows customers and partners that you take security seriously. It’s a must for building trust.</p><h4>37. Skipping QA</h4><p>Rushing through or skipping QA can lead to critical bugs that frustrate your best customers. Speed is important, but quality assurance is non-negotiable.</p><h4>38. Lack of user behavior monitoring</h4><p>Without proper analytics to track user behavior, you risk app abuse and other issues. Implement monitoring tools from the beginning to prevent misuse and improve user experience.</p><h4>39. Perfectionism</h4><p>Delaying a launch in the pursuit of perfection can hurt more than help. Sometimes, “good enough” is better than perfect — especially when speed to market is key.</p><h4>40. Overspending on AI</h4><p>Avoid creating fancy automation or AI systems when they aren’t necessary, or when the cost of implementation far outweighs the benefits. If simple rule-based systems can do, you won’t have to use Large Language Models.</p><h4>41. Automating too early</h4><p>Related to the point above, trying to automate every aspect of your business too soon can waste time and money. Some processes require human oversight, most likely that’d be YOU.</p><h4>42. Poor version control practices</h4><p>Without proper processes, you risk code conflicts, lost progress, and a chaotic development cycle. Invest time on creating a healthy workflow with your engineering team.</p><h3>IV. Sales and marketing problems</h3><h4>43. Not dressing properly for client meetings</h4><p>In client-facing roles, presentation matters. Show up looking professional and prepared — it’s not just about what technology you’ve built, but how you present yourself.</p><h4>44. Not following up with customers enough</h4><p>Just like with investors, persistence is key. Don’t give up on potential customers after one meeting — enterprise sales require long-term nurturing and patience.</p><h4>45. Avoiding casual meetings with key customers</h4><p>First-time founders, especially those from engineering backgrounds, often avoid informal chats or parties. Don’t let your introversion keep you from building relationships and selling your product.</p><h4>46. Not researching all stakeholders</h4><p>In enterprise sales, it’s not enough to just check out LinkedIn profiles. You need to understand the positions, goals, and requirements of all stakeholders involved in the decision-making process.</p><h4>47. Involvement in customer company’s politics</h4><p>Getting involved in internal politics at your customer’s company can backfire. Stay neutral and focused on your product — avoid stepping on toes to maintain strong relationships.</p><h4>48. Over-reliance on a single customer contact</h4><p>Relying too much on one internal champion at a customer’s company is risky. If they leave, you’re left scrambling. Develop relationships with multiple contacts at one target company to ensure long-term success.</p><h4>49. Ignoring customer retention</h4><p>Focusing solely on acquiring new customers while neglecting existing ones is a mistake. Retention is often cheaper and more profitable than chasing new leads.</p><h4>50. Fluff marketing</h4><p>Hiring a marketing team who fills the air with fluff but delivers no substance is a waste of time and resources. Your marketing efforts need to be results-driven, not just about sounding good.</p><h4>51. Stayed in stealth too long</h4><p>Keeping your startup in stealth mode for too long can hurt you. Early engagement with your audience helps build anticipation and loyalty. Though timing is important, don’t wait until it’s too late.</p><h4>52. Overspending on ads</h4><p>Do not accidentally blow $100k on Google Ads simply because you like a particular keyword. Effective ad spending requires expert planning and constant monitoring to ensure a strong ROI.</p><h4>53. Misleading brand name</h4><p>Choosing a brand name that doesn’t clearly communicate what your product does is a missed opportunity. Clarity is essential for attracting the right audience.</p><h4>54. Ignoring public perception</h4><p>When you see a negative comment online about your product, respond immediately. Regardless of whether the comment is fair or not, try your best to rebuild trust with your customers.</p><h4>55. Bad launch</h4><p>Do not launch your product online just to attract investors when your target audience is actually offline. A strategic launch matters. Don’t rush it for appearances.</p><h4>56. Overspending on SEO</h4><p>Avoid pouring too much money into SEO. While important, SEO should be part of a balanced strategy that includes other marketing efforts for holistic growth.</p><h4>57. Frequent rebranding</h4><p>Rebranding too often confuses customers and investors alike. Consistency builds recognition and trust — don’t keep changing your identity.</p><h4>58. Ignoring influencer marketing</h4><p>Your product could be a good fit for influencer marketing. Influencers can help expand your reach and build credibility faster than traditional channels.</p><h4>59. Inconsistent messaging</h4><p>Sending mixed signals about your products will confuse your customers. Keep your messaging clear and consistent to build trust with both customers and partners.</p><h4>60. Poor social media strategy</h4><p>Do not give admin access of your social accounts to junior marketers. Not everyone has the social media magic of Elon Musk. Hire experts to manage it effectively.</p><h4>61. Not investing in a good homepage</h4><p>Your homepage is often the first impression customers have of your business. Do not create one using a generic template just to save money.</p><h4>62. Exclusivity overuse</h4><p>How often times do you see “sign up for the next available spot” on startup’s websites? While exclusivity can create buzz, overdoing it may limit your market reach and slow user adoption, especially for consumer-facing products.</p><h3>V. Idea problems</h3><h4>63. Bad timing</h4><p>Starting too early or too late can be fatal. For example, launching an AI company ten years ago might have been premature, while in 2023, the AI hype was at its peak. You don’t want to be late to the game, but you also don’t want to be too far ahead that users and investors aren’t ready for your tech.</p><h4>64. Loose lips</h4><p>Be careful not to spill details of your next big idea to a competitor who can move faster than you. While sharing is generally a good practice, be mindful of what — and how much — you disclose. Broad strokes are fine, just don’t give away the whole playbook.</p><h4>65. Product distraction</h4><p>Chasing multiple ideas without a solid reason can spread your resources too thin and undermine your main product.</p><h4>66. Pandemic impact</h4><p>The COVID-19 pandemic may be over, but its aftershocks linger. Products tied to physical activities, like office space rentals, may not be as viable as they once were. External disruptions can happen overnight, so flexibility and contingency planning are crucial.</p><h4>67. Missed tech trends</h4><p>Failing to recognize and adapt to emerging technologies, like large language models, can mean missing the window of opportunity. Even though your product may not need the new tech, your customers may want it.</p><h4>68. Overestimating market size</h4><p>It’s tempting to throw out big numbers like a $1B TAM (Total Addressable Market) and a $10M SOM (Serviceable Obtainable Market), but without solid research to back it up, these figures are just fluff. Especially with experienced VCs, be sure your analysis is grounded in reality.</p><h4>69. Weak competitive analysis</h4><p>When investors ask, “Why isn’t your competitor already doing this?” you need a sharp answer. Don’t rely solely on Google searches. Use your network to gather deeper insights and understand the competitive landscape.</p><h4>70. Skipping the MVP</h4><p>Never launch a full product without going through the MVP phase just because you are in a rush. Production-level apps require high development costs and are hard to iterate on. An MVP allows you to test, learn, and refine before going all in.​</p><h3>VI. Culture problems</h3><h4>71. Lack of diversity</h4><p>Diversity isn’t just for big tech companies; it reflects your team’s mentality and influences how you’re perceived by customers, partners, future hires, and investors.</p><h4>72. Poor work-life balance</h4><p>Startup life often means long hours, but pushing your team too hard can lead to burnout and turnover. Set high standards, but don’t expect your employees to work the way you do.</p><h4>73. Ignoring employee feedback</h4><p>Do not dismiss feedback because you believe the focus should solely be on building the product. Ignored employees can create a toxic culture and lead to high turnover. Listen and act when needed.</p><h4>74. Pushing a “Kool-Aid” mentality</h4><p>Building a strong company culture is important, but don’t overdo it. Employees have practical concerns like compensation. Don’t simply tell them to stay happy with a low pay.</p><h4>75. Failure to celebrate successes</h4><p>While giving pay raises might not always be possible, recognizing and celebrating achievements is essential. Without it, your best talent will look for appreciation elsewhere.</p><h4>76. Overspending on company events</h4><p>While celebrating milestones is important, going overboard on company offsite events can strain your finances.</p><h4>77. Lavish employee benefits</h4><p>Offering overly generous perks may attract talent but can quickly become financially unsustainable. Balance is key — focus on benefits that motivate without breaking the bank.</p><h4>78. Overspending on office space</h4><p>Spending millions on a fancy office may boost your ego, but it won’t guarantee business success. Invest wisely in critical areas that drive growth rather than spending on aesthetics.</p><h4>79. Not defining company culture</h4><p>Founders must take the time to establish core cultural values, even if it feels cliché. A well-defined culture serves as a guiding framework for daily decision-making and helps in screening job candidates to ensure they align with your company’s ethos.</p><h3>VII. People problems</h3><h4>80. Never looking for a cofounder</h4><p>Do not get overly confident in your own expertise and not bringing on cofounders or senior hires. You need to learn to trust others and work collaboratively to succeed.</p><h4>81. Only hiring personal connections</h4><p>Hiring a cofounder just because they’re your close friend or family member may lead to a situation where it’s impossible to fire them, even when it’s clear they’re not a good fit.</p><h4>82. Overhiring</h4><p>Make sure you have a clear need before expanding the team. Hiring too quickly to handle anticipated work can easily lead to overstaffing. Instead, focus on addressing burnout in your current team.</p><h4>83. Hiring too many juniors</h4><p>Are you filling your team with too many junior employees because they’re cheap or less challenging to work? You’ll spend all your time mentoring instead of focusing on more strategic, valuable work.</p><h4>84. Hiring too many seniors</h4><p>On the flip side, hiring too many senior people can lead to slow decision making and overspending on salaries.</p><h4>85. Employee conflicts</h4><p>When two of your top employees clash and both leave because you failed to step in, that’s a sign of poor conflict resolution. Managing team dynamics is crucial for maintaining a stable, productive environment.</p><h4>86. Too hands-off with senior hires</h4><p>Even senior team members need direction and support. Being too hands-off can lead to a lack of alignment and integration into the company culture, so don’t assume they can handle everything on their own.</p><h4>87. Lack of talent pool</h4><p>Not developing a strong talent pipeline can hurt you when key employees leave. Always keep a list of potential candidates to avoid long gaps in critical positions.</p><h4>88. Firing without care</h4><p>Firing employees without considering the consequences can lead to legal trouble. Handle terminations with respect, empathy, and legal safeguards in place.</p><h4>89. Poor ethics evaluation</h4><p>Failing to vet employees for ethical behavior can lead to disasters like data theft. Always run basic background checks and reference checks, especially for the senior hires.</p><h4>90. Lack of in-person time for remote teams</h4><p>While flying in the entire remote team for in-person meetings can be costly, it’s essential for building stronger connections, especially with your top employees.</p><h4>91. Tolerating low performers</h4><p>Holding on to underperforming employees for too long can drag down team productivity and morale. Letting them go sooner can create space for stronger contributors and a more motivated team.</p><h4>92. Leadership politics</h4><p>Senior leaders playing politics with the board to push you out as CEO isn’t just something from the news — it happens more often than you’d think. Stay vigilant and protect your role as a founder.</p><h3>VIII. Personal reasons</h3><h4>93. Not enough personal savings</h4><p>If you’ve only got $100 in your savings account, now might not be the best time to dive into entrepreneurship. Without a financial cushion, you may find yourself chasing short-term gains instead of focusing on building a sustainable, scalable business.</p><h4>94. Pressure from family</h4><p>This ties into the previous point. It’s crucial to help your family understand your long-term vision. Many founders feel pressured by loved ones to make quick money, which can lead to compromising on the big picture.</p><h4>95. Unsupportive friends</h4><p>Surrounding yourself with pessimists can kill your motivation. If your best friends don’t support your vision, it’s easy to second-guess yourself. Build a circle that lifts you up, not one that drags you down.​</p><h4>96. Neglecting health</h4><p>Ignoring your physical and mental well-being can easily lead to burnout. A healthy founder is a productive founder, so don’t wait until it’s too late. Go for that run, eat something other than hot dogs, and get a good night’s sleep — even if tomorrow’s pitch feels like the most important one of your life.</p><h4>97. Over-networking</h4><p>Networking is important, but if you’re attending conferences and meetups every day without actually building your product, you’re just collecting business cards. Without something tangible to back up those connections, they’ll quickly lose value. Your team also needs your presence and leadership.</p><h4>98. Underpaying yourself</h4><p>Paying yourself so little that you’re forced to work on side gigs just to make ends meet can also be a recipe for disaster. While frugality is a virtue, your time is your most valuable asset. Discuss with your board on a reasonable pay for yourself.</p><h4>99. Missed meetings</h4><p>Forgetting critical board meetings because of burnout or disorganization is a big red flag. Start grooming your calendar daily and build solid organizational habits.</p><h4>100. Unethical behavior</h4><p>Some founders inflate revenue or stretch the truth to attract investors, but these tactics almost always backfire. Success built on dishonesty is never sustainable.</p><p>There you have it — 100 reasons why startups fail. In reality, many startups fail without one clear reason. It’s often a mix of multiple factors, leading to a slow decline that founders don’t recognize until it’s too late. Understanding these challenges highlights just how tough the startup journey is. Respect to all the founders out there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efb244aadeea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Transition from Traditional Machine Learning to Generative AI — Riding the New AI Wave]]></title>
            <link>https://charlottetao.medium.com/how-to-transition-from-traditional-machine-learning-to-generative-ai-riding-the-new-ai-wave-65e49c41a6ed?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/65e49c41a6ed</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Wed, 26 Jun 2024 00:16:34 GMT</pubDate>
            <atom:updated>2024-12-31T13:13:45.196Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Transition from Traditional Machine Learning to Generative AI — Riding the New AI Wave</h3><h4>How to Transition Your Career to Gen AI</h4><p>Generative AI is undoubtedly emerging as the most exciting field for machine learning (ML) talent. Many engineers who previously worked on traditional ML projects are now considering a move to generative AI.</p><p>The market signals are loud and clear: Apple recently announced a <a href="https://www.npr.org/2024/06/10/nx-s1-4999051/apple-artificial-intelligence-partnership-openai-chatgpt-siri-iphone">strategic partnership with OpenAI</a> to integrate generative AI features into Apple products, just three months after <a href="https://www.theverge.com/2024/2/27/24084907/apple-electric-car-project-titan-shuts-down">shutting down their entire self-driving car project</a>. This shift highlights the growing potential of generative AI over traditional ML, at least at the business level.</p><p>Self-driving cars have long been the prime showcase for AI from a traditional ML perspective, as they use the most advanced computer vision and path planning techniques. While it is disappointing to see Apple giving up on self-driving, it serves as a good reminder for traditional ML engineers to prepare for the new era of generative AI.</p><h3><strong>What can we learn from the self-driving car revolution?</strong></h3><p>Prior to working on LLM products at my startup, I dedicated seven years to the self-driving car space. I’m always surprised to see how each tech revolution unexpectedly mirrors its predecessors. The hype around self-driving began around 2014. Back then, most talent in the self-driving car industry had no prior experience in autonomous driving or building cars. Self-driving startups had to draw talent from traditional software or hardware industries, such as mapping, gaming, and mechanical engineering. Despite this, people managed to learn and build self-driving cars together as a team.</p><p>Today, we see the hype around generative AI. Similarly, most talent in this space has no prior experience in generative AI or large language models (LLMs). Some may have knowledge of traditional natural language processing (NLP) or ML in general, but LLMs are quite different. Startups are again drawing talent from related industries, such as software development, data science, and infrastructure.</p><p>The key here is that generative AI, just like self-driving cars ten years ago, is a highly cross-disciplinary field and attracts talent from many existing industries. It’s important to understand the nuances involved and see how your existing experience can be leveraged in generative AI.</p><h3><strong>How do traditional ML skills translate Into generative AI?</strong></h3><p>While generative AI requires new ML skills, the foundational skills in traditional ML roles remain highly valuable. Here’s why:</p><h4>Math is the king</h4><p>In the wave of new AI breakthroughs, the importance of fundamental math often gets overlooked. Both traditional ML and generative AI require a strong foundation in linear algebra, calculus, and statistics. These mathematical principles are crucial for understanding complex AI concepts, such as transformers and the attention mechanisms. Without a solid math background, it would be difficult to master any forms of machine learning. The stronger your math skills, the more intuitive you will find working with machine learning models. (Read more <a href="https://medium.com/geekculture/why-you-need-math-for-machine-learning-d9aca2437ee8">here</a>.)</p><h4>Back to basics with model training and evaluation</h4><p>The core principles of training models and evaluating model performance are universal across ML domains. Although generative models come with new nuances, the fundamental principles still apply. For example, traditional ML involves metrics such as precision, recall, and F1-score, while generative AI frequently uses BLEU scores for language generation and inception scores for image generation. Regardless of the type of metrics, ML engineers should learn to strike a balance between metrics and model performance.</p><h4>Data quality is still a prerequisite</h4><p>High-quality training data is essential, regardless of what types of AI you work on. Traditional ML typically deals with structured data and tasks like feature engineering, normalization, data labeling, and handling missing values. Generative AI, on the other hand, involves handling vast amounts of unstructured text data, with tasks like text cleaning, tokenization, and ensuring data diversity and quality. Despite the differences, both fields require strong data handling skills.</p><h3><strong>How to transition to Generative AI</strong></h3><p>Transitioning to generative AI may seem daunting, but I’d recommend starting early because the field of generative AI is evolving faster than before. Here’s how you can start.</p><h4>Step 1: Start a personal project using LLMs</h4><p>Rather than taking a full course on Transformers and getting overwhelmed by technical terms, try a quick personal project. Pick something fun and easy to build. <a href="https://www.projectpro.io/article/llm-project-ideas/881#mcetoc_1hv4vkjbi1ts">Here’s</a> a list of 30 ideas to pick from. The goal here is to experience the end-to-end process by yourself, from model selection to app deployment. Leverage pre-trained models available from OpenAI, Hugging Face, or other platforms. Hands-on projects can provide practical insights and build your confidence.</p><h4>Step 2: Deepen your understanding</h4><p>Once you’ve encountered issues or bottlenecks from the experience above, use your insights as the starting point for a deeper study of the model you picked. For example, if your app fails at answering certain types of questions, consider learning how to fine-tune the LLM with a small dataset.</p><h4>Step 3: Join communities</h4><p>If you can’t find peers to build LLM apps with you, join online communities or offline meetups. Attend generative AI conferences to network and get inspired. This journey doesn’t need to be alone. Plus, your next job opportunity may arise from these connections. You just never know.</p><h3><strong>Note for hiring managers</strong></h3><p>Engineers with existing LLM experience are extremely hard to get. I’d recommend giving a chance to engineers with traditional ML background. Just don’t forget to evaluate the core ML skills mentioned above. Most importantly, evaluate their adaptability and willingness to learn.</p><h3><strong>Ready to ride the gen AI wave?</strong></h3><blockquote>Technical trends come and go, but mastering fundamental skills will help you stay relevant and competitive.</blockquote><p>If you are in tech but new to LLMs, remember that you don’t need prior LLM experience to jump into the world of generative AI. Focus on the long-lasting skills, and you will thrive in any new era of technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EN-Y4oPYBwz8Gkxhwmll2g.png" /><figcaption>Transitioning from traditional machine learning to generative AI</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65e49c41a6ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How PMs can Master the Generative AI Game]]></title>
            <link>https://charlottetao.medium.com/how-pms-can-master-the-generative-ai-game-5-challenges-and-solutions-for-managing-llm-products-7e594eb569c8?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e594eb569c8</guid>
            <category><![CDATA[large-language-models]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Wed, 21 Feb 2024 00:25:51 GMT</pubDate>
            <atom:updated>2024-12-31T13:14:34.465Z</atom:updated>
            <content:encoded><![CDATA[<h4>5 Challenges and Solutions for Managing LLM Products</h4><h3><strong>Adapting PM skills to LLM-powered products</strong></h3><p>Many Product Managers (PMs) are considering diving into the new<strong> large language models (LLMs) </strong>game but are unsure how to proceed. <strong>Generative AI</strong> products, or products powered by LLMs, are gaining lots of traction these days. OpenAI recently hit the <a href="https://www.ft.com/content/81ac0e78-5b9b-43c2-b135-d11c47480119">$2 billion revenue mark with 10 million weekly active users</a>. Many products across different industries are emerging: AI coding assistants, AI artists, AI customer support, all powered by various large language models.</p><p>This trend poses new challenges for the PM world. As more products begin incorporating LLMs, it’s becoming clear that traditional PM skills might not fully meet the demands of LLM products. Let’s dive into these unique challenges and explore how PMs can adapt to the evolving landscape of LLMs.</p><h3><strong>Understanding LLM product tiers</strong></h3><p>First, it’s important to understand that LLM products are largely categorized into two tiers, each with its own set of challenges. Knowing which tier of product you’re working with can help you better craft product strategies, especially if you are interviewing for a PM role in LLMs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7-Gk9TCA2FTCFFENeu48-w.png" /><figcaption>LLM Product Tiers</figcaption></figure><h4><strong>Tier 1: Direct-use applications of LLMs</strong></h4><p><strong>What is it?</strong></p><p>These are simpler LLM applications where users use LLMs for quick tasks without any technical setup. No need for connecting with external data sources or any other applications. Examples include many LLM-powered chatbots and virtual writing assistants. These applications are often free or low-cost.</p><p><strong>Who are target customers?</strong></p><p>Target users are typically non-technical individuals and small business owners who need a quick and easy way to accomplish tasks without a high standard for quality or data privacy.</p><p><strong>What are the PM goals?</strong></p><p>The main goal for PMs in this tier is growth. It’s crucial to launch LLM-powered features quickly to stay ahead of competitors. Use data to measure how LLM features bring real value to users and iterate the product as quickly as possible in order to grow the product.</p><h4><strong>Tier 2: Customized applications of LLMs</strong></h4><p><strong>What is it?</strong></p><p>This tier involves more sophisticated LLM applications, where users integrate LLMs into their systems or customize LLMs for specific uses. This can involve fine-tuning LLM models using specific datasets or customized integrations of the model APIs. Products in this tier are often for enterprises and come with a higher cost, like tools for generating financial reports for large enterprise teams, coding assistants for tech companies, or document managers for research teams.</p><p><strong>Who are target customers?</strong></p><p>Target users are typically enterprise users with specific product requirements for LLMs and a high standard for data security. They usually have a lot of private data and a technical team to help with LLM integration.</p><p><strong>What are the PM goals?</strong></p><p>The main goal for PMs in this tier is customer engagement. PMs need to focus on user education and make sure the integration process is easy and repeatable. The requirements for enterprise users are usually very complex, but PMs should be the master of managing the requirements to ensure high retention rates and upselling opportunities.</p><h3><strong>5 PM challenges with LLM products</strong></h3><p>Now we understand the two tiers of LLM products. Let’s dive deeper into the PM challenges and how PMs can gear up to tackle them.</p><h4><strong>Challenge 1: Lack of understanding the new product management lifecycle</strong></h4><p>You might be familiar with the traditional AI-powered product lifecycle, which typically involves data preparation, model training, and evaluation- a process that can take months or even years. However, the lifecycle for an LLM-powered product is quite different.</p><ol><li>Data preparation can be much more efficient for LLM products, as prompt engineering can address most issues, eliminating the need for data training. Some teams go further by using fine-tuning to enhance model accuracy or leveraging external datasets (e.g., <strong>Retrieval Augmented Generation, or RAG</strong>) for LLMs to analyze, especially for tier-2 products where accuracy standards are higher, but the data size requirements are not as large as for traditional machine learning (ML).</li><li>In most cases, LLM models don’t need to be trained from scratch, which is great news for small teams without extensive compute resources or large numbers of ML researchers. Most teams can just use pre-trained models like GPT, but PMs need to collaborate with their engineering counterparts to carefully select the appropriate foundational model for their specific goals.</li><li>Regarding evaluation, PMs must establish new metrics to measure model performance, such as <a href="https://www.databricks.com/blog/llm-inference-performance-engineering-best-practices">latency</a>, <a href="https://wandb.ai/ayush-thakur/llm-eval-sweep/reports/How-to-Evaluate-Compare-and-Optimize-LLM-Systems--Vmlldzo0NzgyMTQz">cost</a>, and <a href="https://ramblersm.medium.com/the-significance-of-perplexity-in-evaluating-llms-and-generative-ai-62e290e791bc">perplexity</a>, in addition to traditional metrics like F1 scores.</li><li>Regarding model deployment, LLM products focus on collecting human feedback to improve the model, which can be used to refine the prompt or further fine-tune the model.</li></ol><p>At a high level, the iteration process for LLM products is much shorter than for traditional ML products but needs to be extremely iterative to achieve good inference quality. PMs must work with engineering to develop an efficient, scalable process for each iteration.</p><h4><strong>Challenge 2: Lack of product differentiation</strong></h4><p>Everyone claims to use LLMs. We see almost every technical product website mentions the term generative AI. Off-the-shelf LLMs such as OpenAI’s GPT are very easy to set up nowadays. Unlike traditional machine learning where teams can leverage private data to train their own models, owning proprietary data is no longer a true competitive advantage. <a href="https://www.nfx.com/post/ai-like-water">An article from NFX</a> mentions that many LLM applications “are exactly the same under the hood”.</p><blockquote>“AI differentiation is heading to zero”.</blockquote><p>In the age of LLMs, rather than simply claiming the use of AI, PMs should focus on the perceived value of AI for their products, perhaps through<strong> a better marketing channel or a better launch strategy</strong>, rather than the LLM technology itself.</p><p>For example, a standout product from this year’s CES was <a href="https://www.rabbit.tech/">Rabbit</a>, a small hardware device that enables interaction with LLMs to perform tasks in various apps, like adding a new calendar event. Despite its technology not being truly groundbreaking — OpenAI’s ChatGPT already performs similar functions with its plugins, and <a href="https://www.reddit.com/r/ArtificialInteligence/s/M86lfLA0G8">one critique</a> saying the product reminds people of “the part in Silicon Valley where they are forced to build a box because that’s what makes money” — Rabbit managed to sell 10,000 devices by the second day of CES. Its success was not just about the technology but also how it was marketed and presented. They picked CES as the main channel where there are more potential users passionate about tech gadgets and quickly gained traction.</p><h4><strong>Challenge 3: User education</strong></h4><p>We have to admit that user knowledge about new technologies is usually limited. Most people today still have never heard the term large language models, let alone used them.</p><p>When dealing with LLM products, PMs should prioritize UI/UX, considering how much AI to expose to users and how. For example, if you want to design a feature where users can write a prompt to the LLM directly, do not expect them to write very high-quality prompts. Try to limit the scope of the LLM as much as possible so we can limit user errors. Meanwhile, balance flexibility and usability so you don’t overwhelm users with too many fancy LLM features.</p><p>For tier 2 products, don’t underestimate the complexity of enterprise integrations. LLM integration may need more customization and performance monitoring. PMs should be patient with enterprise customers unfamiliar with LLM best practices and focus on user education during integration and onboarding.</p><h4><strong>Challenge 4: Risks with LLM providers</strong></h4><p>Although it’s great not having to train your own LLMs form scratch, using third-party LLMs comes with many risks.</p><ol><li>You do not control how the foundation models are trained or updated, which can affect your own product.</li><li>The stability of the model also depends on the stability of the provider’s company. If they go out of business or have a huge outage, your own product will also be impacted.</li><li>Your cost also depends on the provider. If they increase their API cost, your cost will inherently go up.</li><li>Data privacy is another huge risk, discussed more in the next section.</li></ol><h4><strong>Challenge 5: Data privacy</strong></h4><p>Data privacy can be a major concern for customers using products with third-party LLM APIs. While many providers claim they don’t use customer data to train their models, PMs should take their claim with a grain of salt. Always scrutinize the vendor’s security measures and think of mechanisms to protect customer’s data. For example, consider anonymizing customer PII (personally identifiable information) data before sending it to the LLM API and using encryption during the process.</p><h3><strong>Conclusion</strong></h3><p>All in all, to ride the wave of LLM products, PMs must take the time to study the nuances while maximizing the benefits of traditional product management. By understanding these challenges and preparing to address them, PMs can ensure their LLM-powered products stand out in the market and deliver real value to their users.</p><p>Any thoughts on product management in the age of LLMs? Feel free to drop a line on my LinkedIn and let’s discuss. <a href="https://www.linkedin.com/in/charlottetao/">https://www.linkedin.com/in/charlottetao/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e594eb569c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is the Classic Product Management Role Obsolete?]]></title>
            <link>https://charlottetao.medium.com/is-the-classic-product-management-role-obsolete-skills-for-transitioning-to-a-technical-pm-in-tech-4d51fa1825bb?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d51fa1825bb</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Fri, 03 Nov 2023 13:52:09 GMT</pubDate>
            <atom:updated>2024-12-31T13:15:03.516Z</atom:updated>
            <content:encoded><![CDATA[<h4>Skills for Transitioning to a Technical PM in AI</h4><h3>Understanding the shift in product management roles</h3><h4>The decline of traditional product management</h4><p>There’s been a noticeable trend in the tech industry: traditional product management (PM) is giving way to technical product management. According to Glassdoor, technical PMs’ average salary in 2023 is $155k, while it is $132k for traditional PMs. Becoming a technical PM is clearly the new gold standard for product management.</p><p>Having witnessed this trend firsthand during my 10+ years in tech and AI, I’d like to shed some light on the differences between traditional PMs and technical PMs and offer guidance for those interested in becoming a technical PM.</p><p><strong>Many of us are familiar with </strong><a href="https://martineriksson.com/"><strong>Martin Eriksson</strong></a><strong>’s </strong><a href="https://medium.com/@bfgmartin/what-is-a-product-manager-ce0efdcf114c"><strong>Venn diagram</strong></a><strong> for product managers, balancing business, technology, and UX. However, this model is becoming outdated for technical PMs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*BEFsvwlE9LJ98Lf8QayFzQ.png" /><figcaption>Traditional product manager’s Venn diagram</figcaption></figure><p>Previously, a “product” was assumed to be a tangible, interactive entity with established business value. However, today’s products might be extremely tech-centric and entirely intangible without much requirement on business or UX, such as breakthrough machine learning algorithms or complex API gateways.</p><p><strong>Here are a few key sectors where technical PMs are increasingly needed than traditional PMs.</strong> This is not an exhaustive list but it gives an idea on the sectors that are experiencing the shift.</p><ul><li>Machine learning innovations such as Large Language Models</li><li>Advanced robotics, such as autonomous vehicles and surgical robots</li><li>Space technologies</li><li>Brain-computer interaction technologies</li><li>Biotechnology</li></ul><h3>Differences between traditional and technical product management</h3><ul><li>Nature of product: Technical product managers (TPMs) tend to work on innovative tech products, often without a clear precedent.</li><li>Stakeholders they collaborate with: While traditional PMs work with UX designers and business analysts, TPMs typically work more with engineers and researchers.</li><li>Skill set: TPMs must understand the technical construct of their products, enabling them to make informed decisions without the constant need to defer to engineers, whereas traditional PMs are more user-centric and spend less time on technical aspects.</li></ul><h3>What has caused the rise of TPMs?</h3><p>A few observations:</p><ul><li>Growing complexity of tech products: AI products, for instance, have distinct demands.</li><li>Role overlap: Engineers and data scientists today are increasingly acquiring skills traditionally associated with PMs, blurring the lines between their roles</li><li>Advancements in PM tools: Many tools now simplify tasks once central to the traditional PM’s role. For example, there are advanced workflows and data insights that can be done automatically without relying on a PM.</li></ul><h4>New Venn diagram for technical product management</h4><p>Given these nuances, I propose<strong> a fresh Venn diagram for TPMs: Domain knowledge, technical knowledge, and system design knowledge.</strong></p><figure><img alt="A new Venn diagram for technical PMs balancing domain knowledge, technical knowledge, and system design knowledge." src="https://cdn-images-1.medium.com/max/1024/1*8251OpVnY6Z717oDIaH-pw.png" /><figcaption>A new Venn diagram for technical product management</figcaption></figure><ul><li>Domain knowledge: This circle replaces the traditional business circle. A successful TPM must understand the subject area very well, ensuring the technology addresses specific pain points.</li><li>Technical knowledge: TPMs must have a genuine understanding of technical best practices beyond merely using technical jargon. They should foresee potential technical bottlenecks and have a strong sense of solving technical problems. A lack of this understanding can result in unrealistic product goals and unavoidably conflicts with engineers.</li><li>System design knowledge: Moving past user-centric design, TPMs need to plan and visualize how various technical components interplay and depend on each other. This is particularly vital due to product complexity.</li></ul><p>Let me use an example to dive deeper into how this new Venn diagram works: <strong>Autonomous navigation systems in robotics.</strong></p><ul><li>Domain knowledge: TPMs must understand that navigation quality is tied to sensor quality and the fusion algorithms. Additionally, they must keep up with tech trends, like choosing between<a href="https://medium.com/0xmachina/lidar-vs-camera-which-is-the-best-for-self-driving-cars-9335b684f8d"> a camera-only sensing suite or incorporating LiDARs</a>, and keeping up with regulatory requirements such as <a href="https://www.cnbc.com/2023/10/24/california-dmv-suspends-cruises-self-driving-car-permits.html">permits</a> and traffic rules.</li><li>Technical knowledge: TPMs should have a high-level understanding of major algorithms, their pros and cons, limitations of different sensors and <a href="https://en.wikipedia.org/wiki/High-definition_map">HD maps</a>. Leverage these insights to make informed decisions and set realistic targets.</li><li>System design knowledge: System design thinking is crucial for TPMs building autonomous navigation systems. This includes determining whether to run something on cloud, how to capture reliability, or how to optimize for performance.</li></ul><h3>How to become a technical product manager?</h3><p>Considering transitioning to a TPM role? Here are a few tips:</p><ul><li>Go deep. Learn tech basics but make sure to pick a domain and go deep. Understand key technical challenges in that domain and eventually become the go-to expert.</li><li>Hone fundamental skills. For example, if your focus is machine learning (ML), learn how to read ML papers efficiently. Be able to sketch simple technical diagrams and convey technical concepts in plain language.</li><li>Learn engineering best practices such as continuous integration, version control, modularity, and documentation. These are the universal rules for almost every technical development. What’s the difference between a prototype for research and a production level solution?</li><li>Join a tech-oriented team. Immerse yourself in a technical culture. Partner with an experienced engineering buddy to get you up to speed. Get hands-on. Learn as you go.</li></ul><h4>Challenges to anticipate in technical product management</h4><p>Though TPMs get to work on many cool projects, there are a few common challenges you should also consider.</p><ul><li>Navigating tech-first environments: In teams led by engineers, it can be hard to make an impact as someone without a PhD in tech. Top-level decisions are typically made by engineers instead of business people. Therefore, TPMs must learn how to steer product directions with a strong business sense. Educate your team on how to incorporate business strategy into decision making.</li><li>Balancing between technical depth and product vision: Here is a challenge related to the first one. TPMs must understand the technical nuances of their products but can sometimes get too deep into the details, losing sight of the broader product strategy or user needs.</li><li>Balancing between soft Skills and technical skills: One must not forget to develop soft skills while focusing on technical skills. Regardless of which type of PM you are, you have to be good at communication, stakeholder management, ownership, time management, etc.</li></ul><h3>Conclusion</h3><p>Transitioning to a TPM role is a process. It can even be a mindset shift. In my own journey, embracing the technical aspects of product management opened doors to opportunities I never imagined.For those of you eager to contribute at this intersection of tech and product, TPM definitely offers an exciting and impactful opportunity.</p><p>How do you see the role of traditional product management evolving in your sector? What skills do you believe will be most crucial for the technical PMs of tomorrow? Feel free to drop a line on my LinkedIn and let’s discuss. <a href="https://www.linkedin.com/in/charlottetao/">https://www.linkedin.com/in/charlottetao/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d51fa1825bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are Product Managers the Future Founders?]]></title>
            <link>https://charlottetao.medium.com/product-managers-vs-startup-founders-a-complete-side-by-side-comparison-2663e07efced?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/2663e07efced</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Fri, 01 Sep 2023 13:16:31 GMT</pubDate>
            <atom:updated>2024-12-31T13:17:53.252Z</atom:updated>
            <content:encoded><![CDATA[<h3>Are Product Managers the Future Founders? A Side-by-Side Comparison Between PMs and Startup Founders</h3><h4>Plan the Next Career Move for Aspiring Founders</h4><p>Many folks have asked me if the PM experience is a stepping stone to entrepreneurship, especially with the rising trend of PMs becoming founders. Having worn both hats — as a product manager and a startup founder — I can intimately relate to the unique challenges and joys each role offers. In this article, I try to shed light on both the similarities and differences between product managers and startup founders.</p><h3>Similarities between PMs and founders:</h3><p>Both product managers and startup founders demand a versatile skill set. Let’s delve into the similarities first. Indeed, compared to other job functions, product manager is probably the job that aligns most closely with a future CEO. Like CEOs, PMs are known to be the jack of all trades in most organizations. If you are considering a career in PM and potentially transitioning to entrepreneurship, check out this list and see why PM is a great stepping stone to starting your own startup.</p><h4>Similarity 1: product instinct</h4><p>”Instinct” is probably a complex term, but it’s a must-have skill when making a product decision with limited data. Some people have to work for years to have the right product instinct, while others have it right away when they start their careers. PMs and founders have to have it because they usually face problems without a right or wrong answer, often without the benefit of supporting data. They also have to trust their instincts, especially when faced with challenges.</p><h4>Similarity 2: vision crafting</h4><p>Vision crafting is a shared skill for PMs and founders because both need to bring people together toward a common future that people can visualize. PMs craft visions to lead a team. Founders craft a vision to lead an organization. Both work hard to make sure the vision tells a compelling story and is easy to understand by their believers.</p><h4>Similarity 3: presentation</h4><p>Beyond shaping a vision, PMs and founders must also articulate their ideas, which brings us to presentation skills. Both have to make lots of presentations on a daily basis, some with large audiences, some are 1:1s. Both PMs and founders need to be able to explain complex concepts in plain language and engage the audience throughout the presentation.</p><h4>Similarity 4: negotiation</h4><p>PMs negotiate for product requirements and resources, while founders negotiate business deals and investments. Different scenarios but both require an understanding of the art of negotiation, such as seeking win-win, handling difficult conversations, active listening, etc.</p><h4>Similarity 5: sales</h4><p>Sales may seem more typical for founders, but PMs turn out to be selling a lot as well. It’s just that they sell product visions internally rather than real products to customers. Good selling skills will help PMs secure resources and align product roadmaps.</p><h4>Similarity 6: stress management</h4><p>While no one desires this skill, it’s undeniably crucial. To some degree, founders face a higher stress level than PMs, but because they at least are the boss and have more autonomy when making decisions, their stress level can be similar to PMs. PMs also face an incredible amount of stress from internal politics.</p><h4>Similarity 7: prioritization</h4><p>Both PMs and founders have a long wish list of features to build that must be prioritized based on potential impact, cost, feasibility, and many other dimensions. They must master the art of making trade-offs with limited development resources.</p><h3>Differences between PMs and founders:</h3><p>Although PMs and founders share many skills, there are still many surprising differences and unique challenges in each role. Make sure to consider these differences before making a career decision. In general, the founder’s role is a lot broader, more complex, and involves more risks than PMs, but PMs get to stay focused on building great products.</p><h4>Difference 1: overall ownership</h4><p>PMs own products. Their job is to get the product to the finish line, grow the product with the highest efficiency, and defend the product during challenging times. Other factors such as employee turnover, runway, and Legal, though important, aren’t on the top of their list.</p><p>Founders own the entire company. Their job is to keep the entire company functioning and survive during challenging times. Their decisions are usually impacted by non-product-related factors such as limited budgets, a newly recruited industry expert, or a change in security regulations. They also make product decisions but usually within a very broad scope.</p><h4>Difference 2: leadership</h4><p>PMs lead by influence without authority. They do not have the title power as founders do. To use absolute authority, they usually have to borrow it from their managers or other stakeholders with authority.</p><p>Founders can lead with authority. They get to have the final say when making strategic decisions. Obviously, this doesn’t mean they can abuse their power. A well-respected founder should also practice active listening and humility to maintain their authority.</p><h4>Difference 3: people management</h4><p>PMs usually do not have many direct reports. As their title says, they manage products, not people, which means they don’t worry about fighting for headcounts or promotions. However, they do get to influence product directions, which indirectly affects headcounts.</p><p>A significant portion of a founder’s time, perhaps more than 50%, is dedicated to people management. They have to actively look for new talent, get them to join the team, keep them happy, and fire the ones that drag their feet.</p><h4>Difference 4: product lifecycle management</h4><p>PMs focus on product development, launch, and subsequent iterations.</p><p>Founders cover a broader scope than the product itself by adding ideation, sales, marketing, sunsetting, etc. Unlike PMs who can follow a so-called product lifecycle template, founders often navigate without a set template and have to adjust lifecycles as needed.</p><h4>Difference 5: support system</h4><p>The support system is often an overlooked aspect. When there are challenges, PMs usually have their managers to support them or their internal ‘sponsors’ such as a PM counterpart who shares the same product vision.</p><p>Founders are on their own. They can ask for help from their investors and other founders, but the best they can get is just advice. Although both PMs and founders have to handle lots of stress, founders can often feel isolated.</p><h4>Difference 6: stakeholder management</h4><p>PMs predominantly manage internal stakeholders with some external stakeholders tied to specific projects. It’s pretty straightforward because everyone shares one underlying assumption which is to build a successful product and get paid.</p><p>Founders mainly need to manage external stakeholders, such as investors, customers, and key business partners. It’s tricky because different stakeholders have very different interests they have to entertain, e.g., investors usually want a return on their money while customers care more about the product quality and pricing.</p><h4>Difference 7: decision making</h4><p>PMs must rely on data or different types of analysis to convince the company’s leadership and get all internal buy-ins before making a decision.</p><p>Founders have the autonomy to make decisions without relying on data, especially when data is rare. This ensures speed but also involves a considerable amount of risk. They sometimes have to bite the bullet and make difficult decisions for the greater good.</p><h3>A recap</h3><p>Here is a table comparing product managers and startup founders. Drawing from my personal experiences in both roles, I’ve come to appreciate the intricate dance between PMs and founders. As you reflect on your own career, whether you are a PM aspiring to become a founder or vice versa, understanding these facets can help you make a much more informed decision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NPKZZ2FGz2d-fRN4" /><figcaption>A side-by-side comparison between product managers and startup founders</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2663e07efced" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating Office Friendships: Who Says Coworkers Can’t be Friends?]]></title>
            <link>https://charlottetao.medium.com/navigating-office-friendships-who-says-coworkers-cant-be-friends-f0ebcb50526b?source=rss-5a658beec450------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0ebcb50526b</guid>
            <category><![CDATA[friendship]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[happiness]]></category>
            <dc:creator><![CDATA[Charlotte Tao]]></dc:creator>
            <pubDate>Tue, 22 Aug 2023 13:52:22 GMT</pubDate>
            <atom:updated>2024-12-31T13:16:26.442Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to Find Genuine Friendships at Work? Any Precautions?</h4><p>According to a <a href="https://www.cpapracticeadvisor.com/2022/08/23/new-study-reveals-why-having-friends-at-work-matters/69777/">recent research</a>, over 9 in 10 people said friendships at work impact their willingness to stay at a company, while only <a href="https://apnews.com/article/workplace-friendships-poll-relationships-best-friends-office-faa0858e623e78c70e6f7eb02c55c7f1">2 in 10 say they have a “best friend” at work</a>.</p><p>In today’s crazy-busy work world, true friendships seem like a luxury. Yet, beyond all the deadlines and meetings, we all have a desire for genuine connections — a space for laughter, understanding, and support. So, what makes it so tough to find true friends at work, and how can we turn coworkers to genuine friends?</p><p>Let’s first delve into the challenges of workplace friendships.</p><h3>The Challenges</h3><h4>The elephant in the room: Conflict of interest</h4><p>We’ve all seen it — two close friends start together at an entry level, but soon one climbs the corporate ladder much faster. The dynamics inevitably change. It’s hard to imagine your best buddy today becoming your boss tomorrow. Even if you can handle a promotion gracefully, you and your friends may no longer share common topics because your roles and responsibilities have changed. Plus, people tend to team up with their own friends for projects, which can seem like favoritism.</p><h4>Maintaining professionalism is not always easy</h4><p>Friendship means fun, but work typically is not as fun. In roles that require precision, such as accounting, casual chatter may lead to a serious mistake. A lunch chat about a party is great, but switching gears to an important board meeting in a minute is not easy.</p><h4>To share or not to share? That’s the question</h4><p>There is a delicate balance between professionalism and intimacy. More often than not, people overshare their personal matters with their so-called friends at work and unexpectedly become the hot topic for <a href="https://www.betterup.com/blog/gossip-in-the-workplace">workplace gossip</a>. Where should we draw the line for sharing?</p><h4>Mentors vs. Friends</h4><p>Although both mentors and friends are invaluable, their <a href="https://www.mentorcollective.org/blog/friendship-and-mentorship#:~:text=Friendship%20offers%20a%20level%20of,creates%20nuance%20within%20each%20role.">roles are different</a>. A mentor offers guidance, while a friend offers support. I’m not saying mentors cannot become friends or vice versa, but in most cases, mentors are much more senior and lack the level of intimacy found among peers. Many workplaces encourage mentorship and rarely emphasize peer bonding, but a healthy organization should invest in both.</p><p>With these challenges in mind, how can we make real friends at work?</p><h3>Some tips</h3><h4>Tip #1: Embrace all types of interactions</h4><p>Dive into every chance you get to mingle at work. Events like weekly all-hands meetings, team-building activities, office lunches, 1:1s aren’t just routines. They are opportunities to meet new people, get to know your colleagues better, or simply listen to others.</p><p>In particular, take full advantage of <a href="https://www.pmi.org/learning/library/implementing-buddy-system-workplace-9376">new employee orientations</a>. They offer one of the best opportunities to get to know people outside your team. It creates a unique setting where you meet people with passion from diverse teams, all eager to find new friends like you.</p><h4>Tip #2: Bond over shared hobbies</h4><p>Have a love for sci-fi, cycling, or bird watching? Chances are someone in your office does, too. Such shared hobbies can be a great way to start a friendship. The problem is that we usually don’t know who shares the same hobbies in the office unless there’s a Slack channel or formal groups for the hobby. In that case, proactively tell others about your hobbies and let them come find you.</p><h4>Tip #3: Branch out</h4><p>To avoid conflict of interest, seek friends from other teams. Collaborating on a project with someone from a different department can lead to fresh perspectives and, quite possibly, a new friend. It can also help you understand how other parts of the company function.</p><h4>Tip #4: Look beyond office walls</h4><p>If you are part of a startup or a small-sized organization, don’t let the size of your team limit your friendship options. External workshops or industry seminars can be great opportunities for genuine connections. As a startup founder myself, I try to make a goal to find a friend at every event I go to, in addition to any business goals. This adds more joy and motivation to my work.</p><h4>Tip #5: Be visible online</h4><p>If face-to-face isn’t your thing, make yourself more visible online. You need to be seen to let your potential office friends know about you. A funny meme (as long as it’s office appropriate), a thought-provoking article, or a simple Happy Friday message can go a long way.</p><h3>Precautions</h3><h4>Think before you share any personal matters</h4><p>Everyone loves a good story, but your story could become a topic for gossip and may unexpectedly backfire your career. Also, if you have to discuss personal matters, do it outside the office or after work. Yes, I get that you are a workaholic, and it’s tempting to discuss everything at the office, but you need to keep work life and personal life at least somewhat distinct.</p><h4>Manage your expectations</h4><p>It’s natural to expect more from friends. However, over-leaning on friends at work is unfair to everyone and can cause unintended disappointments. You typically expect one to finish a project in a week, but because you know your friends are quite good at it and they should obviously prioritize your request, they must finish it in a day. Remember, avoid putting undue pressure on friends and communicate openly to ensure expectations align with reality.</p><h4>Prepare for changes</h4><p>Change is an inevitable part of the corporate landscape. Whether it’s shifts in job roles, promotions, or new projects, it’s essential to adapt without compromising your work relationships. Jobs change and roles evolve, but friendships should last. When one of you gets promoted to a more senior role, have an open conversation about it. Support each other rather than letting jealousy ruin your relationship.</p><h4>Just move on</h4><p>Don’t feel guilty if you can’t maintain all the relationships. It’s normal if work friendships fade over time. People change jobs and even change industries all the time. Cherish the moments shared and be open to building new connections. If you do want to maintain a friendship, make sure to put in extra effort and check in with them regularly after you work at different places.</p><h3>Work is more than career growth</h3><p>When we reflect on our professional journeys, it’s rarely the titles or compensations that stay in our memories. Instead, it’s the faces of colleagues who became friends, their laughter after a long meeting, and a genuine pat on the back for a job well done. Despite the challenges of workplace friendships, it’s worthwhile to make an effort to find and nurture friendships at work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Znt5irlCWNgdm4MeOyP9kA.jpeg" /><figcaption>Friends at work</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0ebcb50526b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>