Use these optional opportunities to help students carry learning from a completed collaboration into future teamwork, consider what Feedback Forward reveals, and use insights from the experience to inform your teaching.
Help Students Continue Developing What They Carry Forward
Feedback Forward asks students to identify what they have learned about themselves as collaborators and what they want to carry into future team experiences.
As students provide feedback to one another, help them distinguish being affirming from being genuinely supportive. If they have a specific observation that could help a teammate recognize a strength or continue developing, withholding it simply because positive feedback feels easier to give does not serve the teammate's development.
You might make that distinction explicit:
Some learning may transfer quite directly. Other situations may call for students to apply the same principle differently. Still others may introduce collaborative demands they have had little opportunity to practice.
Your disciplinary, professional, or community experience can make those differences concrete.
For example, a student may learn that clearly dividing responsibilities helped their design team follow through. On a later civil engineering project, a new accessibility regulation takes effect after the initial design has been approved. The change affects the site plan, cost estimates, permitting work, and several people's responsibilities. Accountability still matters, but following through now includes recognizing that the original division of work no longer fits and helping the team renegotiate responsibilities and dependencies.
Or consider a student who learned that speaking up earlier helped their team address problems before they grew. Later, they join a neighborhood organization planning a community event. As a new volunteer, they notice that the planned location creates access problems for residents with limited mobility. Raising the concern still matters, but doing so effectively may require understanding who made the decision, what constraints the team is working within, and how a new volunteer can introduce an overlooked issue without assuming they understand the whole situation.
Use a comparable situation from your field or community where the same collaborative principle might transfer directly, need to be enacted differently, or reveal something the person still needs to develop.
No single course project can surface every collaborative capacity students will eventually need. Future experiences may ask them to use what they already know, apply it under different conditions, or develop practices they have not yet had reason to use.
Carry Collaborative Principles Beyond the Activities
The activities in the Collaboration Development Activity Chain provide structured opportunities to practice collaborative principles that students can use even when the formal structures are absent.
How you make that connection depends on the framework experiences your students actually had.
If Students Used the Activity Chain
Help students look beyond the activity formats to recognize the principles they were practicing.
- A Team Charter gave students a structured way to make expectations explicit. A future team may never create one, but students can still help surface expectations about communication, responsibilities, participation, and decision-making.
- A Pulse Check created a planned opportunity to notice how collaboration was functioning. A future team may never complete a survey, but students can still ask whether the way the team is working is actually working and whether anything needs to change.
- Feedback in Progress created a structured opportunity to exchange useful information while there was still time to act. A future team may never schedule peer feedback, but students can still raise useful observations, invite feedback, and make concerns discussable before the work is over. Sometimes supporting another person or the team's work means making a useful observation discussable rather than leaving it unsaid because saying it feels uncomfortable.
You can make the transition from scaffold to principle explicit:
Use examples from your field or community to show what one of these practices looks like when no formal activity is prompting it.
If Feedback Forward Was Used Independently
Work from the collaborative experience students actually had and the principles Feedback Forward asked them to examine: Communication, Collaboration & Professionalism, Accountability & Contribution, and Adaptability & Team Problem-Solving.
Help students consider what effective collaboration looked like in this team and what they could do to help create those conditions in a future one.
A field- or community-specific example can help students see how those principles become practices they can initiate for themselves.
Consider What Feedback Forward Reveals
When you review Feedback Forward, look across what students generated rather than treating peer ratings as the outcome of the activity.
Consider the Full Picture of Collaboration and Learning
How effectively a student collaborated and what the student learned from the collaborative experience are related, but they are not the same outcome.
For example, teammates may consistently report that a student missed agreed deadlines and was difficult to depend on. The student's self-assessment may recognize the same pattern, while their reflection may show what they are learning from the experience and what they want to carry into future work.
The collaboration concern and the student's learning from it may both be visible, but they are not the same outcome and do not serve the same purpose. Use observations about the collaboration to understand what occurred. Use reflection to understand what the student is making of the experience.
The same distinction applies to strengths. Peer feedback and self-assessment may make an effective collaborative practice visible, while reflection may show what the student has learned from recognizing that strength and what they want to carry forward.
Look for learning as deliberately as you look for concerns.
Look Beyond Peer Ratings
Different sources can tell you different things:
- Peer ratings and feedback — What did teammates observe and experience?
- Self-assessment — How does the student understand their own collaboration?
- Reflection — What is the student making of the experience and feedback? What learning are they taking from it?
- Other course or project information — What additional context do your observations, project records, earlier concerns, or team agreements provide?
Use each source for what it can reasonably tell you. Look for where they converge, complement, complicate, or differ.
Consider the usefulness of the feedback itself as well. Predominantly positive feedback is not necessarily superficial, and more critical feedback is not necessarily more informative. Look at what the feedback actually helps make visible about the student's collaboration.
Thoughtful reflection can demonstrate meaningful learning even when the student's collaboration itself was ineffective. A student also does not need to agree with every peer observation to engage thoughtfully with the feedback.
Reflection can therefore reveal learning that is distinct from how effectively the student collaborated. Use reflection to understand what the student is making of the experience, not to substantiate a consequential judgment about the student's project contribution. Feedback Forward gives credit for completing the required reflection; the quality or conclusions of that reflection are not graded.
Peer ratings likewise should not mechanically become grades students assign one another.
If students ask how Feedback Forward relates to grading, you might clarify:
See Grading Guidance for guidance on grading the framework activities and considering project-contribution concerns while keeping peer ratings distinct from student-assigned grades.
Decide When Feedback Forward Requires a Response
Not everything Feedback Forward reveals requires instructor involvement.
When the Learning Remains Student-Owned
Students should ordinarily retain responsibility for:
- interpreting the feedback they receive;
- comparing their own perspective with others';
- deciding whether differences among perspectives are meaningful; and
- determining what they want to carry forward.
A difference between self-assessment and peer feedback does not itself require you to determine which perspective is correct.
If a student asks you to resolve the difference, you might ask:
The student companion resource can support students when the work is primarily interpreting feedback and deciding what to learn from it.
When to Look More Closely
Additional instructor attention may be useful when:
- feedback raises a significant collaboration concern that may benefit from instructor attention;
- information suggests a possible substantial shortfall in a student's project contribution;
- substantially different accounts matter to a decision you are responsible for making; or
- a student needs context or support they cannot reasonably provide for themselves.
Feedback Forward may be the first structured point at which individual experiences become visible, particularly when the activity is used independently.
Start with what the available information can reasonably establish. Consider whether the sources converge, provide different context, or leave something important unresolved. Draw on other course or project information when it is relevant.
If the team used a Team Charter, its current Team Charter and Team Success Commitments can provide a student-created reference point for what the team had actually agreed to. If the team did not use a Team Charter, consider the shared expectations and working practices that developed through the team's experience together, while recognizing that they may not have been explicitly discussed or understood in the same way by everyone.
Because the collaboration has concluded, returning students to the team to “work it out” may no longer be useful or appropriate.
When Direct Instructor Involvement Is Warranted
Use the appropriate course or institutional response when Feedback Forward reveals harmful or inappropriate feedback, discrimination, retaliation, exclusion or inequitable treatment, or another matter students should not reasonably be expected to resolve themselves.
A developmental observation does not require instructor involvement simply because it may be difficult to hear. Distinguish discomfort from harmful or inappropriate feedback by considering the observation, how it is expressed, and the broader context.
Look for Patterns Across the Completed Experience
Patterns may become visible through student ratings and feedback, self-assessments and reflections, questions students bring forward, normal course interaction, project records, or implementation technology.
Look for strengths and effective practices as deliberately as you look for difficulties.
Also look at the usefulness of the feedback, not only its tone. Patterns may reveal feedback that is overly harsh or disrespectful, but they can also reveal the opposite: feedback that is consistently positive or general without giving teammates much they can use.
Predominantly positive feedback is not necessarily weak, and every student does not need criticism. Differences between ratings and written feedback can be especially revealing. If ratings show meaningful variation while comments remain uniformly affirmative, students may need help distinguishing supportive feedback from feedback that leaves potentially useful observations unsaid.
Turn Patterns Into Instructional Opportunities
A pattern across students or teams can give you something worth reinforcing, clarifying, or connecting to authentic practice.
For example, suppose students across several community-planning teams describe one teammate's habit of summarizing decisions and unresolved questions before meetings end as particularly helpful. You might connect that strength to public or community work in which participants have different responsibilities and may leave the same meeting with different assumptions about what happens next.
Or suppose several teams report that concerns were not raised until late in the project. A film-production instructor might connect that pattern to a production setting where waiting to flag an issue with equipment, scheduling, continuity, or a location can make the eventual problem substantially harder and more expensive to address.
Use your knowledge of the field and the students' work to make the consequence or value of the pattern visible.
Use Patterns to Inform the Next Learning Experience
Patterns can also tell you something about the project and the conditions in which students were collaborating.
Ask:
What was happening in the course or project when this pattern appeared?
Then consider whether there is something worth:
- Preserving — a condition or structure that appears to support effective collaboration.
- Preparing for — an authentic or productive challenge students could be better prepared to navigate.
- Making visible — a project transition or collaborative demand students may not recognize until they encounter it.
- Adjusting — a course or project condition that may be interfering with the intended learning.
- Watching — a pattern worth noticing again before deciding whether a change is warranted.
For example, several teams may struggle when a project moves from relatively independent tasks into a phase where everyone's work becomes highly interdependent. If that interdependence is an important part of the learning design, removing it may not improve the experience. The next time you teach the course, you might instead make the transition more visible and give teams an opportunity to reconsider how they communicate dependencies and changes.
Patterns can also show you what is working well and worth preserving.
The opportunity is not to diagnose what went wrong with the course. It is to use information from students' completed collaborative experiences to consider whether anything could strengthen the next teaching and learning experience.
Look for Patterns That Help You Ask Better Questions
Consider:
- Within a team: Do several sources point toward a similar strength or challenge?
- Across teams: Does the same collaborative experience recur across teams?
- Across Collaboration Criteria: Does one criterion stand out?
- Self and peers: Where do perspectives converge or meaningfully differ?
- Reflection and project context: What are students learning, and what was happening when the pattern appeared?
Treat patterns as places to ask better questions, not conclusions on their own.
If You Are Using FeedbackFruits
FeedbackFruits can make these signals easier to find without requiring you to manually piece together every individual review.
The built activity uses FeedbackFruits' Detect Outliers feature to automatically flag certain rating patterns that may warrant a closer look, such as substantial differences between self- and peer ratings, unusually high or low ratings, possible conflicts between individual team members, or possible rating divisions within a team. These indicators can direct your attention to students or situations worth examining without requiring you to find those patterns manually in the analytics.
Treat an outlier as a signal to look more closely, not a conclusion. Read it alongside the underlying ratings, written feedback, self-assessment, and relevant course or project context. Use reflection separately to understand what the student is learning from the experience, not as evidence for a consequential judgment about project contribution.
Because Feedback Forward looks back on a completed collaboration, consider whether the available information warrants a response and what the experience might inform in future teaching.
Other valuable patterns will not necessarily generate an outlier. Depending on your implementation, useful views may also include:
- student and team progress;
- average peer and self-assessment ratings;
- ratings by Collaboration Criteria;
- written feedback comments;
- individual given and received reviews;
- time spent on reviews;
- recurring terms or themes through keyword filtering; and
- downloadable activity data.
FeedbackFruits can make signals easier to find. Your knowledge of the students, project, and course context is what helps determine what they may mean and whether anything is worth doing with them.
FeedbackFruits guides: