Course Proposal

As part of my retrospective engagement with Navigating Disruption, I analyzed and discussed the original course proposal—a document created before any content was built. It outlines intended learning outcomes, target audiences, modular structure, and the course’s role in a larger series. Together with my LXD mentor, I reviewed the official course proposal as a way to explore the strategic planning that precedes development. Analyzing it gave me insight into how design theory gets translated into institutional documents, how goals are framed for multiple stakeholders, and how structural decisions are scaffolded in writing before becoming learning experiences.

Core Competencies

  • Using Research and Evaluation Skills

    Reading the proposal through an evaluative lens helped me think more critically about how pedagogical goals are articulated for multiple audiences—learners, stakeholders, and institutional partners. I reflected on how backward design principles were embedded in the proposal’s structure, and how learning outcomes, sequencing, and audience framing were already influencing decisions before development began. This retrospective analysis sharpened my ability to trace the connection between theoretical frameworks and practical decisions, even when working from documentation rather than finished content. It showed me how evaluation can begin at the earliest stages of design—not only through data, but through close reading and critical interpretation of the planning process itself.

Before this experience, I hadn’t fully appreciated how much a course proposal can reveal about the thinking behind a learning experience. Analyzing the Navigating Disruption proposal gave me the opportunity to evaluate design decisions at their earliest stage—before any content, media, or assessments were created. It pushed me to read closely and interpret how goals were framed, how audiences were defined, and how structure was imagined, all within the constraints of an institutional setting. This process showed me that design documentation can be a powerful site of insight—not just for understanding what a course is, but for anticipating how it might grow and adapt over time.