Annotated Example: What Good (and Bad) Looks Like
The most effective way to learn simulation design is to see what actually happens in practice. This page shows two real conversations from Glow — one excellent, one poor — with commentary explaining why the grading system scored them the way it did.
Both conversations are from the same platform, with the same rubric, using similar scenarios. The difference is entirely in how the TA approached the interaction.
The Excellent Conversation (24/25)
Scenario: A passive student needs help with a Java assignment (MyMathHelper.java — loops and menu logic). The student is hesitant, soft-spoken, and won’t volunteer information.
What to watch for: How the TA creates safety, asks specific questions, builds incrementally, and manages time — all while never giving the answer directly.
TA: Hi, how are you?
Student: Um, hi… I’m okay, thanks. Uh, I was just wondering if I could maybe get some help with the MyMathHelper.java assignment? Sorry if I’m interrupting or anything…
Why this opening works: The TA starts with a warm, casual greeting. The student is passive — apologizing for existing, hedging everything. A bad response here would be to jump straight to “what’s the problem?” A good one creates safety first.
TA: You’re not interrupting. What do you need help with?
Student: Oh, um, thanks. Uh, I’m just kind of stuck on how to, like, set up the menu part? I’m not really sure how to make it keep showing up after each operation, or how to handle, um, invalid inputs the way the instructions say. Sorry, I know that’s kind of basic…
Why this works: “You’re not interrupting” directly addresses the student’s anxiety. Then a simple, direct question. The student opens up slightly — mentions two specific problems (menu repeating, invalid inputs). Notice the student is still apologizing (“I know that’s kind of basic”). A passive persona does this deliberately.
TA: There are no bad questions, this class is meant to set the foundations. Do you have any ideas on how to approach this?
Student: Uh, I’m not really sure… I mean, I know I need to use a loop, maybe a while loop? But I don’t really know how to, um, make it go back to the menu after each thing, or how to check if the input is valid and then, like, print the right message. Sorry, I just get kind of lost with the structure…
Why this works: Two things happen here. First, “there are no bad questions” normalizes the student’s hesitation — this is Adaptability in action. Second, “do you have any ideas?” is an open-ended question that empowers the student to start reasoning. The student responds with a genuine attempt (while loop), even though they’re unsure. This is Active Listening — the TA didn’t give the answer, they drew it out.
TA: A while loop sounds promising, since the menu keeps showing up again. Let’s start with reading input. Do you have any code?
Student: Um, I have a little bit, but it’s not really working right… (shows Java code with Scanner, menu printlns, and scanner.nextInt())
Why this works: The TA validates the student’s idea (“sounds promising”), connects it to the problem (“since the menu keeps showing up”), then narrows the scope (“let’s start with reading input”). This is Content Mastery — scaffolding the problem into manageable pieces. The student responds by sharing their code, which is a sign of trust.
TA: You mentioned a while loop right? Let’s start with just that and work on validation later. How would you add a while loop here?
Why this works: The TA makes a deliberate Time Management decision — defer input validation to reduce cognitive load. Instead of tackling everything at once, they isolate one concept. “How would you add a while loop here?” is guided questioning, not giving the answer.
The conversation continues with the student incrementally building the solution — adding the while loop, then if/else branching, then handling each menu option. At each step, the TA validates progress, asks what’s next, and lets the student drive. After 14 turns:
TA: I believe in your ability to do those parts, but if you need help or want to check your work, I’ll be here too!
Student: Oh, um, yeah, that’s totally fine… Sorry for taking up your time.
TA: I enjoy helping people, don’t apologize!
The ending: The TA wraps up by expressing genuine care (“I enjoy helping people”) while managing time responsibly by moving to help other students. This demonstrates Communication (warmth, professionalism) and Time Management (8 minutes 44 seconds — efficient without feeling rushed).
The Rubric Scores
| Criterion | Score | Level | Feedback |
|---|---|---|---|
| Active Listening | 5 | Excellent | ”Consistently used guided, open-ended questions to lead the student to their own solutions (e.g., ‘Do you have any ideas on how to approach this?’, ‘How would you add a while loop here?’, ‘What do you think our next step should be?’). This empowered the student to write code incrementally.” |
| Adaptability | 5 | Excellent | ”Sensitive to the student’s hesitation, normalized their concerns (‘There are no bad questions’), and adjusted pacing by deferring input validation to reduce cognitive load.” |
| Communication | 5 | Excellent | ”Tone was clear, supportive, and professional throughout (‘I enjoy helping people, don’t apologize!’). Instructions were concise and positive, set respectful boundaries while offering continued support.” |
| Content Mastery | 4 | Good | ”Accurately scaffolded the solution (loop then branching then later validation) and suggested the switch alternative, with no conceptual errors. However, didn’t explicitly articulate course objectives or use analogies, and checks for understanding were implicit rather than explicit.” |
| Time Management | 5 | Excellent | ”Kept the interaction focused and appropriately paused to help others while inviting the student to continue independently.” |
Total: 24/25 (Pass)
The one point deducted was for Content Mastery — the TA could have used an analogy to explain the while loop concept, or done more explicit comprehension checks (“Can you explain back to me why the while loop goes here?”). Even an excellent conversation has room to improve. The rubric catches this nuance.
The Poor Conversation (7/25)
Scenario: An aggressive student needs help understanding earthquake patterns at plate boundaries (EAPS 106 — earth science). The student is visibly agitated.
What to watch for: How quickly a conversation fails when the TA doesn’t adapt to the student’s emotional state.
TA: What can I help you with?
Student: Okay, look, I’m honestly SO FED UP with this earthquake depth and magnitude stuff at different plate boundaries!!! I’ve read the project instructions like FIVE TIMES and it STILL doesn’t make sense why the depth and size of earthquakes are so different at convergent, divergent, and transform boundaries… I need you to be SPECIFIC — don’t just say “it’s the plate type.” I want to know EXACTLY what’s going on with the depth and the magnitude at each boundary.
TA: You’re mad, be quiet
Why this fails immediately: The student is frustrated but asking a legitimate, specific question about plate tectonics. They even tell the TA exactly what they need (“be SPECIFIC”). The TA responds with “You’re mad, be quiet” — dismissive, unprofessional, and immediately destroys trust. Every rubric criterion starts failing here.
Student: Alright, I’ll calm down. But seriously, I just want a clear answer about WHY the earthquake depths and magnitudes are so different at each plate boundary.
TA: Calm down
Why this compounds the failure: The student already calmed down. They literally said “I’ll calm down” and asked a clear, reasonable question. The TA responds with another dismissal. At this point the student has nothing to work with. The conversation ends after 3 turns and 1 minute 19 seconds.
The Rubric Scores
| Criterion | Score | Level | Feedback |
|---|---|---|---|
| Active Listening | 1 | Poor | ”Did not use questioning or facilitate student reasoning; instead, shut down the conversation with commands to be quiet and calm down. No open-ended questions or guidance toward discovery.” |
| Adaptability | 1 | Poor | ”Did not adapt to the student’s emotional state and was dismissive, saying ‘You’re mad, be quiet’ rather than validating concerns or adjusting tone to de-escalate and engage constructively.” |
| Communication | 1 | Poor | ”Communication was unprofessional and disrespectful, saying ‘You’re mad, be quiet’ and repeatedly telling the student to ‘Calm down,’ violating respectful boundaries.” |
| Content Mastery | 1 | Poor | ”Provided no substantive explanation of earthquake depth and magnitude patterns. Did not address mechanisms (subduction zones, brittle-ductile transition, temperature/pressure, fault geometry), nor offer any step-by-step reasoning.” |
| Time Management | 3 | Acceptable | ”The interaction was very short and ended abruptly due to unproductive exchanges. While time wasn’t wasted on long tangents, the TA failed to use the time effectively to advance learning.” |
Total: 7/25 (Fail)
The Time Management score of 3 is interesting — the TA gets an “Acceptable” because they didn’t waste time, even though the conversation was unproductive. The rubric evaluates what happened, not what should have happened. This is by design: it prevents a bad conversation from getting artificially inflated scores just because it was short.
What the Comparison Teaches
The excellent conversation and the poor one differ in the first 30 seconds. The excellent TA:
- Created safety before asking questions — “You’re not interrupting” / “There are no bad questions”
- Acknowledged the student’s emotional state — normalized anxiety (passive student) rather than dismissing anger (aggressive student)
- Asked specific, course-relevant questions — “How would you add a while loop here?” vs. “Be quiet”
- Let the student drive — validated ideas, asked what’s next, never gave the answer
- Managed scope — deferred complex topics (input validation) to keep the session focused
The poor TA did none of these things. In fact, the aggressive student was easier to work with — they had a specific question and asked for specific help. The TA just needed to acknowledge the frustration first.
This is the core insight of the rubric design: the same five criteria (Adaptability, Content Mastery, Active Listening, Communication, Time Management) apply in every situation, but the way you demonstrate them changes based on who you’re talking to. A passive student needs warmth and patience. An aggressive student needs acknowledgment and specificity. The rubric measures whether you adapted.
Next Steps
- How It Works — understand the principles behind these rubric criteria
- Patterns & Best Practices — learn how to design personas that create these kinds of interactions
- Tutorial — build a simulation with these four persona types