Last changed on
Mon October 21, 2024 at 4:14 AM PDT
I coach speech and debate at Davis HS.
------
1. I don't want to be on email chains. If there's a dispute about what evidence says, I'll ask to look at a laptop.
2. I flow, but if you communicate clearly, I'll be more likely to look for a way to vote for your side first. Big picture overviews, even in speeches early in the round, can be extremely helpful here.
3. Speed-reading (spreading) is embarrassing and exclusionary. <230 wpm, non-negotiable. Slow down further for taglines, plantexts, and important quotes from the evidence. I invite school board members and new coaches to watch rounds: they should be impressed, not confused, offended, or scared.
4. I don't flow cross unless you explicitly tell me to write something down by looking at me and saying "write that down".
5. I don't like teams that cheat. If your opponents are misconstruing evidence and you want to stake the round on it, a useful phrase to know is: "I am making a formal evidence challenge under NSDA rule 7.3.C., for distortion of evidence. We are stopping the round and staking the round's outcome on the result of this formal evidence violation."
6. Clash is essential. Make arguments at the first opportunity available to you. In policy, this means that I want to see all the neg positions established in the 1NC. In PF, I want you to cover both sides of the flow in every speech from 2nd rebuttal onward.
7. I only vote on arguments that are mentioned in each side's final speech of the round.
8. If you start your speech by saying "3-2-1", I will say "Blastoff"! "3-2-1" is not necessary!
9. I am inclined to give bonus speaker points if I see an effort to "read me" as a judge, even if you read me wrong. Cite my paradigm if you need to. Learning to figure out your audience is a crucial life skill. On a related note: if you use the secret word 'barnacles' in your speech, I will give you and your partner 0.3 extra speaker points, since it means you read my philosophy thoroughly.
10. Kritik arguments: Don't do them in PF. Approach with caution in other events. I have no K background. Go even more slowly and explain thoroughly, in terms accessible to a layperson. Explain either how the K proves/disproves the resolution, or offer an extremely compelling alternative ROTB. I have no shame in writing "I didn't understand half the words in the K so I didn't vote for it."
11. Tips for communicating effectively:
11a. Number your refutations: "my first response is..."
11b. Use cross-ex effectively -- the goal is to get concessions from your opponent that can be used in speeches.
------
PF:
No off-time roadmaps in PF. I will start the clock if you start roadmapping.
Don't steal prep time. If a card is requested, teams have 60 seconds to find the card and add it to the file sharing mechanism of the round -- anything beyond that comes out of the prep time of the team that can't find their own evidence. If evidence can't be found, there needs to be an argument made in a speech to drop it (eg. "Drop their argument because they could not share the supporting evidence: we were not given a fair chance to review and dispute its claims.").
If both teams agree to it before the round, and the tournament doesn't explicitly disallow it, I am fine with waiving Grand Cross and granting both teams an additional minute of prep time.
Plans and fiat are educational; I have an extremely loose interpretation of PF's "advocacy" and I will effectively never vote down a team for presenting a "plan" in Public Forum, unless it's extremely niche.
I am very likely not the judge you want if you're running a non-canonical PF strategy, like a "kritik".
I don't give weight to any argument labeled as an "overview". Overviews are heuristic explanations to help me make sense of the round.
------
POLICY/PARLIAMENTARY:
Policymaker paradigm.
You're welcome to run non-traditional positions (K's included)IF you keep them to a conversational pace and explain why it means I vote for you. Theory/K's should be impacted more than just saying "voter for fairness and education".
Closed cross-x: one person per team speaking!
I like smart counterplans that discuss technical details.
------
LD:
My default is to vote based on the "truth" of the resolution, but you can propose alternative frameworks.
Philosophical "evidence" means very little to me. A professor from Stanford making a specific analytical claim is functionally the same as you making that argument directly.
I'm bad at flowing authors and try to get the concepts down in as much detail as possible instead. For philosophical arguments, I generally prefer clearly explained logic over hastily-read cards. However, evidence related to quantitative things should be cited because those studies are highly dependent on precision/accuracy and are backed up empirically.