<?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 Mandar Kale on Medium]]></title>
        <description><![CDATA[Stories by Mandar Kale on Medium]]></description>
        <link>https://medium.com/@mandarakale?source=rss-80189a81122f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*x1uIbnpatnq1nSw2cHBVjA.jpeg</url>
            <title>Stories by Mandar Kale on Medium</title>
            <link>https://medium.com/@mandarakale?source=rss-80189a81122f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:49:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mandarakale/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 4 Ps of Changing a Job — Making an Emotional Decision an Objective One]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Should I move to another company? Should I take that internal role? Should I just stay where I am?</p><p class="medium-feed-link"><a href="https://mandarakale.medium.com/the-4-ps-of-changing-a-job-making-an-emotional-decision-an-objective-one-a28f4cd774e4?source=rss-80189a81122f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://mandarakale.medium.com/the-4-ps-of-changing-a-job-making-an-emotional-decision-an-objective-one-a28f4cd774e4?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a28f4cd774e4</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[internal-mobility]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Sun, 05 Jul 2026 15:14:04 GMT</pubDate>
            <atom:updated>2026-07-05T15:14:04.593Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[My Experimentation with Vibe Coding]]></title>
            <link>https://mandarakale.medium.com/my-experimentation-with-vibe-coding-fbbe22ad080e?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbbe22ad080e</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[experiment]]></category>
            <category><![CDATA[building-ideas]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Mon, 31 Mar 2025 14:49:37 GMT</pubDate>
            <atom:updated>2025-03-31T14:49:37.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ff1eJCG8fQFs8kcS" /><figcaption>Photo by <a href="https://unsplash.com/@ikukevk?utm_source=medium&amp;utm_medium=referral">Kevin Ku</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You know that feeling when you have a cool idea, but then the thought of coding, the time it takes and your other priorities get to you? Like, suddenly you’re buried in technical details, debugging some nasty unrelated problem and the fun kind of disappears? Yeah, I’ve been there. Recently, I stumbled upon something called “vibe coding,” and honestly, it’s been a fun and addiction both. It’s all about putting the creative spark first, and letting the technical stuff catch up by just chatting with the command prompt. Let me tell you more about it.</p><p><strong>Curiosity and staying latest</strong></p><p>Like most of us techies, I have been trying to catch up with the trends of tecvhnology and AI. Thats a lot of soaking up tech news and trends. I follow a bunch of YouTube channels, and that’s where I first heard about vibe coding. I listen to Matthew Berman regularly as he distills the latest in like 15–20 mins almost daily. Matthew Berman (check out his <a href="https://www.youtube.com/@matthew_berman">channel</a>), talked about <a href="https://youtu.be/5k2-NOh2tk0?si=-BPCNPGDofGIgaTQ">vibe coding</a> in a way that just clicked. He said it’s about focusing on the <em>feeling</em> of what you want to create, not just the nuts and bolts.</p><p>It was like a lightbulb moment. I always felt this gap between the cool stuff I imagined and the actual coding process. Vibe coding seemed like it could bridge that gap, by starting with the “vibe” and letting that guide the technical decisions.</p><p><strong>Trying It Out: Sketching Feelings, Not Just Code</strong></p><p>So, I decided to give it a shot. I started with a simple ideas and building stack end to end.</p><p>This became a few hours job for vibe coding with cursor.ai. I just had to tell the cursor agents to make things better and be specific about what I wanted to change. Within matter of minutes, I had websites built end to end and also databases created for my dummy projects.</p><p>This meant:</p><ul><li>Just typing on what I was thinking and typing it out in a simple english language</li><li>Playing around/Testing and asking to enhance what I want to change</li><li>Asking specifically what software tech stack I want to build things on</li><li>Being okay with trying weird, out-of-the-box solutions if they fit the vibe :)</li></ul><p>Honestly? It was way more fun. I wasn’t stressed about technical limitations. Rather one weekend I was obsessed with this and spend 4–5 hours straight and just kept on building.</p><p><strong>Putting It to the Test: My Website, </strong><a href="http://www.mandarkale.in/"><strong>www.mandarkale.in</strong></a></p><p>Thyen I decided to knock off one of the long pending items on my todo list, building my own website. Actually also wanted to host my own blogs, instead of putting them on medium (scapped the blog idea later). With simple instructions like get all my details form LinkedIn and Medium blogs, it was able to build a from my bucket list of creating my own webpage. Usually, that kind of thing takes me ages — planning, designing, coding. But using the vibe coding approach, I was able to do it in just a few hours!</p><p>The website also had Django backend for hosting blogs and I only scrapped the idea for hosting costs nothing else.</p><p>What delighted me the most is that, it was able to even push the artefacts out to Heroku to host. The only thing I has to do was linking the domain name to Heroku application.</p><p>There are other apps I am building and more on those later.</p><p><strong>My learnings</strong></p><p>Here are some of the takeaways-</p><ul><li><strong>Ideas are becoming reality faster.</strong> We’re getting to a point where we can actually build what we imagine or have been punting for bandwidth, without getting bogged down in technicalities.</li><li><strong>Coding is becoming less of a hurdle.</strong> With AI and new tools, the technical side is getting easier. What really matters is the creative vision. In other words coding is becoming a commodity.</li><li><strong>You still need some basics, but it’s getting easier.</strong> Knowing the fundamentals of coding is helpful, but the tools are becoming so much more user-friendly. I have been vibe coding for 15 days now and thinking models are making it better and better to just build things faster.</li></ul><p>The biggest change for me was shifting from “What can I build with my skills?” to “What do I want to build, and how can I make it happen?” That shift has made coding feel exciting again.</p><p>There are times when the models hallucinate and you have to be the tester in the process but the future might mean just reviewing the code and testing for us software engineers.</p><p>If you’re feeling stuck in the old ways of coding, or if you just want to add some fun back into the process, give vibe coding a try. Start small, focus on the feeling, and let the tech follow. You might just surprise yourself!</p><p>Go ahead, give it a vibe! The future of coding/building apps is all about chatting with models with clarity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbbe22ad080e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building High-Performance Team: Staying Composed When It Matters]]></title>
            <link>https://mandarakale.medium.com/building-high-performance-team-staying-composed-when-it-matters-9f6711bda2ad?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f6711bda2ad</guid>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[high-performance-culture]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Sat, 24 Aug 2024 12:46:36 GMT</pubDate>
            <atom:updated>2024-08-24T12:46:36.473Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LLhIMmaw3t60ZtuD" /><figcaption>Photo by <a href="https://unsplash.com/@arvindtelkar?utm_source=medium&amp;utm_medium=referral">Arvind Telkar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As leaders at all levels build high-performance teams, leaders must maintain their composure in all situations, most importantly the tough ones.</p><p>The leaders’ demeanour also reflects maturity and thoughtfulness. We, leaders, serve as role models and are constantly under scrutiny and observation. Our actions, whether intentional or not, directly or indirectly influence the learning and behaviour of our team members.</p><p><strong>Important: </strong>Leading by example is always in style.</p><p>In challenging situations, maintaining composure and clarity can be demanding, but it is crucial for leaders. Moments like team conflicts, project delays, or production incidents require a calm and collected approach.</p><p>In this post, I will share my rules for staying grounded and creating a positive impact in difficult circumstances.</p><p>May you be a manager or an individual contributor and technical lead, the following rules should help all leaders at all levels -</p><p><strong>Rule 1: Don’t React, Respond</strong></p><p>First and foremost,<strong> </strong>focus on yourself first. Take a deep breath. Of all the people and teams, make sure you as a leader don’t react and try to respond to the situation. The reaction is generally by <a href="https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow">system 1</a> of the brain and responding is by <a href="https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow">system 2</a>. These types of thought processes by the brain are explained by <a href="https://en.wikipedia.org/wiki/Daniel_Kahneman">Daniel K</a> in his book <strong>Thinking, Fast and Slow</strong>. When something goes wrong, try to respond intentionally with system 2 thinking. Thinking with System 2 in tough situations will bring out the best decisions and outcomes from everyone.</p><p>Bonus points if you can crack a joke or two to keep the mood light — it can defuse tension and reframe the situation positively.</p><p><strong>Rule 2: Fix forward (Focus on solution, not blame)</strong></p><p>Rather than hastily jumping to conclusions, focus on the present situation. Use all available information to find the best solution to the problem at hand. Analyze the situation to identify learning opportunities for yourself and your teams. The aim is to prevent similar mistakes in the future. This approach allows you to maintain a broader perspective and view the current situation as just another problem to be solved.</p><p><strong>Rule 3: Assume positive intent</strong></p><p>Regardless of the situation or the people involved, it’s essential to recognize that everyone’s intentions are generally positive. Embracing the concept of good intent allows us to remove personal biases from the equation. This shift in perspective encourages us to move beyond blame and finger-pointing towards a mindset of “it’s not my fault, but it’s my problem.”</p><h3>Conclusion</h3><p>There are many other strategies that leaders can employ, but I have found the above three rules to be particularly effective and easy to practice. I hope these tips help leaders out there maintain composure and drive positive outcomes in challenging situations.</p><p>I hope this helps the leaders out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f6711bda2ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[High-Performance Team: The Crucial Art of Checking the Ego]]></title>
            <link>https://mandarakale.medium.com/high-performance-team-the-crucial-art-of-checking-the-ego-518f50f25bab?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/518f50f25bab</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Sat, 09 Mar 2024 17:42:25 GMT</pubDate>
            <atom:updated>2024-03-09T17:42:25.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hu11cYwkVkIAzu-U" /><figcaption>Photo by <a href="https://unsplash.com/@denizen?utm_source=medium&amp;utm_medium=referral">Orkun Azap</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the realm of leadership, the ego can be both a formidable ally and a treacherous foe. While a healthy dose of self-confidence and belief in one’s abilities can propel a leader to great heights, unchecked ego can swiftly blind them to their shortcomings and undermine the success of their team. In this blog, we explore why and how leaders must cultivate self-awareness and humility to keep their egos in check, while also acknowledging the importance of a balanced team ego.</p><h3>The Pitfalls of Unchecked Ego</h3><p>Ego, when left unexamined, has a knack for distorting reality. It can lead a leader to overestimate their capabilities, dismiss valuable input from others, and make decisions driven more by personal agenda than the collective good. As a result, team dynamics suffer, innovation stalls, and trust erodes.</p><h3>Blinded by the Ego</h3><p>One of the most insidious ways ego blinds a leader is through the phenomenon of confirmation bias. When leaders are convinced of their infallibility, they become prone to seeking out information that confirms their preconceived notions while disregarding dissenting voices. This tunnel vision can lead to poor decision-making and missed growth opportunities.</p><p>Moreover, ego can cloud judgment by fostering a reluctance to admit mistakes or ask for help. Leaders who are unwilling to acknowledge their fallibility are doomed to repeat their errors, stunting their personal development and hindering the progress of their team.</p><h3>Cultivating Self-Awareness and Humility</h3><p>The antidote to unchecked ego lies in cultivating self-awareness and humility. Leaders must actively seek feedback from their team members and be open to constructive criticism. By acknowledging their limitations and vulnerabilities, they create an environment where others feel empowered to speak up and contribute their insights.</p><p>Practicing humility also involves recognizing and celebrating the contributions of others. A leader who acknowledges the collective effort behind their successes fosters a sense of camaraderie and mutual respect within the team. This, in turn, cultivates a culture of collaboration and continuous improvement.</p><h3>Balancing Individual and Team Ego</h3><p>While individual ego must be kept in check, it’s important to note that not all ego is inherently bad. A healthy level of self-confidence is essential for effective leadership, enabling individuals to inspire others, take calculated risks, and navigate challenges with resilience.</p><p>However, the key lies in ensuring that the ego serves the greater good rather than personal aggrandizement. Leaders must prioritize the success of the team above their ambitions, fostering a culture where collective achievements are celebrated and individual accolades are secondary.</p><blockquote>A simple thing to keep in mind is collective team ego should be greater than an individual ego at all times.</blockquote><h3>Conclusion</h3><p>I wrote about the importance of a <a href="https://mandarakale.medium.com/high-performance-team-building-a-feedback-driven-culture-39d6e71e13b6">feedback-driven culture</a> for nurturing a high-performance team. In the complex leadership landscape, checking the ego is not merely a nicety — it’s a necessity for long-term success. Leaders can steer their organisations towards greater innovation, collaboration, and collective achievement by cultivating self-awareness, humility, and a balanced perspective on individual and team ego.</p><blockquote>As the adage goes, it’s NOT about being the best in the team, but about bringing out the best in the team.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=518f50f25bab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[High-Performance Team — Tough Love]]></title>
            <link>https://mandarakale.medium.com/high-performance-team-tough-love-f66bb1ee1d5e?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f66bb1ee1d5e</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Sun, 21 Jan 2024 06:59:49 GMT</pubDate>
            <atom:updated>2024-01-21T06:59:49.061Z</atom:updated>
            <content:encoded><![CDATA[<h3>High-Performance Team — Tough Love</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ttJn5si2djC4rZbk" /><figcaption>Photo by <a href="https://unsplash.com/@pavement_special?utm_source=medium&amp;utm_medium=referral">Riccardo Annandale</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This blog is all about balancing care, empathy, recognition, and criticism. Effective leadership goes beyond just delegating tasks and giving direction. It involves building a high-performance team that is capable of achieving outstanding results. However, building such a team requires a delicate balance between caring for your team members, building empathy, recognizing their efforts, and providing constructive criticism when needed. ​​We often consider being supportive, empathetic, and acknowledging our team’s achievements as the markers of good leadership. However, the other side of the coin — offering constructive criticism and feedback — is equally important in building a high-performance team.</p><p>At times, being a leader requires showing a tough-love approach to your team members.</p><h3>What is tough love in leadership?</h3><blockquote>This means that you recognise people for achievements and hold them accountable for their actions or lack of action, without compromising on your care for them.</blockquote><p>DON’T BE NICE; BE KIND!</p><p>If we parallel this with parenting, ‘tough love’ is often seen as an approach where parents combine warmth and understanding with firm boundaries and rules. Similarly, in the corporate world, ‘tough love’ merges professional respect with a performance-driven approach, helping the teams reach their full potential and beyond.</p><p>It starts by <strong>clearly setting expectations</strong>, defining responsibilities, and agreeing on measurable <a href="https://mandarakale.medium.com/goal-setting-demystified-b8c665264fb3">goals</a> (SMART Goals). The team and its members need to have a clear understanding of what is expected of them, what their roles and responsibilities are, and how their performance will be evaluated.</p><p>Recognition can be in the form of individual feedback, rewarding individuals, or even the team as a whole if they have exceeded their set targets.</p><p>However, it is equally important to provide constructive criticism. It can be challenging as it can be uncomfortable for both the leader and the team members. However, it is essential to identify areas of improvement and provide feedback in a specific, clear, and non-judgmental way. This will enable team members to take the feedback positively and work towards improving their performance.</p><p>Creating a high-performance team requires building an inclusive culture that fosters responsibility, accountability, and continuous learning. Such a culture challenges the team members to stretch their abilities, innovate, and scout for constant improvement areas. However, fostering this culture needs a leader who is not afraid to show ‘tough love’.</p><p>Often, true leadership is characterized by a leader’s ability to show this ‘tough love’. It may be challenging or uncomfortable, but it is often necessary. Leaders who take the approach of ‘tough love’ are not afraid to push their teams harder, demand more from them, and insist on a higher standard.</p><p>Don’t misconstrue tough love as harshness or absence of empathy though. It is about being enablers, not just enforcers. Being honest about performance lag, creating a clear vision and expectations, and pushing employees beyond their comfort zones are the bricks in the wall of what we call ‘tough love’. It is the fuel that drives the engine of high-performance teams.</p><p>‘Tough love’ in leadership is about valuing the journey of growth more than a moment of comfort, as far as teams are concerned. A real leader aims at nurturing this growth, even if it means being tough today for a brighter, more successful tomorrow.</p><h4>In conclusion, effective leadership requires setting clear goals, acknowledging achievements, and providing constructive feedback through radical candor. That&#39;s leaders’ tough love!</h4><h3>How can we action it in the day-to-day?</h3><ol><li>Create measurable goals for everyone — Get out of your comfort zone — set stretch goals (for yourself and your teams)</li><li>Celebrate wins often and recognise the outcomes</li><li>Be radically candid in providing feedback and raising the bar. DO NOT beat around the bushes!</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f66bb1ee1d5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[High-Performance Team - Building a feedback-driven culture]]></title>
            <link>https://mandarakale.medium.com/high-performance-team-building-a-feedback-driven-culture-39d6e71e13b6?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/39d6e71e13b6</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[feedback-culture]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Sun, 24 Sep 2023 06:47:25 GMT</pubDate>
            <atom:updated>2023-09-24T06:47:25.206Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ScmihTa9igLRpaMo" /><figcaption>Photo by <a href="https://unsplash.com/@blakewisz?utm_source=medium&amp;utm_medium=referral">Blake Wisz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote><strong>TLDR: Feedback-driven culture is pivotal in retaining talent, improving performances, and driving winning results. If you want to improve or know more, read on!</strong></blockquote><p>In the knowledge industry, most of the personal development or personal growth is driven by a feedback loop from the rest of the system. There are other obvious factors like business outcomes and opportunities but even when these are present, growth happens only when there is a feedback loop.</p><p>This post is for everyone in the knowledge industry and for leaders to create this culture of being feedback-driven at every point in the system. The feedback-driven culture I am referring to here includes the people and the system.</p><p>I already wrote about <a href="https://mandarakale.medium.com/performance-management-shift-from-a-black-box-to-a-white-box-8334614d7626">performance management</a> and <a href="https://mandarakale.medium.com/goal-setting-demystified-b8c665264fb3">goal setting</a> in my previous posts and this post is about being more feedback-driven. Feedback is an important part of your performance management. This also helps to re-calibrate anything going wrong in the expectation setting and goal setting in performance management.</p><p>Feedback generally has a negative connotation but I will elaborate on all the types of feedback to uncover that feedback is not necessarily only negative. As you will see, two out of the three below are positive in nature. Let us go deeper.</p><h3>Types of feedback</h3><p>Knowingly or unknowingly, planned or unplanned, whatever it is, all the systems have the following three types of feedback.</p><ul><li>Recognition feedback</li><li>Growth feedback</li><li>Performance feedback</li></ul><p>When anyone gets feedback from the system, it can also be categorized as one of the above.</p><h4>Recognition feedback</h4><p>This is a positive feedback. In a common workplace, this tells you what is going well and how an individual is meeting expectations and sometimes going above the expectations. So overall a positive reinforcement to know what she needs to continue doing or do more of.</p><p>This can come from customers, peers, managers, etc.</p><h4>Growth feedback</h4><p>This is another positive feedback. Growth feedback is for people who are meeting the expectations of the current role and have the potential to do more. The potential could have been displayed before from the previous outcomes of the person.</p><p>Generally, this comes from the fact that — there is a bigger opportunity and the individual can do more to seek and deliver on the opportunity.</p><p>Recognition feedback and growth feedback have very fine lines as they can come together in some cases. After giving recognition feedback, a manager could give you growth feedback knowing that there is potential and opportunity both left untapped.</p><p>This can again come from a customer asking for more features or enhanced features, peers during discussions, and could come from a manager if they are close to the current outcome.</p><p>Growth feedback can open new possibilities and be directly tied to an individual’s learning and growth by the role/responsibilities.</p><h4>Performance Feedback</h4><p>This is the only feedback that talks about the gaps in the current role expectations and the current performance of the individual. This may sound negative or more based on the gaps but this is an important part of the process of learning and growing.</p><p>I have elaborated in my <a href="https://mandarakale.medium.com/performance-management-shift-from-a-black-box-to-a-white-box-8334614d7626">Performance Management</a> post previously that Performance Feedback comes as a third step after expectations setting and goal setting.</p><p>Performance feedback should be quick (like a minute-long conversation) and timely. Collate all the performance feedback and deliver during the formal one-to-one setting but make sure this should not be a surprise. Performance feedback done right, can have a tremendous impact on raising the performance bar for the individual.</p><p>This has a multiplier effect as the performance bar is raised, it becomes a gold standard for others to follow, business is benefiting and on top of all the individual is feeling fulfilled.</p><h3>Receiving Feedback</h3><p>All these feedbacks are also applicable for everyone in the organization including leaders and managers. We have to lead by example when it comes to seeking feedback and working on the feedback. Even if you don’t mean to work on the feedback that someone provided, checking back on the feedback is extremely important. All of us need to remember, “You are not perfect, no one is!”. Receiving feedback gracefully makes you humble. Receiving feedback is another big topic in itself. Probably a topic for the future to write on.</p><p>The more we, leaders and managers lean on understanding and improving feedback, the better the culture you would be setting in your organization and driving winning results.</p><p>I hope this helps a few of my readers out there. Happy learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39d6e71e13b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Goechala Trek and my life lessons]]></title>
            <link>https://mandarakale.medium.com/the-goechala-trek-and-my-life-lessons-9c902f2e7052?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c902f2e7052</guid>
            <category><![CDATA[my-life-lesson]]></category>
            <category><![CDATA[trekking]]></category>
            <category><![CDATA[goechalatrek]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Sun, 11 Jun 2023 08:22:41 GMT</pubDate>
            <atom:updated>2023-06-11T08:22:41.868Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog, I want to highlight my life lessons so I will start with that first. Though this trek was very draining and challenging, every moment of it was worth it for me — I have added a little bit about the trek itself but take it with a grain of salt.</p><h3>My life lessons</h3><p>Trekking can be an enlightening experience that teaches a lot about life. It can help us become more self-aware, understand our boundaries and limits, and learn important life lessons that can help us through various situations in our lives. This was my best, yet very challenging trek. Here are some life lessons that I learned/re-learned from this trek–</p><h3>Lesson 1: Preparation — the journey from SpO2 64 to 94</h3><blockquote><strong>Preparation trumps pressure!</strong></blockquote><p>Last year around the same time we trekked <a href="https://uttarakhandtourism.gov.in/gangotri-gaumukh-tapovan">Gowmukh Tapovan</a>. When on top, my SpO2 level was 64. Yes, 64! I could not enjoy the trek when we were at the summit and so I decided to make sure this year I was prepared to take on the challenge.</p><p>Since the time I came back last year, I have rarely missed my workout. I have gotten into a more healthy routine. Due to all the preparation during the last year and before the trek, I really enjoyed this trek and every day of it. The discipline I got into helping me be fit and maintain a SpO2 of 94 throughout the trek.</p><blockquote><strong>Bringing this lesson back to our day-to-day life, I re-learned the importance of preparing for whatever you are set to do.</strong></blockquote><h3>Lesson 2: One step at a time and one day at a time</h3><blockquote><a href="https://www.azquotes.com/quote/543445?ref=one-step-at-a-time"><strong>You don’t have to see the whole staircase, just take the first step.</strong></a><strong> — Martin Luther King, Jr.</strong></blockquote><p>Trekking requires a steady pace and a regular rhythm. It’s important to remind ourselves that success is not always sprinting but being consistent in our efforts. Just like in life, taking things one step at a time and focusing on the task at hand can make a big difference in achieving our goals. During the trek, my focus was always on the next step and doing the best I could to take that step right. There were days when we trekked/walked for 25kms (~30K steps). Any wrong step can spoil the entire trek and how you go about it. Just making sure you are focusing on the current task/step helps a lot. All of us on the trek were looking down and planning for the next best step possible. During this trek, we experienced all the weather conditions: heat, heavy rains, cold, snowfall, and heavy winds. It is all about just taking that next step.</p><blockquote><strong>In real life, we spend a lot of time thinking about the past, or too much in the future. This lesson, I extended to my life by just focusing on one day at a time. Do your best at each and everything that comes your way just at that moment.</strong></blockquote><h3>Lesson 3: Everything is temporary — more importantly pain</h3><p>Trekking comes with its own set of challenges, such as steep inclines, harsh weather conditions, and exhaustion. During this trek, there were times when it was raining heavily while walking/trekking in the zone of leeches. During other times, you are having a steep climb with heavy rain or hot sun on your head. You really feel like you are done. Then you take a 5 mins water break, have a good laugh on a few poor jokes and you are good to go.</p><p>These challenges are temporary, and pain eventually fades away. It teaches us the importance of resilience, grit, and determination in pushing through tough times in life. It also helps us realize that every situation is temporary and that there’s no need to hold on to difficult times by remembering those.</p><blockquote><strong>In real life also we need to understand that the situation that we all are in is temporary. Howmuchever low (or high) we feel, we all are going to see change. The pain is going to go away, just becoming a memory one day.</strong></blockquote><h3>Where is Goechala?</h3><p>The <a href="https://en.wikipedia.org/wiki/Goecha_La">Goechala</a> trek is one of the most popular treks in the Indian state of Sikkim. Located in the Kanchenjunga National Park, the trek takes you through some of the most breathtaking Himalayan landscapes, including dense forests, alpine meadows, and glacial lakes.</p><p>The trek starts from Yuksom, a small town in West Sikkim, and takes about 10 to 12 days to complete. From Yuksom, the trail leads you through dense rhododendron forests, where you can spot a variety of birds and animals. As you ascend higher, the trail opens up to stunning views of snow-capped peaks and deep valleys.</p><p>After several days of trekking, you reach the Goechala Pass, which is located at an altitude of 4,700 meters. From here, you can see some of the highest peaks in the region, including Mount Kanchenjunga, the third-highest peak in the world. The view from the pass is truly spectacular and is one of the highlights of the trek.</p><h3>Our trek</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_1AcGndLtIBOaZywd-yWEA.jpeg" /><figcaption>Getting ready for the trek!</figcaption></figure><p><strong>On the first day,</strong> we started from Yuksom, and on the first day trekked till Bakhim. The valley view from Bakhim&#39;s stay was very beautiful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gVHNPlNZbaP7vVzp" /><figcaption>Best friends in Bakhim :)</figcaption></figure><p><strong>The second day</strong> was a little easy from Bakhim to Tshoka.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X708MhXpm0Fd1GHr" /><figcaption>Our campsite in Tshoka</figcaption></figure><p><strong>On the third day,</strong> we went to Djongri. The next day morning about 3:30 am we went to Djongri Top to see the viewpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SGmP_y_GkWD8e_rw" /><figcaption>Morning sunrise from the Djongri Top</figcaption></figure><p><strong>Forth day</strong> was from Djongri to Thansing. If you trek a few meters from Thansing base camp, there is a point to see Kanchanjunga Peak if the weather is good.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*Rz0KG307HyBlSH7i" /><figcaption>Posing in front of the Kanchenjunga Peak</figcaption></figure><p><strong>Fifth-day</strong> early morning at about 1:30 am, we went from Thansing to the Goechala viewpoint 1 summit. We came back to Thansing at around 1 pm. Unfortunately, the view from the top was not clear due to the bad weather.</p><p>The Goechala trek is a challenging trek, however, the breathtaking views and the sense of achievement you get after completing the trek make it all worthwhile. If you’re looking for an adventure in the Himalayas, the Goechala trek is definitely worth considering.</p><h3>Some stats</h3><p>If we add up the distances walked on each day of the Goechala trek, it comes out to a total of 112.5 km:</p><ul><li>Sunday — 17.1 km</li><li>Monday — 3.6 km</li><li>Tuesday — 12.2 km</li><li>Wednesday — 15.2 km</li><li>Thursday — 20.4 km</li><li>Friday — 24.8 km</li><li>Saturday — 19.2 km</li></ul><p>Over the course of 7 days and 6 nights, we covered a wide range of terrains, from dense forests to alpine meadows and glacial lakes. The trek’s highlight is reaching the Goechala Pass, which stands at an altitude of 4,700 meters and provides stunning views of the snow-capped Himalayan peaks.</p><p>As with any trek, it’s essential to stay well-prepared and ensure that you have all the necessary equipment and supplies. It’s also crucial to pace yourself and take things one day at a time. By the end of the 7-day trek, trekkers will have walked an impressive distance and accomplished a remarkable feat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*IHEaEyQ0KSesNZQD8BRVqA.png" /><figcaption>Our 112.5 KM Walk in 7 days</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c902f2e7052" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Goal setting demystified]]></title>
            <link>https://mandarakale.medium.com/goal-setting-demystified-b8c665264fb3?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8c665264fb3</guid>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[high-performance-culture]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Sun, 27 Nov 2022 06:21:55 GMT</pubDate>
            <atom:updated>2022-11-27T06:21:55.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L_BgwcBAi-MFCyLv" /><figcaption>Photo by <a href="https://unsplash.com/@javaistan?utm_source=medium&amp;utm_medium=referral">Afif Ramdhasuma</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I wrote a little bit already about types of goals and SMART goals in <a href="https://mandarakale.medium.com/performance-management-shift-from-a-black-box-to-a-white-box-8334614d7626">this</a> blog. Below I am answering some of the basic questions about goal-setting and how to go about it. This write-up will summarise my ways of approaching goal setting and career development. So let’s begin-</p><h3>What is a goal?</h3><p><strong>A goal is a highlight of your career for the year if you achieve it. </strong>What is the <strong>highlight of the year</strong>? — It is quite self-explanatory but here is some elaboration — anything that you can feel proud about when you look back on the year and completing this added significant value to your professional career. Another way to see this is, can you boast about accomplishing it? Can you add it to your resume/portfolio? Can you talk about it in the next interview (yes, I mean it)?</p><h3>Why should we set a goal?</h3><p>Setting the goal will give you the (most sought) clarity on where are you heading for the business and for your own career.</p><p>At the heart of the high-performance culture, is to have each team member clear direction (aka goals). Generally, we do the goal-setting for the year and then keep refining those goals for the rest of the year on a regular basis. What’s interesting is that the goal-setting and check-in process is very much undermined across the engineering/tech community. So I decided to write down my framework of goals and how managers, leaders, and engineers can approach it.</p><h3>What is a SMART GOAL?</h3><p>By definition, SMART stands for <strong>S</strong>pecific, <strong>M</strong>easurable, <strong>A</strong>chievable, <strong>R</strong>ealistic, and <strong>Time-bound</strong>. To create a good goal — one just needs to make sure the goal is <strong>Measurable</strong> and <strong>Time-Bound, the </strong>rest of the things will fall in place. The reason to prioritize these two is, as soon as you make a goal measurable and time-bound, it is very difficult to miss the other aspects like specific, achievable, and realistic. If the answer to the goal completion is a binary “yes/no” then the goal is a measurable goal. Any elaboration needed for answering the goal completion means the goal needs more tuning.</p><p>Some examples of making a goal SMART are -</p><p>Ex 1: Moving from “I want to learn React js framework” to “I want to learn React js framework and have 2 open source contributions by end of Q4”</p><p>Ex 2: Moving from “I want to release XYX to be GA” to “I want to release XYZ to be GA with 90% unit tests, no P0/P1s in prod, 80% e2e happy path automation”</p><h3>What are the milestones/subtasks?</h3><p>This is <strong>how you achieve your goals</strong>. To be precise, 3–5 steps/tasks in each goal that will help you to get to your goal. Not a laundry list but as measurable, and time-bound as possible.</p><h3>What are the types of goals?</h3><p>Generally, the goal would have two primary reasons, business development, and personal development. <strong>Business development goal</strong> aligns with your work to your business deliverables. Example: I want to launch X feature with (measurable aspects) by Y date.</p><p>This is also something that you align with your immediate team and business. Often times this goal is the same for most of the team members, with different milestones.</p><p><strong>Personal development goal</strong> helps you uplevel your skills in lieu of achieving the big long-term vision that you have for yourself.</p><p>Example: One of my direct reports had a vision of shifting my career profile from an engineer to a product manager. So we had personal development goals for her that aligned with how she can learn and get closer to the expectations of a product manager.</p><p>Some of the managers may also benefit and help the team by adding an additional goal called the <strong>Stretch goal </strong>helps in getting all of us out of our comfort zone. These are mostly small exploratory tasks to go above and beyond and benefit by solving some low-hanging ones.</p><h3>What is a business development goal?</h3><p>The business development goal is to help you contribute to the business priority. This could be the goal common for you and your team. What might change is the how-to part for each team member, which means the milestones. This Drives the outcomes that you are accountable for along with your team.</p><p>Example: I want to deliver feature X which is accessible to my customers from the homepage with zero defects and 100% automation tests by Date Y.</p><h3>What could be a timeframe for a business development goal?</h3><p>A reasonable time duration for a business development goal can be anywhere from a few days to multiple quarters and sometimes multiple years.</p><h3>What is a personal development goal?</h3><p>A personal development goal will help you grow your skills on top of your business development goal and bridge the gaps in the expectations of the current level with consistency and will help you start meeting the next level&#39;s expectations. If your employer doesn’t define expectations clearly for the role, I encourage list down things that you are doing and get them checked with your manager and align on what are the gaps and what can you do completely meet the expectations at the current level and the next level (in case the current levels are met already).</p><h3>What could be a timeframe for a personal development goal?</h3><p>Timeframe for personal development goals should be around a quarter (2–3 months). If it is beyond a quarter, you may want to consult and take your manager&#39;s or leader&#39;s opinions on that.</p><h3>What is a stretch goal?</h3><p><strong>“Growth happens out of your comfort zone”. A </strong>Stretch goal is an important fundamental in pushing you out of your comfort zone. Generally, you do take on a stretch goal that is low-hanging. Like one Open Source PR for the month, and one technical blog internal/external in a month.</p><p>These goals are small and will let you explore new areas. Stretch goals can also mean you are signing up for the time stretch in personal development goal/ business development goal in case applicable.</p><p>Example: Business development goal: I want to deliver feature X in 3 months with no P0/P1 issues.</p><p>(Stretch goal applied) Business development goal: I want to deliver feature X in 2 months with no P0/P1 issues.</p><h3>What could be a timeframe for the stretch goal?</h3><p>The ideal timeframe for a stretch goal would be around a month. Beyond a month you may want to consult your boss, as this may not be the right direction or the right initiative for the return on investment. A manager or direct report should keep in mind that not everyone, not every month might be capable of signing up for a stretch goal.</p><h3>How to set the goals?</h3><p><strong>Business development goal</strong> — Do ensure this is the P0 for the business and that you are solving the prioritized problem defined by your employer. There are times when teams are mission-based or value-based. This is a good situation to be in. In case you work with your immediate stakeholders to figure out a backlog that you are solving and measuring the success against the mission.</p><p><strong>Personal development goal — </strong>These are the expectations from your role and beyond if you are looking to get to the next level. The next level doesn’t just mean the title you hold, but roles and responsibilities.</p><p><strong>Stretch goal</strong> — Something that you have been wanting to explore, and learn, that comes under stretch goal. As discussed earlier, these are the low-hanging fruits that will also have a high return on investment. Sometimes you may combine stretch goals with your personal development goal or business development goal.</p><h3>How many goals should we have at a time?</h3><p>Two to three goals: a business development goal and a personal development goal. A business development goal will help you contribute to the business in a meaningful way, while a personal development goal will help keep you steering toward your career aspirations. The third and optional goal is a stretch goal.</p><h3>Career development</h3><p>The general principle of growth is to move from an I-shaped model to a comb-shaped model, for the areas of expertise. This would apply to all professionals. Like the image below -</p><p>A typical T-shaped detailed model would look like this in reality for each area of expertise. In some areas, you would be a knight and in some, you would know just enough to get it done.</p><p>As you grow, the bars with knights would increase, and you would move from T-shaped to comb-shaped.</p><p>The above goal-setting framework helps an individual grow in depth of knowledge and also keeps broadening the areas that you can explore. Stretch goals will force you to add the new subjects that you explore. Over the period, you will become a subject matter expert in the areas that you are exploring today.</p><h3>Performance evaluation</h3><p><a href="https://mandarakale.medium.com/performance-management-shift-from-a-black-box-to-a-white-box-8334614d7626">https://mandarakale.medium.com/performance-management-shift-from-a-black-box-to-a-white-box-8334614d7626</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8c665264fb3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conflict management made easy]]></title>
            <link>https://mandarakale.medium.com/conflict-management-made-easy-24ac703a9e13?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/24ac703a9e13</guid>
            <category><![CDATA[conflict-management]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[conflicts-at-work]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Wed, 17 Aug 2022 02:42:53 GMT</pubDate>
            <atom:updated>2022-08-21T06:32:41.542Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pw6MANuA0bdZeNIF" /><figcaption>Photo by <a href="https://unsplash.com/@krakenimages?utm_source=medium&amp;utm_medium=referral">krakenimages</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As engineers, and it is applicable to knowledge workers and creators as well, we work with ideas. The idea is the currency and ensuring that ideas survive, thrive and grow is the differentiator between successful and not. And when there are many ideas, we would also see conflicts. Here, we discuss conflicts in the workplace. Unresolved conflicts can fester and affect collective morale, interpersonal relationships, and work productivity. We discuss types of conflicts, a way to think about them and tactical steps to manage the conflicts.</p><h3>Idea workers</h3><p>The pace of innovation and constant need for better ideas puts us in the ideas worker category more than knowledge workers. These ideas result in the continuous evolution of knowledge. It is in this light that conflict assumes a very different significance.</p><p>At some point, one has to transition from a “there is a best idea” mindset to “ideas are living”, they may come from anywhere, and need cross-pollination and nurturing before narrowing to selection for execution. Hegel’s Thesis-Antithesis-Synthesis Model is a dialectic method of historical and philosophical progress that postulates (1) a beginning proposition called a thesis, (2) a negation of that thesis called the antithesis, and (3) a synthesis whereby the two conflicting ideas are reconciled to form a new proposition. This is a simple model to think of how new ideas are born. In reality, this can take the form of borrowing ideas, transporting them to completely different domains, modifying them a bit etc. These are also given structured mechanics through six thinking hats like models, where black hat thinking forces an antithesis, often causing synthesis.</p><p>Establishing an authority, allowing a focus group to rip it or evaluating it too early, can kill ideas. Some of the fundamentally new ideas look completely unacceptable in the beginning. Not letting them the required space we shut down progress. Having completely on the same page that we need a space to nurture ideas, we should handle a specific phenomenon that arises often, called conflict. Conflict is in simple words disagreement when there are two ideas and the assumption is that one has to give way to another. It is easy to kill an idea but as an org, we need to nurture diversity and differences of opinion.</p><blockquote>“<em>Great minds don’t think alike. They challenge each other to think differently. … Converging values draw you to similar questions. Diverging views introduce you to new answers.</em>” — Adam Grant</blockquote><p>When you have good diversity, you end up having a variety of ideas and those may end up in good conflicts.</p><h3>Types of Conflicts</h3><p>All conflicts present a learning opportunity for all participants and especially for the leader(s) of the team(s).</p><p>Conflict can be of many kinds. Broadly, there are two types of conflicts in the workplace — <strong>functional conflict</strong> and <strong>dysfunctional conflict</strong>.</p><h4>Dysfunctional Conflicts</h4><p>What are the dysfunctional conflicts? These conflicts are related to people’s problems or very deteriorated functional conflicts. These are mostly caused by ego issues and/or personal interests put ahead of team/business interests.</p><p>A dysfunctional conflict -</p><ol><li>Blocks an organisation or group from reaching its goals</li><li>Gives rise to tension, anxiety, stress and low trust</li><li>Drives out low conflict tolerant people</li><li>Poor decisions from lack of innovation</li><li>Increases stagnancy</li></ol><h4>Functional Conflicts</h4><p>What are functional conflicts? Whatever the conflict is in functional conflict, both the parties have a good intention and want to solve or get unblocked for things that benefit the business.</p><p>Generally functional conflict -</p><ol><li>Works towards the goals of an organisation or group</li><li>Constructive conflict</li><li>Increases information and ideas</li><li>Encourages innovative thinking</li><li>Unshackles different points of views</li><li>Reduces stagnancy</li></ol><h3>Thinking Conflicts</h3><p>What is the right way to think about the conflict? What are the mindsets that get the best out of conflicts? We discuss a model that is very helpful in these situations.</p><h4>Thomas Kilmann Model</h4><p>Kenneth Thomas and Ralph Kilmann’s model has two dimensions,</p><ul><li>Concern for others’ ideas</li><li>Concern for self’s ideas</li></ul><p>At the lowest left is avoiding behaviour where there is low concern for self and others’ ideas. We want a mindset where there is value for everybody’s ideas. This is the collaborating behaviour shown in the top right quadrant. This works as a Hegelian dialectic as described earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8lmmfO50lPh3RM-B" /></figure><h4>Mindsets</h4><blockquote>When all think alike, then no one is thinking. — Walter Lippmann</blockquote><p>It is useful to keep the following points in mind</p><ul><li>See the value in conflict<br>- Not all conflicts are bad, we should encourage functional conflicts<br>- New ideas can emerge out of conflicts<br>- A comprehensive view comes out</li><li>Go with an open mind<br>- Beyond I am right you are wrong<br>- Not conflict but focus on the outcome</li><li>Behaviours you want to drive<br>- Authenticity<br>- No passive aggression<br>- Disagree but commit</li><li>Rules of engagement — The supremacy of data and reason<br>- Aristotle’s ethos, logos, and pathos say convincing can happen based on reason, the emotional state of the audience or the credibility of the presenter. We need to use reason for the long-term stability of decisions.<br>- Set principles before discussing the actual topic. It is easier to agree on principles sometimes than on a concrete situation.</li></ul><p>Every time we think of conflict, we are reminded of training by one who facilitated negotiations in the Middle East where both the parties sat with AK47s on the table. Not only does it show the importance of those conflicts, and the things at stake but also the dysfunctions that it may cause if it doesn’t progress constructively.</p><h3>Managing Conflict — Tactics</h3><blockquote>“Mediocre leaders deflect or decide conflicts, good leaders resolve them, and great ones use them as tools to advance.”</blockquote><p>Let’s talk about how to manage conflicts. Our teachable point of view (TPOV) on conflict management has three steps — before, during and after. While most of us focus on the “during” phase, successful conflict management has disproportionately large “before” and “after” phases.</p><h4>Before step: Mapping the conflict</h4><p>Mapping refers to drawing the lay of the land. General Tzu said, “Every battle is won before it’s ever fought.” One does background work to understand and also set up for the next phase of resolution. This is a recommended list of things to think through and not all may apply to a situation.</p><ul><li><strong>Reason of issue<br></strong>- Clear outcomes are needed, an anchor on the problem<br>- Background on the problem, collect unbiased data, collect points of view</li><li><strong>Stakeholders</strong><br>- Do we have the right people in the room?<br>- Who are the influencers?</li><li><strong>Positions (goals, values and perceptions) of each stakeholder<br></strong>- Where are they on the Thomas Kilmann model?<br>- Asking the right questions — what is going right? Why are they still in the team and project?</li><li><strong>Structure</strong><br>- Alignment, who does what, who gives budget, who gets the credit</li><li><strong>Find allies</strong><br>- Long-term relationships play an important role in ensuring conflicts are handled in the most cordial and right ways. This is built over peacetime, as they say, “fix the roof while the sun is shining”. The credibility of the participants, so built, creates a bridge for people to explain their views.</li></ul><h4>During step: Resolving a conflict</h4><p>This is the active phase where we resolve the conflict. We try to bring everybody together and ensure all are on the same page as a result of this phase. This is the most high-energy phase and has a chance to degrade to dysfunction.</p><ul><li><strong>Control the narrative</strong> — the narrative in the meeting should not be left to chance but should be well guided.<br>- <strong>Framing</strong> — “<em>A problem well stated is a problem half solved</em>” (Charles Kettering). Describing context and the problem well is an extremely important step and can swing the dynamics towards a solution.<br>- <strong>Anchor on the problem </strong>— sometimes it is very hard to align on a solution, it is better to anchor on the problem. Later is easier.<br>- <strong>Time box it</strong> or create a time pressure<br>- <strong>Have a seasoned program manager</strong> or someone playing that role in getting to the decision, managing time and following up on action items. Document objectives, positions, and escalation path.</li><li><strong>Ladder of inference</strong> — The Ladder of Inference describes the thinking process that we go through, usually without realizing it, to get from a fact to a decision or action. Ladder of inference is a process by which we understand what data, perspective and conclusion other people have made compared to yours.</li><li><strong>Positive spin</strong> — At times the disagreements become so wide and the situation appears to become impossible to recover from. At that time focus on what all can agree on rather than disagreements to swing the pendulum to another side.</li><li><strong>Look for unsaid cues</strong> as every reaction may not be verbal.</li><li><strong>Follow-up meetings</strong> may be arranged if needed. We may not get to all details in the main meeting, not every ‘t’ will be crossed and ‘i’ dotted.</li><li>Make sure <strong>everyone is vocal</strong> about their Point of View (POV)</li></ul><h4>After step: A culture of conflict</h4><blockquote>“Workplaces, like movies without healthy conflicts, are so boring” — Patric Lencioni</blockquote><p>Seeing many conflicts one realizes that they are not overheads but are hugely beneficial. So, after conflict resolution, we should think of steps that can encourage a culture of good conflicts. A culture in which we could benefit from them. Here are some tactics to think of.</p><ul><li>End every conflict on a high note, even when the “during” phase had a lot of bad blood.<br>- Fixate on the outcome<br>- Follow-through<br>- Keep people updated</li><li>Think long-term — good relationships make conflicts healthier.<br>Build bridges<br>- Make people work together</li><li>Make structure work for an organization. Structures with strong hierarchies can suppress conflicts, however, flatter structures help encourage conflicts. Use hierarchical structures only when we need to decide quickly or if a situation is getting out of hand.</li><li>Set conflict Mindset. Educate teams on how to think of conflicts, as described earlier. Use conflict case studies to reinforce the benefits and ways to handle them.</li><li>An effective leader doesn’t “wait” for the conflict, but they prompt it and embrace it.</li><li>As the leader, use conflict as an opportunity to create increased alignment.</li></ul><p>We, <a href="https://medium.com/u/9558b5c95f1e">Bala Dutt</a> and <a href="https://medium.com/u/80189a81122f">Mandar Kale</a> collectively wrote our ways and methods for conflict management. We think this is a tough but ever interesting and important skill for any leader to possess.</p><h3>Further reading</h3><p>One may find a lot of content online to learn. Here are a few to start deep dive with,</p><p><a href="https://www.youtube.com/watch?v=2l-AOBz69KU">Why There’s So Much Conflict at Work and What You Can Do to Fix It | Liz Kislik | TEDxBaylorSchool</a></p><p><a href="https://en.wikipedia.org/wiki/Thomas%E2%80%93Kilmann_Conflict_Mode_Instrument">Thomas–Kilmann Conflict Mode Instrument — Wikipedia</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24ac703a9e13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Performance management- shift from a black box to a white box!]]></title>
            <link>https://mandarakale.medium.com/performance-management-shift-from-a-black-box-to-a-white-box-8334614d7626?source=rss-80189a81122f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8334614d7626</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[performance-management]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <dc:creator><![CDATA[Mandar Kale]]></dc:creator>
            <pubDate>Fri, 24 Dec 2021 17:06:40 GMT</pubDate>
            <atom:updated>2021-12-24T17:06:40.297Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Re4AQsJxhUxPFYEL" /><figcaption>Photo by <a href="https://unsplash.com/@rockthechaos?utm_source=medium&amp;utm_medium=referral">Kolleen Gladden</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>While being an engineering manager for some time and talking to other leaders I have seen that performance management is a mystery for most people. This includes both sides — leaders and engineers. In this write-up, I will stick to the performance management of the individual contributors. I will clearly lay down what are the important facets of performance management and how to keep improving them on a day-to-day basis.</p><p>So “why” is performance management so important? There are two things that we all care about at work.</p><ol><li>How am I doing?</li><li>How can I improve my performance?</li></ol><p>It is all about the growth and development of individuals working with you. And because of this, performance management becomes more and more important.</p><p>Before we start talking about “Performance Management”, let’s understand the terms ‘performance management’ and ‘performance evaluation’. Management happens all the time directly or indirectly. Performance evaluation is a snapshot summary at a given point in time.</p><p>Performance management for an individual can be done by himself, peers, or anyone in the chain of hierarchy level up or down. Performance evaluation is generally done by the people manager responsible for your outcomes by considering the inputs/feedback from all the stakeholders and the individual. These practices also change from company to company, team to team and manager to manager.</p><p>First, let’s understand the challenges of performance management. A few reasons that I think make performance management so daunting are -</p><ul><li>We make performance management very complex</li><li>Engineers also don’t show a lot of interest in knowing how is their performance managed</li><li>Though performance management is very important most of the time there are no standards for it. The yardstick changes from manager to manager, company to company.</li></ul><p>As a result of this more often than not the performance ratings (if at all used in the organisation) happen to be a surprise for the individual.</p><p>While I have seen engineers, leaders and managers struggling with this, I happen to have worked with some great managers who helped take out the subjectivity from the topic and make it more objective.</p><p>This is what I call making performance management a white box; not a black box.</p><p>As I see, there are three important pillars of performance management</p><ol><li>Expectation setting</li><li>Goal setting</li><li>Check-ins/Performance evaluation</li></ol><h3>Expectation setting</h3><p>This is the first and the most important pillar, as this is where things go wrong most of the time. If your organisation doesn’t have set expectations for each role, then this can take a lot of time to crack in the first place. Expectation setting is critical as each individual would know what business is going to expect from her to deliver in each area of competency in the role.</p><p>If you are starting from scratch, you can start aligning the expectations and outcomes to the values or mission your organisation has set. Eventually, it is a good idea to land a set of technical and non-technical competencies against which we can set the expectations for the engineers.</p><p>In some of the big organisations, this expectation setting is done and aligned to the values. Like in Intuit we call it a role rubric. Role rubric is one place where we all see the competencies and expectations against each competency at each level. This also aligns competencies to the values that we abide by.</p><p>Whatever your situation may be, well-set competencies or starting from scratch, it is a good idea to have a framework and then keep improving it. The goal of this process is</p><ul><li>to understand what is expected with examples OR in other words what success looks like for a given role</li><li>how these expectations align with the company’s mission/values</li><li>avoid any biases in the process of performance management</li></ul><p>The way I use the expectations framework OR role rubric is,</p><ul><li>whenever someone new starts on the team, this helps them set the goals at the right altitude.</li><li>whenever you want to take on a new goal, you can look at the competencies that you may want to improve on</li><li>Transparency to understand what other engineers in different roles bring to the table</li><li>If you happen to feel you are outperforming this framework can tell you what competencies and what ways you do</li></ul><p>Please note the expectation framework should have some durability. In other words, you can not keep changing the expectations every so often and expect all to align to the new ones. This will throw our people off track very quickly.</p><h3>Goal setting</h3><p>You are off to a good start if you have basic competencies and expectations from each role. The next important step is to make sure we have clear goals and KPIs for each individual.</p><h4>What should be a goal for an individual?</h4><p>A simple way to think of this is — A goal is a highlight of your career for the year. At Intuit, we have two types of goals, business development goal and personal development goal. In my teams, I also have a third goal that I suggest, my team members, to follow it is a stretch goal.</p><ul><li><strong>A business development goal</strong> serves the business-focused outcomes like the project deliverables. This generally spans multiple quarters. This goal is also the goal that will more or less be similar for many of the same team members. The user story level details can be treated as milestones.</li><li><strong>Personal development goal</strong> focuses on the individual’s growth and developing skills beyond just the direct business focus. For example, communication skills, presentation skills, new technology or framework, etc. I suggest to my staff that you should always look at the expectations while taking on a personal development goal. This way all of us can focus on areas of opportunities and keep improving them year over year. By doing this you know in a few years time you are meeting the table stakes on the expectations.</li><li><strong>The stretch goal</strong> in my teams can be either stretching the areas of the above two goals or could be something new altogether that puts the individual out of her comfort zone. The first two goals are mostly the table stakes. This goal is to push us all to go above and beyond what is expected. This should generally span for not more than one or two months. In my team, the stretch goals are flexible and can also be just between the engineer and myself. Though it is advisable to have all the goals as public as possible.</li></ul><p>The idea of these categories is to have a maximum of two or three goals at a time. If the stretch goal is to stretch in one of the personal development or business development areas then we end up having only two goals. So looking at the full year, an engineer might have achieved two or three business development goals; three or four personal development goals; six or so stretch goals. By the way, the stretch goal will not be met all the time, but it is left to the manager and the employee to decide that SMART stretch goal to consistently raise the bar.</p><p>This framework gives you easy ways to focus on table stakes and what is beyond expected.</p><h4>How to make a goal SMART?</h4><p>SMART means specific, measurable, attainable, relevant, time-bound. There are a lot of good articles out there on this topic. Here are some suggestions on making the goals SMART -</p><ul><li>Ask after what outcome are we saying the goal is complete?</li><li>Timelines for the goal</li></ul><p>Some examples that I coach my teams on are</p><ul><li>From “I want to learn this XXX tech” to “I want to learn this XXX tech to write an external blog post and one internal tech talk by end of this quarter”</li><li>From “ I want to become a subject matter expert in ABC” to “I want to have two open-source contributions in ABC this year”</li></ul><p>Another way to validate a smart goal is that — any of your stakeholders or yourself will be able to give a binary answer (yes/no) for the completion of the goal. If there is any elaboration needed for the goal completion then it is not a smart goal.</p><h3>Check-ins/Performance evaluation</h3><p>My fundamental is that everyone should roughly know all the time where you stand in terms of your own performance evaluation.</p><p>For managers, it is not sufficient to just set the goals and expect things will go fine. Managers need to follow up and check in regularly. As you know the intent of this process is to help everyone understand how they are evaluated and avoid surprises in the performance ratings during the evaluation. In this step, I suggest talking to your directs regularly and taking the stalk of the situation, focusing on what are the obstacles to achieving the goals set and in what ways they need help.</p><p>One of the most important things about these check-ins is to make sure the manager and the employee are almost on the same page in terms of how the employee is performing. I generally say 10% — 20% variance of understanding is fine but beyond that is a RED flag. Either the employee is not clear on the expectations or the manager is missing something out from the employee’s outcomes. If this happens a manager needs to sit down with the report to clear things out asap without waiting for a formal performance cycle.</p><p>One simple way to do this evaluation is to see the number of goals set by the report, how many of them were delivered successfully and if the consistency was maintained. So for example an employee has met all the business goals and personal development goals but is missing out on the stretch goals consistently; this means she is not going above what is expected. If she is meeting all three types of goals consistently you know she is surely exceeding the expectations, and so on …</p><p>This is exactly how the employee will also understand to self evaluate. Once everyone in your team would start self-evaluating based on a framework, managers can make the performance evaluation more objective.</p><p><strong>TLDR</strong>; At the workplace, we all want to grow and develop ourselves and to do so, it is important that we understand how we are doing and how we can do better. Here is where transparent performance management will help. To achieve transparency and consistency, we discussed three facets, expectation setting, goal setting and regular evaluations. Following these three in that order makes a huge difference in how you and your team will see the performance management process and avoid surprises even during the evaluation process.</p><p>Hope this write up helps you improve the performance management or at the least forces you to think about how are we managing the performance of our teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8334614d7626" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>