Create roadmaps for students

Students need a semester roadmap for the product design course. Create a roadmap document that lists milestones: research due February 12 assigned to cohort A, wireframes due March 8 for everyone, prototype demo April 20 with presentation slots, and final reflection due May 5. Include deliverable descriptions, expected outcomes, and a timeline view so students can see dependencies and handoff dates.

Before I publish the semester roadmap to students, make it approval‑friendly and easy to follow. Put the top three graded milestones up front with their weightings, highlight hard dependencies that, if missed, block the next milestone, and call out any weeks with heavy workload so students can plan team meetings in advance.

A student team missed the prototype demo because their wireframes were late and they didn't realize the demo depended on that deliverable. I’m worried the grade curve and schedule will be disrupted. I don’t know whether students missed an announcement or the roadmap hides dependencies. What likely broke down and what immediate change will prevent this for the next milestone?

Over several semesters our roadmaps get distributed but teams still miss milestones because dependencies aren’t obvious. That causes regrades and schedule drift. What simple change in how we structure or present roadmaps would surface dependencies and pacing clearly, and how do we roll that out to GSI instructors so it sticks?