Why LMU Stuck With Brightspace When Everyone Else Is Switching
Loyola Marymount University ran a pilot with Canvas back in 2019. It lasted nine months. The migration got pulled because the engineering and fine arts departments had custom integrations that the new platform couldn't support without a two-semester rewrite. They went back to Brightspace, which they had been using since 2013, and spent the rest of the year making it bearable. I've watched three cohorts go through LMU's digital learning infrastructure from the faculty side and one from the admin support side. Brightspace at LMU is not the prettiest LMS you will encounter. It is also not as bad as people complain about once you know where the bodies are buried.
The Brightspace Lms At Lmu A Comprehensive Analysis Of Learning Management In The Digital Age At Loyola Marymount Univer
The full official framing from IT puts it as part of their hybrid learning strategy. In practice, what that means is every course gets a Brightspace shell whether it's online, in-person, or hybrid. The system handles grades, announcements, assignments, and a thing called iLearn that some departments use as a mini-site inside the shell. The gradebook syncs with Banner, which is the SIS they run. That synchronization is both the best and worst thing about the whole setup. The dashboard shows your courses as cards. Click one, and you land on the Course Overview page, which is a mess of widgets by default. Most professors never customize it, so students see a jumble of announcements, course status, upcoming items, and a discussion topic list all compressed into columns that don't stack right on mobile. The mobile app, D2L Learn Mobile, exists but nobody recommends it for anything heavier than checking announcements. The web version on a laptop is where the work actually happens. The interface hasn't changed its core layout since 2017, which means the UX patterns are deeply ingrained for anyone who has used it for more than a year but feel archaic to anyone coming from Canvas or Moodle.
How the Gradebook Actually Works (and Where It Breaks)
LMU configured Brightspace to map assignment categories to grading blocks. If a professor sets up a category called "Exams" worth 40 percent and another called "Participation" worth 10 percent, the weight distribution calculates automatically. That works until someone drops a quiz, changes a category weight mid-semester, or adds an unweighted assignment outside the system. Then the percentage math goes weird and students get an email from the registrar asking why their grade looks like 87 percent when they can add it up manually and get 79. The workaround I use is simple and nobody else seems to do it: export the gradebook to CSV at the end of every Monday for twelve weeks. Check the total weight column. If it doesn't equal exactly 100, something is misconfigured and you flag it before the final grade submission window opens. I learned this the hard way in fall 2022 when a colleague had a hidden ungraded assignment sitting at zero that was pulling every student's final down by three points across the board. The only reason I caught it was because I was doing the export out of habit.
Get the Full Details
Accessibility: The Part Nobody Talks About Much
Brightspace has an accessibility checker built into the content editor. It flags missing alt text, low contrast, and unlabeled links. LMU's disability services office requires a 504 compliance check before any course goes live online. The checker is decent but it misses a lot. Specifically, it does not reliably catch screen reader issues with custom JavaScript widgets or embedded H5P content, which a lot of the education and psychology departments love to use. I spent an entire semester fighting with a professor who insisted on using a proprietary interactive simulation tool that Brightspace's checker marked as compliant but Screen Reader users couldn't navigate at all. The fix was writing custom keyboard navigation notes into the course description and having disability services do a manual audit. The simulated tool stayed. The audit trail did the rest.
Analytics and What They're Actually Good For
Brightspace has something called Learning Analytics that tracks login frequency, content views, and assignment submission times. Department chairs at LMU use it to flag students who haven't logged in for ten days. The threshold is arbitrary. Ten days sounds like a lot but for a course that meets twice a week in person, a student might legitimately be offline over a long weekend. The analytics are most useful when you drill into the assignment-level data, not the dashboard overview. You can see which specific content item had the highest drop-off rate. That tells you something the gradebook never will. In one course I supported, the analytics showed that students who watched the Week 4 recorded lecture had a 22 percent higher quiz average than those who didn't, even though the lecture was optional. That data point changed how the professor framed the lecture going forward without any dramatic intervention.
Integration with the Rest of LMU's Tech Stack
Brightspace connects to Slack for some departments, to Turnitin for plagiarism, and to Panopto for video hosting. The Panopto integration is probably the smoothest part of the whole system. Lectures record, transcribe, and drop into the course automatically. The captions are machine-generated and accurate enough to pass disability services in most cases, but not all. I have corrected captions on recordings where technical jargon got transcribed as completely unrelated words because the speaker had a heavy accent and the auto-caption model didn't have the terminology in its dictionary. The Turnitin integration works but the similarity report timing is annoying. Submissions show as "in progress" for 20 to 45 minutes depending on file size. If a professor sets up an assignment with a hard deadline at 11:59 PM and expects to review submissions at midnight, they will be waiting. The workaround is setting the due date to 11:00 PM and telling students the real cutoff is midnight. It sounds petty but it prevents the support ticket flood that happens every Sunday night.
What the Students Actually Complain About
The #1 complaint is navigation depth. Brightspace buries things. A discussion forum is three clicks away from the course homepage if the professor hasn't reorganized the navigation panel. An assignment dropbox is sometimes four clicks if it's nested under a Content module. Students in surveys consistently rate "ease of finding things" as the lowest satisfaction metric, usually around a 2.4 out of 5. The second complaint is notification spam. By default, Brightspace sends an email for every discussion reply, every grade posting, and every announcement. Students get 30 to 80 emails a week from a single active course. The notification settings page exists but it is buried under Course Options, which most students never find. I have a one-paragraph screenshot guide I send to every incoming TA that shows exactly where to turn off grade notification emails while keeping assignment reminders on. It reduces their inbox load from 60 emails to about eight.
Administrative Headaches That Don't Show Up in Student Feedback
Course shell creation is automated through Banner but the timing is wrong. Shells provision 30 days before the term starts, which sounds generous. It isn't. Professors who teach across multiple colleges often forget to copy materials from their previous term until week three of the preceding semester, which means they have exactly two weeks to rebuild a course that should take four. The result is a broken first week where students log in to empty shells and the help desk tickets pile up. The other issue is section naming. Banner pushes section names into Brightspace, and Banner's section name conventions at LMU include course numbers, credits, and instructor initials all concatenated without delimiters. The navigation panel ends up looking like "PSYCH 300 3cr JD" instead of "Introduction to Developmental Psychology." It looks sloppy and it confuses transfer students who are used to cleaner labels. There is a setting to override the display name but most professors don't know about it and IT never enforces it proactively.
What Works Well Enough That They Keep It
The quiz engine in Brightspace is genuinely better than Canvas's for certain use cases. Randomized question pools, randomized answer choices within each question, and time limits with per-question timers are all straightforward to set up. The question bank organization is also superior. You can tag questions with metadata, filter by tag, and build quizzes from filtered views. Canvas can do this now but LMU was on an older version when these features were being evaluated and the Brightspace implementation felt more mature at the time. The peer review feature for assignments is another area where Brightspace wins on usability. Setting up a rubric-based peer review where students evaluate each other's submissions and leave written feedback takes about four clicks. The interface is clean and the rubric scores auto-populate into the gradebook. I have seen professors use this effectively in seminar-style courses with 25 to 35 students and it actually works without turning into chaos, which is rare for peer review systems.
Customization Limits You Will Hit
Brightspace at LMU is the enterprise edition, not the campus-branded custom version. That means you cannot change the color scheme, the login page branding beyond the logo swap, or the default navigation structure. The UI theme is whatever D2L ships and it won't accept third-party CSS injection. Some departments wanted a more visually distinct experience for their online programs and hit a wall there. The workaround was building a separate landing page in a different tool and linking to it, which defeats the purpose of having everything in one place. Another hard limit is the API rate limiting. If you try to pull grade data for all sections of a large course through the API during finals week, you will get throttled. The support team says the limit is around 100 requests per minute per tenant. I wrote a script once that pulled weekly grade aggregates for 12 sections and it took six hours to complete because of the throttling. A simpler approach is to batch the requests and add a 500-millisecond delay between calls, which cuts the runtime to about 45 minutes. Not great, not terrible, but it means you can schedule the export to run overnight.
The Reality of Training and Support
LMU's Center for Teaching and Learning runs Brightspace workshops every summer and twice per semester. They are optional. Attendance is roughly 30 percent of faculty, concentrated among people who already use the LMS heavily or people who are mandated to attend because they are new tenure-track hires. The workshops cover basic navigation, creating assignments, and posting announcements. They do not cover gradebook troubleshooting, API usage, or accessibility deep-dives because those topics require a longer format than the one-hour workshop slots allow. The faculty support help desk responds within four hours during business days and within 24 hours on weekends. The resolution rate for common issues like password resets and shell problems is high. The resolution rate for pedagogical questions like "how do I set up adaptive release based on quiz performance" is lower because the help desk staff are technically competent but not trained as instructional designers. They will tell you where the button is but not whether using that button is a good idea for your course goals.
Cost and Licensing Considerations
D2L charges per active student enrollment, not per course. That matters at LMU because the average undergraduate carries 15 credits, which is roughly five courses. A campus of 10,000 students generates about 50,000 course enrollments annually. The licensing cost is significant but stable because the contract has been renewed every three years with modest increases. When Canvas was being evaluated, their pricing model was per-student-per-course, which would have been roughly double what LMU pays now. That pricing difference was the decisive factor in staying with Brightspace after the failed Canvas pilot. Group projects are the weak point. Brightspace has a group workspace feature, but the permissions are all-or-nothing. Either the whole group shares a single folder and dropbox, or each student works individually. There is no middle ground where you can have subgroups within a larger project team, which is a common setup in engineering design courses and upper-level labs. Professors work around this by creating separate course sections for each subgroup and merging grades manually at the end of the term. It works for small classes but breaks down in courses with 60 or more students spread across eight groups. The second failure mode is live exam proctoring integration. Brightspace does not have a built-in proctoring tool and the integrations with third-party services like Honorlock and ProctorU are clunky. Students have to launch the proctoring software from within the quiz interface, which sometimes fails to redirect back properly. When it fails, the exam timer keeps running but the student is stuck on a blank screen. The professor has to manually extend the timer and document the incident for the student. This happens often enough during finals that the IT team considers adding a native proctoring module to their roadmap, but that roadmap has been "coming soon" since 2021.
Bottom Line
Brightspace at LMU is functional, moderately well-integrated, and held together by institutional knowledge that lives in the heads of about six people who have been using it since 2013. It is not elegant. It has real gaps in group collaboration and accessibility auditing. But the gradebook math is reliable when configured correctly, the quiz engine handles most assessment needs, and the cost structure makes it economically defensible for a university of LMU's size. The complaints from students and faculty are real but they tend to be about navigation friction, not systemic failure. The system works. It just makes you work a little harder than it should to get through it.
