NB: This is the third post in a series on what we learned in our Fall 2017 Blueprint Course pilot. The previous posts provide an overview of our experience (Lessons Learned about Blueprint Courses: Introduction) and address how we got buy-in from teaching teams and administrative stakeholders for our target courses (Lessons Learned about Blueprint Courses: Getting Buy-In), and a later post discusses replacing a course copy workflow with Blueprint (Lessons Learned about Blueprint Courses: Replacing Course Copy Workflows).
Perhaps not surprisingly, Blueprint Courses (Canvas Release: Blueprint Courses) turn out not to be the right solution for every large-enrollment, multi-section course. In this blog post, I'll talk about the "failed" Blueprint pilot course, where the teaching and admin teams decided not to continue using Blueprint.
Why We Considered Blueprint
In the first post in this series, I described one of our pilot Blueprint courses like this:
MGEC 611 -- a half-term core MBA course with four faculty members each teaching three sections, a small army of TAs, and several support staff. Previously, this course had a single Canvas site (with all 12 sections!) in order to maintain consistency. Some of the faculty, however, wanted to customize the content for their assignments and course materials. We selected Blueprint to provide the teaching team with a common starting point, the ability to keep content in sync (if they chose not to modify their Canvas sites), and the ability to customize content if they chose. This Blueprint course has four associated Canvas courses, each with three sections (more than 800 students in total).
The second half of this course (MGEC 612) is offered in Q2, again with 12 sections taught by a slightly different set of faculty, and with basically the entire MBA class (about 850 or so students).
The teaching and admin teams agreed to use Blueprint during the Q1 course, and we all had the expectation that we'd also use it for the Q2 course (MGEC 612). All the upfront planning and communications included faculty who would be teaching in Q1 and Q2. (Again, I can't stress strongly enough how helpful Ken Black's post on Tips for Designing and Maintaining Blueprint Courses is for this kind of planning, especially his sections "Plan, Plan, Plan" and on deciding whether to lock items.) But in the end, they chose NOT to use Blueprint in Q2 -- and this says a lot more about their evolving understanding of their course needs then it does about the tool.
Challenges Inherent in this Course
These course were challenging for our Courseware Team to set up. (Our team creates Canvas site and populates them with assignments for our teaching teams as part of our standard site setup process.):
- Teaching and administrative teams wanted a single Canvas site for all 12 sections to facilitate distribution of cross-course materials and announcements, to allow TAs to easily assist in grading across sections, to post announcements to all students, and to provide a discussion board accessible to all enrolled students.
- We create both ungraded course preparation assignment and assignments for deliverables (papers, exams, etc.) with varied due dates by sections. (How do I assign an assignment to a course section?) With 12 sections in the same site, making sure that the correct section is assigned to the correct due date and time requires meticulous attention to detail.
- AND there's one faculty member who wants to do his own thing with the ability to modify assignments, but only for his own students. So the assignments index page from Fall 2016 looks something like this:
See the (C3) after what appears to be a duplicate assignment? One faculty member (responsible for "Cluster 3") wanted to be able to modify assignments for the sections he teaches. So each assignment has multiple sections assigned to it with multiple due dates. This makes it hard at a glance to see if we got everything right.
So this level of complexity across all the assignments, twice each fall for these quarter-term courses.
What Blueprint Allowed
When we approached the admin coordinator about trying Blueprint for this course, we used many of the reasons discussed in Lessons Learned about Blueprint Courses: Getting Buy-In -- so please check out that post for discussions of each of these benefits. The key selling points for this course were:
- Consistent starting point for course content, but with the ability for faculty to make changes if they wanted
- Ability to update content (that wasn't changed) at a later date
- Ability to replicate LTI tools (The specified item was not found., specifically because the course uses a shared course pack across all sections)
- Ability to post announcement across all sites at the same time
The combination of these features provided the central functionality that the course required -- the ability to have a common starting point for everyone (with the ability to update that content in a single place, just one), combined with the ability for faculty members to change that content if they chose. And not have those changes overridden. The way that Blueprint handles synced changes for unlocked content fit the bill. (See How do I sync course content in a blueprint course as an instructor? )
Configuring Blueprint for this Course
We created a Blueprint template site, along with four associated Canvas sites -- one for each "cluster" of three sections taught by one of four faculty members.
Configuring the Blueprint site was remarkably straight-forward: We left everything unlocked (How do I lock course objects in a blueprint course as an instructor? - this, we didn't do any of this), which provided faculty with control over what they wanted students to see and what content should be in the assignments, files, and other content. So, they could use the content from the Blueprint as a starting point, but were not required to use it.
Setting up section-differentiated assignments was faster and easier with only three sections (instead of 12!), and there was much less concern about accidental errors.
Teaching Team Enrollment
Our Courseware Team created the template from the shared syllabus and worked with the teaching team to determine who should have access to the Blueprint site and each of the associated cluster sites. In the end, they decided everyone should have access to everything: all five faculty members (teaching in either Q1 or Q2) and eight TAs (two assigned to each cluster) were enrolled in all five sites (the Blueprint template, plus four associated "cluster" sites).
Files and Folders
We spent a while talking through the logistics of how the Files areas should be set up and what (if any) files should be uploaded to the Blueprint template. And ultimately, the faculty members realized that they wanted to upload their own versions of the slide decks for each class meeting, so the template provided a file folder structure but only minimal shared files.
Where We Needed a Workaround: Discussions
By moving to four Canvas sites (one for each faculty member's section) instead of one, the primary functionality that they lost was giving students access to a shared discussion board. After investigating options, we installed Piazza as a course-level LTI tool, and then paired each Canvas site to the same shared Piazza board. This gave all 800+ students a centralized place to discuss course content, problem sets, ask and answer questions, etc.
Most of the Blueprint worked as expected:
- The one faculty member who wanted the ability to make changes did so. Unconstrained, he completely reorganized the navigation of his Canvas site and provided students with links to everything from the home page, hiding basically all other course navigational elements.
- Faculty appreciated being able to control what files their students saw, and especially appreciated that students could now access slide decks and other files posted only by their own instructors.
- Faculty appreciated that they could more readily control the visibility of classroom recordings -- we use The specified item was not found. for classroom lecture capture, without having recordings from one faculty member visible to all members of all sections.
- Announcements (using delay posting -- How do I delay posting an announcement until a specific date in a course?) could be posted across all sites at once.
What Didn't Work?
Though we haven't (yet) surveyed the teaching teams using Blueprint this semester, we have a pretty good idea of what didn't work.
- Learning curve: There's a learning curve and some overhead in keeping track of where changes need to be made (in the Blueprint site) and to remember NOT to make changes in an associated site, if you want to be able to sync the content to any changes made in the Blueprint. If you NEED the functionality offered by Blueprint, then there's incentive to tackle that learning curve.
- Managing multiple enrollments: For many members of the teaching team, their enrollments for the semester went from one (or two) to five (with the expectation of another five for Q2. Concurrent enrollment in so many sites can lead to a variety of challenges: problems keeping track of notifications from Canvas, grading to-do lists, Canvas calendar limits, etc. This was especially difficult for TAs, who also had their own set of Canvas sites for their course work.
- Bugs, and more bugs: In the initial weeks using Blueprint, we reported a number of bugs. And some of these contributed to the learning curve of using Blueprint.
What Are They Doing Now?
In the end, the teaching team realized that what they needed was simply an initial shared starting point, and that they didn't really need the ability to keep content, assignments, files, etc. in sync. Faculty members appreciated the ability to make changes and updates, as well as having complete control over the files and class recordings. So for the Q2 course, they dropped Blueprint and we simply copied the course content from one site to the next -- and this eliminated the extra administrative overhead that comes with Blueprint.
We still count this as a win, though: This teaching team would not have arrived at their current configuration without first trying Blueprint. Blueprint ended up being a way to ease them into having separate Canvas sites.