2.1.3: ABM vs other approaches#
ABM is not the only way to simulate a system, so how does it compare to the main alternatives, and when is it actually the right choice? This section makes two moves: first it sets ABM beside the other two established simulation paradigms to see where each is strong, and then it turns that comparison into judgement about when the extra effort of modelling individuals earns its cost.
2.1.3.1: ABM vs. system dynamics (SD) vs. discrete event simulation (DES)#
Agent-based modelling is one of three main ways to simulate a system, alongside system dynamics, which tracks whole-system quantities as they flow and accumulate, and discrete-event simulation, which advances from one scheduled event to the next. System dynamics describes the world as stocks and flows at the aggregate level (total population, total inventory), so it captures global feedback loops but not the individuals inside those totals. Discrete-event simulation follows entities through a sequence of timed events (an arrival, a service, a departure), which makes it ideal for queues and processes but leaves little room for agents that learn or adapt between events. They differ in the level at which they describe the world, in how much variety between individuals they can hold, and in the kinds of feedback they capture. Knowing where each one is strong matters because choosing the wrong approach can make a problem needlessly hard, or hide the very thing you set out to study. In the table below, click any feature row to read when that feature tips the balance towards ABM, and look for the recurring theme that ABM pays off when the detail of single individuals is what drives the outcome.
| Feature | ABM | System dynamics | Discrete-event |
|---|
The point to remember is that ABM, system dynamics, and discrete-event simulation are not rivals but different tools, and the right choice depends on whether individual differences, adaptation, and local feedback matter for the question you are asking.
2.1.3.2: When to choose ABM#
ABM is particularly suitable when:
Different agents have varying characteristics, behaviours, or decision-making processes that significantly affect system outcomes.
Agents interact primarily with neighbours, specific groups, or network connections rather than through global mechanisms.
You want to discover how unexpected macro-level patterns arise from simple micro-level interactions without pre-programming the outcomes.
Physical location, proximity, geographic constraints, or network topology directly influence agent interactions and system dynamics.
You want to safely experiment with interventions, compare scenarios, and understand unintended consequences before real-world implementation.
These five conditions describe when ABM fits, but recognising them in a real problem is a matter of judgement rather than a checklist. Reaching for ABM by habit is a common mistake, and so is dismissing it when it would help. The skill worth building is judgement: knowing when individual differences and local interactions truly drive an outcome, so that the added effort of modelling individuals buys you something a simpler aggregate model could not. In the activity below, each case describes a situation. Decide whether ABM fits or a simpler model would do, and let the streak of correct answers show you how consistent your judgement is becoming.
The lesson is that the question to ask is never whether ABM is fashionable, but whether the differences between individuals and their local interactions actually matter for what you want to learn.
2.1.3.3: Checklist: when is ABM suitable?#
Having judged individual cases, it helps to turn that judgement into a repeatable check you can run against your own project. The activity below expands the five criteria from 2.1.3.2 into concrete prompts, applies the scoring guide, and recommends the modelling level that best fits the evidence.
Across all of these checks the deciding question is the same: choose the approach that matches whether individual detail actually drives the outcome, rather than defaulting to the paradigm you know best. You will return to this decision with a fuller framework in section 2.3.3 (Decision framework); for now, with a sense of when ABM is the right tool, the next part opens up what an ABM is actually made of, beginning with its agents and their environment.
Key takeaways#
Key takeaways
Agent-based modelling, system dynamics, and discrete-event simulation describe a system at different levels of detail, and the appropriate choice depends on the question being asked.
ABM is preferable when individual heterogeneity, local interactions, spatial or network structure, or emergence are central to the problem.
When only aggregate averages are required, a simpler model is usually the better choice, so ABM should be selected by judgement rather than by default.