<?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 Miljan Bajic on Medium]]></title>
        <description><![CDATA[Stories by Miljan Bajic on Medium]]></description>
        <link>https://medium.com/@miljanbajic?source=rss-f335e051c5b1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*Eo-W6CnN-uIyNlOQvgdJKw.jpeg</url>
            <title>Stories by Miljan Bajic on Medium</title>
            <link>https://medium.com/@miljanbajic?source=rss-f335e051c5b1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:18:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@miljanbajic/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[Moving from Agile to Agility — Kuhn’s Cycle]]></title>
            <link>https://miljanbajic.medium.com/moving-from-agile-to-agility-kuhns-cycle-64cb06991a2b?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/64cb06991a2b</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Fri, 20 Dec 2024 00:36:31 GMT</pubDate>
            <atom:updated>2024-12-20T00:36:31.437Z</atom:updated>
            <content:encoded><![CDATA[<h3>Moving from Agile to Agility — Kuhn’s Cycle</h3><h3>A Paradigm Shift</h3><p>The journey from the Waterfall model to Agile frameworks, and eventually to true organizational agility, can be aptly explained through Thomas Kuhn’s “Structure of Scientific Revolutions” and his concept of the paradigm shift. Kuhn’s framework outlines how paradigms evolve and how revolutionary changes occur when existing systems fail to address emerging challenges. This article explores the transformation in software development and organizational practices through the lens of Kuhn’s cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LmSNpis5p-H-FYBB" /></figure><h3>1. The Pre-Paradigm Phase: Early Software Development</h3><p>In the early days of software engineering, practices were ad hoc and inconsistent. Projects were often managed without structured methodologies, leading to unpredictable results. The absence of a unified framework characterized this pre-paradigm phase, where teams relied on individual experiences and intuition rather than standardized processes.</p><h3>2. Normal Science: The Dominance of Waterfall</h3><p>As software projects grew in complexity, the need for structured processes became apparent. The Waterfall model emerged as a dominant paradigm, introduced by Dr. Winston W. Royce in the 1970s. Waterfall provided a linear and sequential approach, with distinct phases: Requirements, Design, Implementation, Verification, and Maintenance.</p><p>For decades, this model was the “normal science” of software development. It offered predictability and a sense of control, particularly in environments where change was minimal. Organizations thrived under this paradigm until its limitations began to surface in the face of increasing market volatility and customer demands for flexibility.</p><h3>3. Model Drift: The Cracks in Waterfall</h3><p>Over time, cracks in the Waterfall paradigm began to appear. Projects often failed to deliver value on time or within budget. Stakeholders became frustrated with the inability to accommodate changes mid-project. The rigidity of Waterfall was increasingly at odds with the dynamic nature of software requirements.</p><p>This phase of model drift highlighted the inefficiencies and mounting challenges of the existing paradigm. As the gap between expectations and outcomes widened, it became clear that a new approach was necessary.</p><h3>4. Model Crisis: The Emergence of Agile Frameworks</h3><p>The crisis point came as software development projects faced higher failure rates. Reports like the Standish Group’s CHAOS studies revealed alarming statistics on delayed and over-budget projects. Organizations realized that a rigid, one-size-fits-all approach could no longer sustain their needs.</p><p>Agile frameworks emerged as a response to this crisis. The publication of the Agile Manifesto in 2001 marked a turning point, advocating for:</p><ul><li>Individuals and interactions over processes and tools.</li><li>Working software over comprehensive documentation.</li><li>Customer collaboration over contract negotiation.</li><li>Responding to change over following a plan.</li></ul><p>Frameworks like Scrum, Kanban, and Extreme Programming (XP) became the tools of this new paradigm. Agile emphasized iterative development, continuous feedback, and adaptability — a stark contrast to the rigid, linear approach of Waterfall.</p><h3>5. Paradigm Shift: Agile to Agility</h3><p>The adoption of Agile frameworks was not simply a procedural change — it represented a significant rethinking of how organizations approach work, value, and collaboration. The shift to iterative cycles, cross-disciplinary collaboration, and incremental delivery reshaped team dynamics and organizational priorities. Yet, as the initial enthusiasm settled, it became clear that frameworks alone were insufficient. They often provided structure but not substance, direction but not purpose.</p><p>What emerged was a deeper realization: agility is not confined to methods or tools but is instead a systemic capability, rooted in how organizations think, learn, and adapt at every level. It demands more than compliance with a set of practices. True agility is embedded in how people and systems engage with complexity, uncertainty, and change.</p><p>To navigate this shift, organizations must move beyond checklist approaches and adopt a more holistic perspective that recognizes the interplay of individuals, relationships, and systems:</p><ul><li>Mindsets and Values. The starting point for any transformation is the individual. Agility requires fostering adaptive mindsets and behaviors that enable people to work effectively in uncertainty. Emotional intelligence, a willingness to experiment, and the capacity to learn from failure are critical. Psychological safety — creating an environment where questioning, dissent, and innovation are encouraged — is essential for people to thrive and contribute.</li><li>Skills and Behaviors. While mindset sets the foundation, action shapes outcomes. Practical skills such as iterative thinking, situational awareness, and collaboration across boundaries equip individuals and teams to engage with complex problems. Organizations must invest in developing these skills while giving individuals the autonomy and authority to make decisions as close to the work as possible.</li><li>Culture and Relationships. No individual or team operates in isolation. Agility depends on fostering a shared sense of purpose and aligning work across departments and disciplines. Relationships built on trust and transparency enable knowledge to flow and decisions to align with broader organizational goals. Without this shared context, efforts to create agility devolve into fragmented activity, producing friction rather than flow.</li><li>Structures and Systems. At a broader level, agility is constrained or enabled by the systems in which people work. At the heart of structural agility lies the need to move beyond rigid, siloed organizational hierarchies and embrace value stream networks. Value streams represent the end-to-end flow of activities required to deliver value to customers. In traditional organizations, these streams are fragmented by departmental boundaries, leading to inefficiencies, misaligned priorities, and delays. By shifting to value stream networks, organizations can reorient themselves around the seamless delivery of outcomes. These networks emphasize connections rather than divisions, enabling cross-functional teams and systems to align directly with customer needs. This approach not only breaks down silos but also fosters visibility and accountability across the organization. When designed effectively, value stream networks ensure that workflows efficiently from idea to impact, with minimal friction.</li></ul><p>Agility is not a static state — it is an ongoing, dynamic capability. It thrives in environments where feedback loops are frequent, learning is continuous, and decisions are informed by real-time interactions with the broader environment. It is not about eliminating uncertainty but rather developing the ability to engage with it effectively, using it as a source of insight and opportunity.</p><p>In this sense, agility is less about following a predetermined methodology or framework and more about cultivating a way of thinking and acting that embraces complexity. It aligns individuals with collective goals, connects internal strengths to external demands, and integrates purpose with action. Organizations that succeed in this shift are not just improving incrementally — they are evolving into systems capable of sustaining value creation and adaptation in a world where uncertainty is the norm.</p><h3>6. Post-Paradigm: The Era of Continuous Evolution</h3><p>As the principles of agility extend beyond individual organizations and industries, they are becoming a defining feature of how modern societies operate. This marks a shift into a post-paradigm era where agility evolves from a specialized approach to a foundational norm — a form of “normal science” embedded in the fabric of work, decision-making, and societal progress. In this stage, agility is no longer confined to specific frameworks or methodologies but instead becomes a paradigm that drives continuous evolution across diverse domains.</p><p>Agility shifts from being an innovative approach to the “new normal science,” embedded as the default way of managing uncertainty and delivering value. This era emphasizes continuous evolution rather than static solutions. Industries and governments co-create adaptive infrastructures, prioritize real-time learning, and build systems designed to thrive in uncertainty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SuTzh5v_YCUmHQUBfbwL2w.png" /></figure><h3>Lessons from Kuhn: Navigating Paradigm Shifts</h3><p>Kuhn’s cycle teaches us that paradigm shifts are not linear or easy. They involve periods of instability, resistance, and experimentation. Moving from Waterfall to Agile to organizational agility requires:</p><ul><li>Recognizing the signs of paradigm drift and crisis.</li><li>Encouraging experimentation and learning from failures.</li><li>Embracing new mental models and unlearning old habits.</li><li>Viewing change as an opportunity rather than a threat.</li></ul><p>The evolution from Waterfall to Agile frameworks and then to true organizational agility exemplifies a paradigm shift in the truest sense. As Thomas Kuhn’s cycle illustrates, such transformations are inevitable when old paradigms fail to address emerging complexities. By understanding this journey, we can better navigate our own transitions, fostering a culture of adaptability and resilience in an ever-changing world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64cb06991a2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cooks and Chefs: Why Agile Hasn’t Fixed Our Problems]]></title>
            <link>https://miljanbajic.medium.com/cooks-and-chefs-why-agile-hasnt-fixed-our-problems-8d76236226d3?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d76236226d3</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Thu, 29 Oct 2020 19:03:02 GMT</pubDate>
            <atom:updated>2020-10-31T05:56:06.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0YFE6NudZnRXP_KRZPrrBg.jpeg" /></figure><p>If you haven’t had an “Agile” evangelist (like myself) hunt you down yet, here’s what to expect. We might suggest that if you don’t know how Agile and one of its popular frameworks will revolutionize your product, service, or industry, we think your company is squarely located under a rock.</p><p>Okay, I’m just kidding. But you know what I’m saying? Agile has become a jungle of tooling vendors and consulting companies selling frameworks that are implemented as a blueprint. There are too many cooks, when what we need are chefs. Let me explain…</p><p>Cooks follow recipes. Chefs create them. It’s much easier to copy recipes that work, and for many aspects of our life, it probably makes sense to act as a cook. Cooks span a wide range.</p><h3>Cook by the Book</h3><p>On one end, we have cooks who only cook by following a recipe to the letter, carefully measuring every ingredient precisely the way the recipe dictates. The result is a delicious meal that tastes exactly the way the recipe has it designed.</p><p>In the professional consulting and coaching industry, this is somebody who swears by their favorite framework and acts dogmatically like they just drank the agile kool-aid. How many people like this do you know?</p><h3>Cook with Unique Style</h3><p>Down the range a bit, we have more of a confident cook — someone with experience who gets the general gist of the recipe and then uses her skills and instincts to do it her way. The result is something a little more unique to her style that tastes like the recipe but not quite.</p><p>The professional consulting and coaching industry is full of cooks with a unique style. Everybody today calls themselves an agile coach and consultant. They all tend to claim that they have a unique style and experience. All they have is the general gist of agile frameworks and some confidence at this point in the spectrum.</p><h3>Cook with Innovations</h3><p>At the far end of the cook range, we have an innovator who makes her version. But what all of these cooks have in common is their starting point is something that already exists. Even the innovative cook is still making an iteration of a burger, a pizza, and a cake.</p><p>In the professional consulting and coaching industry, these are the experienced coaches and consultants that understand the underlying patterns and principles behind the frameworks. For cooks, even the more innovative kind, there’s almost always a ceiling on the size of the splash they can make in the world unless there’s some luck involved. In the past, there was nothing wrong with being a cook. In today’s environment, cooks without chefs to help them grow will not help you push boundaries and create solutions to the disruptions your industry faces presently and in the future.</p><h3>Chef</h3><p>At the very end of the spectrum, we have the chef. The chef reasons from principles, and for the chef, the principles are the available raw edible ingredients. Those are her puzzle pieces, her building blocks, and she works her way upwards from there, using what’s available, her experience, her instincts, and her taste buds. The chef creates while the cook, in some form or another, copies.</p><p>In the professional consulting and coaching industry, the essential thing the chef knows that the cooks don’t is what it takes to change the culture. In my upcoming book, <a href="https://medium.com/@miljanbajic/wicked-leadership-c044227372e3">Wicked Leadership</a>, I show how organizational culture is shaped by the mindsets, actions, and systems. Chefs know that none of the frameworks work all the time. Instead, they help others learn the underlying thinking and principles (Systems Thinking, Complexity Management, Lean Thinking, Psychology, Culture, etc. ), then co-create a system that works best in their context. Chefs create more chefs. Is it in our DNA to be chefs? How many people do you know that want to be a chef?</p><blockquote>In complex environments, we need to work to evolve our recipes as our ingredients change.</blockquote><p>In the culinary world, there’s nothing wrong with being a cook. Most people are cooks because, for most people, inventing recipes isn’t a goal of theirs. Chefs are iterative and constantly evolving their recipes. When it comes to the reasoning “recipes” or frameworks we use to run our organizations, we may want to think twice about where we are on the cook-chef spectrum.</p><h3>The Last 20 Years</h3><p>Simply being a cook wasn’t the intent of most of the Agile Manifesto signers. The Agile Manifesto was written in February 2001, almost 20 years ago, as of this writing. In the intervening 20 years, organizations of all sizes, from the largest enterprises to the nimblest of startups, have attempted to follow the values and principles of agile. Agile — spelled with the capital A — has informed frameworks, framed transformational business strategies, and, in some communities, elevated to the status of religious dogma. In other words, we’ve become stubborn in our beliefs that agile is the way. We’re ever so sure that we’re right, that they, whoever they are, are wrong. Have you noticed it?</p><blockquote>We’ve become stubborn in our beliefs that agile is the way.</blockquote><h3>Agile Hasn’t Fixed Our Problems</h3><p>As conceived by its creators, the entire premise of agile development was that its focus should be to deliver software and continually improve it to satisfy the customer’s changing needs. Any focus that did not deliver valuable working software to the customer should be eliminated. Somehow along the way, agile got redefined by the consulting industry and what the majority of people (cooks) thought.</p><p>The truth is that most agile transformations and adoptions never delivered what they promised. Agile adoption failure stories are abundant. Just talk to anybody that’s been part of one and hear what they have to say. A very large majority of all of these so-called “Agile” transformations and adoptions fail to generate the capability to adapt to changing market conditions. In this context, failure means that change initiatives that use agile approaches are reversed, canceled, or don’t deliver the desired results.</p><blockquote>Agile, as we know it today, hasn’t fixed our ongoing problems. It never will. It was never meant to do that.</blockquote><p>Regularly, thousands of coaches and consultants are asked if they could help bring agility and responsiveness to the organization. This leadership and organizational addiction to bringing in consultants and coaches to fix their problems have been around since the 1920s when James McKinsey and Marvin Bower injected the consulting industry with a professionalism that would shape it for the next 100 years. Bringing in coaches and consultants is like bringing in outside cooks and chefs to tell our kitchen staff what to do. The problem with this approach is that it only works until it doesn’t.</p><p>We need to trust our people and not be dependent on consultants to tell us what to do. Do you know anyone that’s tired of depending on external consultants? How about anyone that’s tired of not being able to create things and watch them flourish?</p><h3>New England Clam Chowder</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kU9p1N6ALkd74JSY" /></figure><p>To say that I love the New England Clam Chowder would be an understatement. Made as it should be, is a dish to preach about, to chant praises and sing hymns and burn incense before. It has about a dozen ingredients that make it a signature dish here in the North Eastern United States. Similar to New England Clam Chowder, Scrum also has about a dozen ingredients (roles, events, artifacts, values) that make it a powerful framework for product development.</p><p>Now imagine that you are a cook who does everything by the book. But you don’t have all of the ingredients for the New England Clam Chowder. Instead of clam juice, you add white wine, and instead of butter, you add coconut oil because you heard from another cook that those are good substitutes. Now we have something that looks like a New England Clam Chowder but doesn’t taste like it. As a cook, you are not aware of how these new ingredients are reacting to other ingredients. I see this all the time with Scrum, where people pick and choose what they like from the Scrum framework. A few weeks ago, I did a workshop, and I heard somebody say that they’re doing Daily Scrum every other day because the team has too many meetings. It might look like they are doing Scrum on the surface, but when we look at the outcomes and behaviors, it’s not cutting the mustard. There is nothing wrong with using different ingredients if we know what we’re doing. Just don’t call it Scrum or New England Clam Chowder.</p><h3>Why We Need Chefs</h3><p>The new wave of agile is here, and guess what? It’s not coming from the consultants. It’s coming from the people and companies that have realized that to adapt to the changing market conditions, they need to create their own chefs and recipes.</p><p>In a fast-changing work environment, where “ingredients” are changing so rapidly, there is no single framework or recipe to address all our needs. If every team in our company is doing the same thing, we are not “big-A” agile or “little-a” agile. Instead, every team should be evolving its way of working. When we are truly agile we can change our direction very quickly — we can redirect individual teams and what they’re building very quickly. What I’ve seen is that we need about 10–15% of the employees to be able to step in and occupy the full cook-chef spectrum. How do we learn to be more like the chefs of the world, who seem to carve their own way through life so effortlessly? We need both chefs and cooks. We need our chefs to help the organization create more chefs. Our internal chefs need to create something delicious from the ingredients available rather than blindly following popular recipes and frameworks.</p><p>If you start looking for it, you’ll see the chef/cook thing happening everywhere.</p><p>Dare to be a chef!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d76236226d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Collective Sensemaking for Wicked Problems]]></title>
            <link>https://miljanbajic.medium.com/collective-sensemaking-for-wicked-problems-de1291561026?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/de1291561026</guid>
            <category><![CDATA[wickedleadership]]></category>
            <category><![CDATA[wicked-problem]]></category>
            <category><![CDATA[sensemaking]]></category>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 15:25:23 GMT</pubDate>
            <atom:updated>2020-08-11T15:35:49.514Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ewocr9ZZG4BTR9dNka41Ew.png" /></figure><h3>Collective Sensemaking: The Game Has Evolved</h3><p>Imagine you were just invited to play a game, but no one knows the rules. What do you do when something doesn’t make sense? Well, as each player makes a move, you attempt to determine their motives and objectives. Through trial and error, you make your moves and look for acceptance or disapproval from the group. Eventually, you decide the rules and play the game. That’s sensemaking in action. In a way, you are constructing a mental map of what you can’t see.</p><h3>What is sense-making?</h3><p>Organizational psychologist Karl Weick coined the term “sensemaking,” and just like it sounds, it means making sense of the world around us. Sensemaking can be individual or collective, prospective or retrospective. It’s how groups and individuals socially construct the meaning of an ongoing flow of experience and create structure out of the unknown. It’s about the construction of reality and its consequences. Without realizing it, we try to make sense of things all the time so we can see and act on them. Sensemaking is a vital skill. An important benefit of sensemaking is that it helps to build shared understanding and collective action. However, it’s a skill where many people often come up short when it comes to complex environments.</p><h3>The terrain has changed and the map is no longer adequate.</h3><p>Sensemaking has always occurred in individuals and society, however, it is receiving new attention. The economic transition from manual labor to knowledge-based work has pushed sensemaking to the forefront as a useful skill for leadership. The terrain has changed and the map is no longer adequate. Since sensemaking is a cognitive process, we need to create a larger capacity to make sense of uncertainty and emerging behavior.</p><p>Our emotions, thinking, actions, culture, and environment shape the sensemaking process. After my wife and I moved into our first house, we tried to figure out a more efficient layout for our kitchen. We slowly figured out the layout problems by using the kitchen as much as we could. For example, we put our spices on a particular shelf when we moved in. Later, my wife found it inconvenient to turn around every time to reach them when she was cooking. As a result of trying many different things, we installed a spice rack next to the oven which makes a lot more sense. Sometimes, making sense does not make sense right away, it takes time.</p><h3>A constant process of acquisition, reflection, and taking action</h3><p>A former student of Karl Weick taught one of my first classes at college. A significant part of the course was spent discussing how sensemaking is a simple concept, but not so simple to employ in the workplace. Why? Because sensemaking is a constant process of acquisition, reflection, and taking action on things that are both visible and invisible. We’re always trying to make sense of our thoughts, feelings, relationships, culture, behaviors, actions, and systems in our organizations. The sensemaking process shapes organizational structure and behavior. In return, the organizational structure and behavior shape the culture of the organization. In other words, our sensemaking ability is the reflection of our cognitive ability.</p><p>Weick likened the process of sensemaking to cartography. What we map depends on where we look, which factors we focus on, and which aspects of the terrain we decide to represent. Since these choices will shape the kind of map we produce, there is no perfect map of the territory. Therefore, making sense is more than an act of analysis, it’s an act of creativity. Practicing sensemaking is like drawing a map that’s constantly evolving. If you construct an evolving map for a complex situation, you are going to be able to have a better understanding of that situation and you will be able to use the map as a framework to build a shared understanding with others. Sensemaking is not about drawing the right map, but rather, facilitating your team in referring to the same map. The map will change over time, but it’s amazing what you’ll discover through this process.</p><h3>Leadership is about making things happen, contingent on a context.</h3><p>Leaders may create change by playing a central role in the actual change process, or by creating an environment in which others are empowered to act. Good leaders understand that sensemaking is a continuous process, and they let the map emerge. In a turbulent environment, leaders need to spend more time sensemaking and connecting the dots by looking through multiple lenses. Marcel Proust, one of the most influential authors of the 20th century, famously said, “The real voyage of discovery consists not in seeking new lands but seeing with new eyes.” As Proust infers, we don’t have to discover new landscapes to be in the creative process of discovery. Sometimes we simply need to change our perspective, to elevate it, and see what we already know so well through new eyes.</p><h3>Ongoing flows of experience</h3><p>Sensemaking is different than decision-making because we don’t analyze isolated events but rather, more comprehensive, ongoing flows of experience. It moves our thinking to the co-creation of the organizational context of how people are constructing meaning and influencing one another. In the sensemaking process, individuals do not rely on a single source of information. Instead, they integrate multiple sources of information and synthesize that information together.</p><h3>The Ceiling</h3><p>At IDEO, a product design firm, sensemaking is step one for all design teams. According to founder David Kelley, team members must act as anthropologists studying an alien culture to understand the potential product from all points of view. When brainstorming a new design, IDEO’s teams consider multiple perspectives. They build various maps to inform their creative process. One IDEO team was charged with creating a new design for an emergency room. To better understand the experience of key patients, team members attached a camera to a patient’s head and captured his experience in the ER. The result was nearly ten full hours of film showing the ceiling. The sensemaking provoked by this perspective led to a redesign of the ceiling that made it more aesthetically pleasing and able to display valuable information for patients. Sensemaking helps us shift our focus from a rational and static picture that delineates our reality to a continuously changing worldview.</p><h3>Collective Sensemaking for the Wicked Problems</h3><p>We live in a world that’s densely interconnected and exponentially changing. Yesterday’s best practices are rapidly becoming outdated. On top of that, our institutional architectures, the way we build large-scale organizations, are reinforcing these outdated practices and actions.</p><p>Yet, many of our problems are <a href="https://www.google.com/search?q=wicked+problems&amp;oq=wicked+problems&amp;aqs=chrome..69i57j69i59j35i39j0l2j69i61j69i60l2.2849j0j7&amp;sourceid=chrome&amp;ie=UTF-8">wicked problems</a>. These problems are not complicated. They are complex and adaptive. In his seminal book <em>The Inevitable: Understanding the 12 Technological Forces That Will Shape Our Future</em>, author Kevin Kelly describes how the cycle of obsolescence is accelerating and how things may change in the next 30 years. The book is impressive in its breadth and depth. Kelly explains that the average lifespan of a phone app is less than a month, and how we won’t have time to master anything before it is displaced.</p><p>Complex organizational challenges mean we need to embrace collective sensemaking and leadership voids. Advanced sensemaking skills and capacities could enable leaders and organizations to not only face unexpected challenges but also to create opportunities to flourish.</p><h3>Creating A Shared Meaning</h3><p>How can leaders remain effective in an environment that only becomes more and more complex? Sensemaking as leadership is the process of creating shared meaning. Without sensemaking, there’s no common view of reality from which to start. Sensemaking enables leaders to have a better grasp of what is going on in their environments, thus facilitating other leadership activities such as visioning, relating, inviting, and inventing. A sensemaking perspective reminds us that it is not merely the reality that matters, but how the problems and situations are interpreted. In this new world of obsolescence and acceleration, new lenses are required. Our sensemaking capacity needs to grow beyond current abilities. The game has evolved. The question is, have you?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de1291561026" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Four Lenses of Wicked Leadership]]></title>
            <link>https://miljanbajic.medium.com/the-four-lenses-of-wicked-leadership-a12a74be7a39?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a12a74be7a39</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Sat, 13 Jun 2020 05:27:52 GMT</pubDate>
            <atom:updated>2020-11-15T19:48:59.547Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/527/0*8eVhFwOTD5Ui0Vxl" /></figure><h3>The Four Lenses</h3><p>The four lenses operate in a continuum between the poles of the invisible aspects (left side) and the visible aspects (right side), as well as individual (top) or collective (bottom) aspects. If I want to describe an organization, I would use both invisible and visible perspectives. For the visible side of the organization, I can look at its organizational architecture, policies, and strategy (bottom-right). I could also observe employee behavior, practices, and habits (top-right). However, I am not able to see what people are thinking, feeling, and the values that they live by (top-left). I also can’t observe invisible norms, relationships, and shared values amongst the employees that make up the organization’s culture (bottom-left). The culture is intangible and resides within the mind and relationships of the individuals who are part of the organization.</p><p>We can look at any organization from these four lenses. The four lenses are closely intertwined and can help us map every bit of organizational knowledge and experience into a holistic view. We have to look at an organization through all of these lenses in order to adequately describe it. It always has the systems and structures, culture and relationships, practices and behaviors, and individuals who have thoughts, feelings, and values. Evolution in organizations takes place in all four lenses.</p><p>A wicked problem in any of these areas will reverberate through all four lenses because every wicked problem has these four facets. Your mindset lens (upper-left) zooms into your interior experience, intentions, motivations, ethics, emotions, and mindset. The culture (lower-left) lens helps you see the culture of your organization that’s comprised of the shared values and beliefs of your peers. The systems (lower-right) lens zooms into the various contexts in which your organization exists, including its systems, structures, customers, and the wider environment. And the actions (upper-right) lens looks at the exterior actions and behaviors of you and your peers. This includes the way your awareness is expressed in terms of the actions, behaviors, and competencies which are used when you are performing our role effectively. Let’s say that your organization doesn’t have an equal pay system (lower-right). That will reflect in low morale for people that feel that is unjust (upper-left), and that feeling, thinking, and lack of motivation will be apparent in their actions and behaviors (upper-right), leading to a culture of low employee engagement (lower-left). Thus, a dysfunction that shows up most prominently in one lens is also present in the other three lenses.</p><p>Let’s look at each lens in more detail:</p><p><strong>Mindset Lens</strong></p><p>The top left lens represents individual needs, values, mindsets, beliefs, emotions, self-awareness, cognition, worldviews, and attitude. These are things that are invisible and subjective from other people’s point of view. We can’t observe individual mindsets, thinking, and emotions but we can infer it from behaviors and practices in the top right quadrant. For example, nobody can see what I’m thinking, feeling, or what my values are.</p><p><strong>Actions Lens</strong></p><p>In the top right lens, our behaviors, practices, habits, skills, performance, and other observable actions will be visible and highly influenced by our mindset quadrant. The actions lens helps us make sense of how we use our actions to satisfy our needs. For instance, if my mindset and values are very ego-centric, then those will manifest themselves through my actions towards satisfying my needs and controlling my environment to achieve those needs.</p><p><strong>Systems Lens</strong></p><p>In the bottom right lens, this is the big picture and it shows how things fit and work together in an organization as a bigger system. As a group, we use our collective thinking, feeling, values, behavior, and actions to implement organizational systems such as architecture, structure, governance, policies, processes, strategy, and technologies, as well as metrics to measure our organization’s performance across these systems.</p><p><strong>Culture Lens</strong></p><p>Our shared values, shared history, invisible norms, relationships, ethics, stories, meanings, and group dynamics exist in the bottom left quadrant. Culture emerges from the other three quadrants and, in return, this lens reinforces them. In other words, our culture is a reflection and manifestation of our mindset, actions, and systems.</p><p>By considering all four lenses, you acquire a holistic view of the current reality of how your organization functions. These four lenses each reflect organizational reality in their own unique and valuable way. The right side of the quadrant that includes actions and systems focuses on competency and functions. The left side of the quadrant that includes mindset and culture focuses on capacity. What you see through these lenses will depend on the platform that you use. We need to increase our cognitive capacity (top-left) to improve our competence (top-right). If you want to be better able to deal with wicked problems, you need to evolve your mindset lens. Our mindset drives how our actions and organizational systems manifest. Mindset, actions, and systems are what determine your culture. And culture always wins.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a12a74be7a39" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Infinite Game]]></title>
            <link>https://miljanbajic.medium.com/the-infinite-game-613003a0e3cc?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/613003a0e3cc</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Fri, 29 May 2020 05:36:09 GMT</pubDate>
            <atom:updated>2020-05-29T14:02:07.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LWXbq9m9JTbvXvdX1LbTbw.png" /></figure><p>There was a time when Enron Corp. was considered one of the best corporations in the world. It was voted “most innovative” six years in a row by People Magazine. In 1999, the executive committee of Enron Corp. was conducting creative vision sessions to select a new slogan for the company. Enron was on a roll, entering new markets and growing in existing ones. But the old motto, “The world’s leading energy company,” was no longer working for them. Their top choice for a replacement was “World’s coolest company.” When asked by a reporter about their vision, Enron’s President at that time, Jeffrey K. Skilling, said, “It’s a vision of innovation; it’s a vision of creativity.” They even considered wrapping the headquarters building in a pair of giant sunglasses. For Enron, it was all about winning. Everything else came second. Today, the name Enron is synonymous with greed, ego, and win-at-all-cost mindset. Winning is a reasonably standard goal for an organization, of course. And a good one. But how you define “winning” makes all the difference in how your people work to achieve it. Most importantly, how individual values, beliefs, and culture manifest themselves through actions.</p><p>In his book, <em>The Infinite Game</em>, Simon Sinek applies game theory to explore how we look at winning and losing. He describes the difference between finite and infinite games and how the winning for these two types of games is different. A finite game is played for the purpose of winning — an infinite game to stay in the game. If we look at the National Basketball Association (NBA) as an example, we’ll see this idea in the application. Professional Basketball is both a Finite and an Infinite Game. Every season, 30 professional NBA teams play a series of 82 games. These are finite games. There are winners and losers of each game. Teams hire and fire coaches and players, develop tactics and innovative strategies, and do their best to win as many games as possible. All teams play by agreed-upon rules, rules enforced with a high level of scrutiny, with multiple referees and video replay to ensure that players conform to the rules. Teams do everything they can to win. Enough victories in the regular season, and a team can move on to the playoffs, another series of finite games. In the end, there is an annual NBA Champion.</p><p>For teams and fans, each season is a finite game. But from the standpoint of the National Basketball Association, basketball itself is an infinite game. Their objective isn’t to win or lose games, but to make sure that all 30 teams have enough financial success to return next season. Using mechanisms like salary caps, TV revenue sharing, and the player draft system, the league tries to “level the playing field.” It’s in no one’s best interest to have a team fail and go out of business. Players of an infinite game continually adjust the rules to prevent that result.</p><blockquote>There is no winning in infinite games. The objective is to continue playing the game. Leaders who embrace an infinite mindset, says Sinek, will eventually build stronger, more innovative, and more inspiring organizations with the resilience to thrive in an ever-changing world.</blockquote><p>When you put a finite player against a finite player, the system is stable. When you pit an infinite player versus an infinite player, the system is also stable. Problems arise when you put a finite player against an infinite player. The finite player is playing to win, and an infinite player is playing to keep playing. As a result, they will make very different strategic choices.</p><p>The conflict in the Balkans is another example of a finite and infinite game. The Balkans have historically been the key battlefield between Islam and European civilization since the battle at Kosovo, where the Ottoman Turks clashed with the Serbs in 1389, to the present. At its apex, the Islamic tide reached and was stopped at the gates of Vienna in 1683. The Ottoman Empire was finally pushed out in the Balkan War of 1912 when the combined armies of Greece, Serbia, Montenegro, and Bulgaria were stopped at the Gates of Istanbul by the intervention of the great European powers of that period. Why did they do that? Perhaps they knew that they were playing an infinite game. Balkans were under the Ottoman Empire rule for almost 500 years. The conflict in the Balkans in the 1990s was a continuation of this infinite game between religions. However, a lot of people, especially the leaders, during the civil war in Yugoslavia, had a win-at-all-cost mindset and saw these wars as a finite game that they needed to win. The current living conditions in the former Yugoslavian countries such as Serbia, Croatia, Bosnia, and Montenegro were caused by people stubbornly holding on to centuries-old grudges and limited mindsets. All of our actions reflect the mindset behind them.</p><p>In September of 2015, the Environmental Protection Agency (EPA) found that many Volkswagen cars being sold in America had a “defeat device” or software in diesel engines that could detect when they were being tested, changing the performance accordingly to improve results. The German car giant has since admitted cheating emissions tests and said that they suffered from a limited mindset. The bad news for Volkswagen is that a limited mindset, one that’s distorted or out-of-touch, can point people to do things they absolutely shouldn’t do. The good news for all of us is that we can evolve our values, beliefs, and mindsets, including our understanding of “winning.” When we do that, we can foster entirely different choices and create very different results. However, changing mindsets and cultures is not easy. In May 2017, Volkswagen CEO Matthias Mueller, said during a discussion with business representatives, “I don’t know whether you can imagine how difficult it is to change the mindset.”</p><p>Over the past few decades, global corporations have been hit by scandals, and it mostly boils down to individual values, beliefs, and culture. Many have reported stories about behaviors that defy great organizational culture, such as employees falsifying records to help their bosses during the Enron scandal. Or how supervisors were helping their subordinates by overlooking coworkers rule-breaking during the JP Morgan scandals that ranged from dubious recruiting forays in China, manipulation of electricity markets, to paying billions related to the Bernie Madoff Ponzi scheme. Then there was a wide-ranging scandal involving FIFA. The Department of Justice indicted 14 high-ranking soccer officials on racketeering and corruption charges that eventually engulfed organization head Sepp Blatter, who announced his resignation. Martin Shkreli, CEO of Turing Pharmaceuticals, was pilloried for jacking up the price of a drug used by HIV patients by 5,000% to $750 a pill. He would eventually be arrested for securities fraud involving his activities at another company.</p><p>Wells Fargo’s aggressive sales tactics led to the creation of millions of fake customer accounts. The grueling testimonies from CEO John Stumpf, coupled with insights from my industry-wide research into the culture and mindsets of bankers, suggest a win-at-all-cost mindset of senior leaders at Wells Fargo. Along with fixing the sales culture, the bank will have to address these critical mindset gaps to prevent the next scandal.</p><p>Many athletes have this a win-at-all-cost mindset. Each year, thousands of athletes are suspended for cheating. Tennis star Maria Sharapova tested positive for a banned substance and was suspended from the professional tennis tour for nine months. This limited mindset is also present everywhere. In 2019, there was a college admissions scandal, in which Hollywood stars and other wealthy families paid thousands of dollars to get their kids into colleges. The biggest and most deadly scandal in the 2010s was the one that involved Boeing 737 Max. Messages obtained by The New York Times showed Boeing officials knew about severe problems in its 737 Max plane years before the crashes, which claimed the lives of nearly 350 people.</p><p>Tony Hseih, CEO of the online shoe retailer Zappos, once famously said that he didn’t know anything about shoes, but knew a lot about creating workplace culture. Zappos has a well-defined recruitment and induction process called the Zappos Family New Hire Program. It’s not a rubber-stamping probation period, but values fit assessment. Every new hire, regardless of role or department, goes through the four-week program, which combines technical training and culture immersion. In the end, the employee has full knowledge of what the organization stands for and how it does business, and the organization can assess the mindset of the individual and how he or she can contribute to Zappos’ values.</p><p>No leader, no matter how smart they are, will be able to enable alignment in an organization that thinks it’s playing the finite game and has a win-at-all-costs mindset. With a finite game mindset, we are self-focused. We see only our own needs, challenges, and objectives. By contrast, an infinite game culture enables all to envision and pursue a collective result. With an infinite game mindset, people focus on achieving their long term goals in context, with a clear understanding not only of how their actions contribute to collective results but also how they are impacting others’ abilities to contribute.</p><blockquote>As a leader, you need to spearhead the shift to an infinite mindset by focusing on the collective result, your role in it, and how you’re impacting others. As you honestly hold yourself accountable for your impact on others, you model that change, and walking the walk will invite people to change their mindsets.</blockquote><p>Too often, people in organizations primarily identify around their separate, individual roles. With an infinite game mindset, teams and team members break free from the constraints of self-focus and can see options that would not otherwise occur to them. The basic ways they see the world are different: with a finite game mindset, people tend to see each other as objects; with an infinite game mindset, they see each other as people. Instead of acting in ways calculated to benefit or justify themselves, they take into account their impact on others and adjust their efforts to be more helpful. They consider others needs and act in ways that further the collective results they are committed to achieving.</p><p>Playing in the infinite game of business is about evolving our mindset. It’s the value of continuous learning. It’s the value of speaking to people inside and outside of your industry around what’s coming and how to stay relevant. It’s easy to slip up in the infinite game. It’s easy to become finite minded. It’s easy to focus on the expedient, especially when there’s pressure from people inside and outside of our organizations. Together is better. Get ready and play the infinite game.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=613003a0e3cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Operation Cat Drop: Why it’s Important to Think in Systems.]]></title>
            <link>https://miljanbajic.medium.com/operation-cat-drop-why-its-important-to-think-in-systems-9c1f9c832a3e?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c1f9c832a3e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Tue, 10 Mar 2020 22:06:44 GMT</pubDate>
            <atom:updated>2020-03-10T22:06:44.962Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oR6ssw4CuCGJGQ0hDrNVpA.jpeg" /></figure><p>System. We hear and use the word all the time. “There’s no sense in trying to buck the system,” we might say. Or, “ I need a better system.” It seems there is almost no end to the use of the word “system” in today’s society. But what exactly is a system? A system is a construct of different interconnected elements that make a unified whole, which together produce results not obtainable by the elements alone. Systems range in complexity, from ordered systems, such as clocks, to complex adaptive open systems such as the highly diverse and interdependent ecosystems of rainforests. A pile of rocks is not a system. If you remove a single rock, you have still got a pile of rocks. However, a functioning car is a system. Remove the carburetor, and you no longer have a working vehicle. Whether you are aware of it or not, you are a part of many systems such as a family, an organization, a society, a planet, or the whole galaxy. You are a complex biological system comprising many smaller systems. But why is it important to understand systems? The idea behind that question is that a decision you make here today could have unintended consequences in some other place or time.</p><blockquote><em>Everything is interrelated, and changes that are seemingly narrow in scope can set off a domino effect that reaches far wider than ever anticipated.</em></blockquote><p>On March 1, 1992, Nikola Gardovic was the first civilian war victim to be killed in Sarajevo, Bosnia. He was the father of the groom at a wedding party that was attacked. This was the spark that ignited the war in Bosnia. Nobody could have imagined the extent of the damage to come. The Bosnian civil war was part of a European political, social, and economic system. War is a system itself, made up of many other subsystems. The war in Bosnia resulted in the almost complete destruction of infrastructure and society. It created a thorough separation of Croats, Serbs, and Bosniaks. The war left lasting ripple effects on the people who were directly impacted by the war, as well as the rest of Europe. A quarter of a century after the brutal civil war divided it along ethnic lines, Bosnia remains a semi-functional state whose existence depends on the European Union and NATO’s military to enforce the peace deal and exercise political influence. The 1995 Dayton Agreement that ended hostilities introduced four parallel sets of government administrations and a hugely complex system of ethnic quotas, leaving the central government with minimal powers. While it did bring the stability that everyone desired, it cemented the ethnic divisions that had destroyed the country in the first place. The system turned out to be a fertile ground for corruption and shadow influences as it allowed ethnic principles to govern the distribution of state resources. As a result, everything from fossil fuels and military property, to telecom operators and federal taxes, became a subject of ethnic separation and endless political struggle. The result of this political dynamic is that the country and society lives in an almost permanent state of existential anxiety, unable to move forward and unable to come to terms with its violent past. Despite the history of the Balkans, not many people grasped the full implications of the civil war.</p><blockquote><em>Sometimes, even with good intentions bad things can happen.</em></blockquote><p>In the early 1950s, there was a severe outbreak of malaria amongst the Dayak people in Borneo, Southeast Asia. To save lives, the World Health Organization decided to intervene by spraying large amounts of a chemical called DDT to kill the mosquitoes that carried malaria. They succeeded in killing many mosquitoes and significantly reducing the prevalence of the disease. However, the World Health Organization failed to see the full scope of their actions. DDT not only successfully killed mosquitoes, but it also attacked a parasitic wasp population. These wasps, it turned out, had kept in check a population of thatch-eating caterpillars. So with the accidental removal of the wasps, the caterpillars flourished, and thatched roofs started collapsing on people. If that was not enough, many other small insects were affected by the DDT, and were then eaten by geckos. The geckos developed a tolerance to the DDT but the cats who ate the geckos didn’t, and the cat population started to die off. With far fewer cats, rats took over and multiplied, and this, in turn, led to outbreaks of typhus and sylvatic plague passed on by rats. The intended cure had become worse than the initial disease, so the World Health Organization did what any self-respecting world health organization would do; they parachuted live cats into Borneo. The event was known as Operation Cat Drop.</p><p>The World Health Organization had failed to consider the full implications of their actions on the delicate ecology of the region. Because they lacked an understanding of the fundamental effects of DDT, such as its long half-life that allows it to spread through multiple levels of consumption, and the relationships among the animals of the area, they made things worse instead of better and paid a high cost for their mistake. By considering only the straightforward, first-level relationship between mosquitoes as carriers of malaria and humans as recipients of malaria, the World Health Organization unrealistically assumed that this relationship could be acted upon independently of any other variables or relationships. They considered one tiny aspect of the system, rather than the entire ecology.</p><p>The examples in Bosnia and Borneo demonstrate the incredible importance of whole-systems thinking. Systems thinking means having the ability to view things in different time scales simultaneously and thus resolving the paradoxes between them. In the real world, as opposed to the drawing boards at a World Health Organization or NATO meeting room, one relationship strand-like between a mosquito and a human, or a Muslim and a Christian, cannot be separated from the rest of the system. All of the elements are intricately tied together in a complex web of inter-relatedness. Tugging on one string of that web can pull at other components, which may not at first glance appear at all connected to the point of action.</p><blockquote><em>We have to view our world in its holistic terms rather than separating the parts from the whole.</em></blockquote><p>The same idea exists in all areas of organizations. Everything is interrelated, and changes that are seemingly narrow in scope can set off a domino effect that reaches far wider than ever anticipated. Adopting whole-systems thinking allows us to realize our capacity rather than our incompetencies. Unfortunately, the phrase “system thinking” is often used without a fundamental understanding of its implications, to the point where everything is a system, but nothing is treated as one. Many people say they are using a systems approach, but almost no one really is. Furthermore, popular interpretations of systems tend to use inappropriate mechanical models and metaphors. Leaders need to fully understand why our current approaches won’t work and what is different about the systems approach.</p><p>For leaders, the importance of having a systems-thinking mindset is essential if one wants to recognize new realities and be adaptive. New events are invariably systemic by nature. They are not isolated incidents that only affect a local or small part of a system. The repercussions of new events reverberate throughout the system. The ripple effect is often subtle and covert, requiring a systems mindset to be seen and understood. Leaders who develop systems thinking approaches are more flexible and divergent in their solutions. As a result, their outcomes and impacts are much less likely to lead to unintended consequences or the transfer of the issue to someone else. Their solutions are systemic and, thus, address multiple root causes instead of the apparent symptoms of a problem. Systems thinking is all about understanding how one thing can influence others within a whole. It’s the direct opposite of reductive, linear thinking, which results in siloed and marginalized outcomes when applied to a business or problem-solving context.</p><blockquote><em>System thinkers are always seeking to see how parts fit within a complex whole. They look for the interconnectedness of elements within a system, and often do this instinctively. A systems thinker sees the world in a more realistic, connected way.</em></blockquote><p>Just like the first image of Earth from outer space had a significant impact on our society’s ability to see the unity of our planet, systems thinking is a way of seeing ourselves as part of larger interconnected systems. Most importantly, this new perception creates a new consciousness from which the possibility of a new relationship emerges. Astronaut Russell “Rusty” Schweickart never walked on the Moon, but he was the first of the Apollo astronauts to go outside the spacecraft. In an exclusive interview with XPrize, he recalls that when Dave Scott began filming his spacewalk, the movie camera jammed, leaving Schweickart five glorious minutes with nothing to do but take in the incredible view. Schweickart describes systems thinking a view of the Earth as seen from space. The Earth, he says, “…is so small and so fragile, and such a precious little spot in that Universe, that you can block it out with your thumb. Then you realize that on that spot, that little blue and white thing, is everything that means anything to you. All of history and music and poetry and art and death and birth and love, tears, joy, games, all of it right there on that little spot that you can cover with your thumb. And you realize from that perspective that you’ve changed forever, that there is something new there, that the relationship is no longer what it was.”</p><p>From the movement of flocks of birds to the Internet, environmental sustainability, and market regulation, the study and understanding of complex open systems has become highly influential over the last thirty years. Organizations are complex, adaptive systems. As such, typical command-and-control approaches to running them fail to understand their nature. Most organizations have divisions and subdivisions, each with its managers, objectives, priorities, budgets, and performance management targets. As a result, people focus on the piece of the puzzle they’re accountable for, making it difficult for leaders to be able to see the entire system. Managers in each part of the organization are not incentivized to work with the other areas to help meet the overall aim. Corporate culture can mean that people are afraid to be seen to be interfering in a colleague’s domain. As such, there may be no shared vision and purpose. There is no shared “map” of the system. Not only that, but the performance targets that are often implemented in organizations can act as a barrier to systems thinking. They can bring about leadership behaviors that are counterproductive to the overarching mission.</p><blockquote><em>Systems-based leadership means allowing frontline staff to develop a thorough understanding of the organization and empowering them to improve processes from within.</em></blockquote><p>Systems thinking expands the range of choices available for solving a wicked problem by broadening our thinking and helping us articulate problems in new and different ways. At the same time, the principles of systems thinking make us aware that there are no perfect solutions. The choices we make will have an impact on other parts of the system. By anticipating the effects of each trade-off, we can minimize its severity or even use it to our advantage. Systems thinking, therefore, allows us to make informed choices. Systems thinking is also valuable for telling compelling stories that describe how a system works. For example, the practice of drawing causal loop diagrams forces a team to develop shared pictures, or stories, of a situation. The tools are effective ways of identifying, describing, and communicating your understanding of systems, particularly in groups.</p><p>Creating a culture of systems thinking isn’t a quick task. It takes time to embed the knowledge and behaviors needed to make decisions and take actions that will benefit the system as a whole. With this in mind, systems thinking shouldn’t be the preserve of a select group of senior leaders. A whole-system perspective can only be achieved by developing the ability to map workflows and processes among the entire workforce. In this way, any changes to the system can start with a clear idea of the organization’s shared purpose. If the old ways of thinking don’t work, something fundamentally better suited to the task is needed, like a shift in thinking that illuminates the whole, not just the parts. One that is synthetic rather than analytic and one that integrates, rather than differentiates. An effective system thinking perspective requires trust, curiosity, compassion, and courage. This approach includes the willingness to see multiple situations holistically. We have to recognize that everything is interrelated, that there are often various ways of solving a problem. We need to be willing to champion interventions that may not be popular. Systems thinking is about revealing the intersections, overlaps, and seeing how every action, like in the ones in Bosnia and Borneo, could have a ripple effect in the system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c1f9c832a3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership at All Levels]]></title>
            <link>https://miljanbajic.medium.com/leadership-at-all-levels-632f92256da9?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/632f92256da9</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Wed, 04 Mar 2020 07:04:50 GMT</pubDate>
            <atom:updated>2020-03-04T07:04:50.845Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4NL1RjWULCsmqkKom-vAsQ.jpeg" /></figure><p>I will forever remember the night of May 29, 1991. Not because it was my birthday but because my dad and I watched the Red Star Belgrade accomplish the unbelievable by defeating the Olympique Marseille of France for the UEFA Champions’ League soccer crown. Held every four years, winning the UEFA Champions’ league title is almost as important as winning the FIFA World Cup of soccer. This win was forever written in the soccer history books as the single most successful moment of a nation emerging victorious after being on the cusp of elimination. It was just over a year later that the war began and my father was imprisoned in a concentration camp.</p><p>Red Star’s team was made up of players from five of Yugoslavia’s six republics. They were an obscure group of players who managed to beat the odds in a formidable manner and grab the European crown that all but belonged to the French soccer goliath. It was an epic endeavor. But how do you inspire a group of people, like the Red Star Belgrade soccer team, to play for a bigger game and to think beyond their individual gain? It comes down to sharing a greater purpose and fostering leadership at all levels. This soccer team put their personal aspirations aside and took ownership over their collective results. This sort of team effort can, and should, be applied in complex organizations. Team sports such as soccer are complex, dynamic systems.</p><blockquote><em>We are experiencing an unprecedented leadership crisis. The traditional approaches to leadership are no longer working, the game is changing and current leadership practices are not fit for the wicked problems ahead.</em></blockquote><p>Much of the current organizational leadership theory is based on a complicated representation dating back to the industrial age when it was first developed. In other words, the patterns and approaches to leadership in a stable and predictable environment are much different than in complex environments. In complicated environments, the goals are rationally conceived and the achievement of these objectives is realized through structured and linear practices. Fundamentally, there is a core drive toward top-down alignment and control in this type of environment. The traditional bureaucratic mindset that has developed as a result of this complicated paradigm has shown limited effectiveness with the evolution towards the increased complexities of the modern world.</p><p>We need to rethink leadership for the complex organization because leadership and business context are inseparable, and our context has changed dramatically. Many refer to this context as VUCA (Volatile, Uncertain, Complex and Ambiguous) — an acronym borrowed from the US Army to describe the extreme conditions of Afghanistan and Iraq. Leading effectively in this new world requires a very different mindset and cognitive capabilities. Complex challenges can only be solved by having those directly affected by them change their priorities, values, beliefs, perspectives, habits, and loyalties.</p><p>Leadership in complex environments requires everyone to take responsibility for the success of their team, organization, and society, and not just for their own areas. It means that leadership is distributed, rather than being centered on a few individuals in formal positions of authority. That is, everyone in an organization should be able to generate ideas and make decisions from a place of ownership. This creates an environment of aligned autonomy around self-expression, self-organization, self-management, and full accountability for results. Evidence shows us that leadership at all levels not only wins championships, but it also creates resilient organizations that are better suited for complex environments. My experience working with executives from a number of Fortune 500 companies has only confirmed these findings. These organizations all have the same goals: to innovate, to thrive, and to work towards something better. The ones that accomplish these goals are the ones with leadership at all levels.</p><p>People are purpose-driven and choose to align with leaders who strive to empathize with others and make a difference. This is exactly what drove the Red Star soccer team. They weren’t just playing for a championship, they were playing a tournament that could unite a country when it desperately needed to be united. Symbolically enough, the country’s civil war and the subsequent breakup were symbolized by an unbelievable soccer story, which at the same time also stood for the best things for which the former Yugoslavia should be remembered. The last hoorah of a golden team formed of an obscure group of players who managed to beat the odds and grab the European crown from the fingertips of the European soccer giant.</p><blockquote><em>Leadership at all levels means that we need to SENSE which context we’re in, EVOLVE our mindsets, and SHIFT between different perspectives and the changing states of complicated and complex. From there we need to allow the future to EMERGE and lead from it.</em></blockquote><p>Here’s the leadership pattern I call SESE (Sense, Evolve, Shift, Emerge):</p><p>SENSE: Sense the context: As a leader, you need to have a means from which to make sense of a context, and work towards resolving problems in that context. For example, sensing if the context is complicated or complex and whether people’s worldviews are materialistic and socio-centric.</p><p>EVOLVE: Evolve your mindset: As a leader, you transform and evolve your mindset. Your mindset leads your actions. Evolving your own mindset (attitudes, values, operating principles, and beliefs) is the first step.</p><p>SHIFT: Shift between worldviews and states: As a leader, you need to work towards resolving problems in that context, by shifting back and forth between the “problem-space” and “solution-space”. Meet people, teams, and organizations at their current stage, and context to help them evolve and emerge from there.</p><p>EMERGE: Lead from the future as it emerges: The leadership challenge is not so much to adapt to new constraints (as change management had it for decades) but to lead from the future as it emerges, which means anticipating future concerns in societies and organizations and making them a reason for taking action today.</p><p>One key fact about culture stands out: individual and organizational value systems (beliefs, mindset, thoughts) impact the way change happens. Do you consider yourself a leader? What is important to you and your organization? Are your beliefs and mindset evolving? If so, in what ways?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=632f92256da9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Titanic Mindset]]></title>
            <link>https://medium.com/swlh/titanic-mindset-9ac297a2eea?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ac297a2eea</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Wed, 04 Mar 2020 06:52:42 GMT</pubDate>
            <atom:updated>2020-03-05T21:33:55.895Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D_sJ4VqWJVCJ1b36E_HoZA.jpeg" /></figure><p>I have always been fascinated by the story of the Titanic, and why the ship met its tragic fate. From the architects and engineers, to the crew and passengers themselves, everyone was convinced that the Titanic could not sink. What was even more fascinating is that the denial grew and prevailed for some time among the passengers and crew as the ship was sinking. This mindset undoubtedly caused many unnecessary deaths. Since nearly everyone believed so strongly that the Titanic was invincible, they were unable to perceive reality as it unfolded. It seems incredible to us today that anyone could believe that 70,000 tons of steel could be unsinkable, but that was the conventional wisdom of 1912.</p><p>In the book Titanic: An Illustrated History, Don Lynch and Ken Marschall describe how strong this belief was. They quote one of the survivors saying, “From a distance, the Titanic looked like the perfect postcard — all lit up on a clear, calm night. Many crewmen reinforced the false sense of security — either intentionally — or because they themselves could not believe the ship was sinking fast.”</p><p>In Harper’s Weekly, Volume 56, Issue 5, May 21, 1960, William Inglis takes us through the experience of a survivor Henry Sleeper Harper who described how nobody initially believed there was an emergency. Harper explains the incredulity of how, onboard the sinking Titanic, with water creeping up foot by foot, the gymnasium instructor was still helping passengers on the mechanical exercise equipment. The orchestra continued to calm the crowd with waltzes, ragtime, and music hall tunes, and the last drinks were “on the house” in the first-class smoking room. Three ladies who had been walking the deck arm in arm, singing to the other guests who were more alarmed by the inconvenience, ignored the stern warnings to board the lifeboats to escape pending danger. “What do they need of lifeboats?” one woman asked. “This ship could smash a hundred icebergs and not feel it. Ridiculous!” she announced. Everyone seemed confident that the ship was all right.</p><blockquote><em>Those closest to the Titanic were the ones most convinced of her invincibility. The Titanic was sinking; this was the reality. Yet the mindsets of the people on the ship were so strong that they could not see the reality, leading to an unnecessary loss of human life at sea. The fate of people on the Titanic shows how the unimaginable can become possible and how assumptions can be mistaken for facts.</em></blockquote><p>The story of the Titanic is a very powerful example of a “too big to fail” mindset. Kodak, Nokia, Enron, Lehman Brothers, Blockbuster, Toys-R-Us, Borders, Myspace, Sears, and many other companies suffered from the same mindset problem. Today’s organizations struggle with the same types of problems as they did decades ago. They attempt to adopt new methodologies, frameworks, and practices, but the mindset and culture of the organization remain unchanged.</p><p>We all, at some point in time, fall victim to the Titanic mindset, “Since I am so sure, I can’t be wrong,” and some of us fall victim to this mindset most of the time. This is because the way we think influences the way we behave and because we all see the world through the prism of our own attitudes, shaped by our environment and experiences. The first step to evolving our mindset is to understand how we hold a set of basic assumptions, values, and beliefs about how the world works, which are also called our worldviews. This is how we determine our outlook on life or our formula for life. These are the fundamental aspects of our mindset that ground and influence our perceiving, thinking, knowing, and doing. Our worldviews evolve throughout our lives. However, at times, we’re in over our heads. Our cognitive capacity doesn’t always keep up with the complexity of our environment and problems.</p><blockquote><em>Our current mindset does not allow us to see the world as it is, instead our mindset creates blind spots for us.</em></blockquote><p>In 1991, when the war in Yugoslavia first started between Serbia and Croatia, most people in Bosnia didn’t think the war would come to their doorsteps. As most people watched the live images on television of houses burning and dead people on the street, they didn’t think the war would come to their towns. Their mindset, beliefs and worldviews stayed unchanged. I vividly remember my dad saying as I sat next to him, “Go outside and play. This is temporary, our neighbors won’t do anything like that to us.” As the war erupted in Bosnia, just months later, people continued to believe their neighbors would not imprison or kill them, even though town after town was seeing mass expulsions, killings, and ethnic cleansing. Soon after, my whole town of about 80 Christian families would be set upon and taken to the concentration camps by our non-Christian neighbors. Many fell victim to the Titanic mindset during the Civil War in Yugoslavia. The civil wars that demolished this south-eastern part of Europe for several years during the 1990s left more than 120,000 people dead.</p><p>Most organizations are blind to their <a href="https://www.linkedin.com/pulse/wicked-problems-need-leadership-miljan-bajic/">wicked problems</a>. They don’t see it coming, and when a crisis happens, the recovery is very expensive.</p><blockquote><em>Every organization becomes trapped in the myths or assumptions that take on the aura of indisputable truths over time.</em></blockquote><p>You may wonder why is this happening? Why can’t leaders, consultants, and coaches do a better job of helping organizations deal with these wicked problems? The challenge lies in exactly what they do. Or more importantly, what they’re being asked to do by the people who hire them. I once questioned my client about their mindset and culture and his reply was, “The company has been in existence for over 100 years and you are going to presume to tell us that we need to change our mindset and culture?” That engagement didn’t last long. Today’s organizations struggle with the same types of problems as they did decades ago. They attempt to adopt new methodologies, frameworks, and practices, but the underlying mindset and culture of the organization remain unchanged. As a result, organizations continue to produce a lot of waste, such as features that customers don’t find useful and practices that disengage employees.</p><p>Today, many organizations are in trouble as they still believe that things are obvious and predictable. They continue to believe their own myths and that past success means they’re invulnerable to any big failures. But then, the inevitable happens, and they find themselves in crisis. All because of the old Titanic mindset that continues to prevail across many organizations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ac297a2eea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/titanic-mindset-9ac297a2eea">Titanic Mindset</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The demise of the Scrum Master]]></title>
            <link>https://miljanbajic.medium.com/the-demise-of-the-scrum-master-a938d357b356?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a938d357b356</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Thu, 20 Feb 2020 03:17:47 GMT</pubDate>
            <atom:updated>2020-02-25T22:56:09.436Z</atom:updated>
            <content:encoded><![CDATA[<h3>The demise of the Scrum Master role</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r1GUrN3GhWLeisSKMQig6g.jpeg" /></figure><p>Once upon a time, the Scrum Master role was an outlandish concept at the fringes of software development. Now there are thousands of Scrum Masters out there that are falling victim to several common anti-patterns that are diminishing the meaning of the Scrum Master role.</p><p>As an Agile Coach and an active member of the Agile community, I talk to a lot of people who are fueled with frustrations about Scrum and Agile. Many of these leaders and practitioners try to tell me that Scrum and their Scrum Masters suck when really, it’s about how they suck(ed) at Scrum.</p><p>I’ve seen so many organizations that suffer from poor implementations which are driven by PowerPoint slides, lack of leadership at all levels, and Scrum Masters who don’t have the passion, support, skills, and experience necessary to serve their teams and organization. What I see is more and more organizations that don’t see the value of the Scrum Master role, so they start shifting to sharing Scrum Masters across multiple teams to act as facilitators. In worse cases, the role of a Scrum Master is eliminated, and “people managers” are brought back.</p><p>This makes me feel mournful; the Scrum Master role is one of the most crucial roles in driving the organizational change.</p><h3>So, how does an organization know that it has great Scrum Masters?</h3><p>Before I describe what makes a great Scrum Master, let’s look at how the <a href="https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf">Scrum Guide</a> defines the role of a Scrum Master:</p><blockquote><em>The Scrum Master</em> <em>is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values. The Scrum Master is a servant-leader for the Scrum Team.</em></blockquote><blockquote><em>The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.</em></blockquote><p>The Scrum Master should be the oil that helps the team and organization continuously improve and deliver value. I do not know many Scrum Masters that are living up to this definition. Many violate the essence of Scrum.</p><p>That said, these are the seven areas that I look for when I want to know if somebody could be a great Scrum Master:</p><h3>1) A great Scrum Master has a deep understanding of Lean, Agile, and Scrum</h3><ul><li>They understand the roots of Lean Thinking and can explain the concepts of one-piece flow, pull, limit WIP, small batches, kaizen, reduce variability, and teamwork.</li><li>They live the kaizen mindset by focusing on people, optimizing the whole, and relentlessly improving.</li><li>They help the organization minimize waste in the following areas: extra features, partially done work, extra processes, handoffs, defects, delays, and task switching.</li><li>They understand how Agile engineering practices such as continuous integration, test-driven development, collective code ownership improve customer satisfaction.</li></ul><h3>2) A great Scrum Master is a very effective facilitator</h3><ul><li>They understand alternatives to open discussions such as structured go-arounds, individual writing sessions, dialogue in pairs or small groups, and explain when they may be effective.</li><li>They know how to support meeting participants during divergent thinking, integration, convergent thinking, and closure that will support the development of an inclusive solution.</li><li>They understand visual facilitation techniques for a collaborative session such as card questions, clustering, dot voting, and visual note-taking.</li><li>They are great at facilitating remote meetings by using techniques such as turn-taking between that face-to-face with remote participants, establishing communication protocol, and shared note-taking.</li></ul><h3>3) A Great Scrum Master is an authentic coach</h3><ul><li>They demonstrate a coaching stance such as neutrality, self-awareness, client, and agenda in an interaction with one or more people.</li><li>They understand the fundamental psychological concepts that help understand and transform individual behavior such as emotional intelligence, mindset, and empathy.</li><li>They apply coaching techniques such as active listening, powerful questions, reflection, and feedback with team members, Product Owners and/or stakeholders.</li><li>They understand the elements (role of the coach, duration, expectations, feedback, responsibilities) of a fundamental coaching agreement.</li></ul><h3>4) A great Scrum Master serves the Dev Team by helping them deliver the Increment</h3><ul><li>They understand how technical practices may impact the Development Team’s ability to deliver a potentially releasable Increment each sprint.</li><li>They act as the Servant-Leader for the Scrum Team and/or organization.</li><li>They apply various team development models to their teams and organizational growth.</li><li>They organize and facilitate the creation of a strong Definition of Done with the Product Owner and Dev Team.</li><li>They help teams understand the benefits of scalable engineering practices.</li><li>They make sure that the Dev team gets coaching support to build team capability within components for code development, automated testing and frameworks, test automation frameworks, production monitoring, and continuous delivery/integration.</li><li>They guide Dev Team on Agile technical best practices and emerging technology.</li><li>They actively promote professional software development behavior (pair programming, continuous integration, clean code, and refactoring).</li></ul><h3>5) A great Scrum Master serves the Product Owner</h3><ul><li>They apply effective collaboration techniques such as engaging the team in the shared purpose of their work, providing transparency of priorities, ensuring a shared understanding of product backlog items.</li><li>They understand and prevent negative impacts that arise when the Product Owner applies excessive time pressure to the Development Team.</li><li>They help Product Owners leverage techniques for moving from product vision to product backlog.</li><li>They know how to help the Product Owner structure a complex or multi-team product backlog.</li></ul><h3>6) A great Scrum Master serves the Product Organization</h3><ul><li>They understand the organizational impacts when the Scrum Team fails to adopt Scrum in its entirety.</li><li>They are familiar with techniques for visualizing, managing, or reducing dependencies between teams.</li><li>They know how to facilitate causal loop analysis and value stream mapping to help their organization improve their Scrum adoption.</li><li>They understand the cultural and organizational change models such as Kotter’s, ATKAR, Schneider, and Laloux.</li></ul><h3>7) A great Scrum Master has a desire to get better at Scrum Mastery</h3><ul><li>They continuously evaluate their personal fulfillment of the five Scrum Values.</li><li>They understand and share their fundamental driving factors</li><li>They are skilled communicators</li><li>They are system thinkers</li></ul><p>The only way that I see how we can stop the decline and fall of the Scrum Master role is by becoming a great Scrum Masters for our teams and organizations.</p><h3>So, how many Scrum Masters do you know that are great at these seven areas? Could it be that we’re seeing the decline and fall of the Scrum Master role?</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a938d357b356" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accepting What “Already Is”]]></title>
            <link>https://miljanbajic.medium.com/accepting-what-already-is-649ddcf7369c?source=rss-f335e051c5b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/649ddcf7369c</guid>
            <dc:creator><![CDATA[Miljan Bajic]]></dc:creator>
            <pubDate>Tue, 18 Feb 2020 00:11:51 GMT</pubDate>
            <atom:updated>2020-02-18T00:11:51.420Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5eh0ehBinHdiOzc0O7vWQQ.jpeg" /></figure><p><em>The status quo of forcing and imposing change in organizations can only be transcended by leadership first accepting what “already is”. Acceptance is the first step of transformation. Then you can invite and inspire.</em></p><p>Making a positive change first requires that we embrace our genuine selves. It is the great paradox of change that sometimes the most effective adjustments occur by accepting what already is. This is certainly something that I have struggled to embrace throughout my life.</p><p>Humans have a fascinating relationship with change. There is no entity in the world that has not witnessed and experienced growth or decline. While we may ride change like the current of the ocean, we often resist it and actively fight hard against it, usually out of fear. The strange fact is that we often resist change even when we know that it will likely bring us better outcomes in the long run. There is something about the familiarity and comfort of now that causes the human mind to push back against any threat of change, whether it be good or bad.</p><p>As digital leaders, we support a whole industry of professional change agents dedicated to showing us how to improve our organization and business practices.</p><p>On an individual level, of course, change is at the very heart of personal and professional development.</p><blockquote>Without change, we can’t grow, we can’t learn, and we can’t improve the quality of our lives or the lives of those around us.</blockquote><p>When I was ten years old, my family was torn apart and separated by the civil war in Yugoslavia. My father spent 18 months in three different concentration camps across Bosnia. By the time he was released, he was sick of every sight in front of him and was desperate to leave the Balkans. He got drunk one night with his friends and they decided to head to Belgrade the next day in order to apply for visas. He applied to Denmark, Germany, Canada, the United States, and Australia. Perhaps my father accepted what already is.</p><p>My younger sister loved the idea of living somewhere new. I did not share her unrivalled enthusiasm. I was afraid of the thought of having to learn a new language, making new friends, and getting used to a very different way of life. I was afraid of change. Would my friends see me as a deserter? I was conflicted. Part of me wanted to experience a change from my life just outside Sarajevo during wartime, as it brought both misery and fun in equal abundance. While the living conditions were terrible, it did bring me joy that schools were cancelled most days due to tank shellings. Perhaps a change was better for my education as well as my wellbeing.</p><p>We all want to change. No matter how big or small, how seemingly life-changing or insignificant, we all have parts of our lives that are unhappy. And yet we resist change more often than not, no matter our true and underlying desires.</p><blockquote>Change, for me, was a matter of new identity. I knew who I was, but I didn’t know who I was going to be. I imagined it was going to be a fantastic adventure wherever we went, and yet I felt a sense of comfort being where I was. There was an inner fight between who I was and who I could become.</blockquote><p>As I got into coaching and organizational transformation many years later, I realized that change does not take place by insight, interpretation, coercion, or persuasion. Rather, change can occur when a person abandons, at least for the moment, what they would like to become and attempts to be what they are.</p><blockquote>In other words, the possibility for real change opens up when the individual or organization stops trying to become what they are not and fully acknowledges what they are. This can be a hard concept to wrap your head around, which is why many of us have such fierce internal battles over change.</blockquote><p>Many of my clients seeking change are in conflict with at least two internal or external opposing sides, the force for change and the force for comfort and consistency. Caught between what should be and what is, yet never fully identifying with either, the client is paralyzed between competing commitments. One of the first things that I do when I’m working with new clients is to ask them to make a sincere effort to be fully invested in the opposing sides, one at a time, with awareness and without judgment.</p><p>First, the point of view and values of the current “what is” situation are sincerely explored and, from the inside, the client shifts their mindset to what it should be. In doing so, the client may simply live in the moment.</p><p>If the client is to be able to truly stand outside the current situation, they must risk identifying with the opposing point of view or views. In other words, and here lies the paradox, to be able to change, a client has to want to change badly enough that they are willing to approach problems in a radically different way by identifying with the opposing perspective. When this happens, opposite differentiations melt into creative irrelevance, fresh possibilities emerge, and the client is free to step into an entirely new “what is.”</p><blockquote>Accepting the current “what is” becomes the source of transformation. Leadership starts from within, and if you don’t understand and acknowledge what lies within, how can you make the necessary changes to bridge gaps between the leader you are now and the leader you strive to be?</blockquote><p>Look at your current life or business now. What are you resisting? Identify it, name it… then accept it. Accept who you are right now, including your flaws, your contradictions, and your inconsistencies. Accept your resistance. Accept you. Accepting is different than liking or agreeing, it just means you are willing to confirm the reality in which you live. Acceptance is the first step of transformation. And when you transform, your beliefs and views evolve, and you grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=649ddcf7369c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>