What this simulation shows
Alf Garnett never approached an argument with an open mind. The conclusion was settled before the discussion started, and Mike’s evidence was irrelevant because Mike belonged to the wrong tribe. Once identity places someone on the other side, whatever they say is wrong.
Tajfel and Turner called the underlying mechanism Social Identity Theory: people form group attachments remarkably fast and almost immediately begin favouring their own group, seeking information that confirms its competence and discounting evidence that challenges it. Football supporters recognise this instantly — the officials always do seem harsher on your club.
Businesses assume they are exempt. They are not, and this simulation demonstrates why without needing anyone to behave irrationally.
Warehouse becomes frustrated with Transport for demanding vehicles before loading is finished. Transport complains that Warehouse never appreciates the cost of idle drivers and missed delivery windows. Finance believes everyone spends too freely. Everyone else concludes Finance has never dealt with an unhappy customer. None of these positions is unreasonable. Each accurately reflects the reality experienced inside that department.
Senge’s term for this is mental models: the deeply held assumptions that shape how people interpret what they see. They are necessary — they make complexity manageable — and they create blind spots, because each department builds a coherent view of the business from the information it happens to see and the outcomes it happens to be measured against.
How to use it
Set each of the four departmental controls — Sales, Warehouse, Transport, Planning — to what that department would reasonably ask for. Maximise service on Sales. Maximise loading efficiency on Warehouse. Minimise idle time on Transport. Maximise plan stability on Planning.
Then press Run scenario and read Whole-system performance.
Every department is hitting its target. The system is performing worse than a configuration where none of them are. That is the entire lesson, and it survives repeated attempts to beat it: try to find settings where all four departments are individually optimised and the whole system performs well. The trade-offs are real, not artefacts of a badly built model.
Then use Management controls to intervene. Notice that the interventions which help most are usually the ones that make an individual department’s own metric slightly worse. This is exactly why they are so hard to get agreed.
What to take away
The danger is not that departments hold partial views — that is unavoidable. The danger is mistaking a partial view for the whole system. Sales, Operations, Finance and Technology can each act rationally within their own frame and collectively produce decisions that make no sense for the organisation.
For product managers this is the central challenge and the actual job. The role is not to contribute one more departmental perspective, but to expose the assumptions behind competing views, connect them across the wider system, and help the organisation reach a more complete understanding of the problem — the argument the systems thinking article develops in full.
Interactive systems-thinking simulation
When Departments Become Football Teams
Adjust departmental identity, KPI pressure and cross-functional practices to see how sensible local decisions can damage whole-system performance.
Whole-system performance
Local scoreboards
Every department can be right and the business can still lose
Sales
Planning
Warehouse
Transport
High identity bias and strong local KPI pressure encourage teams to defend their own measures rather than solve the end-to-end problem.
What the model represents
How the simulation works
Each department receives a local score based on what it is incentivised to protect. Sales gains when it accepts more customer changes, Warehouse gains when it batches work efficiently, Planning gains when orders remain stable, and Transport gains when vehicles leave on time and run full. The conflict appears because the action that improves one local measure often makes another department's work harder.
The identity bias control represents the strength of the “our team versus their team” mentality. Local KPI pressure represents how strongly people are rewarded for their own departmental result. Customer volatility increases late changes and operational disruption. The three interventions reduce silo behaviour by creating shared measures, broader mental models and decision rights that sit above departmental turf.
How to use this simulation
Change one input at a time, run the model, and compare the result with the starting state. Then repeat the experiment with a different constraint or strategy so you can see which relationships drive the outcome.
What to look for
Look for trade-offs, thresholds, feedback loops, and points where a locally attractive decision produces a worse system-wide result. The simulation is intended to make the article's idea observable, not to predict a real operation.
Limitations
This is a deliberately simplified model. It omits the data quality, exceptions, human judgement, and operational constraints of a live system, so treat its behaviour as an illustration of a mechanism rather than as a planning recommendation.
Read the related article
Read: It Stands to Reason: What Alf Garnett Can Teach Us About Organisational Tribalism →
Explore the complete Systems Thinking for Product Managers series