Category: Organizational Change & Culture

Biological Metaphors for Organizational Design: Learning from Natural Intelligence Frameworks

Posted on January 30, 2025 by - Organizational Change & Culture

Organizations, much like living organisms, exist in constantly changing environments. To survive and thrive, they must adapt, responding to new pressures, challenges, and opportunities. While traditional management models often emphasize rigid hierarchies and control mechanisms, nature provides a different blueprint—one built on adaptability, emergence, and distributed intelligence.

By studying biological systems, we can gain valuable insights into organizational design. The principles of evolution, self-organization, emergence, and distributed intelligence reveal pathways for creating adaptive, resilient enterprises. Just as ecosystems do not resist complexity but harness it for survival, organizations can rethink structure and strategy to embrace change as a competitive advantage.

The Parallel Between Biological Evolution and Organizational Adaptation

Evolution is not about the survival of the strongest but the survival of the most adaptable. In ecosystems, species find evolutionary niches—unique roles that ensure their survival. Likewise, organizations must continually refine their value propositions to carve out sustainable competitive advantages.

  • Biological Example: Darwin’s finches evolved distinct beak shapes based on available food sources, demonstrating that adaptability, rather than brute force, determines success.
  • Organizational Analogy: In the business world, companies that iterate, experiment, and pivot in response to market shifts are the ones that endure. Just as ecosystems foster diversity to sustain balance, organizations must cultivate innovation and learning to remain relevant.

This aligns with the idea of turning complexity into a competitive advantage rather than seeking to simplify it. Complexity can be an asset when managed correctly, enabling organizations to respond dynamically rather than reactively.

2. Principles of Emergence in Nature and Organizations

In nature, emergence occurs when simple interactions among individual components lead to complex, adaptive behavior. Ant colonies and schools of fish display remarkable coordination without central command.

  • Biological Example: In ant colonies, no single ant dictates the actions of the group. Instead, ants follow simple rules and respond to environmental cues, creating a sophisticated system that efficiently finds food, builds structures, and defends territory.
  • Organizational Application: When companies encourage decentralized decision-making, they enable emergent solutions that would be impossible under rigid, top-down control. Agile and Lean methodologies leverage this principle, allowing teams to self-organize and innovate in response to challenges.

Organizations that design for emergence rather than enforcing control can unlock new levels of agility and responsiveness.

3. Self-Organization: A Blueprint for Scalability and Resilience

Self-organization is a core feature of natural systems, where order arises through local interactions rather than central direction. This principle applies to everything from cellular structures to bird flocks in flight.

  • Biological Example: Flocks of birds exhibit coordinated movement patterns without a leader dictating direction. Each bird adjusts based on its neighbors, ensuring cohesion while maintaining flexibility.
  • Implication for Organizations: Enterprises can encourage autonomy while maintaining shared goals, much like how biological systems self-organize. Adaptive workflows, empowered teams, and flexible governance structures allow organizations to scale efficiently without losing coherence.

Rather than enforcing rigid operational models, organizations should create conditions where structure emerges naturally, balancing autonomy with alignment.

4. Distributed Intelligence: A Model for Collective Learning

Nature provides countless examples of distributed intelligence, where no single entity possesses all knowledge, yet the system as a whole functions adaptively.

  • Biological Example: Neural networks process vast amounts of information through distributed connections rather than a single command center. Similarly, fungal mycelial networks transfer nutrients and signals across vast forest ecosystems, enabling collective survival.
  • Organizational Application: Companies can foster distributed intelligence by democratizing data and empowering decision-making at all levels. Systems of Insight—where knowledge flows across teams rather than bottlenecking at the top—enable organizations to respond faster and more effectively to change.

By leveraging AI-driven analytics as an enterprise “nervous system,” and intelligently orchestrating the technology and processes required to support the strategy, organizations can process and react to internal and external stimuli dynamically.

5. Conceptual Models for Organizational Learning and Transformation

Just as genetic material encodes an organism’s traits, organizations carry an inherent DNA—a set of values, principles, and structures that shape their behavior.

  • Organizational DNA: Organizations that intentionally shape their culture, knowledge-sharing practices, and decision-making frameworks create a foundation for long-term adaptability.
  • Ecosystem Thinking: Organizations should be viewed as interconnected ecosystems where various functions interact symbiotically, not as isolated entities. Encouraging mutual support across departments strengthens resilience and innovation.
  • Guided Evolution: Change does not have to be disruptive. Evolution in nature occurs through gradual, iterative refinements. Organizations that experiment in small, controlled ways can drive meaningful transformation over time without destabilizing operations.

Many experts in organizational theory believe the “organization as organism” metaphor falls apart under conditions of continuous change. We believe this concept of guided evolution makes the difference. With expert guidance leading steady, iterative improvements, organizations can rise to the challenge of continuous change and even turn it into an advantage.

6. Actionable Insights for Leaders

Leaders seeking to build adaptive organizations can take key lessons from biology:

  • Adopt Adaptive Structures: Move from rigid hierarchies to flexible, intelligently orchestrated models that enable resilience.
  • Embed Systems Thinking: Recognize how different functions interact, ensuring alignment across people, processes, and technology.
  • Experiment and Iterate: Treat initiatives like evolutionary experiments by constantly learning, refining, and adapting based on results.

By embracing these principles, organizations can move beyond static models of operation and design structures that evolve naturally in response to the world around them.

Conclusion

Success in today’s world is about navigating change effectively. Stability is stagnation. Just as ecosystems thrive through adaptability, organizations that embrace biological principles—emergence, self-organization, and distributed intelligence—will be best positioned for long-term resilience and growth.

Enabling ITSM Change Management Using Jira Service Management

Posted on August 9, 2023 by - Organizational Change & Culture, Service Management

In the fast-paced world of IT and software development, changes are inevitable. From software updates to infrastructure modifications, transitions can often lead to challenges and frustrations within an organization. But what if there was a way to manage these changes effectively, reducing the impact and scope of disruptions? Enter Jira Service Management (JSM), a powerful tool for enabling ITSM change management.

This is the first in a three-part series covering ITSM principles and applying them using JSM:

  • Enabling ITSM Change Management With JSM
  • Streamline Your ITSM—Service Catalog and CMDB Powered by JSM 
  • Perfecting Customer Management Using JSM

Change management is crucial in any organization. Without it, companies run the risk of encountering server downtimes, leading to confusion, stress, and frustration among employees and users alike. These downtimes not only affect productivity but can also tarnish a company’s reputation.

This article is based on the webinar, How to Enable Change Management With Jira Service Management. Watch the recording now to learn more about what’s discussed here and to see a thorough demo of JSM reflecting the key learning points. 

Unpacking the basic change management concepts 

The webinar linked above covered some important concepts every IT professional should know:

Change Management and Change Enablement

At the core of any IT operation lies the ability to manage and enable change effectively. But, what do these terms mean in the context of IT services and software development?

Change management, as defined by ITIL, is an Information Technology Service Management (ITSM) practice designed to minimize risks and disruptions. It ensures that critical systems and services remain functional amidst changes. This could mean anything from updating API documentation to deploying code to different environments. Any addition, modification, or removal that directly impacts services, processes, configurations, or documentation falls under this umbrella.

On the other hand, change enablement is a term used in Atlassian documentation. It refers to team standards that permit users to handle change requests effectively. Unlike change management, which is often associated with processing changes from outside, change enablement facilitates changes originating from within the organization.

Implementing change using ITIL 

It’s important not to rush the implementation of change. As counterintuitive as it might sound, taking extra time to set up and stick to a change management program can actually improve the process. It might seem to slow down work initially, but embracing ITIL patterns and automation will improve efficiency and reduce the heavy costs associated with botched tasks. The mantra here is to slow down to go fast.

Automation is a valuable tool for minimizing the burden of heavier tasks like documentation. Traditional tools may have complex, manual components that slow down processes and increase the chance of error. In contrast, tool automation can alleviate this heaviness. For example, automating ticket creation and linking various components can significantly reduce the time and effort required for these tasks.

Explore how AI-powered service management can take automation to a whole new level!

Roles and responsibilities in change management

Two key roles in change management are the Change Advisory Board (CAB) and the Release Manager.

Change Advisory Board (CAB)

The CAB plays a pivotal role in overseeing changes within an organization. Composed of senior individuals knowledgeable about the area undergoing change, the CAB provides a holistic perspective on the implications and potential impacts of proposed changes.

Release Manager

Working closely with the CAB is the Release Manager. This role involves reviewing content submitted by the development team, ensuring all aspects of a change request are in place, from documentation to testing assurances. The Release Manager serves as an agent to the CAB, mitigating risk through standardization and completion of requests.

In addition to their review responsibilities, the Release Manager coordinates the personnel involved in implementing changes, checks schedules for conflicts, tracks the process with the CAB, and ensures communication among all stakeholders.

The importance of timing in change management

However, effective change management isn’t just about having the right roles in place. It’s also about timing and planning. 

Respecting the process means submitting changes well before the release date. Common issues like time crunches for development and deployment can pose challenges to the change management process. To alleviate this, sufficient time should be allocated for change management processes during project planning. For example, incorporating an extra sprint for deployments could help manage changes more effectively.

Categorizing changes in a technology organization

Changes are categoric and can be differentiated based on size, risk, and urgency. Understanding these categories is crucial for efficient change management, particularly in a Continuous Integration/Continuous Deployment (CI/CD) setting.

There are three main types of changes:

  1. Standard Change: A low-risk, pre-authorized change that is well understood, fully documented, and proven. Due to CI/CD pipeline practices, standard changes are becoming more frequent.
  2. Normal Change: This refers to non-emergency deployments that must be scheduled and planned. These changes typically require a review from the Change Advisory Board (CAB)
  3. Emergency Change: These are changes that require immediate fixes due to an urgent issue. They often involve a separate procedure with a shorter timescale for approval and implementation.

Regardless of the type, no matter how small the change, it should not bypass the established process for change management. Each change must be properly documented, reviewed, and authorized to ensure minimal disruption to services and operations.

Moreover, understanding the nature of these categories and the associated efforts helps organizations manage changes efficiently. It provides clarity on the level of risk involved, the amount of effort required, and the urgency of the change.
Organizations may need to adjust internal policies based on the perceived risk level of each change. For instance, well-performing teams that have demonstrated their ability to manage risks effectively might be allowed to make production deployments multiple times per day.

Embracing ITSM change management in Jira Service Management

Effective change management strategies create a stable environment and help avoid panic-driven experiences. And at the heart of this strategy lies Jira Service Management.

JSM is a comprehensive tool that assists organizations in planning, controlling, and understanding the impact of changes on their business. It simplifies the change management process, from the initial change request to implementation.

With the ability to provide richer contextual information around changes, JSM empowers IT operations teams to better manage and mitigate potential disruptions. Furthermore, its customizable workflow—designed based on ITIL recommendations—helps service agents learn and adapt to change management processes. By implementing a change management process in JSM, companies can keep track of all changes, ensuring nothing slips through the cracks.

Jira Service Management’s alignment with ITIL 4 is one of its key strengths. This association allows it to offer a comprehensive solution that aligns with software development tools and agile practices, making it a favorite amongst software professionals.

This alignment with ITIL 4 makes ITSM change management in Jira Service Management less bulky than its predecessors and more adaptive to an agile mindset. This adaptivity is further enhanced by the free ITSM template within JSM. It includes change incident, new feature, problem, and service request issue types along with the corresponding request types, giving users a head start in their change management journey.

Additional customizable templates are available as well. 

The ease of use and familiarity of Jira Service Management reduces barriers to entry, making it approachable for professionals from the software side. It’s a tool designed to facilitate and not complicate, making it a go-to for many organizations seeking to streamline their change management processes.

Conclusion

In conclusion, the adoption of change management and change enablement practices, underpinned by ITIL patterns and automation, can bring about significant improvements in the efficiency and effectiveness of tasks within an organization. With tools like Jira Service Management, which aligns with ITIL 4 and supports agile practices, organizations can navigate changes smoothly, reducing the risk of disruptions and costly errors.

The journey towards effective change management may seem slow initially, but remember, slowing down to go fast can lead to long-term benefits. With the right tools and guidance, you can minimize risks, improve efficiency, and foster a culture that embraces change.

To dive deeper into how JSM can revolutionize your change management process, consider watching the recorded webinar, How to Enable Change Management With Jira Service Management. It offers practical insights and a demo that can help you understand the capabilities of Jira Service Management better.

Finally, Safe 6.0 Puts Continuous Learning Culture Where It Belongs

Posted on May 9, 2023 by - Agile & DevOps, Organizational Change & Culture

There is a real buzz in the SAFe community with the new changes in SAFe 6.0…

  • Strengthening the foundation for business agility
  • Empowering teams
  • Accelerating flow
  • Enhancing business agility across the business
  • Building the future with AI, Big Data, and Cloud, and
  • Delivering better outcomes with measure and grow and OKRs

Something that may have gotten lost with the buzz created by these themes is how the continuous learning culture competency has finally become part of the foundation for strengthening business agility.

For myself, this is a reminder that the continuous learning culture competency is not some afterthought or nice-to-have competency, but rather a foundational competency like Lean-Agile leadership. Why is this important?

SAFe 6.0 is about business agility

SAFe 6.0 is a framework for business agility. Business agility is the organizational capability for achieving economic advantage by sensing and responding faster than our competitors.

To do this, we need to learn faster than our competitors. And that means developing a continuous learning culture. Moving the continuous learning culture competency icon from its former side position in the framework to the foundation bar finally realizes the critical importance of continuous learning for business agility.

But sensing and responding to change is not just about learning and exploiting new business opportunities, as suggested by the Business Agility value stream. It’s also about sensing and responding to new opportunities to improve our way of working. Our ways of working must also embrace change through learning. Through iteration retrospectives, inspect-and-adapt problem-solving workshops, measure-and-grow workshops, and communities of practices, we have opportunities to improve our way of working iteratively. I often tell my clients if your way of working is the same two years from now as it is today, then you have missed the point.

Avoiding “cargo cult Agile”…

There is a misperception in much of our industry that if we can ritualistically execute a set of Agile practices, we will be agile. Thus, we often use the term “cargo cult Agile” to refer to this mindset.

No framework is immune to the cargo cult mindset. For example, SAI provides the Big Picture and a wealth of training assets and supporting resources that enable large organizations to get started on their business agility journey. Unfortunately, these same enabling assets which help start the journey can devolve into a cargo cult of prescriptive practices if the organizations do not develop a continuous learning competency. Worse, when leadership lacks a growth mindset, their go to strategy is often to strictly enforce compliance with the practices that make it easy to begin.

…by using SAFe as directed

SAFe roles, practices, and artifacts come from proven patterns for realizing Agile and Lean principles. There is nothing sacred about the practices themselves. They are practices to help you begin with realizing business agility throughout the enterprise. They are not rules. If you want to adjust, you simply need data to inform your decisions.

Improvement backlog items need to be written just like a feature with a benefit hypothesis. We need to know what useful performance and outcome data we can collect to determine if the improvement brought real benefit. Otherwise, when adapting and evolving practices, we are at risk of changing the practice because we don’t want to make the necessary changes to realize business agility. How many times have we heard teams complain that they can’t get anything done in a short timebox and ask if we can lengthen the timebox?

It comes back to continuous learning

This is why I am excited to see the continuous learning culture competency added to the foundation for business agility. Without developing both the Lean-Agile leadership and continuous learning culture, it is unlikely an organization can derive the benefits of business agility, regardless of how many practices they can precisely execute.

Dive deeper into all the changes in SAFe 6.0.

You Need Tools for Transformation–But That’s Not All

Posted on January 17, 2023 by - Organizational Change & Culture, Platform Adoption & Governance

I have something to admit: I was that coach. 

I told people I was a tool agnostic coach because I didn’t understand the value of leveraging the best workflow management tools. Luckily for me, I learned, and the results are cool. In this quick read, I’ll explain why tooling can be such a powerful force in your transformation, and discuss what to consider when deciding what technologies enable digital transformation for your organization.

The moment I learned something was missing

For decades, organizations in both the Manufacturing and Software industries have been working to transform to better ways of working. These transformations come in multiple forms:

  • Six Sigma / Lean
  • Agile ways of working
  • Business Agility
  • Push to a Product Organization
  • Digital Transformation
  • …and more 

I have spent much of my career successfully supporting organizations through this change—defining new ways of working, supporting new methods of communication and collaboration, and guiding people through change.

In recent years, how we look at these transformations have fundamentally changed.

  • Workers are tired of change. We need new behavior drivers to motivate the organization.
  • Organizations are sick of single solution frameworks and mindsets. They want change focused on outcomes.
  • The world has accepted that change is the new norm to stay ahead in the competitive market. If change is a competitive advantage, then we need to be mindful of what and why we change.
  • Leaders need data to make decisions. Due to the fast pace of change, more real time data is needed to support these decisions.
  • These days, transformations need to be more holistic, comprising Agile, Digital, and even AI.

Early in my career, I spoke to organizations about outcomes, but we never followed through to validate those outcomes. Looking back now, I see this approach resulted in half the benefit it should have. We did not validate those outcomes because we did not prioritize data and tooling as a competitive advantage during a transformation. Today, I’m convinced that implementing workflow management tooling as a part of your transformation is essential for success.

This being established, let’s dive into what this means and what you should consider when implementing a tooling strategy.

Start with why, define the approach, and validate the outcomes

Templates_Medium_black_coralAs a leader in organizational change, I often get calls that start by asking questions like

  • Can you turn us into a product-led organization?
  • Can you help us implement SAFe or Scrum at Scale?
  • Can you support our use of OKRs (Objectives and Key Results)? 

My answer… Yes, but why do you want to do this? Further, what pains are you facing and what outcomes are you hoping to achieve? Surprisingly, many organizations do not know the answers to these questions. And sometimes, when they cannot find the answer, they want to start over completely. But that won’t help.

They don’t know these answers because they do not have the data they need.

So, before we jump into a framework, let’s begin by

  • Creating a high-level process and data value stream to understand how things flow through the organization
  • Educating the organization’s executives and leaders on what is possible by establishing new ways of working
  • Establishing expected outcomes and key results for the organization
  • Setting the path with a roadmap for achieving those key results, not compliance with a framework
  • Setting a cadence to measure the key results so we can build in continuous  improvement

The key takeaway that fundamentally changed my approach to transformation is this: Organizations must establish the results they hope to achieve and enable change to reach those results, rather than deciding how they expect the organization to function and trying to force change into that frame.

Looking back, this seems so logical. We even thought and spoke about this years ago, but our efforts moved in another direction. I now believe that happened because the market did not have the flow-based tools we have today, and I would argue our modern tools still don’t offer the ideal state. 

So, which tool best enables this mindset?

The fact is, there is no perfect workflow management tool or framework. But the right tool can aid you in reaching your objectives. Here are some things I have found to be critical to understanding what tooling solution will best enable your transformation.

  1. Start by understanding the dashboards you need to validate the organizational results you’re after. Having the end in mind will allow the solution to remain focused on only building what the organization needs and filtering out unnecessary data. This will help you focus on the minimum feature set you need from your tooling solution.
  2. Establish systems and data that can serve as your single source of truth. There will be multiple tools and data being exchanged across the system. Ensure only the source of truth can be changed, and only by authorized users. This avoids people overriding the data intentionally or accidentally to tell a different story.
  3. Different users will want different tools based on what they do and how they do it. Do not assume that one tool can support OKRs, create and manage a product roadmap, manage user stories, and support your help desk. All those users have unique personas and will need unique features to do their work successfully. Pushing the output from those different tools to a single tool will support the organization’s source of truth.
  4. One tool will not magically solve your problems. Your organization is a large, complex, living thing. Multiple tools will need to come together to provide the insights needed. Establish an enterprise architecture for how tools will exchange data. Leveraging cloud-based tools and tool integration solutions will be essential to your enterprise solution.
  5. Do not forget about communication and collaboration. The tooling is not just about work management and flow-based systems. The users will need an integrated collaboration feature to support them, especially as they work more in a remote and hybrid mode.

In conclusion, don’t be that coach. Or, for that matter, that organization. Don’t ignore tooling as a vital piece of the transformation puzzle. And, at the same time, don’t focus on trying to find the perfect single tooling solution to solve all your problems. Instead, approach your transformation from the standpoint of objectives and results. And use the unique tool stack that best guides you to those results.