<?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 Rajeev Kumar on Medium]]></title>
        <description><![CDATA[Stories by Rajeev Kumar on Medium]]></description>
        <link>https://medium.com/@rajeevprasanna?source=rss-e5c37be32e0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gallo8TnPbsr1qOZ5IZL4g.jpeg</url>
            <title>Stories by Rajeev Kumar on Medium</title>
            <link>https://medium.com/@rajeevprasanna?source=rss-e5c37be32e0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:24:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rajeevprasanna/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[Learning from Nature: How to Handle Tough Situations at Work]]></title>
            <link>https://medium.com/@rajeevprasanna/learning-from-nature-how-to-handle-tough-situations-at-work-c97406cf2378?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c97406cf2378</guid>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Fri, 21 Jun 2024 15:25:13 GMT</pubDate>
            <atom:updated>2024-06-21T15:25:13.172Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Disclaimer: Generated content with ChatGPT and formatted with Grammarly</blockquote><h4>Nature as a Mentor</h4><p>Nature is a complex and diverse system that can offer us valuable lessons on resilience and strategy. One of the most important lessons we can learn from the natural world is how to confront and navigate the difficulties we encounter in our professional lives. The wild teaches us that challenges similar to those animals face in their daily survival can be met with strength, wisdom, and grace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/0*XWeU6Z0lnjKtFfCW" /></figure><h4>The Art of Facing Giants</h4><p>Imagine a situation where a small animal comes across a predator. The expected response from the smaller animal would be to run away immediately, which would signal its vulnerability and lead to its death. However, sometimes these smaller creatures choose to stand their ground and display a facade of bravery, causing the larger adversary to hesitate. This moment of hesitation can give the smaller animal a valuable opportunity to escape. This tactic, which combines courage and calm, demonstrates the importance of maintaining composure and confidence in the face of fear and uncertainty.</p><h4>Workplace Dynamics: Navigating the Jungle</h4><p>The modern workplace is full of challenges, much like the natural world. Leaders and team members may often feel like smaller animals facing larger predators, under great pressure to perform. Often, tasks seem impossible to achieve, deadlines too tight, and expectations too high to manage. However, the lesson we can learn from nature is that we should face challenges with confidence and clarity. When given a daunting project, it&#39;s essential not to give up under pressure. Instead, we should communicate effectively, stand firm, and explain our position. This approach diffuses tension and opens avenues for negotiation and understanding.</p><h4>The Power of Feedback</h4><p>Feedback is essential for improvement and growth despite sometimes being uncomfortable. Bill Gates beautifully captures this idea: &quot;<strong>We all need people who will give us feedback. That&#39;s how we improve.</strong>&quot; Being open to positive or constructive feedback indicates a willingness to evolve, better oneself, and consequently contribute to the overall success of the team or organisation. Embracing Discomfort for Growth</p><p>Satya Nadella, the visionary leader of Microsoft, encourages people to embrace discomfort as a sign of growth. He emphasises the importance of clear communication, particularly during times of uncertainty or challenge. This mindset of viewing discomfort not as a hindrance but as a catalyst for development is essential for anyone looking to thrive in their professional and personal lives.</p><h4>Conclusion: Lessons from the Wild</h4><p>The natural world has much to teach us about facing adversity with confidence, calmness, and an open mind to learning. By following the strategies used by animals in the wild, such as standing firm in the face of danger, clear communication, and being receptive to feedback, we can better navigate the complexities of the workplace with grace and effectiveness. This approach leads to professional success and personal growth and development, ultimately enriching our lives in meaningful ways.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c97406cf2378" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secret to Cracking Ambitious Goals]]></title>
            <link>https://medium.com/@rajeevprasanna/secret-to-cracking-ambitious-goals-a6c090e4ea2b?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6c090e4ea2b</guid>
            <category><![CDATA[goals]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Fri, 21 Jun 2024 11:13:48 GMT</pubDate>
            <atom:updated>2024-06-21T15:26:29.956Z</atom:updated>
            <content:encoded><![CDATA[<p>Here I learned a valuable secret to achieving any ambitious goals. All it takes is to split that goal into manageable small tasks and achieve them one after another. Making minor adjustments to daily routines, process will compound into a great result as it effect into achieving one step at a time.</p><p>Speaker explained how he could achieve A grade from c grade using the above approach and spoke about his achievements in learning rock climbing, pilot a flight, yarn the boulders, learning german, book reading etc. Even though every goal seems very ambitious and unachievable when you look at the end goal, but hitting one step at a time repeatedly will take you to the near to the goal post.</p><p>Even i have my own share of examples. Recently i joined a community where everyone set a 90 day challenge to achieve a goal of their own. Each member has to share three important tasks to do on a day to achieve the goal and share it with the community. At the end of the day, we all meet together to asess if the day is successful or not. Day is marked as successful if one completes all three tasks else no. It really results in making great progress towards the goal over the time and many of us achieved the desired goals. What seems impossible at start became possible as we reached the end of the challenge. This is truly a magical approach one can adopt to crack any goal.</p><p>Source: <a href="https://www.youtube.com/watch?v=TQMbvJNRpLE">https://www.youtube.com/watch?v=TQMbvJNRpLE</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6c090e4ea2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership blindspots]]></title>
            <link>https://medium.com/@rajeevprasanna/leadership-blindspots-0aed4bf15d0c?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/0aed4bf15d0c</guid>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Thu, 20 Jun 2024 13:16:10 GMT</pubDate>
            <atom:updated>2024-06-20T13:16:10.298Z</atom:updated>
            <content:encoded><![CDATA[<p>I came across an interesting TED talk which offered an interesting perspective on action fallacy and blindspots in identifying and celebrating good leaders.</p><p>Most of the times, we associate leadership qualities with people who</p><ol><li>Appear confident (regardless of their competence)</li><li>Speak more (regardless of what they speak)</li><li>Perpetually busy(regardless of what they are doing)</li></ol><p>This creates a toxic environment where wrong people are celebrated as leaders as they are attention seekers and move from one crisis to another crisis without much planning or readiness to handle situations. It discourages true leaders who work behind the curtain to prevent crisis.</p><p>We often associate Good story with Good leaders. But in reality good leadership is boring. They don’t have much crisis to handle as they work lot of time in planning to prevent crisis. These people don’t create drama or seeks attention. So not many people feel fascinated about their leadership eventhough they do the splendid job. It is our responsibility to ensure good leadership is recognised and celebrated to create a good work place and culture.</p><p>Stop giving attention to people who celebrate solving crisis. Start asking questions on why they couldn’t avoid crisis to understand their abilities in planning, listening to advices from team, anticipating potential fallouts etc.</p><p>Source: <a href="https://www.youtube.com/watch?v=DU06c7f9fzc">https://www.youtube.com/watch?v=DU06c7f9fzc</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0aed4bf15d0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cheatsheet on Kafka]]></title>
            <link>https://medium.com/@rajeevprasanna/cheatsheet-on-kafka-03944e4b55bf?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/03944e4b55bf</guid>
            <category><![CDATA[kafka]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Thu, 02 May 2024 02:22:24 GMT</pubDate>
            <atom:updated>2024-05-02T02:22:24.763Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Note: All text/images are captured from the internet and kept in the note for a quick read.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ML3agvzD9UqC9Z49F4lO5Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03944e4b55bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Secure Transaction System: Detecting and Handling Fraudulent Credit Card Use]]></title>
            <link>https://medium.com/@rajeevprasanna/designing-a-secure-transaction-system-detecting-and-handling-fraudulent-credit-card-use-594521417da9?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/594521417da9</guid>
            <category><![CDATA[system-design-concepts]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Sun, 07 Jan 2024 09:26:49 GMT</pubDate>
            <atom:updated>2024-01-07T09:26:49.793Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Problem: </strong>The scenario is about managing a platform that allows users to book various services using credit cards while ensuring a secure transaction environment and preventing credit card fraud. The system receives a feed of known fraudulent credit cards, and the main objective is to identify and reject any transactions attempted with these fraudulent cards. If a transaction has already been processed using a fraudulent card, the system must be capable of cancelling that transaction and notifying the affected users promptly. They should also be encouraged to rebook the service using a valid payment method. This article will focus on designing an architecture diagram that outlines a robust system capable of handling these requirements.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0Z7huRa75mAi2TLXa3zkw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=594521417da9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make my trip System design.]]></title>
            <link>https://medium.com/@rajeevprasanna/make-my-trip-system-design-9b76c81fe4a2?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b76c81fe4a2</guid>
            <category><![CDATA[system-design-concepts]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Wed, 27 Dec 2023 14:46:17 GMT</pubDate>
            <atom:updated>2024-01-01T17:16:21.060Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Functional Requirements:</strong></h3><p>1. Select source and destination with date to search for flights<br> 2. See the price for travel<br> 3. Select a flight with optional seat selection for booking a ticket<br> 4. Cancel booking<br> 5. Reschedule booking<br> 6. Filter and Sort options on results</p><h3><strong>Non Functional Requirements:</strong></h3><p>i. Availability<br> ii. Highly concurrent<br> iii. Scalable<br> iv. Security</p><h3>System Architecture:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-dr2liQYn7XTXO4k06_cw.png" /></figure><h3>API Design:</h3><p><strong>Location Suggestions</strong>:</p><ul><li>Endpoint: GET /locations/suggestions</li><li>Query Parameters: query (partial city or airport name)</li><li>Description: Returns a list of locations matching the search criteria to aid the user in selecting an accurate departure or arrival location.</li></ul><p><strong>Get Flights for Route</strong>:</p><ul><li>Endpoint: GET /flights/search</li><li>Query Parameters: from, to, date, duration, details</li><li>Description: Retrieves a list of available flights based on the specified route, date, and optional duration or details such as a specific airline or direct flights only. It should also include dynamic pricing information.</li></ul><p><strong>Book Ticket with Seat Selection:</strong></p><ul><li>Endpoint: POST /bookings</li><li>Request Body: Contains flightInstanceId, userId, seatSelection (with seat numbers), paymentDetails, and any other necessary information.</li><li>Description: Books a ticket for the specified flight and seat. It should handle payment processing and return a booking confirmation with the PNR and booking status.</li></ul><p><strong>Cancel Booking:</strong></p><ul><li>Endpoint: POST /bookings/{PNR}/cancel</li><li>Path Parameters: PNR (Passenger Name Record)</li><li>Request Body: Optional details if needed, like cancellationReason.</li><li>Description: Cancels the booking associated with the given PNR and processes any refunds or cancellation charges as applicable.</li></ul><h3>Data Modelling:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CVgQfvXjApOXECGRrGcqvQ.png" /></figure><p>Note: The above image has an incorrect relationship between payments and the Flight Model. It has to be removed.</p><h3>Estimates:</h3><h4>Estimating Storage:</h4><p>Assumptions:</p><ul><li>Number of flights per day: 10,000</li><li>Number of active days for booking retention: 365 days</li><li>Average size of a booking record: 1 KB</li><li>Average size of a flight record: 500 bytes</li><li>Average size of a user record: 500 bytes</li><li>Total number of users: 1 million</li></ul><p>Calculations:</p><ul><li>Storage for bookings per day: 10,000 bookings * 1 KB = 10,000 KB/day</li><li>Storage for bookings per year: 10,000 KB/day * 365 days = 3,650,000 KB/year</li><li>Storage for all flights: 10,000 flights/day * 365 days * 500 bytes ≈ 1,825,000 KB/year</li><li>Storage for all users: 1,000,000 users * 500 bytes = 500,000 KB</li></ul><p>Total Estimated Storage: Sum of all above.</p><h4>2. Estimating Bandwidth:</h4><p>Assumptions:</p><ul><li>Average number of daily users: 100,000</li><li>Each user makes an average of 10 requests per day</li><li>Each request/response pair averages 10 KB</li></ul><p>Calculations:</p><ul><li>Daily data transfer: 100,000 users * 10 requests/user/day * 10 KB = 10,000,000 KB/day</li></ul><h4>3. Estimating System Capacity:</h4><p>Assumptions:</p><ul><li>Peak concurrent users: 10% of daily users</li><li>Each user’s session lasts an average of 10 minutes</li><li>The system must support double the peak capacity for redundancy</li></ul><p>Calculations:</p><ul><li>Peak concurrent users: 100,000 daily users * 10% = 10,000 users</li><li>Requests per second at peak: (10,000 users * 10 requests) / (10 minutes * 60 seconds) = ~167 requests/second</li><li>Capacity with redundancy: 167 requests/second * 2 = 334 requests/second</li></ul><p>Final Estimates:</p><ul><li>The storage required would be the sum of the calculated values for bookings, flights, and users.</li><li>The required bandwidth would be enough to handle daily 10,000,000 KB of data transfer.</li><li>The system should handle at least 334 requests per second for redundancy.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b76c81fe4a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Entity Relation Diagram of BookMyShow]]></title>
            <link>https://medium.com/@rajeevprasanna/entity-relation-diagram-of-bookmyshow-76b9998bc0c0?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/76b9998bc0c0</guid>
            <category><![CDATA[system-design-concepts]]></category>
            <category><![CDATA[entity-relationship-model]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Sun, 24 Dec 2023 17:09:27 GMT</pubDate>
            <atom:updated>2023-12-24T17:09:27.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewZMF9e9sPV9d5U-3VG7Ag.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76b9998bc0c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you motivate your team to stretch on meeting deadlines?]]></title>
            <link>https://medium.com/@rajeevprasanna/how-do-you-motivate-your-team-to-stretch-on-meeting-deadlines-c9edc2946997?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9edc2946997</guid>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Wed, 08 Nov 2023 10:27:02 GMT</pubDate>
            <atom:updated>2023-11-08T10:27:02.400Z</atom:updated>
            <content:encoded><![CDATA[<p>Before asking the team to stretch on meeting deadlines, we need to assess the risk of missing timelines. I see the following critical factors to evaluate before making any decisions.</p><ol><li>Identify if the team understands requirements before taking up the project and committing to it.</li><li>Does the team have enough technical skills and domain expertise to handle this project?</li><li>Does the team have enough resources to deliver the project within the committed timelines, including consideration of employee leaves?</li><li>Are the requirements frozen after committing timelines? Identify if new features are added directly or in the form of feedback later without considering the impact on timelines. It is the most common cause of putting stress on the team to meet the timelines.</li><li>Does the project have enough intermediate checkpoints/milestones to assess if the project is on track or not? Projects without checkpoints are bound to fail.</li><li>Sometimes, projects are delayed due to unplanned long leaves by critical or senior employees due to emergencies. If the rest of the team is not skilled enough, it will derail the entire plan. We need to keep the risks in mind when allocating resources to the project at the planning time.</li><li>Another common cause of delays is external team dependencies. Project planning should clearly define external dependencies in a bound manner. Any delay in getting a resolution from external teams will delay the delivery timelines.</li></ol><p>After assessing all the points mentioned above, we need to understand the impact of failing to deliver before the committed timelines. There are times when business teams broadcast delivery timelines to customers to generate sales leads. In such a scenario, the team may not have much flexibility to push the timelines unless it is impossible to meet them. If the team made most of the progress and struggled to meet the last mile, the manager should assess if adding expertise from other teams will help the team or not. If yes, it could be an easy option without straining the team. Otherwise, negotiate with the business team to go for the incremental release without holding everything for one out. Many times, businesses agree to this proposal unless critical features are incomplete. Stretching beyond work hours should be considered if the team can meet the timelines by allocating reasonable extra work hours. Otherwise, committing to failure doesn’t help anyone. Engineering managers should ensure that tasks are well defined by understanding all risks.</p><p>Engineering managers should be transparent while requesting the team to stretch beyond work hours by explaining the reason for being in that situation, explaining the necessity to deliver within the timeline and rewarding people after meeting the timelines. Managers can give past such scenarios where the team ran for long hours and benefitted not just the team but the entire company, either in adding customers or bringing new revenues, etc. It will motivate the team to work hard and build trust in management. Management should not take this for granted and exploit employees without learning from their mistakes in planning, staffing and raising risks. If it does, it puts the entire team at the risk of losing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9edc2946997" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of Journaling: A Catalyst for Clarity and Growth]]></title>
            <link>https://medium.com/@rajeevprasanna/the-power-of-journaling-a-catalyst-for-clarity-and-growth-34593722035a?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/34593722035a</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[journaling]]></category>
            <category><![CDATA[habit-building]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Tue, 24 Oct 2023 14:02:27 GMT</pubDate>
            <atom:updated>2023-10-24T14:02:27.832Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Journaling has the power to transform our lives in ways we’ve yet to imagine. Let’s delve into its multifaceted benefits and how to harness them.</em></p><h4>Understanding Journaling</h4><p>At its core, journaling is about capturing our thoughts, ideas, and experiences on paper (or a digital medium). But what holds many back are misconceptions: the need for sophisticated templates or the belief that only groundbreaking ideas deserve a spot in our journals. Let’s debunk these myths. Everyone can journal, and anything can be chronicled. It’s about granting ourselves the freedom to express unfiltered, devoid of external judgments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Ga46Y7zA5u2IpqQ-" /><figcaption>Credits: yourvisualjournal.com</figcaption></figure><h4>The Benefits of Journaling</h4><ol><li><strong><em>Distanced Reflection</em></strong><em>:</em> Translating our inner monologue to text creates a separation, allowing us to observe thoughts objectively. This detachment allows introspection, offering a clearer lens to refine ideas.</li><li><strong><em>Mental Organization</em></strong><em>:</em> With minds often echoing repetitive thoughts, journaling serves as an external memory bank, ensuring no idea gets lost in the mental noise.</li><li><strong><em>Validation and Planning</em></strong><em>:</em> Be it personal disappointments, creative endeavours, or daily to-dos, the act of documenting sharpens clarity and direction.</li><li><strong><em>Decision-Making Assistance</em></strong><em>:</em> Facing dilemmas? Structured pros and cons in a journal can be the guidance you seek.</li></ol><h4>Practical Tips for Effective Journaling</h4><ol><li><strong><em>Prioritize Privacy</em></strong><em>:</em> A journal is your sanctuary. Let thoughts flow uninhibitedly. For those with privacy concerns, digital solutions or secure physical storage can be alternatives.</li><li><strong><em>Find Your Rhythm</em></strong><em>:</em> The best time to journal? Whenever it feels right for you. Initiation is more valuable than waiting for a “perfect” moment.</li><li><strong><em>Journey, Not Destination</em></strong><em>:</em> Begin with recent experiences and delve into emotions, learnings, and aspirations. Over time, curate prompts that resonate.</li></ol><p><em>As you weave journaling into your daily routine, it promises to be not just an act of recording but a mentor guiding you on life’s intricate journey.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34593722035a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding and Handling Venting Team Members: A Guide for Empathetic Leaders]]></title>
            <link>https://medium.com/@rajeevprasanna/understanding-and-handling-venting-team-members-a-guide-for-empathetic-leaders-f751b763375b?source=rss-e5c37be32e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f751b763375b</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Rajeev Kumar]]></dc:creator>
            <pubDate>Mon, 09 Oct 2023 10:06:56 GMT</pubDate>
            <atom:updated>2023-10-09T10:07:44.897Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When team members vent, it’s not just about the noise. It’s a call for understanding, guidance, and sometimes change.</em></p><h3>1. The Silver Lining of Venting</h3><p>When a team member chooses to vent in front of you, it might initially seem like a challenge. But look closer. This act of openness is a testament to the trust they place in you. It’s a sign that you’ve created a space where they feel safe to be vulnerable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/0*bRfS8Z4na9oiDOUS" /><figcaption>Credits: <a href="https://www.hrmagazine.co.uk/">https://www.hrmagazine.co.uk/</a></figcaption></figure><h3>2. The Two Faces of Venting</h3><p>Venting is a spectrum. On one end, you have individuals who let off steam and then move on. On the other, some are trapped in their emotions, struggling to find a way out.</p><p>Guided Conversations: For those who find it hard to move on, engage them. Use open-ended questions, devoid of judgment, to help them reflect and potentially find their own solutions.</p><h3>3. Digging Deeper: The Context Matters</h3><p>If the venting continues, it’s time to play detective. Dive into the context or environment that’s triggering these emotions.</p><p>Environment Analysis: Is it the workplace dynamics? Team interactions? External pressures? Understand the factors at play.</p><p>Behaviour Reflection: If changing the environment doesn’t help, it’s time for some introspection. Help them see the line between constructive venting and disruptive behaviour.</p><h3>4. The Path Forward: Actions to Consider</h3><p>If supportive measures don’t bring about change, it might be time for a different approach.</p><p>Behavioural Coaching: Offer sessions that focus on emotion management and effective communication.</p><p>Disciplinary Measures: As a last resort and in line with company policies, consider disciplinary actions.</p><h3>In Closing: An Empathetic Strategy</h3><ul><li>Open Communication: Foster regular one-on-one sessions.</li><li>Skill Building: Organize workshops on emotional intelligence and conflict resolution.</li><li>Feedback is Gold: Implement an anonymous feedback system.</li><li>Mental Health First: Provide access to counselling or mental health resources.</li></ul><p>Being an empathetic leader means leading with both heart and mind. It’s about understanding, guiding, and, when necessary, making the tough calls.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f751b763375b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>