Specializations as Navigation

Responding to the Complexity of Immersive Practice

Executive Summary

Michael Golembewski’s A Field Guide to Immersive Practice offers a useful provocation for the development of specializations in an interdisciplinary immersive media program. The guide presents immersive practice through multiple lenses and multiple forms of representation. A reader can encounter the field as an alphabetical index, a branching hierarchy, or a constellation of relationships. The content can be approached through disciplines, roles, methods, and other overlapping categories. The result is not a single career ladder. It is an ecology.

That ecology may contain thousands of plausible career paths, role combinations, technical configurations, creative identities, and professional contexts. No undergraduate curriculum can represent all of them, and no specialization committee should attempt to do so. The task is not to construct a comprehensive directory of jobs. It is to create navigational structures that help students enter the field, recognize possible directions, develop meaningful depth, connect their learning across courses, and produce evidence that they are prepared to continue learning after graduation.

The central claim of this response is therefore:

A specialization should function as a map, not a box.

A box defines what belongs inside and what must remain outside. A map establishes orientation, shows relationships, identifies routes, and helps a traveler make decisions without pretending that only one journey is possible. This distinction changes how specializations should be designed, staffed, communicated, assessed, and revised.

It also makes clear that the Specializations Committee cannot work independently. Its decisions rely on the work of the Coding, Portfolio, Labs, IMDM101, and Vision committees. Each committee controls part of the environment through which a specialization becomes real. Course sequences alone cannot carry the full responsibility.

Purpose of This Response

The field guide is valuable because it renders visible something that academic structures often conceal. Immersive media is not one discipline with a stable set of professional roles. It is an intersection of creative, technical, research, production, cultural, and experiential practices. A single project may require knowledge associated with game design, sound, animation, programming, physical computing, performance, cinematography, interaction design, accessibility, ethics, production management, user research, exhibition design, and many other domains.

Universities must translate this complexity into a manageable curriculum. Courses need titles, prerequisites, instructors, credit hours, learning outcomes, rooms, equipment, and enrollment caps. Degree requirements must be understandable enough for students to follow. Specializations must be concise enough to appear in advising materials and durable enough to remain operational across several academic years.

The danger is that administrative clarity can be mistaken for an accurate description of the field. A clean sequence of four courses may be necessary, but it does not mean the corresponding professional pathway is equally clean. The specialization is an educational interface with a complex field, not a miniature reproduction of that field.

This response uses the field guide as a conceptual model for explaining the scope of the Specializations Committee’s task to faculty, program leadership, and interested administrators. It does not propose that the program replicate the guide or adopt its taxonomy wholesale. Instead, it considers what the guide reveals about the kind of curricular reasoning that specialization design requires.

What the Field Guide Makes Visible

Immersive Practice Is Multidimensional

The field guide can be viewed as an index, a set of branches, or a constellation. Each view reveals something different. An index supports discovery and definition. Branches show grouping, inheritance, and increasing specificity. A constellation emphasizes proximity, connection, density, and the fact that one practice may relate to many others.

This is more than an interface choice. It exposes a fundamental problem in curriculum design. The same field can be organized in several valid ways, and each organization produces a different understanding of what matters.

A course catalog usually resembles an index. It tells students what exists. A prerequisite structure resembles branches. It tells students what should come before what. Professional practice more closely resembles a constellation. It is organized through relationships among people, tools, methods, responsibilities, institutions, and projects.

Specialization design must work across all three views.

• The index view asks what courses, competencies, resources, and opportunities currently exist.
• The branch view asks how students progress from introduction to practice, depth, and independent application.
• The constellation view asks how learning in one area connects to other practices, projects, communities, and career possibilities.

A specialization built only from the index becomes a list of electives. A specialization built only from branches becomes an inflexible pipeline. A specialization built only as a constellation may be intellectually rich but impossible to administer or explain. The committee must construct a usable relationship among all three.

Roles, Disciplines, and Methods Do Not Align Neatly

Academic programs often use the same vocabulary for several different things. A specialization may be named after a discipline, such as game design. It may be named after a technology, such as artificial intelligence. It may imply an industry, such as entertainment or cultural heritage. It may point toward a role, such as technical artist or interaction designer. It may also represent a method, such as creative coding or practice-led research.

These categories overlap, but they are not interchangeable. Game design is a field of practice, while a game designer is a role. Artificial intelligence is a technical and research domain that can support many roles and industries. Creative coding may be a method, an artistic identity, a technical competency, or a professional differentiator. Immersive media itself may describe a field, a set of formats, a family of experiences, or an institutional umbrella.

The specialization committee must therefore decide what each proposed specialization is intended to organize. Is it primarily organizing knowledge, technical capacity, creative practice, professional identity, application context, or some combination? Without that clarity, the same specialization title can produce very different expectations among students, faculty, administrators, and employers.

The Field Is Combinatorial

The apparent number of career paths expands rapidly because roles, practices, tools, industries, and project types combine in many ways. A student interested in sound may work in games, virtual production, installation art, museum experiences, accessibility, data sonification, performance, film, research, or spatial computing. A student interested in AI may become a developer, artist, interaction designer, researcher, technical producer, critic, data practitioner, or tool builder. A game-oriented student may specialize in systems, narrative, audio, art, animation, production, level design, technical design, user research, accessibility, or experimental practice.

These are not merely different job titles. They often require different mixtures of foundation, depth, collaboration, infrastructure, and evidence. The curriculum cannot create a unique sequence for every combination. It must identify capacities that remain useful across combinations while preserving enough choice for students to develop a coherent direction.

This is why the committee’s task is more complex than selecting four courses and attaching a label. Every course choice privileges some routes, closes others, creates resource requirements, and communicates a theory about what the field is.

The Field Changes Faster Than Degree Structures

Professional titles, platforms, tools, and production methods can change within a single student’s time in the program. A specialization approved today may not be fully experienced by students until several years later. If it is defined primarily through current software or current job titles, it may become dated before the first cohort graduates.

Durable specializations should therefore be organized around transferable capacities as well as recognizable practices. Tools matter, particularly when students need professional fluency, but tools should be situated within larger abilities: prototyping, systems thinking, spatial reasoning, interaction design, collaborative production, iterative testing, critical interpretation, documentation, and ethical judgment.

The goal is not to make a specialization timeless. Nothing in an emerging field is timeless. The goal is to make it revisable without making it incoherent.

A Specialization Is a Promise

A specialization makes several promises at once.

To students, it promises that a coherent route exists and that following it will produce meaningful development. To faculty, it promises that courses will relate to one another rather than operate as isolated offerings. To administrators, it promises that the program can deliver the pathway with available staffing, facilities, scheduling, and advising. To external audiences, it promises that the title corresponds to recognizable knowledge and practice. To employers and community partners, it suggests that graduates can bring certain capacities into collaborative work.

These promises create obligations beyond course approval. A specialization needs:

• an intelligible entry point;
• an appropriate technical and conceptual foundation;
• opportunities for increasing depth;
• more than one route through the area;
• access to necessary facilities, equipment, software, and expertise;
• project experiences in which competencies are integrated;
• connections to adjacent practices;
• advising language that students and faculty can use consistently;
• portfolio evidence that makes the learning visible; and
• a process for review as the field and program change.

If any of these elements is missing, the specialization may exist administratively without functioning educationally.

What Specializations Should and Should Not Do

Specializations Should Provide Orientation

Students need a manageable answer to the question, “Where might I begin?” A good specialization identifies a family of practices, explains why they belong together, and helps students understand the kinds of questions, projects, and professional contexts associated with them.

Orientation is especially important in IMDM101. Students should encounter the breadth of immersive media early enough to make later choices deliberately. Exposure to VR, games, interactive installations, immersive cinema, spatial sound, performance, creative coding, research, and field experiences can help students recognize that the program contains multiple legitimate forms of practice.

Specializations Should Establish Depth

Breadth alone does not prepare students for advanced work. A specialization should identify what students must practice repeatedly, what increasing independence looks like, and where introductory exposure becomes durable capacity. Depth may involve advanced technical work, sustained creative inquiry, production leadership, research, or a combination.

Depth should not be confused with isolation. The strongest specialists can communicate across roles and understand how their work participates in a larger system.

Specializations Should Preserve Bridges

Students should be able to connect one specialization to another. A game design student may need spatial audio, AI, animation, user research, or physical computing. An AI student may need visual design, ethics, data storytelling, interaction design, or game systems. A student working in installation may depend on coding, fabrication, sound, performance, and exhibition practices.

Bridges can take the form of recommended electives, shared studios, cross-listed projects, common technical foundations, open labs, community events, or Capstone collaborations. These bridges are not secondary features. They reflect the actual structure of immersive practice.

Specializations Should Support Navigation, Not Prediction

A program cannot predict every role a student will occupy after graduation. Many graduates will work in positions that do not yet have stable titles, combine responsibilities that appear separate in the curriculum, or move between industries over time.

The specialization should therefore help students explain what they know, recognize adjacent opportunities, and continue learning. It should not imply that completing a prescribed sequence guarantees a particular job.

Specializations Should Not Attempt Exhaustive Coverage

If the field contains thousands of plausible paths, completeness is impossible. Attempting it would produce either an unmanageable degree or a superficial catalog of disconnected topics.

The committee should make principled exclusions. It should be able to explain what the program can support well, what it can introduce but not develop deeply, what can be reached through electives or external partnerships, and what currently lies outside the program’s capacity.

Honest boundaries are stronger than inflated promises.

The Specializations Committee as an Integrating Committee

The Specializations Committee occupies a distinctive position. It does not control all the components required to deliver a specialization, but it must assemble them into coherent student pathways. Its work intersects with every other committee’s charge.

This intersection means that specialization work should not be conducted as a closed sequence of internal decisions followed by a final announcement. Each major design decision should create a communication obligation.

For example, if the committee proposes an AI specialization requiring model development, data work, and creative application, it must communicate with Coding about foundations and prerequisites, with Labs about compute and software access, with Portfolio about documenting process and provenance, with IMDM101 about introductory exposure, and with Vision about the career and industry claims being made. The specialization is the visible structure, but its feasibility is distributed across the program.

A More Useful Model for Specialization Design

Rather than beginning with course lists, the committee can design each specialization through eight connected layers.

1. Field Orientation

What area of practice does the specialization help students navigate? What does the name include, and what does it not include? How does it relate to immersive media as a whole?

2. Shared Foundations

What should every IMD student know before entering this pathway? Foundations may include computational reasoning, visual and sonic literacy, interaction, research, collaboration, ethics, spatial thinking, and documentation.

3. Specialization Depth

Which competencies require sustained practice? What distinguishes introductory familiarity from advanced capability? Which experiences must be repeated across more than one course?

4. Pathway Variations

What legitimate variations exist inside the specialization? Game Design might include systems, narrative, technical design, game audio, level design, or experimental games. AI might include creative AI, intelligent interaction, data practice, technical development, critical study, or applied research. The program does not need to formalize every variation, but it should make room for more than one identity within the pathway.

5. Bridges and Dependencies

Which other specializations, courses, labs, and communities does this pathway depend on? Where can students cross into adjacent practices without losing coherence?

6. Integrative Experiences

Where do students combine knowledge in projects larger than a single technique? This may occur in studios, research experiences, internships, collaborative productions, exhibitions, or Capstone.

7. Evidence and Translation

What would demonstrate meaningful development to faculty, peers, employers, graduate programs, and community partners? Evidence may include prototypes, finished works, process documentation, technical breakdowns, research findings, reflective writing, public presentations, and collaborative credits.

8. Renewal and Governance

Who reviews the pathway, how often, and using what evidence? A specialization should have a revision process that considers student experience, enrollment, staffing, facilities, project outcomes, alumni trajectories, and changes in professional practice.

Community as Navigational Infrastructure

Formal course sequences cannot carry the entire complexity of specialization. Students also need settings in which they can encounter practices that are not yet part of their own coursework, observe more advanced work, locate collaborators, and revise their sense of direction.

Open labs, playtesting sessions, public critiques, demonstrations, research salons, visiting practitioners, exhibitions, student organizations, shared repositories, and cross-cohort project reviews can function as navigational infrastructure. They allow students to experience the field as a constellation rather than only as a set of branches.

This community layer is important because specialization is partly an academic sequence and partly the formation of an identity. Students become game designers, creative technologists, researchers, sound artists, technical artists, or AI practitioners through participation, recognition, and sustained practice as well as through credit accumulation.

Community also protects the curriculum from excessive rigidity. A student cannot take a course in every adjacent field, but they can encounter another practice through a collaborator, workshop, critique, or shared project. These encounters do not replace instruction. They help the formal curriculum remain connected to the wider ecology it is attempting to represent.

A Recommended Sequence of Work

The complexity of the task does not require paralysis. It requires an order of operations that keeps decisions visible and allows other committees to respond before pathways harden.

Phase 1: Establish Shared Principles

The Specializations and Vision committees should begin by defining what specializations are expected to accomplish. This includes their relationship to program identity, career exploration, interdisciplinary practice, and student choice.

Phase 2: Map Current Capacity

The committee should inventory existing courses, faculty expertise, laboratories, equipment, software, partnerships, recurring projects, and community practices. This is the index view of the program.

Phase 3: Map Progression

Working with Coding, IMDM101, Portfolio, and relevant faculty, the committee should identify where competencies are introduced, practiced, advanced, integrated, and demonstrated. This is the branch view.

Phase 4: Map Relationships

The committee should identify shared courses, bridges, dependencies, cross-specialization projects, and resource intersections. This is the constellation view.

Phase 5: Develop and Stress-Test Cases

Proposed structures should be tested through concrete student journeys. Game Design and AI provide useful cases because each contains many possible roles, levels of technical intensity, and connections to other practices. The committee should test whether different students can enter, develop depth, change direction, access required resources, and produce credible evidence of learning.

Phase 6: Share Draft Maps Before Final Decisions

Drafts should be circulated as pathway maps, dependency notes, unresolved questions, and resource implications rather than as nearly finished proposals. This gives other committees a meaningful opportunity to shape the work.

Phase 7: Use the Faculty Retreat for Deliberation

The faculty retreat should not begin with approval of completed specializations. It should present the field’s complexity, the proposed design principles, the current capacity map, and a small number of pathway cases. Faculty can then identify omissions, hidden dependencies, unrealistic promises, and opportunities for collaboration.

Phase 8: Establish a Review Cycle

Once adopted, specializations should be reviewed on a regular cycle. The question should not be only whether the required courses still exist. The review should ask whether students can enter the pathway, progress through it, access the necessary resources, integrate their learning, build strong portfolios, and connect the specialization to plausible futures.

Questions That Should Accompany Every Proposal

Before recommending a specialization, the committee should be able to answer the following questions:

1. What does this specialization help students understand, make, investigate, or do?
2. What range of practices and professional directions does the title reasonably include?
3. What shared foundations does it require?
4. Where does sustained depth occur?
5. What variations can students pursue within it?
6. What facilities, software, equipment, staffing, and scheduling does it require?
7. What other pathways and committees does it depend on?
8. How will students encounter the pathway before committing to it?
9. What projects or experiences integrate the learning?
10. What portfolio evidence should students leave with?
11. How can students move into, out of, or across the pathway?
12. How will the program know when the specialization needs revision?

These questions do not eliminate complexity. They make it discussable.

Implications for Program Leadership

The complexity revealed by the field guide should not be interpreted as evidence that specializations are impossible. It demonstrates why they require coordinated program-level design.

Leadership can support the work by recognizing several realities:

• Specialization design is not only a curricular paperwork task. It includes advising, staffing, scheduling, facilities, portfolio development, community formation, and external communication.
• A pathway may be academically persuasive but operationally unviable without lab access, instructional support, or predictable course rotation.
• A specialization title creates expectations that must be matched by student experience.
• Interdisciplinary pathways require shared ownership. No single faculty member or committee can sustain them alone.
• Revision is a feature, not a failure. A living field requires a curriculum capable of learning.

The program should therefore evaluate specialization proposals not only by counting required credits, but by examining whether the supporting system is coherent and sustainable.

A Concise Administrative Framing

The following language may be useful when introducing the committee’s work:

Immersive media contains thousands of plausible combinations of disciplines, roles, methods, technologies, industries, and professional contexts. Our goal is not to build a separate curricular track for every possible destination. Our goal is to create a small number of legible, rigorous, and permeable pathways that give students orientation, depth, mobility, and evidence of achievement. Each specialization must function as part of a larger program ecology, supported by shared foundations, laboratories, advising, portfolio development, community experiences, and ongoing external review.

Conclusion

A Field Guide to Immersive Practice is powerful because it does not reduce the field to one authoritative hierarchy. It allows the same terrain to be encountered as an index, a set of branches, and a constellation. That multiplicity offers an appropriate model for specialization work.

Students need an index so they can see what exists. They need branches so they can progress. They need constellations so they can understand relationships, recognize hybrid possibilities, and navigate a field that will continue to change.

The Specializations Committee’s responsibility is not to tame the entire field into a fixed set of boxes. It is to design reliable maps through complexity. Those maps should provide enough structure for students to move with purpose and enough permeability for them to discover destinations the curriculum could not have predicted.

That work is necessarily collaborative, visible, and iterative. It belongs at the intersection of curriculum, community, infrastructure, professional identity, and institutional capacity. Its complexity is not evidence that the committee’s charge is unclear. It is evidence that the charge matters.

Reference

Golembewski, M. (2026). A field guide to immersive practice [Interactive web resource]. MWG Design & Research. https://mwgdesignresearch.com/field-guide/

Note: The field guide identifies itself as an early public alpha based on the creator’s accumulated project notes and practice. It presents the field through multiple lenses and three principal views: Index, Branches, and Constellation. The present response treats the guide as a generative model for curricular reasoning rather than as a complete or definitive taxonomy.