# data[].attributes.headline
There is something positive from a mistake.

# data[].attributes.subject
There is something positive from a mistake.

# data[].attributes.headline
Seeing an instructor oversight and an apology

# data[].attributes.subject
Seeing an instructor oversight and an apology

# data[].attributes.body
Michele learned how it's okay to revise what you think. It's unclear how much the other students experienced because this interaction did not directly engage them.

# data[].attributes.body
Michelle heard things she did correct (venn diagram) and incorrect (definition of rhombus)

# data[].attributes.headline
Michelle got clarification on her definition, but also got praise/acknowledgement for appealing to a definition and correctly placing it using that definition.

# data[].attributes.subject
Michelle got clarification on her definition, but also got praise/acknowledgement for appealing to a definition and correctly placing it using that definition.

# data[].attributes.body
I love that Nina puts some of the onus on herself--"I should" have given you the definition, here it is now, to normalize her mistake but also to share that she's not perfect either.

# data[].attributes.body
While she's made aware of her confusion about the definition, she also sees the instructor take some responsibility for clearly communicating the definition.

# data[].attributes.headline
Its ok to make "mistakes" - you always do something right

# data[].attributes.subject
Its ok to make "mistakes" - you always do something right

# data[].attributes.headline
Positive... Student is allowed express her thinking without holding back.

# data[].attributes.subject
Positive... Student is allowed express her thinking without holding back.

# data[].attributes.headline
Ask a student to follow up on her questions or offer their own answer. But do not confirm or reject her answer

# data[].attributes.subject
Ask a student to follow up on her questions or offer their own answer. But do not confirm or reject her answer

# data[].attributes.headline
she knows mathematical definitions are made by humans

# data[].attributes.subject
she knows mathematical definitions are made by humans

# data[].attributes.headline
Ask another student to revoice next or ask Michelle a question?

# data[].attributes.subject
Ask another student to revoice next or ask Michelle a question?

# data[].attributes.body
She definitely is referencing a definition (perhaps incorrectly). This is good. I think it's hard to judge what to do next without seeing her comfort level in the class.

# data[].attributes.headline
she's thinking about the definition of a trapezoid with a lot of nuance (but not the definition of a rhombus)

# data[].attributes.subject
she's thinking about the definition of a trapezoid with a lot of nuance (but not the definition of a rhombus)

# data[].attributes.body
She's using a different definition (for a trapezoid). She's open to questioning the specifics of that definition.

My first instinct is to either say that this is not the definition of a rhombus, or run her statement by other students to get their thoughts (perhaps someone will supply a different definition)

# data[].attributes.headline
She's using what she thinks is the definition of a rhombus to classify this shape. She knows how to use the diagram. She is asking good questions about "does a pair of parallel lines mean exactly 1, or at least 1?" I might say "Hmm, I'm not sure about this definition. Does someone else want to share what they think a rhombus is?"

# data[].attributes.subject
She's using what she thinks is the definition of a rhombus to classify this shape. She knows how to use the diagram. She is asking good questions about "does a pair of parallel lines mean exactly 1, or at least 1?" I might say "Hmm, I'm not sure about this definition. Does someone else want to share what they think a rhombus is?"

# data[].attributes.headline
She knows what definitions mean and that details matter (exactly one versus at least one)

# data[].attributes.subject
She knows what definitions mean and that details matter (exactly one versus at least one)

# data[].attributes.headline
Should we be sensitive to using "should" or "would" when asking a question?

# data[].attributes.subject
Should we be sensitive to using "should" or "would" when asking a question?

# data[].attributes.body
I'd be temped to ask why, but maybe would also wait and see what the rest of the class thinks, or if they ask for clarification.

# data[].attributes.headline
I would ask her to explain her choice.  Why do you think it goes there?

# data[].attributes.subject
I would ask her to explain her choice.  Why do you think it goes there?

# data[].attributes.headline
I would ask her why she would put it there. I'd like to get at her reasoning.    Or perhaps ask another student to explain?   

# data[].attributes.subject
I would ask her why she would put it there. I'd like to get at her reasoning.    Or perhaps ask another student to explain?   

# data[].attributes.body
Follow up with "And why would it go there"? As of yet, I don't have an idea of what Michele's thinking. It seems important to make this question seem like a natural part of the conversation, rather than an indicator that "something wrong has happened".

# data[].attributes.body
I think I would ask her to justify her answer. like, "Okay, so you'd put it in the middle. Can you explain why you would choose that?" because it's not clear to me why she wants to do that, and maybe she'll figure it out on her own while she's answering.