From Repetitive Support to Scalable Self-Service
Across four years of Canvas use, I transformed recurring workflow questions into reusable, point-of-need instructions embedded in hundreds of assignments and shared with parents and other educators—standardizing common processes and reducing repeated one-to-one troubleshooting.
.png)
Verified Professional Experience
Course-level Canvas administration & user support | Public K–12 education
2022-2026
Skills Demonstrated
Technical Writing, Workflow Documentation, Self-Service Support, Knowledge Management, User Enablement, Troubleshooting, Process Improvement, Course-Level LMS Administration
Challenge
Across four years of Canvas use, I repeatedly encountered the same workflow problems: downloading files, editing them, saving or recovering work, naming files correctly, using OneDrive, uploading files, and confirming successful submissions. Solving those problems individually was repetitive, produced inconsistent support, and made successful completion dependent on someone being available to explain the process again.
Role & Scope
Within my course-level Canvas administration and user-support responsibilities, I identified the workflows creating the most recurring friction, authored reusable step-by-step guidance, embedded that support into hundreds of assignments, and shared the resources with parents and other educators. My role combined LMS administration, user education, documentation, and troubleshooting; it did not involve enterprise Canvas ownership or system administration.
Approach & Execution
I treated the repeated questions as a support-system problem rather than a series of isolated user errors. I identified the high-frequency failure points, translated the workflow into clear sequential directions, and embedded the guidance directly inside assignments where users would encounter the task. Instead of relying on users to remember previous explanations or search elsewhere for help, the documentation traveled with the workflow. The same guidance could then be reused across hundreds of assignments and shared with additional users and educators.
Key Decisions & Rationale
Instead of creating one broad Canvas manual, I focused documentation on the specific actions users were repeatedly struggling to complete. I also placed the instructions directly within the workflow rather than expecting users to remember prior training or search elsewhere for help. The goal was to make support easier to find, easier to follow, and more useful at the moment a problem occurred.I deliberately avoided creating one broad Canvas manual. The recurring problems were specific actions—download, edit, save, name, locate in OneDrive, upload, and verify—so I documented those actions at the point of need. I prioritized the steps that repeatedly stopped users from completing the workflow and made the guidance available during the task itself rather than expecting users to remember prior training. That made support easier to find, more consistent, and less dependent on live intervention.
Outcome & Impact
The point-of-need documentation gave users a consistent answer each time they encountered the workflow and reduced how often I needed to re-explain the same process individually. The approach also turned repeated one-to-one troubleshooting into a reusable self-service support system that could scale across hundreds of assignments.The point-of-need documentation standardized recurring support across hundreds of assignments, gave users a consistent answer each time they encountered the workflow, and reduced how often I needed to re-explain the same process individually. Sharing the guidance with parents and other educators extended its usefulness beyond a single interaction and turned repeated one-to-one troubleshooting into a reusable self-service support system.
What This Demonstrates
This project demonstrates my ability to identify recurring user friction, convert tacit knowledge into clear documentation, design point-of-need support, standardize recurring processes, and help users complete technology workflows more independently. It reflects strengths in technical writing, customer/user education, self-service support, knowledge management, troubleshooting, LMS administration, and process improvement.This project demonstrates my ability to identify recurring user friction, convert tacit troubleshooting knowledge into clear workflow documentation, place support at the moment of need, standardize a repeated process, and reduce reliance on one-to-one assistance. It reflects strengths in technical writing, self-service support, knowledge management, user enablement, troubleshooting, process improvement, and course-level LMS administration—and shows that I think beyond answering individual questions to designing support that can be reused at scale.