The Business Analyst and Systems Thinking
Summary
This presentation explores systems thinking as a holistic mindset for business analysts, emphasizing understanding complex interrelationships rather than just dissecting parts. It contrasts systems thinking with traditional analysis, highlighting its focus on interconnectedness, feedback loops, and emergent outcomes. The speaker discusses how to apply systems thinking to identify root causes, avoid unintended consequences, manage delays, and adapt to limits of growth, ultimately advocating for a broader perspective to solve problems effectively.
Key Insights
Systems thinking, combined with strategic and critical thinking, enhances business analysis capabilities.
When integrated with strategic thinking, critical thinking, and the core skills of a business analyst, systems thinking adds valuable dimensions to both problem analysis and solution synthesis.
Systems thinking expands organizational focus, looking at the bigger picture beyond assigned tasks.
Systems thinking, in contrast, is depicted as expanding the organizational focus, considering how a current task or project affects the overall organization. It's described as being perpendicular to strategic thinking.
Systems thinking emphasizes interconnectedness, shifting from linear to circular cause-and-effect understanding.
A fundamental shift in systems thinking is from linear thinking to circular thinking, recognizing that everything is interconnected. All parts of a system are dependent on each other.
Synthesis, combining parts to create something greater, is the goal, contrasting with analysis which breaks things down.
The goal of systems thinking is synthesis – combining elements to create something new and greater than the sum of its parts. This contrasts with traditional analysis, which dissects components.
Emergence is when larger, non-linear outcomes arise from the synergies of smaller, self-organized parts.
Emergence describes how larger, non-linear, and self-organized outcomes arise from the synergistic interactions of smaller parts. These emergent outcomes are not predictable by analyzing the individual components alone.
Taking multiple perspectives is vital to uncover the real problem, not just its symptoms.
A best practice in systems thinking is to examine problems and solutions from multiple points of view to ensure the actual problem is being addressed, rather than just treating symptoms.
Delays in feedback loops can lead to overcorrection and unintended negative consequences.
Delays within feedback loops are a critical aspect. Unawareness of these delays can cause individuals or systems to overcorrect, leading to oscillating or detrimental outcomes, as illustrated by adjusting shower water temperature.
Drifting goals occur when the desired future state is lowered or changed, avoiding necessary corrective action.
Drifting goals involve changing or lowering expectations to eliminate a perceived problem, rather than taking action to reach the original goal. This can prevent actual progress and leave one in the current state.
Changes in one system can have cascading, often unforeseen, impacts on interconnected systems and downstream processes.
Changes made to a specific system, especially within Agile development focusing on short cycles, can have significant and often unnoticed impacts on other interconnected systems, data flows, and subsequent decision-making processes.
Systems thinking should be incorporated *into* Agile methods, with the BA often leading this integration.
Instead of fitting Agile into systems thinking, systems thinking should be brought into Agile. The business analyst, with their broader view, is well-positioned to integrate systems thinking into Agile practices like Scrum.
Sections
Introduction to Systems Thinking
Systems thinking is a holistic mindset, not a rigid practice, focusing on interrelationships and contributing factors to outcomes.
Systems thinking is presented as a way to investigate various factors, interactions, and elements contributing to an outcome. It's characterized as a mindset rather than a prescribed practice with a step-by-step methodology.
It applies to human and social systems, not just technological ones, improving interrelationships and collaborative processes.
Contrary to common perception, systems thinking is not limited to computer or technological systems. It applies broadly to human beings, how they interact, and how to improve collaboration within teams and processes.
Systems thinking, combined with strategic and critical thinking, enhances business analysis capabilities.
When integrated with strategic thinking, critical thinking, and the core skills of a business analyst, systems thinking adds valuable dimensions to both problem analysis and solution synthesis.
Differentiating Systems Thinking and Strategic Thinking
Strategic thinking focuses on looking forward in time and outside a specific area of focus.
Strategic thinking involves looking at the future impact of changes, considering the temporal effects, and thinking hypothetically. It's visualized as expanding outward from one's immediate work area into the future.
Systems thinking expands organizational focus, looking at the bigger picture beyond assigned tasks.
Systems thinking, in contrast, is depicted as expanding the organizational focus, considering how a current task or project affects the overall organization. It's described as being perpendicular to strategic thinking.
Core Concepts of Systems Thinking
Systems thinking views change holistically, identifying patterns to predict future changes and their effects.
Systems thinking is a holistic approach that focuses on how a system's parts interrelate and change over time. It provides means to track changes, identify patterns, and predict future effects.
Understanding systems requires recognizing the interaction of all components, including people, hardware, software, and processes.
Systems include not just technical components like hardware and software, but also processes, data, and importantly, people. Understanding how these social systems interact with other systems is crucial.
Systems thinking emphasizes interconnectedness, shifting from linear to circular cause-and-effect understanding.
A fundamental shift in systems thinking is from linear thinking to circular thinking, recognizing that everything is interconnected. All parts of a system are dependent on each other.
Synthesis, combining parts to create something greater, is the goal, contrasting with analysis which breaks things down.
The goal of systems thinking is synthesis – combining elements to create something new and greater than the sum of its parts. This contrasts with traditional analysis, which dissects components.
Emergence is when larger, non-linear outcomes arise from the synergies of smaller, self-organized parts.
Emergence describes how larger, non-linear, and self-organized outcomes arise from the synergistic interactions of smaller parts. These emergent outcomes are not predictable by analyzing the individual components alone.
Feedback loops, positive or negative, are critical for maintaining interconnectivity and driving system behavior.
Feedback loops are essential for interconnectivity within a system. They can be reinforcing (positive), leading to more of the same, or balancing (negative), regulating behavior. Intervening in these loops can cause significant change.
Understanding causality goes beyond simple cause-and-effect to grasp complex interdependencies and relationships.
Systems thinkers aim to understand causality, which involves looking beyond simple cause-and-effect to grasp deeper perspectives on agency, feedback loops, and relationships within a dynamic system.
System mapping is a key tool to visualize and understand how systems interconnect and function.
System mapping uses various techniques to visualize and understand the interconnections within a system and how it interacts with other systems. It aids in comprehending complex systems that cannot be directly seen or touched.
Taking multiple perspectives is vital to uncover the real problem, not just its symptoms.
A best practice in systems thinking is to examine problems and solutions from multiple points of view to ensure the actual problem is being addressed, rather than just treating symptoms.
Characteristics of Systems
Systems possess organization (structure), interaction (communication), interdependence (mutual reliance), and integration (holism).
Systems are defined by several characteristics: organization (structure and order), interaction (communication between components), interdependence (mutual reliance of parts), and integration (holism, where the whole is more than the sum of its parts).
Every system has a central objective, which may be stated or unstated and might differ from operational reality.
All systems have a central objective. This objective can be formally stated or implied. Importantly, the stated objective may not always align with the system's actual operational objective or behavior.
Delays in feedback loops can lead to overcorrection and unintended negative consequences.
Delays within feedback loops are a critical aspect. Unawareness of these delays can cause individuals or systems to overcorrect, leading to oscillating or detrimental outcomes, as illustrated by adjusting shower water temperature.
Systems Thinking Challenges and Anti-Patterns
Fixes can have unintended consequences by addressing symptoms rather than root causes.
A common challenge is that fixes may address symptoms and lead to unintended consequences, failing to solve the real problem. A systems view helps identify the root cause versus the symptoms.
The Hawthorne Effect shows temporary productivity gains from observed changes, which later revert.
The Hawthorne Effect demonstrates that changes made to a system can temporarily boost productivity simply due to the attention received, but this effect often fades, returning productivity to previous levels.
Limits to growth occur when systems hit natural boundaries, requiring different strategies or behavior changes.
Systems often encounter limits to growth, where continued application of the same methods yields diminishing returns. Overcoming these limits may require changing the approach or behavior.
The 'Einstein effect' describes the tendency to solve problems using established, familiar methods, hindering adaptation.
The 'Einstein effect' or isolating effect refers to the human tendency to rely on previously successful methods, even when a different approach is needed for new challenges.
Shifting the burden involves addressing symptoms instead of core issues, potentially delaying fundamental solutions.
Shifting the burden means focusing on managing symptoms rather than solving the underlying problem. While sometimes a necessary temporary measure (like stopping bleeding), it can distract from addressing the root cause.
The Tragedy of the Commons arises when shared resources are depleted by individual actions, leading to collective suffering.
The Tragedy of the Commons occurs when individuals exploiting a shared resource for their own benefit deplete it, ultimately harming everyone involved.
Drifting goals occur when the desired future state is lowered or changed, avoiding necessary corrective action.
Drifting goals involve changing or lowering expectations to eliminate a perceived problem, rather than taking action to reach the original goal. This can prevent actual progress and leave one in the current state.
Systems Thinking for Business Analysts
Business analysts must maintain focus on the big picture, understanding how their project fits into the larger system.
Even when working on specific, detailed tasks within a project (like user stories in Agile), business analysts must keep the overall system goal and the transition from the current state to the future state in mind.
Changes in one system can have cascading, often unforeseen, impacts on interconnected systems and downstream processes.
Changes made to a specific system, especially within Agile development focusing on short cycles, can have significant and often unnoticed impacts on other interconnected systems, data flows, and subsequent decision-making processes.
A systems thinking BA identifies complex and recurring problems, understands interdependencies, and explores patterns and feedback structures.
A systems thinking business analyst recognizes complex and recurring problems, explores interdependencies, identifies patterns, and understands feedback structures, including delays. They help managers grasp the full impact of decisions.
Best practices include identifying the status quo, taking a big-picture view, challenging jargon, and experiencing time differently.
Best practices include establishing the current state, stepping back to view the big picture, questioning jargon like 'productivity', experiencing time differently by altering timelines, and looking at operations from various angles.
Exposing mental models, challenging assumptions, and using clear, specific language are crucial for effective communication.
It's important to expose mental models, diagram systems, invite reviews, honor and distribute information accurately, use specific and precise language (avoiding vague terms like 'inefficient'), and expand vocabulary to discuss complexity.
Focus on the whole system's properties like growth and resilience, not just optimizing individual parts.
Prioritize enhancing the total system's properties such as growth, stability, diversity, resilience, and sustainability over optimizing individual components, especially if those components are not essential to the overall goal.
Listen to the system's wisdom, identify its self-maintenance capabilities, and pay attention to triggering events and decisions.
Pay attention to how the system behaves, its history, and its self-maintenance capabilities. Understand triggering events, user application of behaviors, and decisions made within its operation.
Embrace complexity and failure, using intuition alongside rationality through experimentation and learning.
The universe is complex and non-linear. Systems thinkers should embrace complexity, celebrate failure as a learning opportunity, fail fast and early, and trust intuition as well as rationality.
A systems thinking BA defines the system goal, practices empathy, seeks diversity, and uses tools like impact analysis and system mapping.
Key actions for a systems thinking BA include defining the system goal, practicing empathy, seeking diverse perspectives and team members, and utilizing tools such as impact analysis, system mapping, and affinity diagrams.
Continuously review the vision, assess impacts on other areas, and seek diverse reviewers to check for negative feedback.
Regularly review the system against the vision, assess its impact on other organizational areas, and use diverse reviewers to identify potential negative feedback and ensure the system remains aligned and effective.
The ultimate goal is to be humble and holistic, understanding the system's dynamic nature.
The overarching aim is to approach systems with humility and a holistic perspective, recognizing their dynamic, transient, and often messy nature.
Questions and Answers
A 'process owner' is the closest role to someone who owns the central objective of a system.
The role closest to owning the central objective of a system is often a 'process owner', responsible for an entire end-to-end business process that may span multiple functional areas.
Systems thinking should be incorporated *into* Agile methods, with the BA often leading this integration.
Instead of fitting Agile into systems thinking, systems thinking should be brought into Agile. The business analyst, with their broader view, is well-positioned to integrate systems thinking into Agile practices like Scrum.
Prototyping and impact analysis are key tools to avoid production failures and backfiring fixes.
To avoid production issues, robust prototyping and thorough impact analysis are essential. While no method guarantees zero errors due to human interaction, these tools significantly reduce the likelihood of backfiring fixes.
Ask a Question
*Uses 1 Wisdom coin from your coin balance
