<?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 Eunice on Medium]]></title>
        <description><![CDATA[Stories by Eunice on Medium]]></description>
        <link>https://medium.com/@warstories?source=rss-8c5aa3c99ed2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WfiJ6Keb22pEuJMN6Z2s9A.png</url>
            <title>Stories by Eunice on Medium</title>
            <link>https://medium.com/@warstories?source=rss-8c5aa3c99ed2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:45:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@warstories/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[At Google, I Stopped Treating Reorganizations Like Strategy.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/illumination/at-google-i-stopped-treating-reorganizations-like-strategy-07bba46ece30?source=rss-8c5aa3c99ed2------2"><img src="https://cdn-images-1.medium.com/max/1672/0*LSj2FFGFNO98VaCF.png" width="1672"></a></p><p class="medium-feed-snippet">The org chart kept changing. Some of the hardest decisions underneath it did not.</p><p class="medium-feed-link"><a href="https://medium.com/illumination/at-google-i-stopped-treating-reorganizations-like-strategy-07bba46ece30?source=rss-8c5aa3c99ed2------2">Continue reading on ILLUMINATION »</a></p></div>]]></description>
            <link>https://medium.com/illumination/at-google-i-stopped-treating-reorganizations-like-strategy-07bba46ece30?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/07bba46ece30</guid>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[reorganization-strategy]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[business-management]]></category>
            <category><![CDATA[team-dynamics]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 02:29:59 GMT</pubDate>
            <atom:updated>2026-09-19T02:29:59.096Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[At Google, I Stopped Believing Internal Competition Raised Everyone’s Performance]]></title>
            <link>https://medium.com/@warstories/at-google-i-stopped-believing-internal-competition-raised-everyones-performance-f6dfc791ecf4?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6dfc791ecf4</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[internal-competition]]></category>
            <category><![CDATA[performance-improvement]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 14:14:56 GMT</pubDate>
            <atom:updated>2026-08-29T14:14:56.870Z</atom:updated>
            <content:encoded><![CDATA[<p>I thought talented people competing would make the team sharper. Eventually I noticed what we had started protecting from one another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2HvUjNFSWN3QS6r9.png" /><figcaption>Metronome with teamwork quote about rhythm</figcaption></figure><p>There was a moment at Google that lasted perhaps five seconds and has embarrassed me for much longer.</p><p>An engineer on another part of our project was explaining a problem his team had been chasing for several days. I knew the problem. We had run into almost the same thing weeks earlier, and I had notes that could probably save them a great deal of time. I knew which assumption had been wrong, where the misleading signal appeared, and which part of the system I would inspect first.</p><p>I should have interrupted immediately.</p><p>Instead, I hesitated.</p><p>Review season was approaching. The boundaries between our contributions had already become less distinct than I would have liked. I had spent months developing expertise in this particular corner of the system, and for a few seconds I found myself doing an ugly little calculation: if I handed over everything I knew, what exactly remained mine?</p><p>Nobody in the room knew I had thought this.</p><p>That was part of what disturbed me.</p><p>I had always imagined unhealthy competition would look more dramatic.</p><p>Apparently sometimes it looks like a competent engineer sitting quietly for five seconds.</p><p>* * *</p><p>I arrived at Google with a fairly uncomplicated belief about competition.</p><p>Talented people make one another better.</p><p>There was plenty of evidence for it. School had taught me that being surrounded by strong students raised my standards. Technical interviews had taught me that knowing thousands of capable engineers wanted the same opportunity was an excellent cure for procrastination. My career had repeatedly improved because somebody nearby understood something I did not.</p><p>Google seemed to confirm the theory almost immediately.</p><p>There was always someone who had gone deeper.</p><p>Someone who knew the system you had just discovered existed.</p><p>Someone who could read your design document and find the assumption you had spent three days carefully avoiding.</p><p>You could leave one meeting feeling unusually clever and enter another twenty minutes later where a person half your age calmly asked a question that rearranged your understanding of the problem.</p><p>This was good for me.</p><p>Humility delivered by exceptionally competent strangers is still humility.</p><p>So I worked harder.</p><p>I prepared more carefully. I learned faster. I stopped confusing familiarity with expertise because the environment corrected that illusion too quickly.</p><p>Competition appeared to be doing exactly what I had been told it would do.</p><p>Then I began noticing what else it was doing.</p><p>* * *</p><p>The change was not that people suddenly became selfish.</p><p>That would have been easier to recognize.</p><p>Google contained many of the most generous engineers I have ever worked with. People shared knowledge, reviewed documents, debugged other teams&#39; problems, mentored younger engineers, and routinely gave away hours of thought that would never appear in any performance summary.</p><p>But generosity was happening inside another system too.</p><p>We were collaborating while being evaluated individually.</p><p>We were encouraged to share context freely while also making our personal impact sufficiently distinguishable that somebody could evaluate it later.</p><p>We were supposed to think as a team, preferably without creating any confusion about which member of the team deserved the promotion.</p><p>Nobody needed to say the contradiction aloud.</p><p>We learned it.</p><p>You began noticing which projects had clean ownership.</p><p>You noticed which work had senior visibility.</p><p>You noticed that helping another person&#39;s project could consume a week while contributing only a sentence to your own story.</p><p>You noticed which problems were important and which important problems were legible.</p><p>At first I thought noticing these things simply meant I was becoming more sophisticated about my career.</p><p>Perhaps I was.</p><p>Sophistication has been known to provide respectable names for instincts we would find less attractive if they arrived without PowerPoint.</p><p>* * *</p><p>I did not stop helping people.</p><p>That is important.</p><p>What changed was the small accounting system that sometimes appeared underneath the help.</p><p>How much should I contribute?</p><p>Who will own the final result?</p><p>If I solve this part, will anyone know?</p><p>Should I take the useful supporting role or the more visible leading one?</p><p>Would I still want this project if somebody else&#39;s name were attached to the launch?</p><p>These are uncomfortable questions because none of them are entirely illegitimate.</p><p>Credit matters.</p><p>Accurate attribution matters.</p><p>Careers are built partly from evidence of contribution, and pretending otherwise does not make the system disappear. Senior engineers especially need to demonstrate scope, judgment, influence, and impact.</p><p>The trouble began when I discovered how easily a reasonable desire for fair recognition could become a habit of measuring everything.</p><p>I noticed when someone else got credit for an idea I had shaped.</p><p>I noticed when another engineer got a project I wanted.</p><p>I noticed when someone appeared to be progressing faster than I was.</p><p>I noticed other people&#39;s careers with an attentiveness I would have found impressive if it had been directed toward almost anything else.</p><p>And eventually another person&#39;s success could produce two reactions inside me at once.</p><p>I was happy for them.</p><p>Then came the quieter question.</p><p>What does this mean for me?</p><p>* * *</p><p>That was when competition changed character.</p><p>Other people&#39;s excellence had once been evidence of what was possible.</p><p>Now it sometimes became evidence about my position.</p><p>The distinction sounds small.</p><p>It isn&#39;t.</p><p>When someone else&#39;s strength teaches you, you look outward with curiosity.</p><p>When someone else&#39;s strength ranks you, you look sideways with anxiety.</p><p>I had spent years calling both feelings ambition.</p><p>They are not the same thing.</p><p>The first makes another person&#39;s success useful.</p><p>The second can make it threatening.</p><p>* * *</p><p>For a while, I blamed the system.</p><p>There was enough truth in that explanation to make it comfortable.</p><p>Any company that evaluates individuals creates individual incentives. Managers need to understand contribution. Promotion committees need evidence. Organizations cannot simply announce that everybody did a wonderful job and promote the entire building.</p><p>Measurement requires distinction.</p><p>Distinction creates comparison.</p><p>Comparison produces behavior.</p><p>All true.</p><p>But blaming the system allowed me to remain morally uninvolved in a system I was participating in quite enthusiastically.</p><p>Competition gave me something I wanted.</p><p>It told me where I stood.</p><p>That is one of rivalry&#39;s quieter pleasures.</p><p>The harder question in a career is: Am I becoming the person I actually want to become?</p><p>Comparison offers a much simpler substitute: Am I doing better than that person?</p><p>The second question is wonderfully efficient.</p><p>It requires almost no philosophy.</p><p>You merely need a scoreboard.</p><p>* * *</p><p>I eventually began thinking about this through the image of a rowing crew.</p><p>Competition during training can make every rower stronger. Put serious athletes beside one another and they push. Nobody wants to be the person weakening the boat.</p><p>That part of the metaphor is obvious.</p><p>The less obvious part is what happens during the race.</p><p>The boat does not care which rower can prove they are strongest.</p><p>It cares whether the force arrives together.</p><p>A rower who pulls brilliantly at the wrong rhythm does not create an exceptionally high-performing crew. They create an exceptionally tiring afternoon.</p><p>This was the mistake in my original belief.</p><p>I had assumed that whatever improves individuals must necessarily improve the group.</p><p>But teams are not collections of independent performances added together.</p><p>They are systems of dependence.</p><p>Sometimes the thing that makes the individual look strongest makes the system weaker.</p><p>* * *</p><p>I began seeing this in the best collaborative work around me.</p><p>An engineer would share an unfinished idea before protecting themselves against being wrong.</p><p>Someone would hand another team context that had taken weeks to acquire.</p><p>A senior engineer would say, “She should lead this,” about an opportunity they could easily have kept.</p><p>People recommended colleagues for work they wanted themselves.</p><p>Someone solved a problem quietly, then let the person closest to the project explain the result.</p><p>None of these actions would look heroic in a performance dashboard.</p><p>Some might actually make individual contribution harder to distinguish.</p><p>That was exactly why they interested me.</p><p>They required a person to believe that another person&#39;s strength did not reduce their own.</p><p>I wish I could say I always behaved that way.</p><p>I did not.</p><p>I was generous when generosity and ambition wanted the same thing.</p><p>The harder moments were when they disagreed.</p><p>Those moments taught me more about myself.</p><p>* * *</p><p>This became especially uncomfortable as I became more senior.</p><p>Early in an engineering career, a great deal of value can come directly from individual execution. You build the thing. You fix the bug. You understand the system.</p><p>At senior levels, your value increasingly appears through other people.</p><p>You make the decision clearer.</p><p>You transfer context.</p><p>You remove obstacles.</p><p>You help an engineer become capable of solving something without you.</p><p>You build enough trust that another team can move independently.</p><p>Some of your best work walks out of the room attached to somebody else&#39;s name.</p><p>This creates an odd test for an ambitious person:</p><p>Can you still feel successful when the evidence of your success is another person&#39;s competence?</p><p>I found that harder than I expected.</p><p>For years, I had been trained to collect evidence that I was becoming more valuable.</p><p>Then part of becoming more valuable was making myself less necessary.</p><p>There is a small cruelty in how sensible that sounds after you have learned it.</p><p>* * *</p><p>Once I saw this, I stopped asking whether internal competition made people work harder.</p><p>Of course it did.</p><p>That had never been the interesting question.</p><p>I started asking what competition made people reluctant to give away.</p><p>Context?</p><p>Credit?</p><p>Opportunities?</p><p>Unfinished ideas?</p><p>Help?</p><p>Ownership?</p><p>If engineers compete heavily for visible scope, then invisible work becomes expensive.</p><p>If promotions depend on individual narratives, helping another person&#39;s narrative can become complicated.</p><p>If the best projects are scarce, friendly colleagues can slowly become obstacles to one another without anybody behaving badly.</p><p>This is what makes internal competition difficult to diagnose.</p><p>You do not need villains.</p><p>You only need rational people responding to incentives.</p><p>I had done exactly that.</p><p>* * *</p><p>I also stopped romanticizing the opposite.</p><p>A team does not become healthy merely because nobody competes.</p><p>Ambition matters.</p><p>Standards matter.</p><p>I still want to work with people who make weak reasoning uncomfortable. I want colleagues who know things I do not know and whose work reminds me that I still have somewhere to go.</p><p>Some of my greatest professional growth came from being surrounded by people who were better than me at something important.</p><p>What I stopped believing was that the <em>competition</em> deserved all the credit.</p><p>Often the thing that improved me was simpler.</p><p>Exposure.</p><p>I saw what excellence looked like.</p><p>Someone taught me a better way.</p><p>Their judgment expanded mine.</p><p>I did not need to beat them to benefit from them.</p><p>That distinction eventually mattered enormously.</p><p>One relationship turns another person&#39;s excellence into instruction.</p><p>The other turns it into a scoreboard.</p><p>* * *</p><p>This pattern travels far beyond Google.</p><p>Friends celebrate one another while quietly comparing salaries, houses, marriages, children, travel, and progress.</p><p>Founders begin trying to build useful companies and somehow end up making product decisions because a competitor raised a larger round.</p><p>Writers stop asking whether an idea deserves to be written and start wondering why somebody else&#39;s audience grew faster.</p><p>Siblings who genuinely love one another can spend decades carrying invisible rankings assigned in childhood.</p><p>Comparison is powerful because it turns another human being into a measuring instrument.</p><p>Then their good fortune becomes complicated.</p><p>You still want them to succeed.</p><p>You would simply prefer that their success not require you to reconsider your own.</p><p>I know this because I have felt it.</p><p>Calling the feeling “drive” did not change what it was.</p><p>* * *</p><p>I think differently about strong teams now.</p><p>I still want ambitious people.</p><p>I still want high standards.</p><p>I still want the discomfort of working beside someone who can see further into a problem than I can.</p><p>But I pay much more attention to what happens when one person becomes stronger.</p><p>Does everyone gain access to what they learned?</p><p>Can someone admit uncertainty before they have a polished answer?</p><p>Do people share context before securing credit?</p><p>Can we give the most important problem to the person best positioned to solve it rather than the person most in need of visible scope?</p><p>Can I help somebody become exceptional without experiencing their growth as evidence that I am becoming less important?</p><p>Those questions tell me more about the ceiling of a team than how competitive the room feels.</p><p>* * *</p><p>I did eventually speak in that meeting.</p><p>I shared the notes.</p><p>The other engineer found the issue much faster than they would have otherwise, and the project moved on.</p><p>Nobody knew there had been a five-second debate inside my head.</p><p>Nobody congratulated me for overcoming it.</p><p>There is something appropriate about that.</p><p>The choice mattered precisely because there was no credit available for making it.</p><p>For years, I thought talented people competing would inevitably make everyone better.</p><p>Google complicated that belief.</p><p>Competition made me work harder.</p><p>It also occasionally taught me to protect things that became more valuable when shared.</p><p>The best engineers I worked with eventually showed me another kind of ambition.</p><p>They wanted to be excellent without requiring the people around them to become smaller.</p><p>I still want to work beside people who raise my standards.</p><p>I simply no longer need their excellence to tell me where I stand.</p><p>That turned out to be a much quieter way to work.</p><p>It also made the boat move faster.</p><p>* * *</p><p><em>P.S. My writing workflow has changed quite a bit over the past year. I write the long-form article first—usually on Substack—because that’s where I do my best thinking. Once it’s published, I don’t consider the work finished. I turn the article into several Substack Notes, rewrite different sections for LinkedIn and Medium, create shorter versions for X, Threads, and Bluesky, then watch which ideas actually bring readers back to the original article.</em></p><p><em>I use </em><a href="https://www.narrareach.com/"><em>Narrareach as my content distribution platform for writers</em></a><em> because it keeps that entire workflow in one place.</em></p><p><em>If you’re looking for a </em><a href="https://www.narrareach.com/features/content-distribution-platform"><em>content distribution platform for writers that helps distribute one article across Substack, Medium, LinkedIn, X, Threads, and Bluesky while tracking which posts actually bring subscribers</em></a><em>, this is the workflow I’ve been using.</em></p><p><em>The biggest surprise wasn’t how much easier publishing became. It was how often the second or third version of an idea ended up reaching more people than the original article. Distribution isn’t about repeating yourself—it’s about giving a good idea multiple opportunities to be discovered.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6dfc791ecf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[At Amazon, I Stopped Calling More Responsibility A Promotion]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/illumination/at-amazon-i-stopped-calling-more-responsibility-a-promotion-01f790af5cb0?source=rss-8c5aa3c99ed2------2"><img src="https://cdn-images-1.medium.com/max/1672/0*hP-cJPFE48zK15_R.png" width="1672"></a></p><p class="medium-feed-snippet">My scope kept growing. It took me longer to ask what else was growing with it.</p><p class="medium-feed-link"><a href="https://medium.com/illumination/at-amazon-i-stopped-calling-more-responsibility-a-promotion-01f790af5cb0?source=rss-8c5aa3c99ed2------2">Continue reading on ILLUMINATION »</a></p></div>]]></description>
            <link>https://medium.com/illumination/at-amazon-i-stopped-calling-more-responsibility-a-promotion-01f790af5cb0?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/01f790af5cb0</guid>
            <category><![CDATA[workplace-responsibility]]></category>
            <category><![CDATA[professional-growth]]></category>
            <category><![CDATA[job-title-dynamics]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[career-advancement]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Thu, 20 Aug 2026 21:17:11 GMT</pubDate>
            <atom:updated>2026-08-20T21:17:11.450Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[At Google, I Stopped Believing Internal Competition Raised Everyone’s Performance.]]></title>
            <link>https://medium.com/@warstories/at-google-i-stopped-believing-internal-competition-raised-everyones-performance-dd885a647238?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd885a647238</guid>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[newsletter]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Thu, 20 Aug 2026 10:26:40 GMT</pubDate>
            <atom:updated>2026-08-20T10:26:40.029Z</atom:updated>
            <content:encoded><![CDATA[<p>I thought talented people competing would make the team sharper. Eventually I noticed what we had started protecting from one another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fPGE8faZzqDyyH_Q.png" /><figcaption>Quote about teamwork with a wooden paddle</figcaption></figure><p>There was a moment at Google that lasted perhaps five seconds and stayed with me much longer than several projects I worked on there.</p><p>An engineer on another part of our project was explaining a problem his team had been struggling with. I knew the answer. Or at least I knew enough to save them a few days of investigation because we had encountered almost the same failure weeks earlier. I had notes. I knew which assumption had been wrong. I knew where I would tell them to look first.</p><p>And for a few seconds, I said nothing.</p><p>I wish I could tell you that I was thinking carefully before speaking. I wasn&#39;t.</p><p>I was calculating.</p><p>The boundaries between our contributions had already become blurry. Review season was not far away. I had spent months building expertise in this particular part of the system, and some primitive part of me understood that expertise partly through scarcity. If everyone knew what I knew, what exactly was mine?</p><p>Then I heard the question inside my own head.</p><p>That frightened me more than the answer.</p><p>* * *</p><p>I had spent most of my life believing competition made capable people better.</p><p>There was plenty of evidence for it.</p><p>At school, the strongest students pulled the standard upward. In interviews, knowing thousands of other engineers wanted the same job made me prepare harder. In my career, I had learned by working around people whose abilities made my own gaps impossible to ignore.</p><p>Google intensified that feeling.</p><p>You could sit in a design review with someone who understood a system more deeply than you did, then walk into another meeting and meet someone who asked a question you had not thought to ask. There was always another person who had solved something harder, learned something faster, or seen further into a problem.</p><p>For an ambitious person, this can be intoxicating.</p><p>You either become insecure or you improve.</p><p>Usually you do some of both.</p><p>I told myself the improvement was the important part.</p><p>* * *</p><p>Competition really did make me work harder.</p><p>That is why I am reluctant to tell this story as though the whole idea was obviously mistaken.</p><p>I prepared more thoroughly because I knew other people would notice weak reasoning. I learned faster because there were engineers around me whose standards embarrassed shortcuts out of me. I became more precise because vague thinking did not survive long in rooms full of people capable of examining it.</p><p>There is a kind of generosity in being surrounded by excellence. Other people&#39;s ability shows you what is possible.</p><p>But slowly I began noticing another effect.</p><p>The same environment that encouraged me to improve also encouraged me to look sideways.</p><p>Who owned the important project?</p><p>Whose name was associated with the decision?</p><p>Who presented the work?</p><p>Who had enough scope?</p><p>Who was operating at the next level?</p><p>Whose contribution would be easiest to explain when the year was compressed into a review?</p><p>None of these questions had to be spoken aloud to influence behavior.</p><p>That was what made them powerful.</p><p>* * *</p><p>The changes were rarely dramatic enough to call selfishness.</p><p>Nobody locked important documents in a drawer.</p><p>Nobody announced that they wanted a colleague to fail.</p><p>It was subtler.</p><p>You volunteered for work with clear ownership.</p><p>You were slightly less enthusiastic about the useful task that would disappear inside somebody else&#39;s project.</p><p>You shared information, but perhaps after you had already established your own understanding of it.</p><p>You helped another engineer, while noticing with surprising accuracy how much help you could give before the work stopped looking like theirs or yours.</p><p>You felt happy when a colleague succeeded.</p><p>Then, occasionally, their success produced a second feeling before you had time to stop it.</p><p>What does this mean for me?</p><p>That question was where competition changed character.</p><p>I was no longer simply using talented people as evidence of what I could become.</p><p>I was beginning to use them as evidence of where I stood.</p><p>* * *</p><p>I have noticed that pride rarely arrives announcing itself as pride.</p><p>It is much more respectable than that.</p><p>Mine often arrived disguised as fairness.</p><p>I wanted my work to be recognized accurately.</p><p>That was reasonable.</p><p>I wanted ownership to be clear.</p><p>Also reasonable.</p><p>I wanted promotions to reflect contribution.</p><p>Still reasonable.</p><p>But somewhere inside those perfectly defensible desires, I had started keeping an account.</p><p>I noticed when another person received credit for an idea I had helped shape.</p><p>I noticed when someone presented work that several of us had carried.</p><p>I noticed when an engineer appeared to be moving faster than I was.</p><p>And once you begin keeping that kind of account, generosity becomes surprisingly expensive.</p><p>The difficulty is not that you stop helping people.</p><p>The difficulty is that part of you begins asking what the help will cost.</p><p>* * *</p><p>For a long time, I blamed the system for that.</p><p>There was truth in the criticism. Any organization that evaluates individuals inevitably creates incentives around individual contribution. Managers need to distinguish performance. Promotion committees need evidence. People want to understand who did what.</p><p>But blaming the machinery allowed me to avoid looking at the part of the machinery I carried around inside myself.</p><p>Competition gave me something I wanted.</p><p>It gave me a way to measure my worth.</p><p>If I was solving harder problems, moving faster, receiving stronger feedback, or being trusted with greater scope, I could tell myself I was doing well.</p><p>Another person&#39;s performance made the scale feel objective.</p><p>This is one of the attractions of rivalry that I did not understand when I was younger. It saves you from having to answer the more difficult question of whether the thing you are pursuing is actually worth pursuing.</p><p>You can simply ask whether you are ahead.</p><p>* * *</p><p>Eventually I began thinking about it like a rowing crew.</p><p>Competition during training can make every rower stronger. Put capable athletes beside one another and they will push themselves. Nobody wants to be the weak person in the boat.</p><p>But the race asks something different from them.</p><p>The boat does not care which rower can demonstrate that they are pulling hardest.</p><p>It cares whether the force arrives together.</p><p>One athlete trying to prove exceptional strength at the wrong moment can make the crew worse.</p><p>That was the part I had missed about teams.</p><p>We often take a principle that improves the individual and assume it must therefore improve the group.</p><p>It does not always follow.</p><p>A team can contain extraordinarily ambitious people and still perform below what those people could accomplish together.</p><p>The missing ingredient is often not ability.</p><p>It is whether anyone feels safe giving some of that ability away.</p><p>* * *</p><p>The best collaboration I experienced began to look different once I noticed this.</p><p>Someone would share an unfinished idea before they had protected themselves against being wrong.</p><p>An engineer would hand another team a piece of context that had taken weeks to acquire.</p><p>Someone would say, “She should probably lead this,” even though they could have kept the visible role themselves.</p><p>A senior person would solve a problem quietly and let the person closest to the work present the result.</p><p>People would recommend colleagues for opportunities they wanted too.</p><p>Those actions look small from outside.</p><p>Inside a competitive environment, they can be expensive.</p><p>They require believing that another person&#39;s strength does not reduce your own.</p><p>I was not always good at that.</p><p>That may be the admission from my years in Big Tech that makes me least comfortable.</p><p>I liked being generous when generosity and ambition pointed in the same direction.</p><p>The more important test came when they did not.</p><p>* * *</p><p>As I became more senior, the contradiction became harder to ignore because my work increasingly depended on other people becoming effective.</p><p>A junior engineer can create enormous value through individual execution.</p><p>A Staff Engineer who tries to personally own every important solution eventually becomes a bottleneck with an impressive résumé.</p><p>The job changes.</p><p>Your context has to travel.</p><p>Your judgment has to make other people better.</p><p>Some of your best ideas need to leave the room attached to somebody else&#39;s name.</p><p>You need engineers around you to become more capable, more trusted, more independent, and sometimes more visible.</p><p>That creates a strange career test.</p><p>Can you still feel successful when the evidence of your success is another person&#39;s competence?</p><p>I did not always find that easy.</p><p>For years I had been trained to collect evidence that I was growing.</p><p>Suddenly some of the strongest evidence was that people needed me less.</p><p>* * *</p><p>This changed the way I thought about internal competition.</p><p>I stopped asking whether competition made people work harder.</p><p>Of course it can.</p><p>The better question became: <strong>What does it make people reluctant to give away?</strong></p><p>If engineers compete for ownership, context becomes valuable to possess.</p><p>If they compete for visible impact, preventive work becomes less attractive.</p><p>If promotion depends heavily on individual narratives, helping another person&#39;s narrative becomes professionally complicated.</p><p>If every important opportunity is scarce, colleagues can remain friendly while quietly becoming obstacles to one another.</p><p>Nobody has to behave badly for this to happen.</p><p>Ordinary rational people will respond to the incentives around them.</p><p>I had.</p><p>That was why I could no longer dismiss the problem as something caused by unusually political people.</p><p>* * *</p><p>I also stopped romanticizing the opposite.</p><p>A team without ambition is not automatically healthy.</p><p>I still want to work with people who care deeply about doing excellent work. I want colleagues who challenge my thinking, who notice when my standards slip, who make me aware that a better solution exists.</p><p>There were moments at Google when another engineer&#39;s excellence made me substantially better.</p><p>I am grateful for that.</p><p>What I stopped believing was that the competitive part of the experience deserved all the credit.</p><p>Often what made me better was not that I wanted to defeat the person beside me.</p><p>It was that they showed me something I had not yet learned.</p><p>Those are different forces.</p><p>One makes you look at the work.</p><p>The other eventually makes you look at the scoreboard.</p><p>* * *</p><p>The distinction matters because scoreboards are difficult to ignore once they appear.</p><p>You see this outside technology too.</p><p>Two siblings can love one another and quietly build identities around who is more successful.</p><p>Friends can celebrate each other&#39;s lives while privately measuring houses, careers, marriages, children, travel, and money.</p><p>Founders can begin by trying to build something useful and end up making decisions because a competitor raised more capital.</p><p>Writers can stop asking whether something is worth saying and begin asking why somebody else&#39;s audience is growing faster.</p><p>Comparison turns another human being into a measuring instrument.</p><p>Then their good fortune becomes strangely complicated.</p><p>You want them to do well.</p><p>Just not in a way that makes you feel as though you are doing badly.</p><p>I know that feeling because I have had it.</p><p>Calling it ambition did not make it prettier.</p><p>* * *</p><p>I think differently about strong teams now.</p><p>I still expect people to pull hard.</p><p>I still believe standards matter.</p><p>I still think being surrounded by highly capable people can change the trajectory of a career.</p><p>But I pay more attention to what happens when one person gets stronger.</p><p>Does everyone gain access to what they learned?</p><p>Do people share context before they have secured credit?</p><p>Can an engineer admit uncertainty without wondering how it will be remembered?</p><p>Can somebody help a colleague become exceptional without treating that person&#39;s growth as a threat?</p><p>Can the team give the most important problem to the person best positioned to solve it rather than the person most in need of visible scope?</p><p>Those questions tell me more about collective performance than how competitive the room feels.</p><p>* * *</p><p>I eventually shared what I knew in that meeting.</p><p>The other engineer found the issue faster because of it.</p><p>Nothing dramatic happened afterward.</p><p>Nobody recorded the five seconds I had hesitated. Nobody knew there had been a choice.</p><p>That may be why I remember it.</p><p>The most revealing decisions about culture are often too small for anyone else to see.</p><p>I had thought competition was useful because it made each of us pull harder.</p><p>At Google, I began to understand that a team asks something more difficult of ambitious people.</p><p>It asks us to become excellent without needing somebody beside us to become smaller.</p><p>I still like working around people who make me raise my standards.</p><p>I just no longer believe the purpose of their excellence is to tell me where I stand.</p><p>The best people I worked with eventually taught me something much harder than how to compete with them.</p><p>They taught me how much better the work became when I stopped needing to.</p><p>* * *</p><p><strong><em>P.S.</em></strong><em> A reliable Notion-to-Substack workflow needs more than copy and paste. Narrareach imports approved Notion pages into a publishing workflow where the writer can review the article, apply destination settings, and decide when it goes live. See how to </em><a href="https://www.narrareach.com/features/notion-to-substack"><em>import Notion articles into Substack.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd885a647238" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[At Amazon, I Stopped Being Proud Of How Much Dysfunction I Could Absorb]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/never-stop-writing/at-amazon-i-stopped-being-proud-of-how-much-dysfunction-i-could-absorb-41140957f625?source=rss-8c5aa3c99ed2------2"><img src="https://cdn-images-1.medium.com/max/1672/0*Wd2KU-BXKUGZEfYJ.png" width="1672"></a></p><p class="medium-feed-snippet">I thought being the person who could always figure it out was a strength. Eventually, it became part of the system.</p><p class="medium-feed-link"><a href="https://medium.com/never-stop-writing/at-amazon-i-stopped-being-proud-of-how-much-dysfunction-i-could-absorb-41140957f625?source=rss-8c5aa3c99ed2------2">Continue reading on Never Stop Writing »</a></p></div>]]></description>
            <link>https://medium.com/never-stop-writing/at-amazon-i-stopped-being-proud-of-how-much-dysfunction-i-could-absorb-41140957f625?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/41140957f625</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Wed, 19 Aug 2026 18:29:56 GMT</pubDate>
            <atom:updated>2026-08-19T18:29:56.147Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Stopped Letting On-Call Hide A Staffing Problem]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/illumination/i-stopped-letting-on-call-hide-a-staffing-problem-213265496398?source=rss-8c5aa3c99ed2------2"><img src="https://cdn-images-1.medium.com/max/1672/0*zcahxWuKt9WwFyxA.png" width="1672"></a></p><p class="medium-feed-snippet">The rotation kept the service alive. It also made an understaffed system look sustainable.</p><p class="medium-feed-link"><a href="https://medium.com/illumination/i-stopped-letting-on-call-hide-a-staffing-problem-213265496398?source=rss-8c5aa3c99ed2------2">Continue reading on ILLUMINATION »</a></p></div>]]></description>
            <link>https://medium.com/illumination/i-stopped-letting-on-call-hide-a-staffing-problem-213265496398?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/213265496398</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[on-call-management]]></category>
            <category><![CDATA[staffing-challenges]]></category>
            <category><![CDATA[operational-efficiency]]></category>
            <category><![CDATA[engineering-practices]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Sun, 16 Aug 2026 16:50:45 GMT</pubDate>
            <atom:updated>2026-08-16T16:50:45.597Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[At Google, I Stopped Believing Good Work Would Speak For Itself]]></title>
            <link>https://medium.com/@warstories/at-google-i-stopped-believing-good-work-would-speak-for-itself-6191693edfe3?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6191693edfe3</guid>
            <category><![CDATA[self-promotion]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[professional-growth]]></category>
            <category><![CDATA[recognition-workplace]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 23:46:23 GMT</pubDate>
            <atom:updated>2026-08-14T23:46:23.016Z</atom:updated>
            <content:encoded><![CDATA[<p>I wanted the work to be enough. In a company that large, someone still had to explain why it mattered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eRC558vvhZKCCb60.png" /><figcaption>Envelope with message about work and travel</figcaption></figure><p>During a review at Google, someone described a project I had spent months helping untangle.</p><p>They praised the launch, mentioned the engineers who had implemented the final version, and moved on. Nothing they said was wrong. The project had shipped. The engineers they mentioned had done excellent work. The outcome deserved to be celebrated.</p><p>What stayed with me was everything that had disappeared from the story.</p><p>Months earlier, two teams had disagreed about who owned the hardest part of the problem. The original design carried a dependency that looked harmless until we traced what would happen at scale. We spent weeks simplifying the approach, removing work, changing assumptions, and finding a version that would be easier to operate long after the people in the room had moved on to something else.</p><p>By the time the project became visible, most of the difficult work had already done its job.</p><p>It had made itself unnecessary.</p><p>I sat there listening to a perfectly accurate version of the story that barely contained me.</p><p>For years, I had believed good work should speak for itself.</p><p>That afternoon, I began to confront the obvious problem with the phrase.</p><p>Work cannot speak.</p><p>* * *</p><p>Earlier in my career, I considered this almost a matter of principle.</p><p>Do excellent work. Be useful. Solve difficult problems. Treat people well. Let the results create the reputation.</p><p>I distrusted the alternative because I had seen what self-promotion could become. Some people could stretch a routine contribution until it sounded historic. A modest improvement became transformation. Joining a project became leading it. Being present near an important decision somehow became evidence of having caused the outcome.</p><p>Engineering gave me a comfortable refuge from that kind of theater. Code either worked or it did not. Systems behaved according to what we had built, not what we claimed to have built. I liked the idea that substance could protect us from performance.</p><p>So I developed an instinctive suspicion of talking too much about my own work.</p><p>If I had to explain repeatedly why something I had done mattered, perhaps it had not mattered enough.</p><p>That belief sounded humble.</p><p>It took me a long time to see the pride hiding inside it.</p><p>* * *</p><p>The less flattering truth was that I wanted to be the kind of person whose value was so obvious that explaining it would be unnecessary.</p><p>I wanted recognition without having to ask for recognition.</p><p>I wanted other people to notice the difficult judgment, the quiet interventions, the decisions that reduced risk, and the work that prevented bad outcomes without requiring me to point at any of it.</p><p>There is a particular vanity in wanting to be discovered.</p><p>It feels nobler than self-promotion because you remain silent. But silence can carry its own demand: surely they should know.</p><p>Surely my manager remembers.</p><p>Surely the people making the decision understand what happened.</p><p>Surely someone will connect the outcome with the months of work that made it possible.</p><p>The word “surely” was doing a great deal of work.</p><p>I had called silence humility while quietly assigning someone else the responsibility of remembering me.</p><p>* * *</p><p>This became harder as my work became more senior.</p><p>Early engineering produces visible objects.</p><p>You write the code. You close the ticket. You launch the feature. Someone can point to a thing and say, “She built that.”</p><p>Senior work often produces conditions.</p><p>You ask a question that changes the plan before implementation begins.</p><p>You notice that two teams are solving different versions of the same problem.</p><p>You simplify an architecture before complexity becomes expensive.</p><p>You convince people not to launch something that looks impressive but creates a maintenance burden nobody has agreed to own.</p><p>You mentor an engineer until she no longer needs you in the room.</p><p>The outcome belongs to many people.</p><p>That is usually a sign the work is going well.</p><p>It also makes individual contribution harder to see.</p><p>Some of my best work became invisible precisely because it worked.</p><p>The bad project did not happen.</p><p>The unnecessary system was never built.</p><p>The conflict was resolved before it became an escalation.</p><p>The engineer I had helped grew into the person everyone later saw succeeding.</p><p>There is no dashboard for many of these things.</p><p>Absence is difficult to measure.</p><p>* * *</p><p>For a while, I blamed the organization for this.</p><p>It was tempting.</p><p>Large companies reward visibility, I told myself. People closer to leadership get more credit. Projects with clean metrics travel further. The person with the better story wins.</p><p>There was truth in some of that. Organizations are made of people, and people remember what they see. A launch with a clear number attached to it is easier to explain than months of preventing complexity. Work near senior leaders has more opportunities to become familiar. A project that concludes two weeks before review season will naturally be easier to remember than something quietly resolved eight months earlier.</p><p>But eventually I noticed something that weakened the comfort of my complaint.</p><p>Some of the people I dismissed as “good at visibility” were simply good at explaining what had happened.</p><p>They did not necessarily exaggerate.</p><p>They documented.</p><p>They connected decisions with consequences.</p><p>They made sure their managers understood the before and after.</p><p>They could describe the work in language that made sense outside the team that had lived through it.</p><p>I had treated that skill as slightly beneath me.</p><p>Then I was surprised when their work travelled further than mine.</p><p>* * *</p><p>The distinction I had failed to make was between boasting, visibility, and legibility.</p><p>Boasting makes yourself larger than the facts.</p><p>Visibility makes the facts available.</p><p>Legibility explains why those facts matter to someone who did not live through them.</p><p>I had bundled all three together and rejected the entire category.</p><p>That was convenient because it allowed me to avoid something I found uncomfortable: saying clearly where my judgment had changed an outcome.</p><p>I could write a design document describing every technical trade-off in extraordinary detail and still feel awkward writing three sentences about why my contribution had mattered.</p><p>That was not humility.</p><p>It was an inconsistency.</p><p>Humility does not require making the truth difficult to find.</p><p>* * *</p><p>Eventually I began thinking about the problem as translation.</p><p>Technical value often lives in one language.</p><p>Organizational decisions are made in another.</p><p>An engineer might say:</p><p>We removed a dependency from the critical path.</p><p>A director may need to understand:</p><p>Three teams can now ship independently.</p><p>An engineer might say:</p><p>We rejected the generalized abstraction.</p><p>The organization may need to hear:</p><p>We avoided committing several teams to maintaining infrastructure they did not need.</p><p>An engineer might say:</p><p>We changed the rollout strategy.</p><p>Someone outside the project may need to understand:</p><p>We reduced the chance that one failure could affect every customer at once.</p><p>Nothing dishonest has happened in the translation.</p><p>The meaning has been preserved.</p><p>My mistake was believing that translation cheapened the work.</p><p>Good translation does the opposite.</p><p>It allows the meaning to survive the journey.</p><p>* * *</p><p>Google made this especially obvious because competence was everywhere.</p><p>In a smaller environment, solving a difficult technical problem may naturally make someone stand out. In a company filled with people solving difficult technical problems, competence alone does not provide much context about why one contribution mattered more than another.</p><p>Everyone has a complicated project.</p><p>Everyone has a technical challenge.</p><p>Everyone can describe something that required intelligence and effort.</p><p>The useful question becomes more specific:</p><p>What changed because you were there?</p><p>That question initially made me uncomfortable because it sounded self-centered.</p><p>Over time, I realized it could be answered without making myself the hero.</p><p>Here was the situation.</p><p>Here was the constraint.</p><p>Here was the judgment required.</p><p>Here was the decision I influenced.</p><p>Here is what became possible afterward.</p><p>That is not self-promotion.</p><p>It is an accurate account of causality.</p><p>* * *</p><p>The change in my behavior was quieter than I expected.</p><p>I did not start posting victory laps after every project.</p><p>I started keeping better records.</p><p>When a difficult decision happened, I wrote down why it had been difficult.</p><p>When we removed scope, I recorded the complexity we had avoided rather than allowing the smaller result to look like smaller ambition.</p><p>When I helped another team unblock something, I documented the outcome rather than assuming everyone involved would remember six months later.</p><p>When someone I mentored became more independent, I stopped treating that disappearing dependence as evidence that I had done nothing.</p><p>I also started giving my manager better material.</p><p>Not praise.</p><p>Context.</p><p>What existed before?</p><p>What changed?</p><p>Which risk disappeared?</p><p>Which decision required judgment rather than execution?</p><p>Which outcome belonged to a team but depended on something I had specifically contributed?</p><p>This relieved my manager of a burden I had barely acknowledged.</p><p>I had spent years expecting one person to reconstruct my contribution from dozens of conversations, projects, documents, and memories while doing the same thing for everyone else.</p><p>Then I called the inevitable loss of detail politics.</p><p>* * *</p><p>There is still a danger here.</p><p>Once people understand that visibility matters, some begin optimizing for visibility rather than value.</p><p>They choose projects because executives will notice.</p><p>They attach themselves to successful work.</p><p>They produce elaborate narratives around ordinary contributions.</p><p>They become very skilled at describing motion.</p><p>I had seen enough of this to become suspicious of the entire practice.</p><p>But avoiding one vice does not automatically produce a virtue.</p><p>You can become so afraid of vanity that you make a virtue of disappearing.</p><p>That was closer to my mistake.</p><p>I thought understatement protected me from becoming boastful.</p><p>Instead, it occasionally made other people guess.</p><p>And when people guess, they do not always guess correctly.</p><p>* * *</p><p>The deeper lesson was not really about promotion.</p><p>It was about the strange expectation that quality should possess its own distribution system.</p><p>We believe good work will get noticed.</p><p>Good writing will find readers.</p><p>A good product will spread.</p><p>A good employee will be recognized.</p><p>A good relationship will survive without uncomfortable conversations because surely the other person knows how we feel.</p><p>Sometimes these things happen.</p><p>Often they do not.</p><p>Worth and visibility are different properties.</p><p>One does not automatically produce the other.</p><p>That is not necessarily evidence that the world is corrupt.</p><p>Sometimes it is simply evidence that other people are not inside our heads.</p><p>They cannot know what we refuse to communicate.</p><p>* * *</p><p>I still want the work to come first.</p><p>That part has not changed.</p><p>I would rather produce something valuable and describe it plainly than become brilliant at describing something ordinary. I still distrust empty visibility, inflated narratives, and the kind of career strategy that treats every interaction as an opportunity to accumulate credit.</p><p>But I no longer believe silence makes the work purer.</p><p>At Google, I stopped waiting for good work to speak for itself because eventually I understood what I had been asking it to do.</p><p>I had expected code, decisions, prevented failures, quieter systems, and other people&#39;s growth to carry my name into rooms I had never entered.</p><p>Sometimes they did.</p><p>Often they arrived without it.</p><p>Now I think the responsibility is simpler.</p><p>Do the work.</p><p>Tell the truth about what happened.</p><p>Do not make yourself larger than that truth.</p><p>Do not make yourself smaller than it either.</p><p>For years, I thought the second part was humility.</p><p>Eventually, I learned that humility does not require disappearing and hoping someone notices.</p><p>Sometimes humility is simply making the truth easy enough to find.</p><p>* * *</p><p><strong><em>P.S.</em></strong><em> If you are trying to understand which Substack Notes and articles brings subscribers, I have been using a clearer </em><a href="https://www.narrareach.com/features/subscriber-attribution-substack"><strong><em>Substack subscriber attribution</em></strong><em> workflow inside Narrareach.</em></a><em> It connects </em><a href="https://www.narrareach.com/"><em>Notes performance, article analytics, Substack traffic sources, and subscriber growth</em></a><em>, then helps turn the content that worked into follow-up posts. </em><a href="https://www.narrareach.com/features/subscriber-attribution-substack"><em>See how to track which Substack posts bring subscribers</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6191693edfe3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Stopped Saying “Customer Obsession” When We Had No Customer Evidence]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/illumination/i-stopped-saying-customer-obsession-when-we-had-no-customer-evidence-113055335459?source=rss-8c5aa3c99ed2------2"><img src="https://cdn-images-1.medium.com/max/1672/0*poKPDrr7OaH-8xRk.png" width="1672"></a></p><p class="medium-feed-snippet">A reflection on customer obsession, product judgment, and why teams must separate real customer evidence from persuasive internal opinions.</p><p class="medium-feed-link"><a href="https://medium.com/illumination/i-stopped-saying-customer-obsession-when-we-had-no-customer-evidence-113055335459?source=rss-8c5aa3c99ed2------2">Continue reading on ILLUMINATION »</a></p></div>]]></description>
            <link>https://medium.com/illumination/i-stopped-saying-customer-obsession-when-we-had-no-customer-evidence-113055335459?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/113055335459</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[customer-obsession]]></category>
            <category><![CDATA[customer-evidence]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Sat, 08 Aug 2026 17:03:36 GMT</pubDate>
            <atom:updated>2026-08-08T17:03:36.521Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[At Google, I Stopped Believing Performance Reviews Measured Performance]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/activated-thinker/at-google-i-stopped-believing-performance-reviews-measured-performance-930da971681a?source=rss-8c5aa3c99ed2------2"><img src="https://cdn-images-1.medium.com/max/1672/0*_pgI13j7EWla8jxx.png" width="1672"></a></p><p class="medium-feed-snippet">The work happened all year. The rating was shaped in a room I never entered.</p><p class="medium-feed-link"><a href="https://medium.com/activated-thinker/at-google-i-stopped-believing-performance-reviews-measured-performance-930da971681a?source=rss-8c5aa3c99ed2------2">Continue reading on Activated Thinker »</a></p></div>]]></description>
            <link>https://medium.com/activated-thinker/at-google-i-stopped-believing-performance-reviews-measured-performance-930da971681a?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/930da971681a</guid>
            <category><![CDATA[performance-reviews]]></category>
            <category><![CDATA[organizational-behavior]]></category>
            <category><![CDATA[employee-feedback]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 10:05:26 GMT</pubDate>
            <atom:updated>2026-08-07T10:05:26.555Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Stopped Building Features Just Because Early Customers Asked]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/illumination/i-stopped-building-features-just-because-early-customers-asked-f50271a2ebc1?source=rss-8c5aa3c99ed2------2"><img src="https://cdn-images-1.medium.com/max/1536/0*77nRNPk--vQ_U1xA.png" width="1536"></a></p><p class="medium-feed-snippet">Why Early Customer Feature Requests Should Not Become Your Roadmap</p><p class="medium-feed-link"><a href="https://medium.com/illumination/i-stopped-building-features-just-because-early-customers-asked-f50271a2ebc1?source=rss-8c5aa3c99ed2------2">Continue reading on ILLUMINATION »</a></p></div>]]></description>
            <link>https://medium.com/illumination/i-stopped-building-features-just-because-early-customers-asked-f50271a2ebc1?source=rss-8c5aa3c99ed2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f50271a2ebc1</guid>
            <category><![CDATA[customer-feedback]]></category>
            <category><![CDATA[feature-request]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[startup-advice]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Eunice]]></dc:creator>
            <pubDate>Thu, 30 Jul 2026 22:11:12 GMT</pubDate>
            <atom:updated>2026-09-03T05:31:26.978Z</atom:updated>
        </item>
    </channel>
</rss>