From Repetitive Support to Self-Service
Turned recurring Canvas support problems into reusable, point-of-need self-service guidance embedded in hundreds of assignments—improving consistency and reducing repeated one-to-one troubleshooting.
.png)
Verified Professional Experience
Public K–12 education across multiple districts
Approximately 3 years
Skills Demonstrated
Technical Writing, Self-Service Support, Knowledge Management, User Education, Troubleshooting, Process Improvement, LMS Administration
Challenge
Over roughly three years of Canvas use, I repeatedly encountered the same user-support problems: downloading files, editing them, saving or recovering work, naming files correctly, using OneDrive, uploading files, and confirming successful submissions. Answering the same workflow questions individually was repetitive and made support dependent on someone being available to explain the process again.
Role & Scope
I provided course-level Canvas administration and user support as part of my educator role. I identified recurring areas of friction, translated repeated explanations into reusable step-by-step directions, embedded that guidance in hundreds of assignments, and shared the resources with parents and other educators. My work was at the course/user-support level rather than enterprise LMS administration.
Approach & Execution
I treated the repeated questions as a documentation problem rather than a series of isolated user errors. I identified the workflows that consistently caused difficulty, standardized the guidance into clear step-by-step directions, and embedded those instructions directly inside the assignments where users would need them. This moved support closer to the actual task and allowed the same guidance to 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.
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.
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.