Feedback and Cooperative Learning
What this concept is
Feedback compares an artifact with a purpose or criterion and helps decide a next action. Cooperation needs an agreement about roles, decisions and what to do when someone is unavailable. It is not merely dividing pages among people.
Why it matters here
Future engineering work depends on reviewing claims, explaining tradeoffs and revising work with others. You can practice these behaviors on small study artifacts before a large team project.
Concrete example
Unhelpful feedback: “This explanation is confusing.” Actionable feedback: “The example says to move the file, but then asks the learner to reopen the old location. Explain that moving changes the location and update the next step.”
The author can reply: “I will fix the path and test the steps on a new practice file.” If a reviewer instead says “every copy protects against device loss,” the author should not accept it merely to be agreeable. Show the case of two copies on one failed device and narrow the claim.
Common confusion / misconception
Kind feedback can still be precise. Critical feedback need not judge character. Accepting every suggestion is not collaboration; rejecting every suggestion is not independence. A simulated reviewer cannot establish that a real person understood your work.
How to use it
Agree on the artifact, intended reader, review criterion, roles and a response time that both people can meet. Review one high-impact issue first. Separate observations (“the example lacks an empty case”) from interpretations (“readers may assume it requires data”) and proposed actions.
When receiving feedback, restate the concern, ask for missing evidence, then accept, adapt or decline with a reason. Preserve the before/after difference. If disagreement remains, identify a small example or criterion that could resolve it. Rotate explaining and questioning roles so neither person only watches.
Check yourself
A partner misses a session. Is the correct response to do all their work silently? No. Clarify availability, reduce or reassign scope and record the new agreement. Avoid assigning motive without evidence.
Mini drill or application
Review a 150-word explanation using correctness, clarity and audience fit. Give one specific improvement. Revise after reviewing it yourself or with a consenting peer. Label solo role-play explicitly; real peer review remains a separate opportunity.
Read this only if stuck
Waterloo's group-work guidance discusses structuring cooperative tasks. Our small role agreement is an adaptation for self-study, not evidence of demonstrated team performance.