Playwise

Project brief
Project timeline
Aug 2024-May 2025
Project type/ Client
learning management system / UMD College of Information

Why We Built Playwise:

Playwise is a learning platform designed for graduate-level courses that follow the Read- Watch-Play( RWP) pedagogy(the study and practice of teaching). Unlike traditional Learning management system platforms focused on grades and rigid deadlines, Playwise encourages flexible, student-driven learning through exploration, reflection, and play

It was inspired by Dr. Caro Williams-Pierce’s question:“What if a platform was designed to explicitly support a pedagogy that uses the power of play for learning, with a flexible structure that easily incorporates new technologies?”

The Goal:
The client challenged us to design a learning platform that fully supports the Read–Watch–Play (RWP) pedagogy not just in theory, but in practice.The goal was to move beyond traditional LMS tools and create an experience that felt more intuitive, playful, and flexible for both students and instructors. The platform needed to support modular learning paths, assignment sequencing, interactive feedback, and clear visibility across the course journey.
What i learned
User testing
Co-design
Project
management
Building Design system
Team members
Yabing
Samita
Samarth
Ananya
The Challenge

Existing LMS platforms weren’t designed for flexible pedagogies like RWP. Instructors worked around rigid systems, while students faced disconnected tasks and unclear feedback. We set out to create a platform that supports sequenced, playful learning for both sides without adding complexity.

How We Built It: Step-by-Step Project Timeline

I was the lead designer throughout the project, responsible for both the user experience and user interface design. My work included synthesizing insights from affinity mapping, creating user journey maps, and leading ideation sessions. I designed and tested mid-fidelity prototypes, iterated on the mobile experience based on user feedback, and played a key role in defining the visual direction of the platform. While we began mobile-first, I also led the design of the web version, focusing on the instructor experience and adapting flows for a larger interface

01: Research & Discovery
This section explores how we built Playwise, from user research and ideation to testing and iteration. Grounded in real feedback, every design decision aimed to solve genuine needs for both students and instructors.
1.1
Understanding the Pedagogy ( Teaching Method)

What we learned:
RWP (Read · Watch · Play) supports flexible, student-driven learning focused on experimentation, community, and personal learning paths.

How we learned it:
Literature review + project proposal docs from the client.

1.2
Finding Gaps in Current LMSs

What we learned:
Most LMS platforms lack support for creative, iterative "Play" tasks and flexible planning flows needed for RWP-style teaching.

How we learned it:
Competitor study (Canvas, Moodle, etc.) + contextual inquiry with instructors using ELMS Canvas.

1.6: Extensive, explorative ideation.

Conceptualizing Playwise

What we made:
Sketches, wireframes, ideas explaining features.Mobile screens, layouts and user flows.

How we made it:
Brainstorming Quick, non-constrained ideation sessions using the crazy-8s method to generate ideas in and out of the screens.
Co-designing with PIs
2 co-PIs of the RWP project pitched in their ideas to help guide the instructor’s side of the platform.

1.7 User Testing

Fixing what wasn’t quite right.

What we learned:
Students appreciated interactive features like live classes and chat, but struggled with unclear labels and dense layouts.
Instructors found the task flows intuitive for RWP, but needed better navigation, structure, and UX copy clarity.

How we learnt it:
Usability Testing

5 participants for student-side.5 participants for instructor-side.
02 From Insight to Interface
This section showcases the prototype and key interaction flows demonstrating how Playwise supports the Read–Watch–Play model for both students and instructors.

Why Students Loved This: Calendar-First Home View

Our mobile prototype opens on a calendar-first dashboard, designed to ease “what’s next?” anxiety. In usability testing, students strongly preferred this layout over digging into each course for deadlines.A playful, color-coded design system makes it easy to toggle between Calendar and List modes, while the Read / Watch / Play cards scale based on point value helping students instantly spot high-impact tasks in their week.

Assignment Flow - Connected Learning Modules

The platform allows instructors to build intentional assignment sequences, like Watch → Read → Play or Read →Watch → Play, so tasks feel like steps in a cohesive learning journey rather than isolated checkboxes. Each assignment card shows where it fits in the sequence, helping students understand the purpose behind each activity. This structure improves motivation and context retention, as earlier tasks (like a reading or image review) lead naturally into reflections, projects, or interactive submissions.

Feedback That Feels Like a Conversation

Instructors can leave highlighted annotations directly on student submissions, whether it's a written response or an image-based task. Students can reply in-line, turning feedback into a two-way conversation.This approach keeps feedback clear and contextual across all assignment types Read, Watch, and Play, promoting deeper understanding and engagement.

Built for Builders: The Instructor Side

Next, we explore the web-first experience for instructors, designed to help them shape every step of the student journey.

Creating with Context: Instructor Module Builder

Early user research revealed a disconnect between instructor and student views—what instructors built often looked different to students. To solve this, we designed for transparency: instructors see exactly what students will. While creating a module, they also get a live overview of existing content to maintain consistency without breaking flow.

Why Instructors Loved This: Course Presets

During user testing, instructors told us they often reused the same assignment setups. That insight led to course presets custom templates designed to speed up creation and ensure consistency.This feature proved especially useful for teachers, saving time while keeping their content structured. Here’s how presets are created we’ll show how they’re used in the next section.

Applying Presets When Creating Assignments

When building a new assignment, instructors can select the module it belongs to, choose the assignment type Read, Watch, or Play and then apply a preset to streamline the setup.This makes the process faster and more consistent, especially for instructors managing multiple modules with similar structures. Once finalized, the assignment is ready to publish with just a few clicks.

03 Branding Playwise
This section covers how we defined Playwise’s brand and built a design system with reusable components for consistent web and mobile experiences.

Bringing the platform to life.

What we learned:
A unified design system supporting both the student mobile experience and the instructor web interface, along with high-fidelity prototypes for each.
How we made it

How we made it:
We developed the design system by auditing existing UI components, establishing a consistent visual language, and creating reusable components in Figma. To support consistent usage, we also documented clear guidelines for the team.

Visual Identity & Moodboarding

We pulled colors, type, and tone from our moodboard to shape Playwise’s brand identity. These visual and emotional cues helped inform not just the design system but also the platform’s name, voice, and overall feel.

Sanjay kumar
Portfolio 2024
Product Designer
Visual Designer
All right reserved.