Last changed on
Sun January 7, 2024 at 4:26 PM CDT
I use she/her pronouns.
I debated in college. I have worked with high school policy debate for five years.
I believe debate is a forum for advocacy. I believe it should be accessible to all audiences. I am not lay, but I prefer styles that cater to lay audiences (big pictures, clear impacts, clear explanations, clear voters, etc.)
-Both teams must share speech docs: forgetting to share will result in docked speaker points, refusal will result in an auto-win to your opponent
-I don't flow or vote on new arguments in rebuttals--responsive evidence to support previously made arguments are okay though. If you intend to split the block, you need to articulate that.
-Ad hominem attacks, offensive rhetoric, and any other forms of abuse/violence will not be tolerated. At a minimum, I will dock speaker points. I reserve the right to end a round early due to excessive inappropriate behavior. No one should ever be personally attacked, bullied, or made to feel like they as a person don't matter. Be professional and respectful. Leave it in the ring.
-I'm fine with moderate-fast speeds. Once you have to go way up in your head voice to spread, you're gonna lose me. Enunciation is key no matter the speed. The clearer you are, the faster you can go for me.
-I could not care less about planks. I view plank complaints and arguments as a time-suck rather than proper clash. Debates that focus on the substantive content of the topic are going to automatically get higher speaker points from me than those that don't.
-Roadmap and signpost. Don't leave me searching my flow to figure out what you are talking about. I like titles, tags, and clear delineation between points.
*Framework is a priori.
I will vote how teams tell me to vote, regardless of my real-life opinions. Give me weighing mechanisms. Give me voters. Give me standards.
If you tell me to weigh the round using impact calculus, I need to know how to weigh impacts (magnitude, timeline, probability, etc.).
All conceded frameworks will stand. All competitive frameworks need to be justified.
*Persuasion is key.
I do not flow jargon. "Extend BlahBlahBlah" should be followed with a brief summary/explanation.
"They dropped BlahBlah" should be followed with an explanation of why that is important and why that is beneficial to you.
I like analytics. I love analytics backed up with a card.
*Counterplans
Sure! If you can solve better, do it. I'm cool with viable perms, too. Win the links and impacts, win the CP/Perm.
*Topicality
Not my favorite, but if there is a strong argument for loss of ground/education, then sure! But you have to make the argument; I won't make it for you. I need clear standards and voters. Answer the "so what?"
If an AFF team reasonably convinces me that either they meet a NEG definition or their counter-interpretation is preferable, I will give it to the AFF. There are few instances where I will award the NEG a T win on predictability/ground if I have seen the AFF before. Making ground claims and then running specific DAs or using specific link scenarios moots your grounds argument for me.
*Kritiks
Sure! Clear alt. Clear world of the aff vs. alt impact calc. Clear links. Clear explanations. Don't assume I am familiar with the literature (remember I prefer lay styles), but don't get caught misconstruing the literature (keep in mind I am experienced).
*Advantages/Disadvantages
I'm not going to vote for time-sucks. Walk me through the links and impacts. Weigh the impacts. If you don't have the time to explain it, you probably shouldn't be running it.
I flow. If you tell me that the other team dropped something and I clearly have it on my flow, you will not win any of your extensions.