The Problem with How Most Businesses Deploy AI
Most AI deployments fail not because the technology was wrong, but because the system around the technology was misunderstood.
Teams optimise a model in isolation, then wonder why the outcomes are biased. They satisfy a compliance checkbox, then discover the requirement touched fifteen other processes they hadn’t mapped. They fix a symptom – only to watch the underlying problem resurface somewhere else six months later.
Systems thinking is the discipline that closes this gap. It shifts attention from the components of an AI deployment to the relationships between them, such as the feedback loops, delays, and interdependencies that determine whether an AI initiative actually delivers what was intended.
This toolkit gives business leaders and their teams a practical entry point into that discipline. It is structured around three phases of AI deployment and eleven tools, each adapted from established systems thinking methodology and grounded in Australia’s regulatory and ethical landscape.
Table of Contents
Phase 1: Confirm the Goal and Understand the AI System
- Principle 1: Identify Key Issues and Establish a Collaborating Community with a Shared Goal
- Tool 1 – Rich Pictures: Expressing a Summary of the AI System
- Tool 2 – The Stakeholder Model: Understanding Diverse Views of the AI System
- Principle 2: Reach a Shared Understanding of the AI Problem
- Tool 3 – Context Diagrams: Identifying AI System Boundaries
- Tool 4 – Behaviour Over Time Graphs and AI System Problem Statements: Articulating Your Problem and Goal
- Tool 5 – Identifying Enablers and Inhibitors: Exploring the Causes of Your AI Problem
- Tool 6 – Creating a Causal Loop Diagram: Mapping Your AI System
- Tool 7 – Causal Loop Diagram: Analysis and Narrative
Phase 2: Co-design and Test Possible AI Interventions
- Principle 3: Explore Interventions Using an Understanding of the AI System and Its Possible Leverage Points
- Tool 8 – Identifying AI Systems Leverage
- Principle 4: Test the Ideas
- Tool 9 – Stock and Flow Diagrams for AI Systems
- Tool 10 – Theory of Change Maps for AI Initiatives
Phase 3: Implement Systemic AI Interventions, Monitor and Evaluate
- Principle 5: Monitor, Evaluate, and Learn with the Community
- Tool 11 – Monitoring and Evaluation Strategy for AI Systems
What Does It Mean to Take a Whole-System Approach to AI?
An AI system is not a piece of software. It is a dynamic arrangement of algorithms, data pipelines, organisational cultures, human workflows, customer relationships, and regulatory obligations – all of which interact continuously and produce outcomes no single component could generate alone.
This creates a specific kind of risk that technical expertise alone cannot manage: the risk of solving the wrong problem. Addressing algorithmic bias, for example, isn’t a matter of adjusting a model. It requires tracing a causal chain from data collection practices through to deployment context, organisational incentives, and customer impact. That chain is a system, and it needs to be mapped and understood as one.
Systems thinking offers several concrete advantages for businesses navigating this terrain. It surfaces root causes rather than symptoms, which means interventions last. It maps feedback loops and interdependencies before deployment, which means unintended consequences are anticipated rather than discovered. It builds shared understanding across technical, legal, and executive stakeholders, which means AI decisions carry broader organisational legitimacy. And it embeds regulatory requirements into the design of AI systems rather than treating them as afterthoughts, such as Australia’s Voluntary AI Safety Standard (VAISS), the Privacy Act 1988, the Australian AI Ethics Principles, and obligations under Section 912A of the Corporations Act for AFSL holders.
The toolkit in this document is most valuable in specific situations: when designing AI strategy before significant resources are committed; when an AI system is producing biased or unexpected outcomes; when data governance obligations require a privacy-by-design approach; when regulatory compliance needs to be integrated into the AI development lifecycle; and when you need to evaluate the broader and longer-term impacts of a deployment beyond model accuracy.
How This Toolkit Works
The eleven tools in this document are not a recipe to follow once and set aside. Their value is iterative: each tool builds on the last, and the process of mapping, discussing, and refining is as important as the outputs it produces.
The toolkit is built around three phases that mirror the natural lifecycle of an AI initiative. Phase 1 establishes a clear goal and a comprehensive understanding of the system you’re working with. Phase 2 identifies where and how to intervene, using modelling and simulation to test ideas before they’re deployed. Phase 3 embeds the discipline of ongoing monitoring, evaluation, and adaptation.
Data and its visualisation run through all three phases. Effective data work here does more than measure performance. It exposes the AI system’s behaviour over time, reveals disparities across demographic groups, tracks data feedback loops, and provides the evidence base for regulatory compliance. Visualising data lineage, in particular, is one of the most practical tools for identifying the upstream sources of downstream problems.
Phase 1: Confirm the Goal and Understand the AI System
Principle 1: Identify Key Issues and Establish a Collaborating Community with a Shared Goal
Effective AI deployment starts with understanding the problem and the ecosystem it inhabits. The organisations that get this right bring together diverse perspectives early, not as a consultation exercise, but as the primary means of developing a shared, accurate picture of what the AI system actually involves.
Tool 1 – Rich Pictures: Map the Full AI System Before You Build It
Purpose: To create a visual representation of the AI system that captures relationships, stakeholder perspectives, data flows, and the regulatory environment – including the qualitative and human elements that formal diagrams miss.
How to Apply to AI:
- Identify the Core AI System: Place the AI system (for example, an AI-powered recommendation engine or automated decision-making tool) at the centre.
- Map Stakeholders: Draw all relevant stakeholders: internal teams (data scientists, legal, ethics, business units), external partners (AI vendors, data providers), customers, regulators (ASIC, OAIC), and affected communities. Represent their relationships and relative influence.
- Illustrate Data Flows: Show how data enters, moves through, and exits the system. Highlight data sources, transformation points, and where personal information is processed.
- Depict Key Processes and Interactions: Sketch human-AI interactions, decision points, feedback loops (for example, model retraining based on user feedback), and automated processes.
- Capture Perceptions and Emotions: Use symbols or speech bubbles to represent stakeholders’ concerns (privacy risk, bias), expectations, and conflicting views.
- Include the Regulatory Context: Represent relevant Australian regulations – the Privacy Act 1988, AFSL obligations, the Australian AI Ethics Principles – and show how they interact with the system.
Outcomes: A shared, holistic picture of the AI system that surfaces complexity and disagreement early, before they become expensive problems. Rich pictures are particularly effective at exposing the human and organisational dimensions that technical documentation omits.
Tool 2 – The Stakeholder Model: Understand Who Defines Success
Purpose: To systematically identify and analyse all stakeholders affected by the AI system, understand their differing perspectives on its goals, and establish the basis for a collaborating community.
How to Apply to AI:
- Identify All Stakeholders: List everyone who has a stake in the AI system. Include system owners, operators, users, those affected by the AI’s decisions, and regulators.
- Analyse Their Perspectives: For each stakeholder, understand what success looks like from their perspective, what risks they perceive, and what their level of influence over the AI system is.
- Identify Conflicts and Alignments: Where do stakeholder interests align? Where do they conflict? For example, a business unit’s desire for automated decisioning speed may conflict with a legal team’s requirement for explainable outcomes.
- Establish a Collaborating Community: Based on this analysis, bring together a representative group with the mandate and authority to guide the AI initiative. Ensure the community includes technical, ethical, legal, and end-user perspectives.
Outcomes: A clear map of who needs to be involved, what they care about, and where collaboration will require active facilitation. This prevents the common failure mode of AI projects that are technically sound but organisationally orphaned.
Principle 2: Reach a Shared Understanding of the AI Problem
Once you have a community and a rich picture, the next step is precision: articulating the specific problem the AI is meant to solve and understanding the system dynamics that produced it.
Tool 3 – Context Diagrams: Define the Boundaries of Your AI System
Purpose: To create a concentric circle diagram that shows the relative influence different entities have on the AI system, making clear who can direct it, who can shape it, who matters but operates at arm’s length, and what environmental forces exist beyond anyone’s control.
This is not a data flow diagram. It is an influence diagram. The question it answers is not “what connects to the system?” but “who can actually change what the system does?”
How to Apply to AI:
- Define the AI System Boundary: The system under analysis sits in the innermost circle.
- Identify External Entities: List every person, team, organisation, regulation, and environmental factor that is relevant to the system’s operation.
- Map the Influence: For each entity place within the specific influence circle the different entities:
- Under Direct Control: Those who build, configure, and operate the system. Example: Fraud Detection Developers.
- Able to Influence: Those who shape requirements, priorities, and constraints. Example: Risk Team, Executive Team, users.
- Not able to Influence but important: Forces that matter significantly but cannot be directed. Example: Existing regulations, third-party data providers.
- Enviromental factors: Background conditions that affect the system without any party controlling them. Example: Dark Web activity that drives the threat landscape.
- Validate the Boundaries: Review the diagram with your collaborating community. Misplaced entities – particularly overestimating how much influence an organisation has over regulators or external data providers – are a common source of flawed intervention design.
Outcomes: A formally bounded system that gives the team a shared, unambiguous definition of what they are responsible for, and what they are not.
Tool 4 – Behaviour Over Time Graphs and Problem Statements: Articulate the Problem You’re Actually Solving
Purpose: To visualise how key variables in your AI system have changed over time, and use those patterns to craft a precise problem statement and goal.
How to Apply to AI:
- Select Key Variables: Choose three to five variables that capture the most important aspects of your AI system’s performance. Examples: model accuracy, false positive rate, customer trust score, regulatory breach incidents.
- Plot the Historical Trend: For each variable, draw a graph showing how it has behaved over a relevant time period. Where is it going? Is it deteriorating, stable, or oscillating?
- Identify the Pattern: What is the main pattern you want to change? For example, a steadily increasing false positive rate, or a customer trust score that collapses each time the model is retrained.
- Craft the Problem Statement: Write a clear, specific problem statement that names the variable, describes its undesirable behaviour, and specifies the timeframe. Example: “Our AI credit model’s false positive rate has increased by 40% over the past 12 months, eroding customer trust and increasing manual review costs”.
- Define the Goal: Articulate the desired future behaviour of the same variables. This becomes the target your interventions are designed to achieve.
Outcomes: A grounded, evidence-based problem statement that the whole team agrees on, a critical prerequisite before any solution is designed.
Tool 5 – Identifying Enablers and Inhibitors: Understand What’s Driving Your AI Problem
Purpose: To systematically explore the factors that support or obstruct the AI system’s ability to deliver its intended outcomes.
How to Apply to AI:
- Use Your Problem Statement as the Anchor: Keep the problem you defined in Tool 4 at the centre of this analysis.
- Brainstorm Inhibitors: Ask, “What factors make this problem worse or prevent us from achieving our goal?” Organise them across four dimensions:
- Technical: Data quality issues, model drift, integration failures.
- Organisational: Siloed teams, unclear accountability for AI outcomes, insufficient resources.
- Regulatory: Ambiguity in compliance obligations, gaps in internal policy.
- Human: Distrust of AI outputs, skills gaps, change resistance.
- Brainstorm Enablers: Ask, “What factors support the system in delivering its goal? What resources can we leverage?” Examples include executive sponsorship, access to cloud infrastructure, clear guidance from the OAIC, and strong customer demand.
- Prioritise: Not all inhibitors carry equal weight. Which ones, if addressed, would have the greatest impact on the problem?
Outcomes: A structured map of the forces at play, the essential input for building your causal loop diagram in the next tool.
Tool 6 – Creating a Causal Loop Diagram: Map the Dynamics of Your AI System
Purpose: To create a visual map of the feedback loops and causal relationships that drive AI system behaviour. This is the central analytical tool of systems thinking.
How to Apply to AI:
- Start with Key Variables: Select the most important variables from your previous analyses. Examples: “Model Accuracy”, “Customer Trust”, “Data Quality”, “Number of False Positives”.
- Connect Variables with Arrows: Draw arrows between variables to show direction of influence. An increase in “Data Quality”, for example, leads to an increase in “Model Accuracy”.
- Label the Links: Mark each arrow with an ‘s’ (same direction – if one increases, so does the other) or an ‘o’ (opposite direction – if one increases, the other decreases). Example: “Number of False Positives” → ‘o’ → “Customer Trust”.
- Identify Feedback Loops: Trace the arrows to find closed loops. Label each as reinforcing (R) or balancing (B).
- A reinforcing loop amplifies change in one direction. Example: Higher model accuracy drives higher user adoption, which generates more data, which improves data quality, which drives higher model accuracy again (R).
- A balancing loop resists change and seeks stability. Example: An increase in false positives triggers more manual reviews, raising operational costs, which drives investment in model improvement, which reduces false positives (B).
Outcomes: A dynamic visual map of your AI system that reveals the underlying structures driving its behaviour. This is the foundation for identifying where to intervene.
Tool 7 – Causal Loop Diagram Analysis and Narrative: Turn the Map into Insight
Purpose: To interpret the causal loop diagram, surface key insights, and develop a clear narrative that explains the AI system’s behaviour to stakeholders.
How to Apply to AI:
- Analyse the Dominant Loops: Which loops are driving the system’s current behaviour? Are there vicious cycles at work, for example, declining trust leading to reduced usage, which degrades model performance, which further erodes trust?
- Look for Delays: Identify where significant delays exist in the system. Delays are a common source of oscillating behaviour and unexpected outcomes. There is often a long lag between deploying a new model and seeing any change in customer satisfaction scores.
- Identify Common Archetypes: Look for recognisable system patterns:
- Fixes That Fail: A short-term intervention (manually overriding flagged transactions) that prevents the system from learning, causing the original problem to return.
- Shifting the Burden: Addressing a symptom (a customer service team handling AI complaints) instead of the root cause (a biased model), which atrophies the organisation’s capacity to solve the fundamental problem.
- Develop a Narrative: Write a concise story that explains the AI system’s behaviour based on the diagram. Use it to communicate findings to stakeholders, build consensus, and justify proposed interventions.
Outcomes: Deep insight into the systemic causes of the AI problem, and a practical communication tool to align stakeholders around a shared understanding.
Phase 2: Co-design and Test Possible AI Interventions
Principle 3: Identify Where to Intervene – Not Just What to Change
With a comprehensive map of the AI system, the question becomes: where will an intervention actually make a difference? Not all interventions are equal. Some address symptoms. Others change the system’s fundamental structure.
Tool 8 – Identifying AI Systems Leverage: Find Where Small Changes Produce Large Results
Purpose: To identify high-leverage points, the places in the system where a well-targeted intervention will produce significant, lasting improvement. This tool applies Donella Meadows’ leverage points framework to AI deployment.
How to Apply to AI:
Consider these leverage points in ascending order of impact:
- Constants and Parameters (least leverage): Adjusting numerical model parameters such as learning rate or decision thresholds. Useful for optimisation, but rarely changes fundamental system behaviour.
- Buffers: The size of data buffers or processing infrastructure capacity. Increasing these improves stability but doesn’t address root causes.
- Stock-and-Flow Structures: The physical architecture of the AI system: data pipelines, hardware, infrastructure. Changes here are costly and time-consuming.
- Delays: The time it takes for information to travel through the system. Reducing delays in feedback loops (for example, faster model retraining cycles) can significantly improve responsiveness.
- Balancing Feedback Loops: Strengthening the controls that keep the system stable. For example, tightening the feedback loop between model performance and data quality assurance improves reliability.
- Reinforcing Feedback Loops: Slowing a vicious cycle (eroding trust) or accelerating a virtuous one (user adoption driving data quality improvement) is a more powerful intervention.
- Information Flows: Who can see what. Improving transparency by giving users clear explanations of AI decisions – consistent with the Australian AI Ethics Principles – builds trust and creates new positive feedback loops.
- Rules of the System: The governing rules, such as the data privacy policies under the Privacy Act 1988, ethical guidelines, performance thresholds. Changing the rules changes behaviour throughout the system.
- The Goal of the System (high leverage): Shifting the goal from “maximising accuracy” to “making fair and transparent decisions” changes the design criteria for the entire system.
- The Paradigm Out of Which the System Arises (highest leverage): The deeply held beliefs shaping the system. The shift from a purely technical view of AI to a human-centred, socio-technical perspective – one that treats human wellbeing as a design requirement, not an afterthought – is the most powerful intervention of all.
Outcomes: A prioritised list of potential interventions, focused on those that create genuine, systemic change rather than temporarily suppressing the problem.
Principle 4: Test the Ideas Before You Deploy Them
Before committing to implementation, test your proposed interventions against a model of the system. Simulation and modelling exist precisely to let you discover failure modes cheaply, before they surface in production.
Tool 9 – Stock and Flow Diagrams: Build a Model You Can Test
Purpose: To create a quantitative model of the AI system that simulates the effects of different interventions over time. This builds on the qualitative insights from the causal loop diagram.
How to Apply to AI:
- Identify Stocks: The key accumulations in the system, the things you could measure at a single point in time. Examples: “Number of active users”, “Volume of training data”, “Level of customer trust”.
- Identify Flows: The rates that cause stocks to increase or decrease. Examples: “New user adoption rate” (inflow to active users), “User churn rate” (outflow from active users).
- Connect Stocks and Flows: Draw stocks as boxes and flows as pipes with directional arrows. Use your causal loop diagram to define the logic of each flow.
- Simulate Interventions: Use simulation software or a spreadsheet to test your proposed interventions. Ask:
- “What happens to customer trust if we reduce the false positive rate by 30%?”
- “How does a three-month delay in model retraining affect overall accuracy?”
Outcomes: A dynamic model of the AI system that lets you test hypotheses, compare intervention strategies, and anticipate long-term consequences before they become real.
Tool 10 – Theory of Change Maps: Articulate the Causal Path from Intervention to Impact
Purpose: To create a visual roadmap showing how an AI intervention produces the desired long-term impact, making the underlying assumptions explicit and testable.
How to Apply to AI:
- Start with the Long-Term Goal: Define the ultimate impact the AI initiative is designed to achieve. Example: “Improved customer financial wellbeing”.
- Work Backwards: Identify the long-term outcomes that must be in place to achieve this goal. Example: “Customers make better financial decisions”.
- Identify Intermediate Outcomes: Continue working backwards through the shorter-term outcomes. Example: “Customers receive fair and transparent credit assessments”.
- Define the Outputs: What does the AI intervention directly produce? Example: “AI model generates accurate and explainable credit scores”.
- State the Intervention: Name the specific AI intervention clearly. Example: “Deploy a new, ethically-designed AI credit scoring model”.
- Articulate the Assumptions: For each link in the chain, state the assumption on which it depends. Example: “We assume that transparent credit assessments will increase customer trust in our services”. These assumptions are where your model is most vulnerable, so surface them, then test them.
Outcomes: A logical map that explains how the AI initiative creates change, surfaces risky assumptions, and establishes the metrics worth monitoring.
Phase 3: Implement Systemic AI Interventions, Monitor and Evaluate
Principle 5: Monitor, Evaluate, and Learn with the Community
An AI system is not static. The model drifts. The environment changes. Regulations evolve. User behaviour shifts. The organisation that treats deployment as the end of the process will watch its AI initiative quietly degrade, or spectacularly fail. The discipline of continuous monitoring, evaluation, and adaptation is what separates AI deployments that deliver sustained value from those that become expensive liabilities.
Tool 11 – Monitoring and Evaluation Strategy: Build Governance That Keeps Pace with the System
Purpose: To develop a comprehensive strategy for monitoring the performance, behaviour, and impact of the AI system across its lifecycle.
How to Apply to AI:
- Define Key Performance Indicators: Based on your Theory of Change map and system diagrams, build a balanced set of metrics that go well beyond model accuracy:
- Performance Metrics: Accuracy, precision, recall, false positive and negative rates.
- Fairness and Bias Metrics: Performance variation across demographic groups.
- Privacy Metrics: Data access requests, privacy incidents.
- Business Metrics: Customer satisfaction, operational efficiency, return on investment.
- Regulatory Compliance Metrics: Adherence to AFSL obligations and Privacy Act requirements.
- Establish Monitoring Processes: Implement automated dashboards and alerting systems. Define clear thresholds for when manual review or escalation is required.
- Conduct Regular Evaluations: Schedule periodic, in-depth assessments covering both quantitative KPI analysis and qualitative stakeholder feedback, from users, customers, and employees.
- Create Feedback Loops for Learning: Build clear processes for using monitoring insights to drive system improvements. This may mean model retraining, process adjustment, or revisiting the system’s fundamental goals.
- Engage the Collaborating Community: Share monitoring and evaluation findings with the stakeholder community established in Phase 1. Use their input to co-design improvements and ensure the AI system continues to meet their needs and reflect their values.
Outcomes: A governance framework for the ongoing improvement of the AI system. One that builds a culture of learning, not just compliance, and ensures the AI initiative keeps delivering what it was built to deliver.
References
Department of Industry, Science and Resources. Voluntary AI Safety Standard.
Department of Industry, Science and Resources. Australia’s AI Ethics Principles.
Office of the Australian Information Commissioner. Guidance on Privacy and the Use of Commercially Available AI Products.