Who Does What?

A practical logistics guide for you, Rolf, and the crossover RCT

Your Section Rolf's Section Both

What this deck covers

This is the "how do we actually do this" guide. Not research theory — just the practical steps, week by week, for both instructors.

Use to navigate • 10 slides

The Two Classrooms, Side by Side

First, the big picture of how each class runs day-to-day:

YOUR CLASS (Treatment) ROLF'S CLASS (Control) ════════════════════════ ════════════════════════ Students open your web app Rolf lectures with slides, on their phones/laptops. whiteboard, and live coding. Students take notes. You project the app too. You walk through: Rolf walks through: ┌──────────────────────┐ ┌──────────────────────┐ │ Animations │ ← SAME for all │ Slide examples │ │ Interactive exercises│ ← SAME for all │ Whiteboard diagrams │ │ │ │ Live coding │ │ AI Hints button │ ← DIFFERENT │ (no AI anything) │ │ (some students see │ per student! │ │ │ it, some don't) │ │ │ └──────────────────────┘ └──────────────────────┘ │ │ └──────────────┬───────────────────────┘ │ SAME quizzes, assignments, exams

Key point

Your web app's animations and exercises are visible to ALL your students equally. The only thing that differs between students is whether the "AI Hint" button appears when they're doing exercises on their own device.

How the Crossover RCT Works in Your Class

This is the part that matters most. Let's walk through exactly what happens:

BEFORE THE SEMESTER STARTS: ─────────────────────────── Your app randomly assigns each student to Group X or Group Y. (Students don't know which group they're in. They just log in.) DURING EACH TOPIC: ────────────────── Say you're teaching "Binary Search Trees" today. You project the app → Everyone sees the SAME animation of BST insertion. You walk through it → Everyone follows along on their devices. You say "try the exercise" → ┌──────────────────────────────┐ ┌──────────────────────────────┐ │ Alice's phone (Group X) │ │ Bob's phone (Group Y) │ │ │ │ │ │ Exercise: Insert 7 into │ │ Exercise: Insert 7 into │ │ this BST... │ │ this BST... │ │ │ │ │ │ [ Need a hint? ] ← YES │ │ ← NO │ │ │ │ (no hint button shown) │ │ Hint: "Compare 7 to the │ │ │ │ root. Is it larger or │ │ She works through it on │ │ smaller? Go that way." │ │ her own or asks a neighbor │ └──────────────────────────────┘ └──────────────────────────────┘ NEXT TOPIC (e.g., Hash Tables): ──────────────────────────────── Groups SWAP — now Bob gets hints, Alice doesn't. This is the "crossover" part.

What Students Actually Experience

Students don't know about groups. Here's what it feels like from their perspective:

Student's View (Group X, BST Topic)

"I opened the app, did the BST exercise, and there was a hint button. I clicked it and it gave me a nudge about comparing to the root. Helpful!"

Same Student (Group X, Hash Tables Topic)

"I did the hash table exercise. No hint button this time. I worked through it myself and asked my neighbor when I got stuck."

Why students won't notice the pattern

  • Hint buttons feel like a feature, not an experiment
  • Some exercises are harder — "maybe hints are only for hard ones"
  • Students focus on the exercise, not on UI differences
  • They have no way to compare their screen to someone else's

What's the SAME for everyone

  • Your projected screen (animations, demos)
  • The exercises themselves (same problems)
  • Your verbal explanations and teaching
  • Office hours, TAs, textbook access
  • All quizzes, assignments, and exams

What's DIFFERENT (the only variable)

  • Whether the "AI Hint" button appears on their personal device during exercises
  • This alternates by topic — everyone gets hints on ~half the topics

Why this is fair

Every student gets AI hints on exactly half the topics. No one is disadvantaged. The groups just get hints on different topics.

What YOU Do Your Section

1

Before Semester: Set Up the App

Add a group assignment feature: when a student first logs in, the app randomly assigns them to Group X or Y (stored in their profile). Build the per-topic hint toggle so the app checks: if (student.group matches this topic's hint-on group) → show hint button.

2

Week 2-3: Administer Pre-Test + Pre-Survey

Give students the pretest.html web app during class. ~30 minutes. They pick their section, create their anonymous ID, take the quiz, fill out the survey. Data goes to Google Sheets automatically.

3

Every Class: Teach Normally

This is the easy part. You teach using your web app exactly as you already planned. Project the animations, walk through examples, have students do exercises on their devices. You don't need to do anything special — the app handles which students see hints automatically.

4

Throughout: Let the App Log Everything

The app silently logs: hint requests, time on task, exercise completion, group assignment. You just teach. The data collects itself.

5

Week 14-15: Post-Test + Post-Survey + Interviews

Repeat the concept test and survey. Conduct 8-12 interviews with selected students (mix of both groups).

What ROLF Does Rolf's Section

Rolf's job is simple — he teaches his way and helps with shared assessments:

1

Teach Normally

Rolf teaches his section however he usually does — slides, whiteboard, live coding, textbook. No web app, no AI, nothing changes about his teaching. That's the whole point of a control group.

2

Week 2-3: Give Pre-Test + Pre-Survey

Rolf gives the same pretest.html to his students during class. They select "Section B (Prof. Rolf's section)." Same quiz, same survey, same Google Sheet. ~30 min of class time.

3

Throughout: Use the Shared Assessments

Both sections take the same quizzes, assignments, and exams. Rolf helps design these (or reviews yours) to make sure they're fair for both teaching styles. This is the main collaboration point.

4

Week 14-15: Give Post-Test + Post-Survey

Same concept test again, plus the post-survey (which has slightly different wording for his section — asks about "lecture examples" instead of "web app").

Rolf doesn't need to know about Groups X and Y

The crossover RCT happens entirely within YOUR section. Rolf just needs to know: "give the same tests, use the same assessments." The randomization and hint toggling are invisible to him.

How You Collaborate Both

There are exactly 4 things you and Rolf need to coordinate on:

1. Shared Assessments

Design quizzes, assignments, and exams together. Both sections must take identical versions. This is the most important collaboration.

How: One of you drafts, the other reviews. Meet 2-3 times during the semester to align.

2. Pre/Post Tests

Both administer the same pretest.html in weeks 2-3 and the same post-test in weeks 14-15. Data goes to the same Google Sheet.

How: Share the URL. Rolf opens it in class, students do it on their phones.

3. Topic Coverage Alignment

Both sections should cover the same topics in roughly the same order. The comparison only works if students in both sections learn the same material.

How: Share syllabi at semester start. They don't need to be identical — just cover the same major topics.

4. Data Sharing

Both instructors have edit access to the Google Sheet with pre/post test responses. Share assessment scores at semester end for analysis.

How: Google Sheet is shared. Assessment scores can be exported from your LMS.

What you DON'T need to coordinate on

Teaching style, lecture format, homework policies, grading curves, office hours — these can all be different. The study is designed to work despite these differences. The shared assessments are the equalizer.

Week-by-Week: Who Does What

WhenYou DoRolf Does
Before Week 1 Build group assignment + hint toggle in app. Decide which topics are AI-on for Group X vs Y. Nothing
Week 1 Share syllabi. Agree on shared assessment schedule. Share syllabi. Review assessment plan.
Week 2-3 NOW Give pre-test + pre-survey in class (pretest.html) Give same pre-test + pre-survey in class
Weeks 4-13 Teach with web app. App auto-toggles hints per student per topic. Log data. Teach normally (slides, whiteboard, coding). No web app.
~Week 6, 10 Both give same shared quiz/assignment/exam. Compare scores later.
Week 14-15 Give post-test + post-survey (treatment version) Give post-test + post-survey (control version)
Week 16 Conduct 8-12 student interviews Nothing
Summer Analyze data together. Write paper together. Submit to SIGCSE 2027.

How the Hint Toggle Actually Works

The technical implementation in your web app:

STEP 1: SETUP (before semester) ──────────────────────────────── Define the topic schedule and group assignment: topics = [ { name: "Arrays", hintGroup: "X" }, ← Group X gets hints { name: "LinkedLists", hintGroup: "Y" }, ← Group Y gets hints { name: "Stacks", hintGroup: "X" }, ← alternates... { name: "Trees", hintGroup: "Y" }, { name: "HashTables", hintGroup: "X" }, { name: "Graphs", hintGroup: "Y" }, ] STEP 2: STUDENT LOGS IN ──────────────────────── First login → app randomly assigns: student.group = "X" or "Y" (stored in database, never changes) STEP 3: DURING AN EXERCISE ─────────────────────────── App checks: currentTopic.hintGroup === student.group ? → YES: Show "Need a hint?" button → NO: Don't show hint button That's it. Everything else (animations, exercises, content) is identical for every student. STEP 4: LOGGING ──────────────── Every interaction is logged: { student: "anon_id", group: "X", topic: "Trees", hintsAvailable: false, exerciseScore: 85, timeSpent: 240s } { student: "anon_id2", group: "Y", topic: "Trees", hintsAvailable: true, hintsUsed: 2, exerciseScore: 90, timeSpent: 180s }

You don't manage this manually

You configure the topic list and group rules once. After that, the app handles everything automatically. You teach the same way regardless — project the app, walk through examples, say "try the exercise." The app shows or hides the hint button per student behind the scenes.

Common Questions

"What if students compare screens and notice the difference?"

Unlikely — students focus on their own work. But even if they notice, it doesn't invalidate the study. You can mention in the consent form that "app features may vary" as part of the research.

"What if a Group Y student asks a Group X student for hints?"

This is "contamination" and it slightly weakens the effect. But it works against finding a difference, so if you still find one, it's even more convincing. Log hint usage to check.

"Is it fair that some students don't get hints?"

Yes. Every student gets hints on exactly half the topics. And at the end, you can unlock all hints for everyone. This is standard in crossover trials (medical studies do the same thing).

"Does Rolf need to change anything?"

No. Rolf teaches his way. He just gives the same tests and surveys. The crossover RCT is entirely within your section — Rolf doesn't need to know the details.

"What data do I get at the end?"

Three powerful comparisons:
1. Your section vs. Rolf's (overall effect)
2. Group X vs. Y per topic (AI hint effect, causal)
3. Hint users vs. non-users (dose-response)

"What if the results show no difference?"

That's a valid finding! "AI hints did not significantly improve learning" is publishable and valuable. Education research needs null results too.