Canvas Design Workshop in Edgemont, South Dakota


A one-day workshop for rural educators that put design thinking ahead of Canvas features, and what an optional, single-session format meant for how far that could go.

  • Project Type: One-day in-person professional development workshop
  • Audience or Client: K-12 educators in Edgemont, South Dakota
  • Timeline: July 2023
  • Role: Workshop designer and facilitator
  • Format or Deliverables: Full-day workshop combining design principles (voice and choice, SAMR, usability), a rapid prototyping exercise, a Canvas build toolkit, and extended guided build time

The Situation

Edgemont’s teachers were already using Canvas, but most of them had had little specialized EdTech professional development, and attitudes toward technology varied across the staff and the community. Bandwidth and access were real constraints. The easy version of a Canvas workshop is a tour of buttons and features, and that version tends to leave teachers able to click through settings without much sense of why one course design works better for their students than another.

The Approach in Brief

I designed the day so that design came before features. It opened with teachers describing how they and their students were actually using Canvas and writing a personal “Canvas Wishlist,” then moved through a short presentation on design principles, a rapid prototyping exercise where teachers sketched course layouts and gave each other feedback, and an introduction to a build toolkit. The longest block, two and a half hours, was open build time with regular stop-and-share breaks, so teachers left having worked on their own courses rather than a sample one.

What Came Out of It

By the end of the day, teachers had drafted designs for course home pages or content pages and started building items from their wishlists in their own courses. The design portion landed better than I expected. One participant told me, “I expected to learn about buttons and features, but I came away with a whole new perspective on course design.” The day also showed me the limits of a single optional session, which is where most of what I’d change comes from.

Key Takeaway

Teachers will engage with design principles in a tool workshop when the principles lead straight into work on their own courses. A single day can start that work, but it can’t carry it far on its own.


Deeper Context

The workshop was a full day, and I planned it assuming everyone would be there for all of it. I only learned on the day that it was optional rather than required. That changed who was in the room and how long they stayed, and it was a detail I should have asked about while planning.

The rural context shaped the content as well. With limited bandwidth in mind, the toolkit and examples leaned on course designs that would load and work for students with weaker connections. With mixed feelings about EdTech in the community, I also wanted the case for any design choice to rest on what it did for students, not on what Canvas made possible.

The Journey

The opening check-in set the agenda for the rest of the day. Teachers talked in pairs about how they used Canvas, how they saw students using it, and what students said about it, then swapped partners once. Each person then submitted three “I wish I could…” or “I wish Canvas…” statements to a wishlist assignment in the workshop’s own Canvas course and copied them to the top of an Excalidraw board they kept open all day. Those wishlists became the material for the build time later, which gave the afternoon a clear purpose for each person.

Slide titled Canvas Wishlist asking participants to quietly reflect on what they wish they could do with Canvas and submit their top three to an assignment, using the stems "I wish I could..." or "I wish Canvas..."

The design presentation was short on purpose, about thirty minutes. It started by asking teachers what Canvas was to them (a file folder, a website, a curriculum, or a co-teacher) and what that said about where their use sat on SAMR. From there it covered ways to add voice and choice, both in individual features and in how modules are structured, and a few usability basics, drawing on Steve Krug’s Don’t Make Me Think. I wanted just enough of a frame that the next hour would have something to work with.

Design cycle diagram: a circle of four arrows labeled Identify Needs, Brainstorm, Test, and Build.

That next hour was the design cycle exercise, which ran through four steps: 1) identify needs, 2) brainstorm, 3) test, and 4) build. Teachers picked a home page or content page to design and worked out what it needed to do, what students would look for on it, and what devices students would use to reach it. Then they sketched at least eight layouts, on paper or in Excalidraw, picked their two strongest, and tested them on someone they hadn’t talked with yet that day, explaining only the needs they were trying to meet and watching for where their partner got confused. Sketching before touching Canvas kept the conversation on what students needed to see and do, and it made revision cheap, since throwing out a sketch costs nothing.

Slide titled Workshop Part 3, the test step of the design cycle: pick your two best sketches, then find someone you haven't spoken with today, tell them only the needs you were trying to solve, give them time for feedback, and pay attention to their first reaction and where they get confused. A note adds that the activity works well with students too.

The build toolkit hour came after the sketches, so the Canvas features arrived as answers to design questions teachers had already raised. The toolkit lived in the workshop’s Canvas course, and teachers used it to start building what they had sketched, working with a neighbor or calling me over when they got stuck. The open build time after lunch was the longest part of the day. Each teacher’s goal was to finish at least one item from their wishlist. Every thirty minutes we took a five-minute stop and share, where I gave a prompt and people found someone who matched it, showed what they were working on, and asked for input. The day closed with teachers exporting their Excalidraw boards as an exit ticket, a course evaluation checklist for what to work on next, and an optional exit survey.

Slide titled Build Time: review the wishlist from the start of the day and try to accomplish at least one item, researching, asking for help, and collaborating as needed. Every thirty minutes, a five-minute stop and share where participants find someone matching a prompt, share what they are working on, and ask for input.

The Work Itself

The slides throughout this case come from the deck I used that day, along with the design cycle graphic that framed the prototyping hour. The agenda below shows how the day was paced, with the longest stretch saved for teachers building in their own courses.

Slide titled Today's Outline: 9:00 to 9:30 check-in on where we are with Canvas; 9:30 to 10:00 design presentation on voice and choice, SAMR, and usability; 10:00 to 11:00 the design cycle; 11:00 to 12:00 using the build toolkit; lunch; 1:00 to 3:30 open build time with a stop and share every 30 minutes.

What I’d Change

The format is the first thing I’d change. For an optional workshop, a full day is a hard ask, and a series of shorter, focused sessions would have let people come for the parts they needed. I’d also confirm whether attendance is required before designing the day, since it changes almost every other decision.

I’d also plan the follow-up as part of the design instead of treating the day as complete. The wishlists showed exactly what each teacher wanted to build next, and shorter sessions built around the most common wishlist items, along with virtual office hours, would have carried the work past the day itself. None of that follow-up happened, and the day’s results stayed with whatever teachers finished during build time.

At the time, I wrote that I’d open the next version with a few quick, high-impact Canvas features to build momentum before the design material. I tried something like that a year and a half later in a Google Sheets session for Douglas School District staff, and it taught me something about which quick wins work. Opening with power features worked for the confident users and put the hardest material first for everyone else. So I’d still open with a quick win, but a simple, everyday one that every teacher in the room can use right away, and save the impressive features for the end.

Connections

For the session where I tested that opening, see Google Sheets Efficiency for Administrative Assistants. For designing courses around the connections rural students actually have, see Low-Bandwidth Course Design.

If you’re planning Canvas training for a small or rural district, you can reach me at licht.education@gmail.com, and there are more tools, articles, and resources at bradylicht.com.


Discover more from Brady Licht

Subscribe to get the latest posts sent to your email.