o Make it good, interesting o Make it another speech o Organize into CX trees Opening question, x answer leads to y question o Never CX about something you’re about to kick Make both partners get on the same page o Use closed-end questions yes/no o Ask specific questions Have specific ev in front of you when referencing it – don’t make them search for it Give context to specific questions o Be assertive – but not a dick “thank you I got it” “next question” Act like you learned something, move on Get judge on same page o Pit of doom Make a trap for the other team into your arguments Be specific not just “how are you unique” Make one arg to thread other args Set up solvency takeout to give i/l to CP o Make CX part of your strategy Block possible generic questions o Answering CX questions Don’t have to answer questions predicated off things not in the 1AC Don’t give links based on things you don’t specify in the 1AC Write plan well but don’t say anything in CX o Court cases Statutory v. constitutional law – congress can just pass it Statutory – congress can revise the law Congressional intent a bad standard – congress can interpret it any way o Iraq timetable CP to establish strict withdrawal, but condition withdrawal timeline o Aff: Have adv. Intrinsic to plan Have a purpose for everything in the plan text Make links to adv distinct Make i/l distinct o CX = CPs • • • Yay dugong malthus