Shared Language for a Coherent Course Sequence
Faculty Working Draft
Prepared September 2026
Purpose
IMD courses are part of a larger student journey. Students should progressively build an identity, body of work, and area of expertise across the curriculum rather than experiencing each course as an independent sequence of assignments.
Some of that continuity can be improved without creating new courses or standardizing every section. Clear, consistent syllabus language can help students understand:
- where a course sits within the program;
- what prior knowledge and experience they are expected to bring;
- what new level of work the course asks them to reach;
- what materials, skills, and projects they should carry forward; and
- when previous work may be extended, remixed, or recontextualized.
This guide provides shared language that faculty may adapt for individual courses. It is intended to improve curricular legibility while preserving instructor autonomy.
The Minimum Continuity Standard
Every IMD syllabus should answer four questions clearly:
- Where does this course sit in the curriculum?
- What should students bring into the course?
- What will students leave the course able to do?
- What work should students preserve or carry forward?
These answers do not need to become a new assignment or a long syllabus section. In most cases, a short course-position statement, a project-continuity policy, and a final-project handoff requirement are sufficient.
1. Recommended Syllabus Section: This Course in the IMD Curriculum
Faculty may adapt the following language:
### This Course in the IMD Curriculum This course is part of a larger progression through the Immersive Media Design curriculum. It builds on prior experience with [incoming skills, concepts, or courses] and develops greater depth in [course competencies]. By the end of the course, students should have work, documentation, and experience that can support future study in [later courses, Capstone, portfolio development, specialization, or professional practice]. Students should preserve their project files, source materials, documentation, reflections, and feedback from this course. These materials may become the foundation for later development, even when the original project itself is not continued.
This statement makes the course's role visible without promising that all students will follow an identical path.
2. Recommended Syllabus Section: Prior Learning
Prerequisites identify courses students must complete. They do not always explain what students are expected to remember or be able to do. Each syllabus should name a small number of incoming expectations in plain language.
Template
### Prior Learning This course assumes that students have prior experience with [two to five specific skills, concepts, tools, or practices]. Students will revisit these abilities, but the course will not begin from zero. Early activities will help students identify areas that may require review or additional support.
Example
This course assumes that students can document a creative process, participate in critique, manage basic digital project files, and contribute to collaborative production. Students will continue developing these abilities through larger, more complex, and more independent work.
The goal is not to list every topic taught in a prerequisite. The goal is to identify the knowledge the current course will actively build upon.
3. Recommended Syllabus Section: Project Continuity
Students should know that new learning does not always require a completely new project. They should also understand that submitting unchanged work from another course is not acceptable.
Shared Project-Continuity Policy
### Project Continuity and Prior Work Students may propose extending, remixing, recontextualizing, or rebuilding work begun in another course or outside the classroom when doing so supports the learning goals of this course. Continuing a project does not mean resubmitting the same work. The new submission must demonstrate substantial new learning, development, and authorship appropriate to this course. Students using prior work must identify what already existed at the beginning of the course, describe the new questions or goals being pursued, and document the work completed during the current semester. Continued projects are subject to instructor approval and must meet all current assignment requirements.
Short Version
Prior work may serve as a starting point, but not as a finished submission. Any continued project must demonstrate substantial new learning and clearly document what was added, changed, reconsidered, or rebuilt in this course.
This language supports continuity while protecting academic integrity and preserving the distinct learning goals of each course.
4. Recommended Syllabus Section: What Students Carry Forward
Every course should identify a small set of materials students are expected to preserve. These materials can be drawn from existing assignments rather than added as separate work.
Template
### Course Handoff Materials By the end of the semester, students will organize and preserve the following materials for possible use in later courses, portfolio development, Capstone planning, or professional presentation: - [project files, code repository, assets, or working prototype] - [project description, artist statement, design rationale, or research summary] - [images, video, audio, diagrams, or other documentation] - [critique notes, testing results, or revision history] - [reflection identifying strengths, limitations, and possible next steps]
The phrase course handoff materials is useful because it signals that the end of one course may be the beginning of another.
5. Shared Competency Language
Faculty may use the following progression to clarify the level at which a course addresses a competency:
| Level | Syllabus Language |
|---|---|
| Introduced | Students encounter foundational concepts, tools, vocabulary, or methods. |
| Practiced | Students apply the competency repeatedly with guidance and feedback. |
| Advanced | Students work with increasing independence, complexity, integration, or specialization. |
| Demonstrated | Students synthesize and publicly or professionally demonstrate the competency through substantial work. |
Suggested Outcome Format
This course practices collaborative production and interaction design, advances project documentation and technical integration, and provides opportunities to demonstrate an individually selected area of depth.
Faculty do not need to label every course outcome. Identifying two to four central competencies is enough to help students see the progression.
6. Suggested Language for the Shared IMDM Sequence
The following statements may be adapted for the relevant syllabus. They are intentionally concise and do not prescribe specific assignments or technologies.
IMDM101: Introduction to Immersive Media
IMDM101 introduces the collaborative, creative, technical, and critical practices that recur throughout the IMD curriculum. Students begin working across physical and digital media, learn to describe and document an immersive-media project, and gain experience contributing to a shared production process. Work from this course may provide early portfolio material and a foundation for later study in computational media and collaborative studios.
Suggested handoff materials: selected project documentation, a short reflection on individual contributions, source files where appropriate, and a list of technical or creative interests the student would like to pursue further.
IMDM127 or Introductory Computing Preparation
This course introduces programming as a creative and problem-solving practice. Students should preserve code, output, documentation, and reflections that demonstrate how computational ideas produce visual, auditory, or interactive results. These materials will support later work in IMDM227 and other courses involving computational media.
Suggested handoff materials: organized source code, representative output, a short README, and a reflection identifying concepts the student can use independently.
IMDM150: Digital Media Theory and Culture
IMDM150 provides the critical and cultural vocabulary students will use to interpret immersive-media technologies and creative work throughout the program. Students should carry forward relevant readings, research questions, and analytical frameworks so that later projects are informed by context rather than treated as technical exercises alone.
Suggested handoff materials: selected writing, an annotated source list, key concepts, and a research question that could inform future creative work.
IMDM227: Introduction to Computational Media
IMDM227 builds on introductory creative and technical experience by developing programming for visual, auditory, tactile, and interactive media. Students are expected to move beyond following examples toward designing computational systems of their own. The course prepares students to integrate code, media, interfaces, and hardware in later collaborative and project-based work.
Suggested handoff materials: working code or repository, setup instructions, media assets, technical documentation, representative images or video, and a reflection on possible extensions.
IMDM290: Collaborative Studio I
IMDM290 is the first major collaborative production course in the shared IMD sequence. It builds on prior experience with computation, digital-media production, design, and critique. Students practice combining different forms of expertise within a team, managing shared assets, and developing a concept through iterative production. The course prepares students for more sustained, complex, and experiential work in IMDM390 and related advanced courses.
Suggested handoff materials: project archive, team roles and credits, asset inventory, production timeline, critique and testing notes, final documentation, and an individual continuation memo.
IMDM327: Computational Virtual Reality
IMDM327 advances the technical study of virtual and augmented reality systems. Students integrate programming, 3D content, tracking, rendering, spatial audio, and user interaction in increasingly independent work. The course provides technical depth that students may carry into collaborative studios, specialized projects, and Senior Capstone.
Suggested handoff materials: working build and source repository, setup and dependency notes, interaction diagrams, representative documentation, testing results, and a technical reflection identifying systems the student can apply independently.
IMDM350: Advanced Digital Media Theory
IMDM350 advances the critical and contextual study of digital culture, creative technology, game culture, networks, AR/VR, artificial intelligence, and related social and ethical questions. Students should use the course to develop research questions and analytical positions that can inform later creative practice, specialization, and Capstone work.
Suggested handoff materials: substantial writing or research, annotated sources, a concise statement of critical interests, and one proposal for translating a theoretical question into creative or practice-based inquiry.
IMDM390: Collaborative Studio II
IMDM390 advances the collaborative, technical, conceptual, and production practices developed earlier in the curriculum. Students move from small-scale sketches toward sustained experiential work, with greater expectations for research, independent decision-making, integration, documentation, and public presentation. The course prepares students for advanced project work, including Senior Capstone, by asking them to define an area of depth and evaluate which ideas, methods, or projects merit further development.
Suggested handoff materials: complete project archive, research summary, production plan, testing and critique record, exhibition-quality documentation, individual role reflection, and a Capstone or future-development statement.
IMDM490: Senior Capstone I
IMDM490 is the research, design, prototyping, and production-planning phase of Senior Capstone. Students draw on prior coursework, projects, and areas of expertise to develop a substantial immersive-media project. An earlier project may serve as a seed, but Capstone must substantially transform, extend, or recontextualize that work. Students are expected to enter with evidence of prior practice and leave with a viable project, tested prototype, documented production process, and realistic plan for completion.
Suggested handoff materials: approved proposal, research and precedent review, prototype, production schedule, team or individual agreement, technical plan, resource and facilities plan, risk assessment, budget where appropriate, documentation plan, and exhibition goals.
IMDM491: Senior Capstone II
IMDM491 continues the work approved and developed in IMDM490. Students refine, complete, exhibit, document, and promote a substantial immersive-media project. The course asks students to demonstrate an integrated creative and technical practice, respond to critique and public context, and translate the completed project into durable portfolio and professional materials.
Suggested handoff materials: completed project and archive, exhibition documentation, portfolio case study, final credits, technical or installation guide, promotional materials, and a reflective account of the project's development and future possibilities.
7. A Common End-of-Course Continuity Prompt
The following reflection can be added to an existing final project, critique, or course evaluation:
### Continuity Reflection 1. What knowledge, process, technique, or area of practice did you develop most substantially in this course? 2. Which part of your work is worth preserving or developing further? 3. If you continued this project, what would need to change rather than simply grow larger? 4. What feedback, evidence, or testing should guide its next stage? 5. Which future course, facility, collaborator, or area of specialization could help you take the next step? 6. What files and documentation would another person, or your future self, need in order to resume the work?
This prompt encourages students to treat project completion as both an endpoint and a decision point.
8. Making Specialization Visible in Any Course
Specialization does not need to begin with a formal concentration. Faculty can help students recognize emerging depth by naming how a course connects to areas of practice.
Suggested Language
This course may contribute to several areas of practice within IMD, including [examples]. Students are encouraged to identify which aspects of the course connect to their developing interests and to document work that demonstrates increasing depth in those areas.
Possible areas include programming and creative coding, game design, XR and spatial computing, interaction design, physical computing, 3D art and animation, technical art, sound and spatial audio, AI-mediated creative practice, collaborative production, and critical research.
This statement should be descriptive rather than restrictive. A student may combine areas, change direction, or use the course to discover that a particular path is not a good fit.
9. Facilities and Equipment Language
When a course uses a specialized facility, the syllabus should identify the level of experience students are expected to gain.
Template
This course provides [orientation / guided practice / independent use / advanced application] with [facility, equipment, or production environment]. By the end of the course, students should be able to [specific action or level of independence]. Students should document this experience as part of their project record.
This language helps distinguish simple exposure from meaningful curricular proficiency.
10. Language to Avoid or Clarify
Some familiar phrases can obscure the relationship among courses unless they are made more specific.
| Avoid or Clarify | More Useful Language |
|---|---|
| “No prior experience is necessary” in an upper-level course | Name the expected transferable skills, even if a particular tool is new. |
| “Students will create a portfolio-quality project” | Identify the required documentation, refinement, audience, and presentation standard. |
| “Students may continue previous work” | State what new learning, transformation, and documentation are required. |
| “This course prepares students for Capstone” | Identify the artifacts, skills, decisions, or level of independence students should carry into Capstone. |
| “Students will use program facilities” | Identify which facilities, the expected level of use, and the evidence students will retain. |
| “Final project” | When appropriate, use “current stage,” “public version,” or “course-complete version” to distinguish course completion from the end of a project's life. |
11. Faculty Adoption Levels
Minimum Adoption
Add three items to the syllabus:
- A This Course in the IMD Curriculum paragraph.
- The shared Project Continuity and Prior Work policy.
- A short list of Course Handoff Materials.
Standard Adoption
In addition to the minimum:
- Identify the course's central competencies as introduced, practiced, advanced, or demonstrated.
- Add the common Continuity Reflection to the final project or critique.
- Tell students which later courses, practices, or specializations may build on the work.
Full Alignment
In addition to the standard:
- Coordinate incoming expectations and outgoing artifacts with faculty teaching adjacent courses.
- Review sample student work together to compare expectations.
- Confirm that final documentation from one course can serve as usable starting evidence in the next.
- Identify unnecessary repetition, missing preparation, and abrupt jumps in complexity.
12. Faculty Checklist
Before finalizing a syllabus, confirm that it:
- [ ] explains where the course sits in the IMD curriculum;
- [ ] identifies a manageable set of incoming expectations;
- [ ] names the competencies the course introduces, practices, advances, or demonstrates;
- [ ] explains whether and how students may develop prior work;
- [ ] distinguishes continued development from resubmission;
- [ ] identifies the project files and documentation students should preserve;
- [ ] connects the course to possible later courses, Capstone, portfolios, or specializations;
- [ ] specifies any meaningful facility or equipment experience;
- [ ] asks students to reflect on possible next steps; and
- [ ] avoids describing every project as a fresh start or a terminal endpoint.
13. What Syllabus Language Can and Cannot Do
Shared language can make the curriculum more legible, establish consistent expectations, authorize thoughtful project continuation, and help students preserve evidence of their growth. It can also reveal where faculty believe continuity exists and where those beliefs differ.
Language alone cannot resolve scheduling conflicts, prerequisite structures, uneven access to electives, staffing limits, facility bottlenecks, or major gaps in course content. It should be treated as an immediate, low-cost intervention and as a way to generate evidence for later curricular decisions.
The central shift is simple:
A course should not only describe what students will do during the semester. It should also explain what they are arriving with and what they will carry forward.