<?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 Govindarao Annigeri on Medium]]></title>
        <description><![CDATA[Stories by Govindarao Annigeri on Medium]]></description>
        <link>https://medium.com/@annigeri?source=rss-52685f1a70ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CR-vy8XA6a9Rc5qW1kWiyg.jpeg</url>
            <title>Stories by Govindarao Annigeri on Medium</title>
            <link>https://medium.com/@annigeri?source=rss-52685f1a70ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:13:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@annigeri/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[20 Years, 70 Believers, A Million Memories and Countless Learnings]]></title>
            <link>https://medium.com/@annigeri/20-years-70-believers-a-million-memories-and-countless-learnings-db18a811354c?source=rss-52685f1a70ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/db18a811354c</guid>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Govindarao Annigeri]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 16:55:41 GMT</pubDate>
            <atom:updated>2026-09-27T16:55:41.437Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, September 27th, I complete twenty years in the IT industry.</p><p>Twenty years. Seventy people who said yes. A few who didn’t. And a million memories and countless learnings that no job title, no offer letter, no LinkedIn badge can ever fully capture.</p><p>That young man who walked into his first corporate office two decades ago with big dreams, from humble roots, and a hunger louder than everything else put together, that was me — Govindarao.</p><p>Today I want to pause. Not to celebrate myself. But to celebrate the 70 odd human beings who believed in me before I fully believed in myself.</p><p>This is their story as much as mine.</p><p><strong>The Math That Humbled Me</strong></p><p>When I sat down and counted recently, here is what I found.</p><p>Fourteen companies gave me offers across twenty years. Each one put me through roughly five rounds of interviews on average. That means approximately seventy leaders, engineers, product managers, business heads, HR professionals, founders, directors, sat across a table, looked at me, asked me hard questions, and said yes.</p><p>Seventy people. Seventy moments of human judgment. Seventy acts of belief.</p><p>And then there are the ones who said no. I do not remember the exact number. But they exist. And honestly, they matter just as much.</p><p><strong>What an Interview Actually Is</strong></p><p>We get this wrong. Completely wrong.</p><p>We walk into interviews feeling judged. Feeling evaluated. Feeling like we are on trial. The rejection stings personally. The silence after the interview feels like a verdict on who we are.</p><p>But here is what twenty years taught me. An interviewer is not evaluating YOU. They are checking if you fit a specific role, at a specific moment, inside a specific organisation with its own culture and chaos. That is it.</p><p>Chanakya in the Arthashastra wrote about the art of identifying the right minister for the right role at the right time. Not the best person in the world. The right person for this kingdom, this season, this challenge. A brilliant warrior is useless if the kingdom needs a diplomat.</p><p>When someone did not hire me, they were not saying I was not good enough. They were saying: not this role, not this moment, not this kingdom.</p><p>That reframe changed everything for me.</p><p><strong>The Ones Who Said Yes</strong></p><p>Every single yes in my career came with a human being who took a bet.</p><p>Someone at my first company looked past all the rough edges and saw the hunger. Leaders across every org I joined trusted me with complexity I had never seen before. Each one handed me a bigger canvas and quietly said, we believe you can paint this.</p><p>None of these were automatic. Each one was a human being exercising judgment, taking a risk, extending belief.</p><p>I do not take a single one of those moments lightly. Not one.</p><p><strong>The Ones Who Said No</strong></p><p>Every rejection I faced pushed me somewhere better. Every door that closed made me sharpen something. My articulation, my depth, my confidence, my self awareness. The interviewers who said no were not my enemies. They were, in hindsight, my coaches.</p><p>There is a beautiful concept in Indian philosophy. Every experience, even painful ones, is a guru. The Sanskrit word guru literally means the one who dispels darkness. Some of my greatest gurus never hired me.</p><p>If you are reading this as a young engineer who just got rejected, please hear this. That person across the table was not rejecting your potential. They were protecting a fit. Keep going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Oz6pMEp1fpB-6dja.jpeg" /></figure><p><strong>What Twenty Years Actually Teaches You</strong></p><p>Learning never ends. This is the one thing I know with absolute certainty after two decades.</p><p>When I started I thought becoming senior would mean I knew enough. Then I became senior and realised I knew very little. Then I led teams and realised leadership was a completely different school. Then I sat in strategy rooms and realised that was yet another universe.</p><p>Every level reveals a new layer of what you do not know. And that is not a weakness. That is the design. The moment you think you have arrived is the moment you start going backwards.</p><p>Chanakya said, a person who thinks they have finished learning has finished growing. The tree that stops reaching for light starts dying.</p><p>Twenty years in and I am still reaching. Still unfinished. Still learning. And I would not have it any other way.</p><p><strong>What I Want Every Young IT Professional to Know</strong></p><p>Keep showing up. Even when the rejection pile is taller than the offer pile. Especially then.</p><p>And while you are on this journey, pay attention to everyone around you. Not just your manager. Not just the senior architect you admire. Your peer who thinks differently from you. The junior engineer who asks the question nobody else dared to ask. The intern who sees the product with completely fresh eyes. Every single one of them is carrying a lesson you haven’t learned yet. Twenty years taught me that wisdom has no hierarchy. It shows up in the most unexpected people at the most unexpected moments. Stay humble enough to receive it from anywhere.</p><p>Build your craft like a Mistry, the traditional artisan who never separates skill from soul. Code, architecture, product thinking, people skills, all of it is craft. Treat it that way.</p><p>Not every interviewer will like you. Some will love you instantly. Some will not connect. That is chemistry, not judgment. Do not internalise either one too deeply.</p><p>The offers will come to those who stay curious, stay humble, and keep sharpening. I have seen it happen too many times to doubt it.</p><p>And most importantly, remember the people who believed in you. Write their names down somewhere. Because on the days when doubt shows up, those seventy faces are the answer.</p><p><strong>To the Next Twenty</strong></p><p>I started with a village, a dream, and a fire in the belly that nobody could explain.</p><p>I am going into the next twenty with scars, wisdom, seventy believers etched into my heart, and a hunger that has somehow only gotten sharper.</p><p>To every person who ever said yes to me, thank you. You did not just give me a job. You gave me a chapter of my life.</p><p>To every person who said no, thank you too. You gave me direction I did not know I needed.</p><p>And to everyone reading this who is somewhere in the middle of their journey, keep going brother. Your seventy believers are out there. Some have already shown up. Some are still waiting to meet you.</p><p>The journey is the destination. Twenty years just taught me that more than anything else.</p><p><em>— Govindarao</em><br><em>Sakkarre Naganna | Leadership through an Indian lens</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db18a811354c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bond or Boundary? The Choice Every Organisation Makes Daily]]></title>
            <link>https://medium.com/@annigeri/bond-or-boundary-the-choice-every-organisation-makes-daily-5e872294f121?source=rss-52685f1a70ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e872294f121</guid>
            <dc:creator><![CDATA[Govindarao Annigeri]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 18:47:02 GMT</pubDate>
            <atom:updated>2026-06-06T18:47:02.894Z</atom:updated>
            <content:encoded><![CDATA[<p>Govindarao Annigeri | Leadership through an Indian lens</p><p>Chanakya, the most ruthlessly practical strategist ancient India ever produced, once said something that most corporate boardrooms have quietly forgotten.</p><p><em>“He is a true friend who does not forsake us in time of need, misfortune, famine, or war — in a king’s court, or at the crematorium.”</em></p><p>He wasn’t being sentimental. Chanakya never was. He was pointing at the one thing that makes kingdoms and organisations actually survive. Bonds that hold under pressure.</p><p>Walk into any corporate office today. What do you see? Org charts. RACI matrices. SLA documents. Ownership definitions. Escalation protocols. Boundaries. Everywhere. Drawn with the best of intentions. And quietly suffocating the very collaboration they were meant to enable.</p><p><strong>The Boundary Illusion</strong></p><p>Boundaries feel safe. They give us clarity , you own this, I own that. They give us cover, not my problem, outside my scope. They give us comfort, I did my part.</p><p>But here is what I have seen across nearly two decades of building platforms and managing teams. Boundaries define where your responsibility ends. <em>Bonds determine how far you will go anyway</em>.</p><p>The engineer who debugs a production issue at 2am , that is not in their boundary. That is their bond to the team. The product manager who fights for an engineer’s idea in a leadership review, not in the job description. Bond. The Director who picks up a junior developer’s call on a weekend because they sounded stuck, definitely not an OKR . <em>Absolutely a bond</em>.</p><p>And this is true at every level. Director to engineer. Engineer to product manager. Business ops to tech. Bonds don’t respect hierarchy. They transcend it.</p><p><strong>What Chanakya Knew That We Have Forgotten</strong></p><p>The Arthashastra is often read as a manual for statecraft. But read it slowly, and a deeper truth runs through it. Chanakya observed that the true character of a person, an ally, a minister, reveals itself not in times of abundance but in times of crisis. The test of a bond is not what happens in a review meeting. It is what happens when the system is down at midnight, when the roadmap is under fire, when the budget gets cut.</p><p>Btw, He also warned a bond where only one side carries the weight is not a bond. It is obligation. And obligation breeds resentment, not results.</p><p>This is the invisible disease in many organisations. We call it collaboration. But what we have actually built is a system of transactional obligation. I will do my part, you do yours, and we will meet at the interface called a meeting. That is not bonding. That is two services communicating over an API and calling it teamwork.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*XDdyU-QPQA0A927_.jpg" /></figure><p><strong>Bonding Across Every Level</strong></p><p>We make the mistake of thinking bonding is a top-down initiative. Leadership retreats. Team offsites. Town halls with free lunch. Those matter, yes. But the real bonding happens in unglamorous moments, across every level.</p><p>The senior engineer who reviews a junior’s code not to gatekeep but to genuinely teach. That bond outlasts any project. The PM who sits with the engineering team during a production crisis , not to track status, but to just be there. That changes the relationship forever. The ops team that proactively flags a customer pain point to the product team , without being asked, without it being in their OKR. That is bonding. The leader who remembers what a team member shared last month about a personal challenge, and checks in. Not because it is on the calendar. Because they actually care.</p><p>I remember once, a product manager was stuck. Not on execution, on thinking. The flow definition itself was broken. It was not my scope. But I sat with him, shared my perspective on the product angle, the business angle, and then walked him through the engineering reality of what he was imagining. And then we went further , connected the dots all the way to org strategy. He did not need someone from his boundary. He needed someone with a bond strong enough to show up uninvited.</p><p>Chanakya observed that a kingdom’s true strength is never its fortifications. It is the loyalty of the people inside them. The walls can be breached. Bonds cannot.</p><p><strong>The Uncomfortable Truth for Leaders</strong></p><p>You cannot mandate bonding. You can only create the conditions for it. Psychological safety. Shared purpose. Genuine curiosity about each other’s worlds. Not meeting time. Real time.</p><p>The highest performing teams I have worked with don’t have fewer boundaries. They have stronger bonds despite boundaries. The org chart exists. But it doesn’t govern how people actually work.</p><p>And here is the uncomfortable part. Organisations optimise for boundaries because bonds are hard to measure. You can put a boundary on a Confluence page. You cannot put a bond in a Jira ticket. So we keep building walls. And then wonder why every collaboration feels like a negotiation.</p><p><strong>Time Always Reveals It</strong></p><p>Go back five years. Think about the org structures, the team boundaries, the ownership debates from that era. How many of those boundaries still exist? How many even mattered?</p><p>Now think about the people. The bonds. Those people still pick up your call. Still root for your next move. Still show up when it counts.</p><p>Chanakya was right. Character and bonds reveal themselves over time. Not in the quarterly review. Not in the annual appraisal. In the moment of need. In the famine. In the war. In the production outage at midnight.</p><p><strong><em>Bonding always wins. Just give it time.</em></strong></p><p><em>— Govindarao</em> <em>Annigeri | Leadership through an Indian lens</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e872294f121" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership Coaching, Neti Neti: Why DON’Ts Matter More Than DOs]]></title>
            <link>https://medium.com/@annigeri/leadership-coaching-neti-neti-why-donts-matter-more-than-dos-c4f5ae74f552?source=rss-52685f1a70ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4f5ae74f552</guid>
            <dc:creator><![CDATA[Govindarao Annigeri]]></dc:creator>
            <pubDate>Mon, 05 Jan 2026 18:37:31 GMT</pubDate>
            <atom:updated>2026-01-05T18:37:31.747Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Govindarao Annigeri</em></p><p>In my early years as a leader, I genuinely believed coaching meant telling people what to do.</p><p>Do this.<br>Handle it this way.<br>Try this approach next time.</p><p>The intent was always right. I wanted my teams to move faster, avoid mistakes, and grow quicker than I did. But over time, something uncomfortable became clear to me:</p><p><strong>Most leadership damage does not come from bad intent.<br>It comes from excess intervention.</strong></p><p>That realisation fundamentally changed how I think about leadership coaching.</p><h3>Neti Neti: Leadership Through Elimination</h3><p>During my time at IIM Lucknow, I was introduced to a philosophical idea that stayed with me far beyond classrooms and frameworks: <strong><em>Neti Neti</em></strong>.</p><p>It means <em>“not this, not this.”</em><br>A way of arriving at truth by eliminating what something is <em>not</em>, until clarity remains.</p><p>Years later, I realised leadership works the same way.</p><p>Most leaders try to improve teams by adding:</p><ul><li>More advice</li><li>More frameworks</li><li>More reviews</li><li>More opinions</li></ul><p>But real leadership maturity often comes from knowing <strong>what not to do</strong>.</p><h3>Why DOs Feel Right (and Why They Don’t Scale)</h3><p>DOs feel good. They make leaders feel useful, relevant, needed.</p><p>When you tell someone exactly what to do, you feel in control. I’ve felt that too.</p><p>But at scale, DOs quietly create problems:</p><ul><li>They replace judgment with dependency</li><li>They slow decision-making</li><li>They turn leaders into invisible bottlenecks</li></ul><p>I’ve seen capable teams hesitate not because they lacked skill, but because they were subconsciously waiting for alignment from above.</p><p>That’s when it hit me:</p><p><strong>Good coaching does not create followers. It creates thinkers.</strong></p><h3>A Situation That Changed How I Coach</h3><p>I remember a phase where a critical system was under stress. Timelines were tight. Visibility was high. Pressure from above was real.</p><p>I knew the system deeply. I had context. I could see issues forming even before dashboards turned red.</p><p>The temptation to step in and “fix things quickly” was strong.</p><p>I joined design discussions early.<br>I shared suggestions, not as mandates, but as “thoughts.”<br>I reviewed details I normally wouldn’t.</p><p>Within days, something subtle changed.</p><p>Decisions slowed.<br>Engineers began waiting.<br>Conversations started ending with, <em>“Let’s check once.”</em></p><p>Nothing was broken.<br>But <strong>ownership quietly leaked upward</strong>.</p><p>That was my <em>Neti Neti </em>moment.</p><p>The system didn’t struggle because the team lacked capability.<br>It struggled because I forgot one critical DON’T:</p><p><strong>Don’t let your competence become the team’s dependency.</strong></p><p>When I stepped back deliberately, something interesting happened.<br>Decisions sped up.<br>Healthy disagreements returned.<br>Ownership settled back where it belonged.</p><p>The outcome wasn’t just delivery. It was confidence.</p><figure><img alt="Do? — Na Na — Don’t" src="https://cdn-images-1.medium.com/max/800/1*yKL7SfgAKtYijc4U_KJJJg.png" /></figure><h3>The Real Power of DON’Ts (From Experience)</h3><p>Over time, a few DON’Ts became very clear to me.</p><p><strong>Don’t jump in too early.</strong><br>Struggle, when safe, is not inefficiency. It is learning.</p><p><strong>Don’t become the smartest person in the room.</strong><br>If your answers end every discussion, growth has already stopped.</p><p><strong>Don’t speak for your people.</strong><br>Protection often turns into silencing. People grow when they own their voice.</p><p><strong>Don’t rescue teams during pressure.</strong><br>Short-term heroics create long-term fragility.</p><p><strong>Don’t reward noise over substance.</strong><br>Confidence is not competence. Delivery often speaks quietly.</p><p>Each of these DON’Ts came from mistakes I made with good intentions.</p><h3>Saying Less Is Also Leadership</h3><p>One of the most underestimated leadership skills is knowing when to say less.</p><p>As leaders, our words carry disproportionate weight.<br>A casual comment becomes direction.<br>A half-formed thought turns into execution.</p><p>I’ve seen well-meaning leaders unintentionally influence decisions in the wrong direction simply because they spoke too early or without enough context.</p><p>Sometimes leadership is not about clarity through words.<br>It is about restraint through silence.</p><h3>Doing vs Not Doing: The Balance That Actually Matters</h3><p>One important clarification I’ve learned over time is this: leadership is not about blindly choosing DON’Ts over DOs.</p><p>Different teams, different people, and different moments demand different responses. Sometimes stepping in early prevents damage. Sometimes saying more brings clarity. Sometimes doing more is exactly what the situation needs.</p><p>The real mistake leaders make is not in doing or not doing.</p><p>The mistake is in <strong>not pausing to think</strong>.</p><p>Instead of reflexively advising or reflexively holding back, leadership lies in asking: <em>Should I act here, or is this a moment where I consciously choose not to?</em></p><p>Leadership is not “do this, do that” or “don’t do this, don’t do that.”<br>It is judgement, restraint, and timing.</p><p>That pause.<br>That awareness.<br>That’s where leadership actually happens.</p><h3>Closing Reflection</h3><p>Leadership coaching is not about adding more rules, more advice, or more instructions.</p><p>It is about <strong>removing what gets in the way</strong>.</p><p>Removing ego.<br>Removing impatience.<br>Removing the need to always be right.</p><p><strong><em>Neti Neti. Not this. Not this.</em></strong></p><p>And somewhere in that subtraction, clarity quietly emerges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4f5ae74f552" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership, Dharma, and the Lost Art of Nishkama Karma.]]></title>
            <link>https://medium.com/@annigeri/leadership-dharma-and-the-lost-art-of-nishkama-karma-97e9ba95d392?source=rss-52685f1a70ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/97e9ba95d392</guid>
            <dc:creator><![CDATA[Govindarao Annigeri]]></dc:creator>
            <pubDate>Thu, 28 Aug 2025 18:38:32 GMT</pubDate>
            <atom:updated>2025-08-28T18:38:32.082Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Prelude: The Mirror Moment</em></strong></p><p><em>Over the past 10 years, I’ve often asked myself a tough question : have I really been leading for my people and my org, or have I been playing for myself?<br>It’s easy to get caught up in the noise, success metrics, designations, public praise. But when we really pause, really look in the mirror, it becomes clear that many of our so-called leadership decisions were more self-serving than we’d like to admit.<br>I’ve done this. You’ve probably done this. And that’s what this post is about, just pausing to reflect, a Mirror.</em></p><p><strong><em>The ‘I’ Behind Every ‘We’</em></strong></p><p><em>We love to say ‘we built this’, ‘we made it happen’, we are the best org etc. But in reality, how often is that ‘we’ just a smart disguise for ‘I’? <br>In tech especially, I’ve seen many leaders, including myself at times, optimise for visibility, for credit, for titles. We call it impact or outcome. But is it really?<br>Truth is, we build echo chambers where everyone claps, but nobody questions. We start believing our own narratives. That’s dangerous.</em></p><p><strong><em>Swa-Karma vs Nishkama Karma</em></strong></p><p><em>In the Gita, Krishna talks about Swa-Karma (doing your duty) and Nishkama Karma (doing it without expecting results).<br>But in our world today, duty often gets mixed up with outcomes. We chase roles, money, next jumps. Somewhere along the way, we forget that leadership is about the role we play in people’s lives, not just the results we chase.<br>Doing the right thing, even if nobody is watching or rewarding you, that’s the tough part and leadership is tough.</em></p><p><strong><em>What Chanakya Would Say</em></strong></p><p><em>Chanakya once said: ‘A king’s happiness lies in the happiness of his people.’<br>That applies to us too. If your team isn’t thriving, you aren’t leading. Period.<br>We can’t just focus on ourselves, our growth, our goals. If your people aren’t growing, no matter how high you rise, you’re falling in some way.</em></p><p><strong><em>The Choices We Make</em></strong></p><p><em>Leadership isn’t about one big moment. It’s about the small, everyday decisions we make:<br>- Did I take the credit or share it?<br>- Did I say yes to that opportunity for the sake of the team or myself?<br>- Did I listen or defend?<br>These choices shape us. They shape our legacy, far more than any award or role ever can.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c24gnnTd6fptNQoU" /></figure><p><strong><em>Time to Reflect</em></strong></p><p><em>So here’s my ask, to myself and to anyone reading:<br>- When was the last time you did a real check-in with yourself?<br>- Are you building others, or just building your own empire?<br>- Are you truly leading, or just moving up?<br>There’s no shame in having gotten it wrong. But there is courage in choosing to get it right from now.</em></p><p><strong><em>Closing Thought</em></strong></p><p><em>In the end, leadership isn’t about shouting the loudest. It’s about being remembered by those who quietly grew because of you.<br>We don’t need more big voices. We need more real ones.<br>Let’s lead with intent. Let’s lead with dharma.</em></p><p><em>- Govindarao Annigeri</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97e9ba95d392" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>