Testing a claim
Many arguments fail not because people lack intelligence, but because they lack a structured way to evaluate claims.
Systems thinking provides a simple process for analyzing information while minimizing bias and avoiding logical errors.
This exercise walks through an example using four investigation questions:
1. What claim is being made?
2. What evidence supports it?
3. What variables are measured or missing?
4. What are the downstream consequences?
Scenario
My school announces a new rule. Phones are now banned during lunch. The reason given is: “Phones are harming student mental health and social skills.”
Students immediately react. Some think the rule is ridiculous. Some think it is a good idea.
Some assume teachers just want control. But before deciding whether the rule is good or bad, I can investigate the claim behind the rule.
Step 1 — What Claim Is Being Made? Before evaluating anything, I need to clearly define the claim.
Possible answers I might give could be:
* Phone use reduces social interaction.
* Phone use harms student mental health.
* Phones prevent students from talking to each other.
A clearer version of the claim might be:
Claim: Phone use during lunch negatively affects student mental health and social interaction. Many arguments fail because people react to different interpretations of a claim. Systems thinking begins by identifying the exact claim being tested.
Step 2 — What Evidence Supports the Claim?
Next, I ask what evidence exists to support the claim. Possible answers I might give could be:
* Research studies on phone use and mental health
* Observations from teachers or administrators
* Student surveys about phone use during lunch
* Reports showing changes in student behavior
At this stage I also ask how strong the evidence is. For example:
Weak evidence might look like: “I saw three students sitting alone on their phones.”
Stronger evidence might look like: “A study of thousands of students across multiple schools found reduced social interaction when phones were used during lunch.”
Systems thinkers distinguish between:
* anecdotes
* patterns
* verified data
Step 3 — What Variables Are Measured or Missing?
Systems are complex. Outcomes are rarely caused by a single factor. To evaluate the claim properly, I need to consider other variables that could influence what is being observed. Possible answers I might give could be:
* Some students are naturally introverted
* Some students use phones to coordinate activities with friends
* Some students communicate with friends outside the school
* Some students already have established friend groups
If these variables are ignored, the conclusion could be misleading. For example:
If students using phones appear less social, is the phone causing the behavior?
Or are students who are already less social simply more likely to use their phones? Confusing correlation with cause is a category error that systems thinkers try to avoid.
Step 4 What Are the Downstream Consequences?
Now I zoom out and consider how the system might change if the claim leads to policy decisions. Positive outcomes might include:
* Students talking to each other more
* More group activities during lunch
Negative outcomes might include:
* Students feeling frustrated or controlled
* Students losing a way to contact family
* Students hiding phone use instead of changing behavior
Systems thinking looks at how decisions ripple through the entire system, not just the original problem.
Bias Check - At this point I also check my own assumptions. If I personally like using my phone, I may be more likely to reject evidence that supports the rule.
If I dislike phones, I may be more likely to accept weak evidence against them.
Bias does not make someone irrational. It simply means preferences exist.
The goal of systems thinking is to notice bias before it limits investigation.
Final Evaluation: After asking the four investigation questions, I can evaluate the strength of the claim. Possible conclusions I might reach could be:
* The evidence strongly supports the claim.
* The evidence does not support the claim.
* There is not enough information to reach a conclusion.
Systems thinkers are comfortable saying: “More evidence is needed before making a decision.”
The LNNP Claim Test: Whenever I encounter a strong claim, I can ask:
1. What claim is being made?
2. What evidence supports it?
3. What variables are measured or missing?
4. What are the downstream consequences?
If these questions cannot be answered clearly, the claim may not be as strong as it first appears.
Core Idea: Systems thinking does not tell me what to believe. It gives me a structured way to investigate claims before reacting to them. In a world full of confident statements and strong opinions, this skill allows me to pause and ask:
Does the evidence actually support the claim?