<?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 Pavan Kristipati on Medium]]></title>
        <description><![CDATA[Stories by Pavan Kristipati on Medium]]></description>
        <link>https://medium.com/@pavan.kristipati?source=rss-4f9854831e8d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Pavan Kristipati on Medium</title>
            <link>https://medium.com/@pavan.kristipati?source=rss-4f9854831e8d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:11:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pavan.kristipati/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 Path to Operational Excellence: Embracing Automation in IT Operations]]></title>
            <link>https://medium.com/@pavan.kristipati/the-path-to-operational-excellence-embracing-automation-in-it-operations-b8f7fc901e79?source=rss-4f9854831e8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8f7fc901e79</guid>
            <category><![CDATA[operations]]></category>
            <category><![CDATA[operational-excellence]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[it-strategy]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Pavan Kristipati]]></dc:creator>
            <pubDate>Sun, 16 Jul 2023 23:38:56 GMT</pubDate>
            <atom:updated>2023-07-16T23:54:48.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WS1GUR25FsPlVISb7mBOgg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@harleydavidson?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Harley-Davidson</a> on <a href="https://unsplash.com/s/photos/fast-quick-satisfied?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Throughout my IT Engineering, Operations, and Automation career, I’ve worked with diverse teams and observed various strategies and operational models.</p><p>One consistent lesson I’ve learned from these experiences is the power of adaptability and constant evolution in the pursuit of efficiency and customer satisfaction.</p><p><strong>Adopting Squads:</strong></p><p>As an advocate for the continual advancement of practices in our field, I’ve been particularly fascinated by the potential of operational automation.</p><p>This fascination grew from observing the real-world functioning of different team structures, including the unique model of self-sufficient teams known as “Squads.”</p><p>A squad is a small, self-contained team, typically consisting of 4–10 individuals.</p><p>These teams are constructed to be versatile and comprehensive, capable of writing code, troubleshooting issues, conducting tests, and production releases.</p><p>Some organizations place additional responsibility on these squads by making them in charge of support for the product they’ve created.</p><p>In contrast, others delegate this support task to a separate dedicated unit.</p><p>The choice between these models resides in something other than a binary right or wrong. I’ve observed teams grappling with the challenges and reaping the benefits of both structures.</p><p>The efficiencies in each model are fascinating, and this continuous evolution and adaptability have truly drawn my attention.</p><h3><strong>Engineering Automation: The Cornerstone of Rapid Deployment</strong></h3><p><strong>The Shift toward Engineering Automation</strong></p><p>Implementing these squad structures often leads to an intriguing development in the organization’s priorities, particularly in “Engineering Automation.”</p><p>In organizations that have dedicated significant investment toward minimizing the time to market, engineering automation becomes a cornerstone of their strategy.</p><p>In these environments, members of the squads, whether developers or engineers, can deploy platforms and infrastructure as easily as by clicking a button.</p><p><strong>Streamlining Complex Tasks</strong></p><p>Complex tasks, like spinning up and down containers for app code, managing VMs for databases, deploying certificates, configuring load balancers, and setting up automatic desired state configurations, are all streamlined. Interestingly, these tasks are optional for the developers to understand each area deeply; everything is presented to them like a set menu.</p><p>The Platform Engineering teams in these organizations focus on enhancing developers’ productivity, an approach that has the potential to be hugely beneficial.</p><p><strong>The Misunderstanding of Being “Customer-Obsessive”</strong></p><p>However, this is where I’ve seen many organizations hit a stumbling block.</p><p>They have an unfortunate tendency to halt their progression at this stage, which stems from a misunderstanding of being “customer-obsessive.”</p><p>Their fixation is on pushing their product or service into the market or releasing the next big feature.</p><p>In their rush for a larger market share and increasing customer numbers, they lose sight of the wider picture.</p><blockquote>This misguided belief that a successful product roll-out signals the end of their journey often leads to premature celebrations and neglects the ongoing needs of their operations.</blockquote><h3><strong>Complacency and the Focus on New Features</strong></h3><p>We all have seen many organizations get caught in a cycle of complacency. They’re so focused on new features they think that’s all their customers care about.</p><p>However, if there’s no plan to address production issues swiftly, they’re setting themselves up for a fall.</p><p>Sure, a new feature could be a hit. But if the service isn’t reliable, customers will leave for competitors in a heartbeat.</p><p><strong>Beware of Complacency: A Lesson from the Trenches</strong></p><p><strong>The Downfall of Neglecting Operational Stability</strong></p><p>Consider the example of a local ISP in my area. They launched with good prices, faster speeds, and easy sign-ups.</p><p>They even had a referral program that offered a free month of internet. But things began to unravel after a few months.</p><p><strong>Reliability Issues and Customer Fallout</strong></p><p>They started experiencing reliability issues. Slow internet speeds, followed by full-blown outages that lasted for days.</p><p>It got to the point where customers couldn’t rely on them for work-from-home needs.</p><p>Many ended up canceling and switching to competitors.</p><p>I discovered that their troubleshooting team lacked the tools to assist their customers effectively.</p><p><strong>The Pitfall of Neglected Operations</strong></p><p>The company focused on acquiring new customers but needed to invest in retaining its existing ones.</p><p>Their IT Operations were underfunded, making their business as unstable as a house of cards. So, they failed to keep the lights on.</p><p><strong>The lesson</strong></p><p>While reducing time to market is important, you can’t neglect your existing customers. They’re the ones who are paying your bills while you’re busy attracting new ones.</p><h3><strong>The Internal Customer Shift: Recognizing the Importance</strong></h3><p><strong>Breaking Free from Outdated Mindsets</strong></p><p>“Taking care of customers” is straightforward when dealing with external customers who pay for your services. But when we treat internal teams who use our product or service as customers, the operations landscape takes an interesting turn.</p><blockquote>Just as external customers have options, internal teams also have avenues to explore. Investing in the satisfaction and success of your internal teams is not only a smart business move but a crucial step in fostering a collaborative and high-performing work environment.</blockquote><p>Many IT leaders perceive their internal IT operations as immovable, a static necessity that end users must utilize simply because there is no other choice.</p><p>This mindset is not only outdated but dangerous. In today’s world full of options, internal customers — your colleagues who rely on your IT services — are not bound by internal provisions.</p><p>If their needs are not met, they will seek alternatives. Let’s face it, they no longer have to come to you for help, and this misconception may have severe consequences.</p><p><strong>The Rise of Internal Customer Options</strong></p><p>Contrary to the belief that your internal customers have no other option but to rely on your IT services, there are numerous avenues they could venture down should they become dissatisfied. SaaS (Software as a Service) platforms, cloud-based services, or even freelance or external IT consultants are a click away.</p><p>These platforms and individuals promise quick solutions and innovation, often offering automated processes, less downtime, and faster problem resolution.</p><p>When we consider the list of tasks often associated with ‘taking care of the customer’ in IT operations — job/service restarts, patching infrastructures, manually executing approved changes — it’s clear that this customer care view is stuck in the past. It’s time we acknowledge that IT operations cannot simply be a reactive force within a company, fixing problems as they occur and being on call for issues.</p><p>By contrast, today’s IT operations must be proactive, constantly evolving and improving. Automation, machine learning, and predictive analytics are not buzzwords but realities of modern IT operations. They offer cost and time savings and can improve the customer experience and drive innovation throughout your business.</p><p>The opportunity, therefore, lies in modernizing IT operations.</p><p>The leaders who do not prioritize this transformation risk losing internal customers to external services and stagnating in an increasingly digital and automated world.</p><blockquote>Investing in capabilities that reduce time to market and ensuring current customers are cared for should be the objective.</blockquote><p>But, to do this, we must first recognize the changing landscape and adapt accordingly.</p><p>The time is now to reassess how we operate, placing our internal customers at the forefront of decisions and ensuring their needs are met and exceeded.</p><h3><strong>Initiating Modernization in IT Operations: The Blueprint</strong></h3><p>Embarking on the path of modernizing IT operations starts with recalibrating our approach. Here’s how:</p><p><strong>First Step: Prioritize Your Customers</strong></p><p>Let’s debunk that IT Operations’ influence doesn’t extend to external customer satisfaction. Encourage your team to break free from this limiting belief.</p><p>Your role in maintaining internal customer contentment and troubleshooting issues effectively plays a critical part in preventing problems that could impact external customers. Empowering teams that troubleshoot issues lays the groundwork for a customer-centric mindset.</p><p><strong>Next: View Incidents as Unplanned Investments</strong></p><p>Adopting the perception of treating each incident as an unplanned investment is the next step in this paradigm shift. This philosophy, which forms the core of SRE (Site Reliability Engineering) practice, has been instrumental for many companies.</p><p>I’ve delved into the details of this concept in another <a href="https://medium.com/@pavan.kristipati/every-incident-is-an-unplanned-investment-transforming-it-operations-through-site-reliability-12148a2a18a9">blog post</a>, emphasizing its transformative potential.</p><p><strong>Then: The Power of Blameless Postmortems (BPMs)</strong></p><p>Blameless Postmortems (BPMs) are crucial for extracting valuable lessons from incidents.</p><p>BPMs allow us to dig deep beyond superficial root causes, fostering an atmosphere of blameless inquiry. Properly conducted, they help us identify opportunities for process improvements. While creating a psychologically safe environment for effective BPMs requires skill, it can be developed and honed over time.</p><p>I’ve previously written extensively on <a href="https://medium.com/@pavan.kristipati/art-of-conducting-effective-blameless-postmortems-5f2b7765424c">maximizing the value derived from BPMs.</a></p><p><strong>Lastly: Identify Opportunities</strong></p><p>Understanding your customers’ pain points and addressing their needs is vital as you embark on this IT operations modernization journey.</p><p>If your work intake is primarily ticket-based, begin by analyzing these tickets.</p><p>If your team receives requests via email, consider implementing a simple ticketing system to document customer needs systematically.</p><p>You could include data fields like the submitter’s name, team name, app name, and problem area (compute, database, etc.), which should all validate against a CMDB. Refrain from using free-form text for these fields since they complicate and slow down data analysis.</p><p>This systematic approach will allow you to run analytics and spot trends in issues, also known as “top-talkers.”</p><p><strong>The Roadmap to Operational Automation:</strong></p><p>Operational automation is the key to modernizing IT operations.</p><p>While engineering automation amplifies developer velocity, operational automation eases the operational burden of support, affording teams the time to add customer value.</p><p>Without operational automation, teams are stuck performing tedious, error-prone tasks that add little enduring value.</p><p>Although end customers may not fully comprehend the depth of IT operations maturity, they will notice the sluggish resolution of issues if it’s lacking.</p><p>Here are some objectives you might consider for your journey toward operational automation:</p><ul><li>Equip production support teams with the tools to diagnose issues independently without involving other teams.</li><li>Introduce self-service.</li><li>Automate issue triage and incident resolution, ultimately striving for self-healing of issues.</li><li>Utilize code to reduce team toil.</li><li>Automate necessary but toil-intensive tasks like patching and version upgrades.</li><li>Implement Compliance as Code.</li></ul><p>In subsequent posts, I’ll share my personal experiences with each of these steps toward modernizing IT operations.</p><p>If you like this post, please consider clapping and following me here on Medium and on <a href="https://www.linkedin.com/in/pavankristipati/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8f7fc901e79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Art of Conducting Effective Blameless Postmortems]]></title>
            <link>https://medium.com/@pavan.kristipati/art-of-conducting-effective-blameless-postmortems-5f2b7765424c?source=rss-4f9854831e8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f2b7765424c</guid>
            <category><![CDATA[it-leadership]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[it]]></category>
            <category><![CDATA[blameless-post-mortem]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Pavan Kristipati]]></dc:creator>
            <pubDate>Tue, 04 Jul 2023 20:57:24 GMT</pubDate>
            <atom:updated>2023-07-04T23:37:38.300Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_RghVBsVUy1nNUMPv2sl9g.jpeg" /></figure><p>In a <a href="https://medium.com/@pavan.kristipati/maximizing-returns-going-beyond-root-cause-analysis-in-blameless-postmortems-72bccdbeee1d">recent blog post</a>, I wrote at length about how Blameless Postmortems (BPMs) differ from conversations on Root Cause Analysis (RCA) and Problem Management (PM).</p><p>I discussed why BPMs are the best-known ways to improve an organization’s resilience, learning culture, and overall system reliability.</p><p>Unfortunately, mileage out of BPMs varies. Some BPMs yield great results, while some fail miserably. When we fail to learn, we often end up where we do not want to be.</p><blockquote>“Management by objective works — if you know the objectives. Ninety percent of the time, you don’t.” — Peter Drucker.</blockquote><p>As writer and renowned management consultant Peter Drucker once said, “Management by objective works — if you know the objectives. Ninety percent of the time, you don’t.”</p><p>This quote perfectly encapsulates the challenge of conducting Blameless Postmortems (BPMs) and the significance of knowing the objectives around them.</p><p>Like Drucker, I too have recognized that most of the time, IT teams are not clear about the objective of BPMs, and hence, despite their best efforts, they don’t yield the desired results.</p><p>I have been there, done that.</p><p>Some BPMs were fantastic, learned a lot from them.</p><p>Some were a flop.</p><p>In this blog post, I will share some of my personal experiences for how I got to a point where I can conduct effective BPMs. I still have a lot to learn, but I sincerely hope this post can be a guide that is helpful to you in your journey to maximize learning and continuous improvement.</p><h3><strong>Goals of BPM:</strong></h3><p>The goal of a BPM is not to point fingers but to understand how a system failure occurred to improve the system and processes as we advance.</p><p>It’s about building a culture where mistakes are seen as opportunities for learning and improvement rather than reasons for punishment.</p><p>This is achieved by fostering an environment of psychological safety where mistakes can be openly discussed and analyzed without fear of blame, thereby allowing for systemic improvements based on the learnings from these incidents.</p><p>When done properly, BPMs encourage a learning and continuous improvement culture, crucial for any organization.</p><p>Here are some examples of how SRE practices like BPMs have helped:</p><p>1. Learning and Improvement: After Google’s Gmail service experienced a major outage in 2011, the SRE team, instead of blaming individuals, worked on identifying the root cause and improving their systems. They learned that a configuration change led to the disruption, so they improved their configuration change validation and management to prevent similar outages. Learning from failures and continuous improvement is integral to the SRE philosophy, as outlined in the Google SRE book: Site Reliability Engineering: How Google Runs Production Systems.</p><p>2. Promoting Transparency: Organizations build a sense of psychological safety among their teams by promoting a blameless culture. This trust encourages employees to take calculated risks, innovate, and learn from their mistakes, which is essential for growth and improvement.</p><p>3. Fostering Trust: Etsy’s SRE team is known for its blameless postmortem culture, which focuses on learning from incidents rather than blaming individuals. This creates an environment of trust, leading to more open incident reporting and deeper systemic improvement.</p><p>4. Improving Resilience: Netflix’s SRE team uses a “Chaos Monkey” tool to terminate virtual machines in their production environment randomly. This approach forces services to be built to withstand failures, thus enhancing the overall resilience of their systems.</p><p>5. Reducing Toil: Google’s SRE team has a rule that toil (manual, repetitive tasks) must not take up more than 50% of an engineer’s time. If an SRE regularly exceeds this, they automate tasks to reduce toil and focus on more meaningful, project-based work.</p><p>6. Risk Management: At Amazon, the SRE team uses “GameDays,” where they intentionally inject failures into their systems to better understand potential risks. These insights are used to update their risk profiles and error budgets, effectively managing the trade-off between stability and innovation.</p><h3><strong>How to get started with BPMs?</strong></h3><p>No need to start with a fanfare.</p><p>I realized that I did not have to wait for the whole organization to embrace the idea of BPMs.</p><p>I took charge and started to conduct post-mortems blamelessly and started to reap benefits. It was not a perfect start, but I needed to start somewhere.</p><p>After doing some of these, I noticed better engagement from my team members.</p><p>Like me, you do not have to wait for everyone involved in an incident to be ready for BPMs. You could start with your team.</p><p>To get started, you need to know the basics like ‘why’ BPMs and ‘what’ the goals are of BPMs. You do not need to master ‘how’ to get started.</p><p>You do need to remember that the teams will NOT open up initially until you, as a leader, create psychological safety and show that you are vulnerable.</p><p>You do that by opening up about your limitations regarding understanding the underlying issues that could have contributed to the issue.</p><h3><strong>Key layers to uncover in a BPM:</strong></h3><p>But how does one approach conducting a BPM? What approach works and what does not?</p><p>I would approach conducting a Blameless PostMortem (BPM), like peeling multiple layers of an onion.</p><p>Each layer represents a different aspect of the system or process that contributed to the incident.</p><p>Here are some of the key layers and the type of questions that could be asked at each level:</p><p>1. Symptom Layer: This is the first layer you encounter, which describes the symptoms of the incident.</p><p>Questions: What exactly happened? What symptoms were observed? When did the incident occur, and who was affected?</p><p>2. Technical Layer: This layer examines the technical details of the failure.</p><p>Questions: How did the failure occur? What part of the system was affected? What were the error messages or logs indicating? Was there a specific sequence of events that led to the failure?</p><p>3. Process Layer: This layer looks at the procedures and practices that may have contributed to the incident.</p><p>Questions: Why did this incident occur? Were there any procedural shortcomings? Were there any gaps in monitoring, alerting, or testing? Did the deployment process contribute to the failure?</p><p>4. People Layer: This layer focuses on the human aspect of the incident. It’s important to note that in a blameless culture, the goal is not to attribute fault but to understand decision-making and communication.</p><p>Questions: Who was involved in the incident? Were decisions or actions based on incomplete or incorrect information? How effective was the communication during the incident? Did training or skill gaps contribute to the incident?</p><p>5. Organizational Layer: This layer looks at the wider organizational context, including culture, policies, and resources.</p><p>Questions: Where within the organization did the breakdown occur? Could resource allocation or organizational culture have contributed to the incident? Are there policies that need to be revised?</p><p>6. Improvement Layer: The final layer uses all the information uncovered to identify improvements.</p><p>Questions: What can we do to prevent similar incidents in the future? What system improvements are needed? How can we improve our processes and communication? Are there training or resources needed?</p><p>Effective BPM involves careful navigation through all these layers.</p><p>It requires curiosity, open-mindedness, thorough analysis, and commitment to improvement.</p><p>The goal is to gain a holistic understanding of the incident, focusing on the technical details and the surrounding processes and context.</p><h3><strong>The Process Layer — The Hidden Gem!</strong></h3><p>I had many ‘aha’ moments when investigating the “Process Layer.”</p><p>People often follow processes/procedures because that’s how they are used to doing things.</p><p>We rarely question why having a hostname in a free-form text field in a user request is acceptable… typos in such free-form text fields are sure causes for disaster.</p><blockquote>Processes that expect people to be perfect are ticking time bombs.</blockquote><p>Know that processes that expect “people to be perfect” are ticking time bombs. Imagine how many explosions are waiting to happen because of poorly designed processes!</p><p>Such processes must be challenged, redesigned, and implemented for imperfect people as users.</p><h3>Price of Ineffective Procedures:</h3><p>In the book, “Leadership and Self-Deception, Getting Out of the Box”, by the Arbinger’s Institute, the authors discuss a very important example of how doctors themselves contributed to the death of hundreds of pregnant women because they were carrying the germs from performing autopsies to the maternity ward. And when that was evident that that was the root cause, they instituted methods to reduce such deaths.</p><p>In this case, the doctors were unaware that their actions (moving from one part of the hospital to another) contributed to the spread of disease, leading to the unfortunate death of many pregnant women. Once this fact emerged, measures were implemented to mitigate the issue.</p><p>This is an example of a ‘Process layer’ issue where harmful actions were unknowingly being taken due to a lack of knowledge or ineffective procedures.</p><p>The <strong>goal is to uncover the underlying factors that contribute to failures or adverse events and then to implement corrective actions.</strong></p><p>The focus is not to blame individuals but to understand the system or process flaws that allowed the problem to occur.</p><h3><strong>Missing Results:</strong></h3><p>It is common for IT leaders to get excited about the need for BPMs to be conducted and implemented in their organizations.</p><p>They feel good about getting started they might have metrics to show the ‘changes’ they have implemented.</p><p>But given a deeper look, they are not reaping full benefits from BPMs or worse their efforts could backfire in the form of employee churn as BPMs are interpreted by their team as ‘investigations’.</p><p>This often results in leaders being skeptical of BPMs.</p><h3>What could you be missing?</h3><p>The missing element could be that you have approached BPMs as one more check box that needs to be taken care of.</p><p>You are in a hurry for that BPM report to be done and have unknowingly made it a priority to get a BPM report out the door.</p><p>BPMs take time to do them the right way. Hurrying up or an incorrect approach only leads the team into thinking of them as ‘investigations’.</p><p>Or you have not taken the time to cultivate psychological safety in their team. You expect the team to open up, but have you created an environment for them to open up?</p><p>The other reason for missing results is that you have delegated the all-important task of conducting BPMs to the wrong person —</p><p>to someone who is not invested in the process,</p><p>to someone that is not technical enough or</p><p>not brave enough to go beyond the first couple of layers of the proverbial onion.</p><p>Is the person in charge of BPMs like a bull in a china shop that does more damage than help, alienating everyone around them?</p><p>Is he here to “argue” with the engineers with boots on the ground rather than being empathetic and learning from their experiences to get to the actual causes of the issue?</p><p>Is it too soon to delegate? or should you delegate this task?</p><p>Such leaders need to realize that the mileage out of BPMs varies significantly.</p><p>And it depends on the person doing them right.</p><p>The constant is BPM.</p><p>The variable is the person/team in charge of running BPMs.</p><p>If the investment in BPMs does not work as expected, it is ‘who’ and ‘how’ they are done that needs to be looked at.</p><p>We should not be tossing away BPMs if they do not work right away for us. Keep iterating and keep learning.</p><p>BPMs need to be an “uncovering” exercise or pure discovery effort.</p><p>In the Vienna Hospital example, the wrong person, at first glance, might quickly conclude that the doctors are the reason for the deaths, and an immature leadership team at that hospital might have fired all the doctors to replace “better” doctors.</p><p>But that will hardly work as the true “cause” of the problem was never “uncovered.” To recollect, the true cause of the problem was “germs.”</p><p>Instead of firing doctors, an effective solution was implementing sanitizing practices, including properly washing hands.</p><p>What is worth mentioning is that spending time to peel the onion layers to get to the ‘Process Layer’ (sanitizing hands) turned out to be a well-worthy investment instead of replacing doctors.</p><h3><strong>The right way to ask questions — The secret for BPMs effectiveness:</strong></h3><p>Blameless PostMortems (BPMs) can sometimes be ineffective due to the unintentional creation of a defensive environment, often stemming from the nature of the questions asked during these sessions.</p><h3><strong>The “Why” questions:</strong></h3><p>One primary reason is using “why” questions, which inherently carry an accusatory tone, fostering a culture of blame instead of learning.</p><blockquote>“Ask the right questions if you’re to find the right answers.” — Vanessa Redgrave.</blockquote><p>“Why” questions, though not always, can tend to be more closed-ended, leading to answers that may not fully understand an issue.</p><p>For instance, asking, “Why did the server crash?” might elicit a response like “Because there was a bug in the code.”</p><p>While this answers the question, it doesn’t delve into the broader context or underlying factors that allowed the bug to exist or to cause a server crash.</p><p>These questions can feel like an audit, with individuals fearing potential retribution or judgment.</p><p>As a result, team members may become defensive or reluctant to share crucial information, hindering the overall learning process and limiting the effectiveness of the postmortem.</p><p>Go ahead and say these “why” questions out loud. You will be hard-pressed not to find them accusatory audit types of questions.</p><p>“Why” questions, even when well-intentioned, can inadvertently shift the focus toward finding a person or team to blame.</p><h3><strong>The “How” questions:</strong></h3><p>On the other hand, “how” questions foster a different environment — one of curiosity and exploration.</p><p>“How” questions are usually more open-ended, encouraging a more detailed and thoughtful response.</p><p>If you ask, “How did the sequence of events unfold that led to the server crash?” it prompts for a comprehensive explanation.</p><p>It allows the respondent to describe the conditions before the crash, the actions taken, the consequences of those actions, and how the system and the team responded.</p><p>These questions steer the conversation towards understanding the underlying systems and processes rather than pinpointing individual mistakes.</p><p>“How” questions encourage an open, collaborative exploration of events leading up to an incident, fostering a problem-solving mindset.</p><p>Curiosity is crucial in a BPM because it promotes a culture of continuous learning and improvement, facilitating a comprehensive understanding of systems and processes.</p><p>It encourages teams to delve deeper into an incident’s technical, procedural, and organizational layers, which is crucial to prevent future incidents.</p><p>Framing questions as “how” instead of “why” can significantly enhance the effectiveness of BPMs.</p><p>My experience taught me that by fostering curiosity, I could facilitate open discussion, promote a blameless culture, and drive meaningful improvements to your systems and processes.</p><p>Now, let us compare the two types of questions using the same layers I mentioned before:</p><p>1. Symptom Layer:</p><p>- “Why” question: Why did we miss this issue initially?</p><p>- “How” question: How did we detect the issue?</p><p>2. Technical Layer:</p><p>- “Why” question: Why did this component fail?</p><p>- “How” question: How did the system’s design contribute to the failure?</p><p>3. Process Layer:</p><p>- “Why” question: Why didn’t we follow the established deployment procedures?</p><p>- “How” question: How are our deployment procedures designed, and how might they have contributed to this incident?</p><p>4. People Layer:</p><p>- “Why” question: Why did you make that decision during the incident?</p><p>- “How” question: How were the team members involved in the incident prepared for such an event?</p><p>5. Organizational Layer (Where):</p><p>- “Why” question: Why do we keep having these incidents?</p><p>- “How” question: How does our organizational culture or structure impact the way incidents are handled?</p><p>6. *Improvement Layer (Future):</p><p>- “Why” question: Why haven’t we fixed these problems before?</p><p>- “How” question: Based on what we’ve learned, how can we improve our system design, processes, communication, and organizational structures?</p><p>Now, some of the ‘How’ questions are harder to ask.. I will be the first one to admit it. We are just not used to asking questions that way.</p><p>Sometimes, I struggle to re-frame some of the ‘Why’ questions into the ‘How’ type.</p><p>When that happens, I make my intention clear.. that I am going after ‘How’ we got here instead of pressing for ‘why’ something happened.</p><blockquote>I never lose. I either win or learn — Nelson Mandela.</blockquote><p>Nelson Mandela once said, “I never lose. I either win or learn.”</p><p>This philosophy lies at the heart of effective BPMs.</p><p>By shifting our perspective from blame to learning, from “why” to “how,” we can fully leverage BPMs to drive improvement, efficiencies, and innovation.</p><p>As a closing thought, wondering, “How did we get here?” is one of the keys for effective Blameless Postmortems.</p><p>Here is to wondering, exploring, learning, improving, and enjoying our work!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f2b7765424c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maximizing Returns: Going Beyond Root Cause Analysis in Blameless Postmortems]]></title>
            <link>https://medium.com/@pavan.kristipati/maximizing-returns-going-beyond-root-cause-analysis-in-blameless-postmortems-72bccdbeee1d?source=rss-4f9854831e8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/72bccdbeee1d</guid>
            <category><![CDATA[blameless-post-mortem]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[it-operations]]></category>
            <category><![CDATA[it-leadership]]></category>
            <category><![CDATA[it-operations-management]]></category>
            <dc:creator><![CDATA[Pavan Kristipati]]></dc:creator>
            <pubDate>Sat, 01 Jul 2023 05:19:21 GMT</pubDate>
            <atom:updated>2023-07-04T17:19:36.814Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0YpTRMQJ3QGbstjKlfpceQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@simonppt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">SIMON LEE</a> on <a href="https://unsplash.com/s/photos/iceberg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Recently I <a href="https://medium.com/@pavan.kristipati/every-incident-is-an-unplanned-investment-transforming-it-operations-through-site-reliability-12148a2a18a9">published an article</a> on why having the mindset to look at technology (IT) incidents as unplanned investments is the way to orchestrate substantial improvements in IT Operations.</p><p>In that article, I discussed how this approach resonated profoundly with me, so much that I was inspired to encapsulate my philosophy in a single phrase — “Every Incident is an Unplanned Investment.”</p><blockquote><em>“We learn from failure, not from success!” — Bram Stoker</em></blockquote><p>Major incidents are unfortunate yet common, regardless of the measures we take to prevent them. These mishaps are inevitable, but they also present a unique opportunity: to learn, fortify our systems, streamline our processes, and elevate our software capabilities.</p><p>Seizing this opportunity powerfully hinges on our commitment to delve into the heart of the incident, understanding its root cause, and taking action to minimize future recurrence.</p><p>But is that the end of the line?</p><p><strong>How does one know if they are doing enough to reap the full benefits of the unplanned investment?</strong></p><p>In this article, I share my thoughts on “Maximizing Returns: Going Beyond Root Cause Analysis in Blameless Postmortems.”</p><blockquote><em>“The only real mistake is the one from which we learn nothing.” — Henry Ford</em></blockquote><p>If looked from the right perspective, Incidents allow us to uncover weaknesses, improve our systems and processes, and enhance our software capabilities.</p><p>However, understanding the root cause of an incident is just the beginning.</p><p>To fully leverage the unplanned investment that incidents represent, we must go beyond root cause analysis and explore the complex interplay between Root Cause Analysis (RCA), proactive Problem Management (PM), and the compassionate approach of a Blameless Postmortem (BPM).</p><h3><strong>Root Cause Analysis (RCA):</strong></h3><p>Root Cause Analysis (RCA) is like a detective trying to solve a case. It’s all about drilling down to find the underlying reason behind a problem.</p><p>The kind of thing that makes you ask “why” five times until you cannot ask “why” anymore. It’s great because it helps us uncover hidden issues that need clarification.</p><p>But sometimes, it limits us to finding just one culprit for an issue when, in reality, there could be multiple factors at play.</p><p>Let’s say we perform a Root Cause Analysis (RCA) and identify that a faulty code deployed to production caused the outage. While it’s correct to say that this specific code issue triggered the problem, focusing solely on it might overlook other significant contributing factors.</p><ul><li>For instance, the code review process may have been rushed because the team was pressured to meet a tight deadline, leading to the faulty code getting past the review.</li><li>The testing environment may not be a true reflection of the production environment, so the problem did not surface during the testing phase.</li><li>Or the monitoring system failed to alert the team quickly enough when the problem began, causing a delay in the response.</li></ul><p>These factors <strong>contributed</strong> to the incident and would be missed if we stopped at “faulty code” as the singular root cause.</p><p>While the RCA helped identify the immediate cause, a broader view is required to understand the system’s multiple weaknesses and improve them.</p><blockquote><em>“Don’t be blinded by the obvious culprit; delve deeper to uncover the hidden accomplices lurking in the shadows.”</em></blockquote><p>The challenge with the RCA approach is that it tends to limit us from thinking as more than one reason could be the contributor to the incident.</p><p>There is an implied assumption that “if XYZ did not happen, the event would not have happened”. This is a limiting belief. It is rare to have a single reason for a major outage.</p><p>The sinking of the “unsinkable” Titanic, a disaster that claimed 1,514 lives a century ago, provides a stark example of how multiple factors rather than a single colossal error can culminate in a catastrophic technological failure.</p><p>Richard Corfield writes in a <a href="https://physicsworld.com/a/the-perfect-storm/">retrospective for Physics World</a>, “No one-thing sent the Titanic to the bottom of the North Atlantic.” Instead, the ship’s fate was sealed by what’s known as an “event cascade” — a series of unfortunate circumstances. Here is <a href="https://www.nbcnews.com/sciencemain/10-causes-titanic-tragedy-620220">an interesting article</a> about this.</p><h3><strong>Problem Management (PM)</strong></h3><p>Problem Management (PM) is like a movie review session. It offers a holistic understanding of an incident, tracing what, how, and the response.</p><p>However, it has limitations, especially when conducted by non-technical resources who, despite their process expertise, lack the deep technical knowledge to reap full benefits.</p><p>Their handling of an incident, like a database disruption, relies heavily on the technical team’s input but offers valuable business or management insights.</p><p>Here’s a brief overview of their process:</p><ul><li>Incident Reporting: They note disruptions and collect initial data.</li><li>Collaborative Investigation: They discuss the incident with technical teams to comprehend the contributing factors.</li><li>Problem Identification: They identify the main problem and contributing factors with the technical team’s help.</li><li>Solution Proposal: They propose mostly managerial or procedural solutions, but their execution capability may be limited.</li><li>Implementation and Follow-up: They communicate the solutions, monitor adherence, and verify effectiveness with the technical team.</li></ul><p>However, like some movie reviews, PM can devolve into blame games. Non-technical members may need more time to grasp the intricate technical roles leading to failure fully.</p><p>Without proper training, they may not acknowledge that they could’ve made the same mistake, a key gap in traditional problem management teams.</p><p>If the person conducting the PM analysis (of the Titanic incident) doesn’t have ‘boots on the ground’ experience, their understanding of the incident and their recommendations may be more high-level or strategic rather than focused on the day-to-day operational issues. For example:</p><ul><li><strong>Communication Procedures:</strong> They might recommend revising how important information, such as iceberg warnings, is communicated between crew members and the captain to ensure vital information is noticed.</li><li><strong>Training Programs:</strong> They could suggest implementing or enhancing training programs for all crew members, focusing on emergency response, ship navigation, and crisis communication.</li><li><strong>Regulatory Compliance:</strong> They could suggest that the company regularly review and update its compliance with maritime safety regulations, and advocate for stricter regulations regarding sailing speeds in dangerous areas.</li></ul><blockquote><em>“Blaming individuals for systemic problems is like blaming a single tree for a forest fire.”</em></blockquote><p>If the person is not trained properly, they might lay fault at the feet of specific individuals in various roles. For example:</p><ul><li>They could blame the captain for not heeding iceberg warnings and sailing too fast in dangerous conditions.</li><li>They might criticize the crew members for not having the binoculars readily available.</li><li>They could fault the ship’s designers or builders for not making it robust enough to withstand an iceberg collision.</li></ul><p>However, it’s important to note that these blame-oriented conclusions might be overly simplistic and won’t necessarily lead to the changes needed to prevent similar incidents in the future.</p><p>They focus on the <strong>actions of individuals rather than the systems</strong> and processes that allowed those actions to happen.</p><p>This is where the value of a blameless approach, like a blameless postmortem or a blameless problem management review, really becomes clear.</p><h3><strong>Blameless Postmortem (BPM)</strong></h3><p>In contrast, a blameless postmortem is an approach that places the focus squarely <strong>on learning and improvement</strong> without resorting to blame. It starts with the premise that everyone involved in an incident had good intentions and acted to the best of their ability with the information available at the time.</p><p>Instead of focusing on who made a mistake, a blameless postmortem encourages open and honest discussions about what happened, why it happened, and how similar incidents can be prevented.</p><p>It seeks to uncover systemic issues, process failures, or gaps in knowledge that contributed to the incident.</p><p>Blameless postmortems create an environment where team members feel safe to share their thoughts, opinions, and ideas without reservation by removing the fear of blame and punishment.</p><p>This openness can lead to more effective problem-solving and robust preventative measures.</p><p>Furthermore, a blameless culture encourages innovation, as team members are not afraid to take risks and make mistakes.</p><blockquote><em>“If there are no critics, then you probably will not have any success either.” — Malcolm X</em></blockquote><p>Critics of BPMs often do not quite get the true value they bring. They raise some criticisms that, to be honest, do not hold up under closer examination. Let us take a look at some of these common critiques and conversationally address them:</p><p>1. **Encouraging Irresponsibility**: Some people wrongly assume that blameless BPMs mean letting people off the hook for their actions. But that’s not the case at all! BPMs are all about learning and improving, not avoiding responsibility. They help us understand what went wrong and how to improve in the future.</p><p>2. **Ignoring Individual Mistakes**: Critics argue that BPMs focus too much on systemic issues and overlook individual mistakes. Well, that’s not entirely true. BPMs look at individual actions within the bigger picture of the system. It’s about understanding why the system allowed the error and finding ways to improve it.</p><p>3. **Perceived Inefficiency**: Some claim that BPMs take too much time and resources. They argue that we could be doing more productive things instead. But here’s the thing: BPMs offer long-term benefits. Investing time in thoroughly analyzing and learning from incidents can prevent future incidents and make our systems more resilient.</p><p>4. **Idealistic Label**: Critics often label BPMs as idealistic or naive. They say that we must assign blame to hold people accountable in the real world. But here’s the reality: BPMs are not about assigning blame but about understanding, learning, and preventing future incidents. Blame doesn’t always lead to effective change, but understanding does.</p><p>5. **Organizational Compatibility**: Some skeptics question whether every organization can implement blameless processes. They argue that it might not fit with their culture or structure. While it’s true that implementing BPMs can be challenging, it’s also important to recognize the potential for cultural change and improvement. Any organization can create a learning culture with the right approach and commitment.</p><blockquote>Blame doesn’t always lead to effective change, but understanding does.</blockquote><p>So, how can we address these criticisms and make BPMs more effective? Here are a few strategies we can consider:</p><p>- Promote Personal Responsibility: Let’s reinforce that BPMs are not about avoiding responsibility but about taking ownership of mistakes and learning from them. We can cultivate a culture of accountability by helping team members understand their role in incidents and the broader impact of their actions.</p><p>- Acknowledge Individual Mistakes within Systemic Context: It’s crucial to emphasize that BPMs do consider individual actions, but always within the context of the larger system. By understanding why the system allowed the error, we can direct our improvement efforts toward the system itself.</p><p>- Emphasize Long-Term Efficiency: Yes, BPMs require time and effort, but let’s highlight their long-term benefits. By learning from incidents and preventing future errors, we can improve overall productivity and the resilience of our systems. Learning is an investment in future reliability.</p><p>- Provide Concrete Examples: Let&#39;s share real-world success stories to counter the idealistic perception of BPMs. We can highlight companies or teams that have effectively implemented BPMs and the positive impacts they’ve experienced, such as reduced incident rates, improved team morale, and stronger system resilience.</p><p>- Demonstrate Cultural Adaptability: Critics may argue that BPMs won’t work in every organization due to cultural differences. But we can show them that BPM principles can be customized to fit different organizational structures and cultures. It may require a gradual culture shift, but with commitment from all levels of the organization, it’s achievable.</p><blockquote><em>“In the middle of difficulty lies opportunity.” — Albert Einstein</em></blockquote><p>Executives’ support is crucial for embedding this culture. Educate leaders about the advantages of this approach and secure their endorsement. Involve diverse teams for a comprehensive perspective, which can yield valuable insights into incident management.</p><p>Finally, the outcomes of a BPM should be tangible action items to prevent future incidents. Designate a senior figure to review and approve these recommendations, ensuring accountability and effective implementation.</p><p>As senior technology executives, we should view blameless postmortems as a catalyst for growth and learning. In an industry marked by complexity and rapid evolution, these practices offer a constructive, empathetic, and forward-looking approach to managing incidents, reinforcing a culture of collaboration and continual improvement.</p><p>RCA, Problem Management (PM), and Blameless Postmortem (BPM) have unique benefits and can be used in different scenarios. In a future article, I will share examples of how to run BPMs correctly.</p><p>Here is to the no-blame game!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72bccdbeee1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every Incident is an Unplanned Investment: Transforming IT Operations through Site Reliability…]]></title>
            <link>https://medium.com/@pavan.kristipati/every-incident-is-an-unplanned-investment-transforming-it-operations-through-site-reliability-12148a2a18a9?source=rss-4f9854831e8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/12148a2a18a9</guid>
            <category><![CDATA[continuous-improvement]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[it-operations]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Pavan Kristipati]]></dc:creator>
            <pubDate>Tue, 27 Jun 2023 02:11:11 GMT</pubDate>
            <atom:updated>2023-07-01T13:16:36.365Z</atom:updated>
            <content:encoded><![CDATA[<h3>Every Incident is an Unplanned Investment: Transforming IT Operations through Site Reliability Engineering Principles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tquUQFEzhEg0XHJ9w5qPEA.png" /></figure><p>In Steven Spear’s book, “The High Velocity Edge,” he presents an in-depth exploration of Toyota’s unique approach to continuous improvement, known as Kata. A significant portion of the success of the Japanese automaker is credited to their relentless pursuit of perfection, always striving to refine and elevate their processes. As Spear aptly puts it, “The most important capability… is the capacity for discovering and developing new capabilities.”</p><p>In my journey as a senior IT leader, this approach resonated profoundly with me. So much so I was inspired to encapsulate my philosophy in a single phrase — “Every Incident is an Unplanned Investment.” By embracing this mindset in Site Reliability Engineering (SRE) and IT Operations, I have orchestrated substantial improvements in production support.</p><blockquote>Every Incident is an Unplanned Investment</blockquote><h3>The Pathway of Continuous Improvement</h3><p>Spear narrates a surprising tale from Toyota’s operations. Upon noting a decrease in the number of production line problems, or ‘andon cord pulls,’ the executives didn’t celebrate. Instead, they deliberately added stress to the production line to unearth hidden issues and further improve the system. This mindset, a paradoxical celebration of problems, is the cornerstone of Toyota’s pursuit of continuous improvement. And it’s an approach that I found to be transformative when applied to the world of IT Operations.</p><p>In a similar vein, I worked on increasing our IT monitoring capabilities, fully expecting that it would lead to a rise in the number of “lower priority” incidents detected. Yet, rather than viewing this increase as a setback, I saw it as an opportunity for continuous improvement.</p><p>Each incident unearthed through enhanced monitoring represented an area of our operations that could be strengthened, leading to fewer high-priority, customer-impacting incidents. This strategy, akin to Toyota’s decision to stress the production line to improve it, reaffirmed the significance of the principle that every incident is an unplanned investment.</p><h3>Incident: A Launchpad for Improvement</h3><p>In the sphere of Site Reliability Engineering (SRE), incidents are often viewed as stumbling blocks, and hindrances to smooth operation. However, guided by the principles of the Improvement Kata, I began to see incidents in a new light. Instead of being a setback, each incident became an unplanned investment — an opportunity to learn, adapt, and grow.</p><blockquote>Instead of being a setback, each incident became an unplanned investment — an opportunity to learn, adapt, and grow.</blockquote><p>However, incidents can often directly result from the ‘toil’ that characterizes IT operations. In other words, it is often manual, repetitive tasks prone to human error that lead to system issues and incidents. Recognizing this, I began to explore the potential of automation to reduce <em>high-priority</em> <em>customer-impacting</em> incidents by reducing toil.</p><h3>Leveraging Automation to Reduce Toil</h3><p>A core principle of Site Reliability Engineering is the relentless reduction of toil through automation. “Toil” in SRE terminology refers to the manual, repetitive tasks that add little enduring value but consume precious time and energy.</p><p>Automation, in this context, serves a dual purpose. First,</p><ol><li>It streamlines operations by taking over repetitive tasks, freeing human engineers to focus on more strategic, value-adding activities and</li><li>Perhaps more importantly, it reduces the incidence of human error, a common cause of incidents in IT operations.</li></ol><p>Orchestration tools like Rundeck Enterprise, for example, allow us to automate responses to IT Service Management (ITSM) events such as incidents and requests.</p><p>Bill Gates astutely reminds us that automation has a transformative effect when it comes to technology in business. Automation magnifies efficiency in an efficient operation, while in an inefficient process, unfortunately, it magnifies inefficiency.</p><blockquote>The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency — Bill Gates</blockquote><p>This quote perfectly encapsulates the importance of applying automation wisely in IT Operations. By seeing every incident as an unplanned investment, we cultivate the wisdom necessary to make informed decisions and continuously enhance our processes.”</p><p>By treating incidents as unplanned investments, we shift our perspective and recognize the value they hold in driving improvements and building expertise. It is through this mindset that we gain the wisdom to make informed choices and propel IT Operations toward greater efficiency and reliability.</p><h3>Reducing Operational Risk: Fewer Hands on the Keyboard</h3><p>Every manual intervention in a system introduces a risk factor — the risk of human error. Automating our responses to ITSM events significantly reduces the need for ‘hands on the keyboard.’</p><p>This risk reduction isn’t just a fortunate byproduct of our approach — it’s a core principle of Site Reliability Engineering.</p><blockquote>Hope is not a strategy.</blockquote><p>As the SRE saying goes, “Hope is not a strategy.” We don’t simply hope for our systems to remain robust; we proactively design them that way, effectively decreasing operational risk and boosting the reliability and stability of our systems.</p><p>In the realm of database management, one such area was database patching, a process formerly manual, error-prone, and time-consuming. With the introduction of automation, we cut down on patching time by an average of 75% and reduced errors during patching by almost 85%.</p><p>A different example would be a case involving incidents related to manual space adds. After noticing a high number of customer-impacting incidents linked to these manual operations, we decided to focus our efforts on standardizing and automating space-add operations. This, in turn, reduced both operational risk and MTTR (Mean Time To Repair) considerably.</p><h3>In Conclusion</h3><p>In the fast-paced world of IT, the ‘high velocity edge’ Spear talks about becomes indispensable. As DevOps and SRE practices become more widespread, the industry is beginning to acknowledge the immense value that these disciplines add. As Michael Dell once stated, “It’s not about being big in revenue. It’s about being profitable and growing sustainably.”</p><blockquote>“It is not about being big in revenue. It’s about being profitable and growing sustainably”</blockquote><p>While software development teams focus on bringing in new revenue, it is crucial to remember that the revenue can be quickly lost due to extended downtime. The IT Production support teams, through disciplines like SRE, work tirelessly to prevent or reduce the frequency of this from happening. They focus on reducing toil, operational risk, and striving for continuous improvement — essentially, ensuring every incident becomes an unplanned investment.</p><p>Just as Toyota strives to improve, so must IT operations continually push for improvements, constantly finding new ways to enhance efficiency, reduce operational risk, and deliver the best possible service to customers. The road to the future of IT operations is one of continuous learning and adapting — a path that, while challenging, ultimately leads to the high velocity edge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12148a2a18a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embracing Deadlines: The Symphony of Time Management]]></title>
            <link>https://medium.com/@pavan.kristipati/embracing-deadlines-the-symphony-of-time-management-f21a96a79b8e?source=rss-4f9854831e8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f21a96a79b8e</guid>
            <category><![CDATA[deadlines]]></category>
            <dc:creator><![CDATA[Pavan Kristipati]]></dc:creator>
            <pubDate>Mon, 26 Jun 2023 02:43:24 GMT</pubDate>
            <atom:updated>2023-06-26T12:09:47.775Z</atom:updated>
            <content:encoded><![CDATA[<p>As a senior IT leader, I’ve discovered a remarkable ally in our industry: deadlines.</p><p>While often perceived as formidable and intimidating, I have come to embrace them as silent motivators that propel us forward.</p><p>In this article, I will share my insights on the significance of deadlines in our professional lives and how I transformed the pressures associated with them into opportunities for growth and success.</p><p>It did not start that way, but in my journey, I have embraced them as silent motivators that keep us moving forward.</p><p>I read somewhere, “Personal accountability is the cornerstone of taking your potential to the next level,” in my experience, all forms of accountability come with deadlines.</p><blockquote><em>Rome was not built in a day, but Eiffel Tower would not be built in two years, two months, and five days if not for deadlines.</em></blockquote><p><strong>Unveiling Hidden Pressures</strong></p><p>This happened a few years ago. One of my team members was, for lack of a better phrase, under the weather about deadlines.</p><p>From what I knew, he was on board with an important effort but was reluctant to estimate the delivery date for his task.</p><p>Attempts were made to have him commit, but it was not getting anywhere.</p><p>As leaders, we need to remember that:</p><blockquote><em>Leadership isn’t just about steering the ship; it’s about ensuring all crew members are </em><strong><em>ready</em></strong><em> and </em><strong><em>willing</em></strong><em> to row.</em></blockquote><p>Key words here are “ready” and “willing.”</p><p>If either is missing, there is no difference between bonded labor and the work most of us do.</p><p>In the face of resistance, let’s remember another insightful quote:</p><blockquote><em>“Leadership is the art of getting someone to do something you want done because they want to do it.”</em></blockquote><blockquote><em>Dwight D. Eisenhower</em></blockquote><p>My personal experience is that we must go beyond the “rah rah” talk to sustain momentum.</p><p><em>Motivational pep talks may have initially spurred this team member to accomplish the desired task within the deadline. Yet, the enduring capacity for consistent performance necessitates the foundation of robust systems and processes.</em></p><p><em>This is true at work, at home, with everything, and everywhere.</em></p><p>This colleague needed help in this situation, and he was lost.</p><p><strong>Developing Empathy and Trust: Building Connections</strong></p><p>At a skip level, I encouraged him to speak openly with a genuine effort to understand him and provide support.</p><p>This colleague was under undue pressure, juggling multiple responsibilities, and always striving to satisfy everyone.</p><p>He was doing everything he could to minimize escalations to senior management, and he was not going to commit to any more deadlines because his head was hardly above the water.</p><p>Frustration in his voice was evident because there was no way things would get better.</p><p>As a team that did Production Support, Engineering work, and Project tasks, there usually is never time for “Continuous Improvement” intending to reduce toil and improve Operational Efficiencies. He was being asked to commit to one such task for which he had no bandwidth. That was the root cause for what seemed to be a lack of commitment from him.</p><p><strong>The Secret to Getting to the Impossible: “Make Work Visible.”</strong></p><p>I knew that a significant part of the strain came from the invisible nature of IT operations work. It was time to bring the invisible into the light.</p><p>“Let’s take a step back,” I proposed during our meeting. The look on my colleague’s face was an unspoken request for guidance because he heard it too many times. I told him that I was not there to talk to him into committing to a deadline but there to help him.</p><p>“Let’s make the invisible visible,” I continued, outlining the concept of using Kanban and other techniques to bring transparency to our work.</p><p>Usually, frameworks like Kanban are met with resistance in IT Operations teams. “I cannot plan my day as I am in Production Support.” That is true to some extent.</p><p>Production Support teams often deal with a high volume of unplanned work, such as handling incidents, which can seem incompatible with a structured framework like Kanban. However, if used appropriately, Kanban can be very effective for managing this type of work.</p><p>I explained to him that the key benefit of using Kanban in a Production Support team is its ability to bring clarity and visibility to work, allowing for better management and, eventually, a more efficient workflow.</p><p>At its core, Kanban is about visualizing work, limiting work in progress, and maximizing flow, which can be applied to even the most unpredictable environments.</p><p>I recommended we use a two-pronged approach. During multiple working sessions:</p><ol><li>We created dashboards that showed us trends, hard numbers, and comparisons (from previous periods). This is exclusively for unplanned work like Incidents etc. Some of the planned work (but with limited visibility into the future) was also tracked here. We started with broad categories like “To Do,” “Doing,” and “Done” and improved from there. This was done in our ITSM tool.</li><li>In our workload planning tool (ADO Boards, for example), we created a framework to identify “Backlogs,” “Ready to work,” “In Progress,” “Blocked,” and “Closed” — essentially different statuses of tasks.</li></ol><p><strong>The Benefits of Work Visibility:</strong></p><p>The adoption of these practices resulted in numerous benefits for our team:</p><ul><li>Visualizing the Work: Team members and leadership could easily grasp the status of each incident or task at a glance. “Who is doing what?” is easy to answer.</li><li>Limiting Work-In-Progress (WIP): By focusing on fewer incidents at a time, team members could resolve them more efficiently rather than being overwhelmed by multiple simultaneous tasks. WIP is the worst offender of bandwidth issues.</li><li>Managing Flow: Monitoring the movement of incidents and tasks through the workflow helped identify bottlenecks and areas for improvement, enabling us to optimize our processes.</li><li>Feedback Loops: Regular meetings to review the Board allowed for discussions on process improvements and addressing any issues.</li></ul><p><strong>From Burnout to Balance:</strong></p><p>Over time, the newfound work visibility brought about a remarkable change in dynamics.</p><p>Prioritization became more straightforward, communication improved, and deadlines became more manageable. We were able to negotiate deadlines when we “showed” others how busy we were with already committed work. Such conversations were met with understanding. Existing priorities must be moved to the backlog to accommodate the new job. This significantly differs from adding to the existing active work that had exasperated the problem.</p><p>Consequently, the pressure my colleague experienced started dissipating, leading to a healthier work-life balance. It took time, but it happened.</p><p>We successfully transformed a situation bordering on burnout into one of equilibrium without losing valuable team members to overwhelming invisible workloads.</p><p><strong>Embracing Deadlines as Markers of Achievement:</strong></p><p>In a recent conversation, the same team member shared with me that he now views deadlines not as burdens but as milestones on their journey toward great achievements.</p><blockquote><em>All great achievements require time.</em></blockquote><blockquote><em>Maya Angelou</em></blockquote><p>Deadlines are not mere limitations; they are the rhythmic pulses that propel us toward greatness, orchestrating the symphony of achievement.</p><p><strong>Conclusion:</strong></p><p>By embracing deadlines and leveraging effective time management techniques, we can transform what was once perceived as a daunting challenge into a symphony of productivity and success. As senior executives, showcasing our ability to navigate deadlines with finesse demonstrates our leadership skills and propels our careers forward. Let us embrace deadlines as our constant companions on the path to excellence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f21a96a79b8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>