Redesigning Canvas, a Learning Management System
Canvas is a widely used platform that overseas learning management for over 6,000+ institutions across more than 70+ countries. As a global platform, it provides tools for faculty to organize course materials, communicate with students, and assess performance, enhancing both teaching and learning experiences.
What is the problem?
Faculty members found the process of creating and editing assignments in Canvas challenging due to a complex user flow and confusing navigation, resulting in task failures and significant time delays.
Why was the faculty struggling?
After analyzing the data from contextual inquiry, with over 1100+ surveys, 70+ introductory and observations interviews we found that faculty members were facing 2 main issues…
I learned that faculty found creating assignments frustrating because the information architecture was too complicated and confusing, making it take much longer to complete the task than needed.
We decided to combine assignments and modules together and to shorten the information architecture by simplifying the details form needed to create an assignment in the following 2 ways:
Introducing Quick Post
We added a "quick post" button on the top right corner of the dashboard to help faculty easily create announcements, assignments, and discussion boards.
B. Decluttering the form to reduce the scroll
Creating assignments was time-consuming because faculty had to scroll a lot and repeat information. To fix this, we reduced the scrolling and added pre-filled categories so they only edit when needed.
The faculty was struggling with editing an already existing assignment because of a lengthy work flow. So to solve this I decided to cut the flow shorter making it easier for them to edit basic details of the assignment.
Introducing an Edit button
Faculty found it difficult to edit minor details like assignment name, due date, and point value with the old design.
To fix this we introduced Quick Edit button
I thought we needed to redesign Canvas completely, but users told us they just wanted the issues fixed. A new design would mean they’d have to relearn everything, which they didn’t want. This taught me to focus on what users actually need instead of assuming.
If I were to revisit this project, I would prioritize conducting more extensive user testing. This would help uncover deeper insights, validate design decisions, and ensure the solution aligns better with user needs.