<?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 Monish Koppa on Medium]]></title>
        <description><![CDATA[Stories by Monish Koppa on Medium]]></description>
        <link>https://medium.com/@monish.koppa?source=rss-b294ecefd357------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*t0ri0vvMeNmm-6ju</url>
            <title>Stories by Monish Koppa on Medium</title>
            <link>https://medium.com/@monish.koppa?source=rss-b294ecefd357------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:39:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@monish.koppa/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[The “Cry For Attention” Bias in the Workplace]]></title>
            <link>https://medium.com/@monish.koppa/the-cry-for-attention-bias-in-the-workplace-aee508652950?source=rss-b294ecefd357------2</link>
            <guid isPermaLink="false">https://medium.com/p/aee508652950</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Monish Koppa]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 20:16:30 GMT</pubDate>
            <atom:updated>2025-11-03T20:17:10.207Z</atom:updated>
            <content:encoded><![CDATA[<h3>The “Cry For Attention” Bias at Workplace</h3><p>Across my 15-year career — first as an individual contributor and later as an engineering manager — I’ve noticed a recurring workplace pattern. I informally call this the <strong>“Cry For Attention” </strong>Bias. It isn’t about complaining or emotional manipulation — it’s about visibility, communication, and how attention naturally flows to perceived urgency or distress.</p><p>Let’s explore this through a couple of stories.</p><h3>Ram vs. Shyam</h3><p>Ram and Shyam worked in the same engineering team.</p><ul><li>Shyam was introverted, quietly delivered high-quality releases, and rarely escalated issues.</li><li>Ram’s projects were noisier — bugs, blockers, escalations — and he often had to stretch to deliver.</li></ul><p>When it came time to recognize contributions, Ram received accolades and appreciation for his efforts and visible hustle, while Shyam’s work went largely unmentioned, despite his smooth and high-quality deliveries.</p><p>Was Ram a better engineer? Maybe, maybe not.</p><p><strong>But Ram communicated challenges early, frequently and visibly</strong>, keeping stakeholders in the loop. Shyam’s work was smooth — but largely <em>invisible</em>.</p><blockquote><em>In workplaces, </em><strong><em>effort and struggle tend to be more visible than frictionless execution</em></strong><em>.</em></blockquote><h3>Sita vs. Geeta</h3><p>Sita and Geeta also worked in the same team.</p><ul><li>Sita openly discussed her concerns, aspirations, and personal pressures.</li><li>Geeta stayed heads-down, delivered flawlessly, and rarely highlighted challenges or needs — even when prompted.</li></ul><p>At appraisal time, Sita was promoted, while Geeta wasn’t — despite having a stronger technical capability.</p><p>Again, the story is not about “complaining your way to growth.”</p><p>It’s about something simpler:</p><blockquote><em>People who communicate challenges and aspirations are </em><strong><em>noticed sooner</em></strong><em>.</em></blockquote><h3>Understanding the Bias</h3><p>This pattern is rooted in basic cognitive psychology. Let’s understand these.</p><p><strong>Salience Bias</strong></p><blockquote>We notice what is loud, visible, or urgent</blockquote><p><strong>Availability Heuristic</strong></p><blockquote>What we hear more feels more important</blockquote><p><strong>Communication Bias</strong></p><blockquote>Those who speak up are perceived as proactive</blockquote><p><strong>Loss-Aversion &amp; Risk Signals</strong></p><blockquote>A dissatisfied employee signals flight risk → more attention</blockquote><p><strong>Leaders Attention Theory</strong></p><blockquote>Leaders allocate more time where noise or risk appears</blockquote><p>Think of parenting — one child is quietly doing fine vs another constantly needing help. The second child naturally receives more attention — not out of bias, but instinct.</p><p>Workplaces are similar: <strong>urgency pulls focus</strong>.</p><h3>Moral of the story</h3><p>This isn’t a call to complain or dramatize problems.</p><p>It’s a reminder that in professional environments:</p><ul><li>Visibility matters</li><li>Proactive communication is a skill</li><li>Sharing blockers isn’t weakness, it’s operational clarity</li><li>Managers don’t celebrate silent success unless they see it</li></ul><p>Quiet excellence is admirable — but <strong>quiet excellence plus structured communication is unstoppable</strong>.</p><h3>Takeaways</h3><p>For high-performers who prefer staying low-key:</p><ul><li>Communicate progress and risks early</li><li>Share achievements regularly</li><li>Use 1-1s to talk about growth, not just tasks</li><li>Vocalize aspirations and support needed</li></ul><blockquote><em>“Silence often hides success.<br>Communication reveals it.”</em></blockquote><h3>Conclusion</h3><p>Performance isn’t just about delivery.<br>It’s <strong>delivery + communication + visibility</strong>.</p><p>Not crying — just <strong>being seen</strong>.</p><h3>Your Turn</h3><ul><li>Is this bias real in your experience?</li><li>Do quieter high-performers get overlooked?</li></ul><p>Share your views in the comments — I’d love to hear your perspective.</p><p>Thank you for reading!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aee508652950" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EC (Encumbrance Certificate) online for Karnataka]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@monish.koppa/ec-encumbrance-certificate-online-for-karnataka-6efb299ff25b?source=rss-b294ecefd357------2"><img src="https://cdn-images-1.medium.com/max/2600/1*nvhyVetcSGv4FYQxRgFUZg.png" width="3380"></a></p><p class="medium-feed-snippet">I live in Bangalore and was trying to obtain an EC (Encumbrance Certificate) online, but I couldn&apos;t find a step-by-step guide that was&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@monish.koppa/ec-encumbrance-certificate-online-for-karnataka-6efb299ff25b?source=rss-b294ecefd357------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@monish.koppa/ec-encumbrance-certificate-online-for-karnataka-6efb299ff25b?source=rss-b294ecefd357------2</link>
            <guid isPermaLink="false">https://medium.com/p/6efb299ff25b</guid>
            <category><![CDATA[encumbrance-certificate]]></category>
            <category><![CDATA[khata-transfer]]></category>
            <category><![CDATA[bangalore]]></category>
            <category><![CDATA[bbmp]]></category>
            <category><![CDATA[bbmp-property-tax]]></category>
            <dc:creator><![CDATA[Monish Koppa]]></dc:creator>
            <pubDate>Sun, 17 Aug 2025 05:37:02 GMT</pubDate>
            <atom:updated>2025-08-17T05:37:02.377Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Kafka Retry Management]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Please note: The article assumes that the readers are familiar with Apache Kafka</p><p class="medium-feed-link"><a href="https://medium.com/@monish.koppa/kafka-message-retry-management-19f4f8dec1ec?source=rss-b294ecefd357------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@monish.koppa/kafka-message-retry-management-19f4f8dec1ec?source=rss-b294ecefd357------2</link>
            <guid isPermaLink="false">https://medium.com/p/19f4f8dec1ec</guid>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[error-handling]]></category>
            <category><![CDATA[kafka-consumer]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[message-queue]]></category>
            <dc:creator><![CDATA[Monish Koppa]]></dc:creator>
            <pubDate>Sun, 20 Apr 2025 05:50:22 GMT</pubDate>
            <atom:updated>2025-08-17T05:46:06.464Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Message Acknowledgement in Apache Kafka]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Message acknowledgment in Apache Kafka is crucial for ensuring the reliability of message delivery between Kafka brokers (servers) and&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@monish.koppa/message-acknowledgement-in-apache-kafka-8daa8524c8e7?source=rss-b294ecefd357------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@monish.koppa/message-acknowledgement-in-apache-kafka-8daa8524c8e7?source=rss-b294ecefd357------2</link>
            <guid isPermaLink="false">https://medium.com/p/8daa8524c8e7</guid>
            <category><![CDATA[streaming]]></category>
            <category><![CDATA[kafka-consumer]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[apache-kafka]]></category>
            <dc:creator><![CDATA[Monish Koppa]]></dc:creator>
            <pubDate>Tue, 26 Sep 2023 18:59:31 GMT</pubDate>
            <atom:updated>2023-09-26T18:59:31.982Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Scaling Kafka to Support PayPal’s Data Growth]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/paypal-tech/scaling-kafka-to-support-paypals-data-growth-a0b4da420fab?source=rss-b294ecefd357------2"><img src="https://cdn-images-1.medium.com/max/932/1*qve4nQWHZngzlCFUnzIGKQ.png" width="932"></a></p><p class="medium-feed-snippet">Apache Kafka is an open-source distributed event streaming platform that is used for data streaming pipelines, integration, and ingestion&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/paypal-tech/scaling-kafka-to-support-paypals-data-growth-a0b4da420fab?source=rss-b294ecefd357------2">Continue reading on The PayPal Technology Blog »</a></p></div>]]></description>
            <link>https://medium.com/paypal-tech/scaling-kafka-to-support-paypals-data-growth-a0b4da420fab?source=rss-b294ecefd357------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0b4da420fab</guid>
            <category><![CDATA[apache-kafka]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[data-processing]]></category>
            <category><![CDATA[data-pipeline]]></category>
            <dc:creator><![CDATA[Monish Koppa]]></dc:creator>
            <pubDate>Thu, 07 Sep 2023 18:03:02 GMT</pubDate>
            <atom:updated>2023-09-08T13:34:14.339Z</atom:updated>
        </item>
    </channel>
</rss>