



Turning recurring Canvas support questions into a self-service microlearning portal, how-to documentation, and coaching — converting one-to-one support into a model that scales with the team.
As the team's Canvas LMS specialist, I was the default person colleagues came to with platform questions. The questions were recurring, the answers were repeatable, and the one-to-one support model didn't scale.
I built an internal enablement solution: a self-service microlearning portal inside Canvas, supported by how-to documentation and targeted coaching. Staff could find answers to common questions themselves, and the documentation became the team's shared reference.
As the team's Canvas specialist, I was the single point of contact for platform questions. The same questions came up repeatedly — how to set up a module, how to configure a quiz, how to fix a common formatting issue. Each question was quick to answer once, but answering the same things over and over didn't scale, and it created a bottleneck whenever I was unavailable.
The team needed a way to get answers to common Canvas questions without waiting for me — and I needed a way to capture what I knew so it wasn't locked in one person's head.
Started from the real questions. Rather than build a generic Canvas course, I started from the questions people actually asked. That kept the content tightly scoped to what the team needed and meant every piece of documentation earned its place.
Built it inside Canvas itself. The microlearning portal lived in Canvas, so staff learned the platform by using the platform. The medium reinforced the message.
Made it self-service first, coaching second. The documentation and screencasts handled the common cases on demand. Coaching was reserved for the situations that genuinely needed a person — which meant my time went to the high-value questions, not the repeat ones.
Kept it short. Microlearning format — short, task-focused pieces a colleague could find, watch or read, and apply immediately, without sitting through a full course to find one answer.
Documentation is a scaling tool. Capturing repeatable answers in self-service form converted a personal bottleneck into a team resource. The work paid for itself every time someone found an answer without asking.
Scope from real demand. Building from the questions people actually asked kept the content lean and relevant — no speculative coverage of features nobody used.
Internal enablement is learning design. The same instructional design skills that go into a learner-facing course apply to internal staff training — audience analysis, task focus, clear structure, and the right medium for the job.
[ Placeholder — one testimonial from someone who worked with you on this specific project. A colleague, manager, or stakeholder who can speak to what you did here. 2–4 sentences. ]
[ Remove this whole section on projects where you don't have a relevant testimonial. ]
Happy to chat about full-time roles or projects — pick whichever option works best for you.