# CS-12: Actionable assignment feedback

Category: Education & learning
Level: Intermediate
Suggested duration: 3–4 weeks

Original UXCharan practice scenario. Validate assumptions; do not present it as a commissioned client project.

## Problem
A fictional course shares feedback across comments, calls and messages. Explore a review workspace that separates questions, required changes and suggestions, while helping students show what changed in a revision.

## People to learn from
Design students and online mentors

## Core scope
- Submit a version
- interpret feedback
- request another review

## Research questions
- How do students decide what to fix first?
- How do mentors compare revisions?

## Edge cases
- Conflicting comments
- inaccessible file

## Specific artefact
A revision history and feedback taxonomy

## Evaluation question
Can a student identify the priority changes and demonstrate a revision?

## Work to share
Problem and role; anonymised evidence; alternatives and rationale; task flow; prototype; accessibility considerations; testing findings; revisions and honest limitations.

## Request feedback
Share a viewable Figma, document or portfolio link with Saicharan on WhatsApp: https://wa.me/917093809350
Include CS-12, your name, project stage and your main feedback question. Confirm review scope, timing and any fee directly.

## Methods
- Research planning: https://www.gov.uk/service-manual/user-research/plan-user-research-for-your-service
- Research consent: https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research
- Design exploration: https://www.designcouncil.org.uk/resources/the-double-diamond/
- Usability testing: https://www.nngroup.com/articles/usability-testing-101/
- Accessible forms: https://www.w3.org/WAI/tutorials/forms/
- Portfolio storytelling: https://www.nngroup.com/articles/ux-design-portfolios/