The Missing Step Between Evidence and Conclusion
Spot the hidden assumption in an argument, test whether it holds, and ask a precise question that reveals what would make the conclusion persuasive.

The most common mistake in an argument is treating a relevant fact as if it settles what should be done. In an argument about a late bus, complaints may establish that passengers are unhappy, but not that extending the service would solve the problem. The cost is a debate that jumps to a remedy before anyone has examined the reasoning that connects the two.
Find the reasoning behind a proposed action
Public arguments often move from a concern to a remedy: a school rule should change, a council should fund a service, or an organisation should alter its practice. The crucial question is not simply whether the concern is real. It is why this particular response should address it.
Take a council proposal to extend a late bus after residents complain about the current timetable. The proposal depends on a practical idea: the people affected need to travel after the service ends, and a later bus would take them where they need to go. If either part fails, the complaints may still deserve attention, but they do not by themselves justify that specific change.
Separate three things in your notes: the problem being described, the action being proposed, and the reason the action is expected to address the problem. This is different from checking whether a claim is broadly supported. It focuses on the choice of response and the reasoning that makes that response relevant.
Make the proposed remedy’s assumption explicit
Ask, “What must be true for this action to address the problem?” Write the answer as a complete sentence. Avoid answers that merely repeat the concern or proposal.
For the bus argument, “Residents have complained” describes the concern; “The council should extend the route” repeats the action. A connecting assumption would be: “The people making the complaints need to travel after the current bus stops, and the extended route would serve their destinations.” That sentence identifies what the proposal relies on.
Keep the assumption tied to the decision in front of you. A proposal about one route does not need to settle every question about public transport. If the assumption becomes too broad, it can hide the specific point that needs examination.
Think of a proposed action as a key offered for a particular lock. The key may be well made, but that does not mean it fits this lock. The question is whether the action suits the problem described.
Check whether the action addresses the stated problem
Look for a practical connection between the problem and the proposed response. A stated need, an announced intention or a sequence of events may explain why someone raised an issue; none alone establishes that the proposed action will deal with it.
Ask what would have to change for the remedy to work. If the concern is that passengers cannot reach a particular destination, a later bus matters only if its route and timing serve that need. If the concern is an unsafe stop, extending the service may leave the underlying problem untouched.
Consider alternatives without assuming that any one is automatically better. A timetable change, a route adjustment or clearer information might address different causes of the same complaint. The argument for a proposal is more useful when it explains why that option fits the problem, rather than merely naming a problem and attaching a preferred action.
What questions expose a weak connection?
What problem is the proposal meant to solve?
State the concern in specific terms, such as missed journeys after the current service ends. If the problem is vague, ask what observable difficulty the action is intended to change.
Who is affected by the problem and the proposed action?
Check whether the people raising the concern are the people the remedy can reach. If they are not, ask whether the proposal is meant for another group or whether a different response is needed.
How would the proposed action change the situation?
Ask for the practical link between the action and the intended result. If that link is missing, the speaker needs to explain the mechanism or narrow the claim.
What plausible case would leave the problem in place?
Imagine the concern remains real but the proposed action does not address its cause. If that situation is plausible, the argument needs to show why it does not apply or consider another remedy.
Use a counterexample to test the proposed response
A useful counterexample keeps the problem in view while changing a condition that matters to the remedy. It does not need to show that the concern is false; it asks whether the recommended action still makes sense when the connecting assumption fails.
Say a councillor argues that residents’ requests justify extending a bus route. Imagine the requests come from people who finish work after the current service ends, but the proposed extension would not reach their workplaces or their homes. The requests still describe a real transport difficulty; the route change simply does not address it. The council would need to explain how the route could be altered to serve those journeys or consider a different response.
Then ask whether the counterexample is a realistic possibility, not merely an imaginable one. If it identifies a likely mismatch, the proposal needs a better fit or a narrower claim. If it relies on an unlikely condition, it may not tell you much about the case being argued.
Tell missing information from a poor fit
Sometimes an argument needs information before anyone can judge whether the proposed action fits. In other cases, the available information already shows that the action does not address the stated problem. Those are different weaknesses.
Suppose nobody has established when the complainants travel. That is missing information: the council needs to clarify whether the requests concern journeys after the current service ends. But if the journeys are late and the proposed route does not serve their destinations, the problem is not merely a lack of information. The action is poorly matched to the need as described.
Make your response specific. Ask for the details needed to assess the fit, or explain which part of the proposed action fails to address the stated problem. This leaves room for a better proposal without pretending that the concern itself has disappeared.
Work through the decision with the details in view
Imagine a residents’ group asks the council to run a later bus. For this invented situation, assume the group says its members finish work after the last service, and the draft proposal adds a later journey on the same route. The question is whether that change serves the journeys that prompted the request.
- Write down the problem: members cannot take the current bus after work. The observable issue is a mismatch between finishing times and the existing timetable.
- Write down the proposed action: add a later journey on the same route. This makes clear what the council is being asked to change.
- State the assumption: a later journey on that route will let the affected members reach their destinations. This is the link that needs support.
- Ask the group whether the route serves those destinations and whether members can reach its stops after work. If the answer is yes, the proposal appears to address the stated difficulty; if not, the council should consider a route adjustment or another option.
- Set the conclusion at the strength the answers allow: if the route serves the journeys, the council has a reason to consider the later service; if it does not, the request supports addressing the transport problem but not this version of the remedy.
The result is not a verdict on whether the residents are right to raise the issue. It is a clearer decision about whether the particular change fits the problem, and what detail would distinguish a workable proposal from a mismatched one.
Choose a conclusion that fits the decision
A proposal can be worth considering without being the only reasonable response. “The complaints give the council a reason to examine a later service” is more limited than “The complaints show that the council must extend this route.” The narrower wording leaves room to compare the proposal with the need it is meant to meet.
Notice verbs such as “supports”, “justifies” and “requires”. They imply different strengths of connection between a concern and an action. Ask whether the argument explains that level of force, or whether the available reasoning supports only a further question or a more limited response.
When you assess an argument, identify the problem, the proposed action and the condition that would make the action suitable. Then ask which practical detail could confirm or challenge that condition. That is the useful missing step between evidence and conclusion: not a formula for winning a dispute, but a way to see whether the remedy follows from the need.
A precise question can keep the discussion productive: “How would this change address the problem people have described?” The answer may strengthen the proposal, reveal a better-fitting option or show what still needs clarification. In public debate, that distinction helps keep attention on the decision rather than allowing agreement about a problem to stand in for agreement about its remedy.


