Module 2: Clashes and prioritization by Enting Lee - YouTube

Channel: unknown

[4]
Hi I'm Enting and the Korea WUDC team has asked me to film a short video on
[10]
clashes and prioritization. I want to start by explaining what I think a clash
[15]
is and why we should judge debates based on clashes. A clash is essentially an
[20]
issue that multiple teams are trying to contest and win. As an example, if we take
[25]
the motion "This House would ban all drugs", one clash might be the necessity
[30]
of a ban, another clash might be its effectiveness. As mentioned in the
[34]
introduction video, BP debating is judged comparatively. The analysis provided by
[40]
teams cannot be evaluated in a vacuum. Arguments need to be judged against each other.
[45]
I'm sure you've all heard the saying
[47]
"apples and oranges" so it is often extremely difficult to compare two
[52]
arguments about completely different issues. Sorting arguments into clashes
[57]
helps provide a structured framework to first compare arguments about the same
[61]
issue without bringing in confounding factors like which issue is more
[65]
important. This thus makes it easier to judge the debate. Additionally, without
[70]
clashes judges might risk missing team contributions and important points which
[75]
would then also make judging more difficult. So how do you identify and
[79]
sort arguments into clashes? Well ideally, teams will do this for you. They will
[85]
save something along the lines of "these are the main clashes of the round" and
[88]
then they'll analyze what each team managed to prove within the clash.
[93]
But teams don't always do this. Most of the time, they just make arguments. The judge
[98]
should then identify the broad themes that the arguments are coalescing around
[103]
that would generally be at least two or three in every debate. A rule of thumb
[107]
might be to look for claims that are being substantively disputed by teams
[112]
across a large portion of the debate. Judging clashes doesn't mean counting up
[117]
arguments within each clash or counting the absolute number of clashes won.
[122]
To evaluate who won a particular clash judges should look closely at the
[127]
analysis provided by teams, including implicit and preemptive material.
[132]
They should evaluate the logical links, mechanisms, examples and
[137]
explanations of impacts provided to see if the argument was proven to a greater
[141]
degree than the opposing teams argument. In addition judges should consider the
[146]
extent to which arguments are refuted. Rebuttal will be covered in significantly
[151]
more detail in the next video but broadly speaking it can do two things.
[155]
First, a rebuttal to an argument can mitigate the scale and scope of an
[160]
arguments impact or provide reasons to believe it is untrue or leads to harmful
[165]
outcomes. A Rebuttal can also offer competing claims to an argument which
[171]
may weaken be persuasiveness of the original argument and strengthen the
[175]
case of the opposing team. The judge should then determine to what extent the
[180]
rebuttal has succeeded in minimizing the original argument, considering of course
[185]
preemptive argumentative material that interacts with this rebuttal, as well as
[190]
any direct responses from the original team to the rebuttal.
[194]
Crucially, an argument being responded to does not mean that it is defeated.
[200]
The response may have been weak or may have only tackled one portion of the argument.
[204]
Judges should therefore evaluate how much of the analysis is left standing
[209]
after the rebuttal has been made and after responses to the rebuttal have been
[213]
given. Since British parliamentary is a four team format, there are two things to
[218]
note here. The first is that judges, when making direct comparisons between two
[223]
teams should not bring in contributions from a third team. For example, when deciding
[230]
between Opening Government and Opening Opposition, a judge shouldn't say well
[235]
but CG respondent to OO by giving this rebuttal, so OO's case is now weaker
[241]
which means OG wins over them. No, when you are comparing two teams you should
[247]
keep the comparison to those issues brought up by those two teams, because it
[251]
is extremely unfair if one team ends up being defeated by two other teams solely
[257]
on the basis of a single other team's response, so really try to be very
[261]
specific when you are comparing clashes. Try not to, in fact, don't bring in
[266]
arguments from a third team when you are doing direct head-to-head comparison.
[270]
Second, when evaluating two teams on the same bench, consider how significant each
[276]
team's contributions were. You would consider for instance, whether the one
[280]
teams arguments provided key logical links without which the other teams
[284]
arguments do not apply or whether one team has provided convincing reasons for
[290]
their argument being more significant. Most debates will revolve around more
[294]
than one clash which may result in a situation where different teams have won
[299]
different clashes. Again this does not necessarily mean that a team that has
[304]
won more clashes wins by default. We do not judge by counting clashes. After all
[311]
one team may have won the most important clash in the round while the other team
[315]
could have won multiple clashes there were more trivial and less contributors
[319]
to the round as a whole. For example, even if a team narrowly proves that a
[325]
particular outcome is likely, another team may be able to successfully show
[329]
that this outcome while likely is actually not going to be particularly
[333]
harmful, thus taken as a whole even if the team has one big clash on the
[339]
probability of something happening what they have ultimately managed to do is
[344]
just to show that it's very likely that a not very bad thing will happen, so
[350]
taken against each other you probably would say that they haven't made a huge
[354]
impact on the round by the end of this clash. So judges should first determine
[359]
who won each clash and then evaluate the impact and the significance of each
[365]
clash in comparison with each other. In determining which clash is more
[369]
meaningful judges should judge based on metrics provided by the teams. So the
[375]
following is going to be a ranked list of steps to follow in deciding how to
[380]
prioritize issues that are brought up within the debate. As far as possible you
[385]
must judge the debate using metrics provided by the teams. If you are very
[390]
very lucky all the teams in the round will have explicitly agreed on a metric
[394]
for what is important in the round. For instance, perhaps all teams have
[398]
explicitly agreed that the most important thing in the round is to
[402]
maximize the number of lives saved and if this is the case then the judge
[406]
should consider which team best achieves this goal. If this does not happen
[410]
meaning teams don't give you an explicit metric for the round then judges should
[415]
derive the criteria from what all teams implicitly consider to be imported.
[421]
So even if teams do not explicitly agree on a criteria they may still implicitly
[426]
agree, for instance if all the analysis by teams is about maximizing the number
[431]
of lives saved that is the criteria of the round even if no one says out loud
[436]
that this is the goal. If no team agrees on which clash is the most important
[441]
either implicitly or explicitly and all teams assert differently then judges
[446]
should consider which team has most successfully proven their metric. Teams
[452]
should give plausible reasons to believe that what they say is important. They
[456]
should not just be asserting that this is the most important thing in the round
[460]
without providing some form of explanation for why this is true. Most
[465]
persuasive reasons are not too divorced from reality. They will tend to mirror
[469]
what we see in the real world. So if a team says that a clash is important, you
[474]
should be giving a number of reasons for it and most of those reasons should be
[478]
because of what the real world will look like. If none of these apply, meaning
[484]
there is no explicit agreement between, teams there is no implicit agreement
[488]
between teams and in teams argumentation and there is no team that has
[493]
successfully proven a metric to be true then as a last resort judges should
[499]
prioritize clashes based on what the average reasonable person would take to
[503]
be important. This does not mean making a random judgement this instead means that
[510]
you should weigh clashes based on your intuitions about what the real world
[515]
will be like and in many cases good judges will be in agreement on what
[519]
those intuitions should be. This will be covered in greater detail in the
[524]
workshop on Goldilocks interventions so please watch that video as well. Last
[528]
there are some situations where arguments are claimed by teams to be off
[532]
clash. A team claiming that an argument is off clash doesn't automatically
[537]
win, just by making that assertion. They do need to justify why they believe the
[542]
other teams argument is irrelevant to the clash or to the round. They cannot
[546]
just assert that this is the case. If they provide justifications for that
[551]
claim then these justifications should be evaluated in the manner discussed
[555]
earlier, both in this video and in the introductory video which discusses how
[559]
to evaluate analysis and consider various kinds of material. So this has
[564]
been the introduction on how to identify, evaluate and weigh clashes. Thank you for
[569]
your attention and good luck.