|
Getting your Trinity Audio player ready...
|
Your institution just wrapped a $400,000 LMS migration. The vendor promised integration. The implementation partner promised change management. The steering committee promised adoption. Six months in, teachers are uploading PDFs to a digital filing cabinet and students are still emailing assignments to their instructors. The platform is failing. Or so the story goes.
The platform isn’t failing. Your institution is implementing it as a control system when it should be implementing it as a teaching system. And until that structural orientation changes, your next LMS will fail for exactly the same reasons.
The Control Orientation
When an institution implements an LMS, it rarely asks: “How does this platform help teachers teach?” Instead, it asks:
- Can we track student time-on-task?
- Can we ensure compliance with course structure requirements?
- Can we standardize course shells across departments?
- Can we measure completion and reduce accreditation risk?
- Can we reduce instructor workload through automation?
These are all legitimate institutional concerns. But notice what they have in common: they’re not about learning. They’re about visibility, standardization, compliance, and control. The LMS becomes an infrastructure for managing institutional risk and regulating teacher behavior, not for supporting teaching practice.
Teachers know this immediately. They feel the platform’s actual purpose in its design: the mandatory course structure modules you can’t customize. The grade book that’s optimized for data extraction, not feedback. The discussion forum that captures institutional liability but constrains genuine dialogue. The analytics dashboard that measures engagement as proxy for learning—because actual learning is hard to quantify and harder to control.
So teachers do what they’ve always done: they work around the system. They use email for real communication. They hand-grade high-stakes assignments instead of using the built-in tools. They keep their real course materials in Google Drive. They conduct live Zoom sessions because the asynchronous framework doesn’t fit their pedagogy. The LMS becomes a compliance layer they perform for, not a tool they use.
And the institution interprets this as adoption failure. “If only teachers would buy in,” administrators say. “If only we trained them better.” If only we made the interface simpler. If only we mandated submission through the LMS.
The adoption isn’t failing. The orientation is.
What Teaching Infrastructure Actually Requires
A teaching infrastructure starts with a different question: What do teachers need to do their best work?
Teachers need to give feedback—not summarize it in a gradebook, but actually communicate with students about their thinking, their growth, their next steps. That feedback is often asynchronous (written), but it’s always directional and responsive. A teaching infrastructure makes that easy and natural.
Teachers need to understand where their students are. Not surveillance-level tracking of login times and page views. Understanding. What misconceptions are live in the room? Which students are struggling with this particular concept? Who’s ready to move ahead? A teaching infrastructure surfaces this through tools that capture authentic learning signals—student work, questions, mistakes—not proxy metrics.
Teachers need to iterate quickly on their practice. They need to try something, see how students respond, adjust, try again. This happens at the pace of a class or a unit, not at the pace of an academic calendar. A teaching infrastructure assumes experimentation and makes it low-friction.
Teachers need to honor the rhythm and depth of their discipline. A history teacher’s inquiry-driven seminar looks nothing like a statistics course or a language class. A teaching infrastructure adapts to disciplinary practice instead of forcing all courses into a uniform structure.
Teachers need autonomy with accountability. They need space to make pedagogical choices—how to sequence material, how to group students, what counts as evidence of learning—while being accountable for that work. A teaching infrastructure trusts teachers while making their practice visible.
None of this is particularly controversial. But it requires an LMS designed around teaching instead of around institutional risk management. And that’s almost never what institutions buy.
Why This Keeps Happening
There are a few reasons this structural mismatch persists.
First, buying committees rarely include practicing teachers. Decisions are made by administrators, IT staff, and accreditation offices—people whose primary concern is institutional stability, not pedagogical quality. Teachers are invited to “input sessions” after the platform is already chosen.
Second, implementation is outsourced. Vendors and implementation partners have an incentive to position the LMS as the solution to institutional problems: “Use our gradebook tool and reduce grading time,” “Use our analytics and identify at-risk students,” “Use our content library and ensure consistency.” These are control promises, not teaching promises. The vendor can deliver them. Nobody can promise that a platform will make teachers better at their craft—that’s on the teacher, not the tool.
Third, success is measured wrong. Adoption metrics reward compliance: course shells created, assignments submitted through the platform, grades entered by deadline. None of these measure whether teaching got better. And because they’re easy to measure, they become the actual goals. You optimize for what you measure, and institutions measure institutional control.
Fourth, there’s a funding alignment problem. The people who allocate budget—provosts, deans, IT directors—benefit from a platform that centralizes data and enforces standardization. The people who would benefit most from a teaching-first infrastructure—faculty and students—have minimal budget power.
The Practical Path Forward
If you’re facing an LMS decision or living through a failing implementation, here’s what matters:
Ask different questions in procurement. Don’t ask “Can this platform track student engagement?” Ask “Can a teacher use this to give meaningful feedback easily?” Don’t ask “Does it enforce course structure compliance?” Ask “Does it let teachers design for their discipline?”
Include practicing teachers on the steering committee. Not as advisors. As decision-makers. Their pedagogical judgment should outweigh institutional risk management in design choices.
Measure what actually matters. Track instructor use of features designed for teaching (feedback tools, formative assessment), not compliance (course shells created). Ask teachers annually: “Did this tool help you teach better this year?” Listen to the answer.
Protect autonomy. Whatever platform you adopt, establish clear boundaries: teachers can customize course structure, teachers choose their own assessment tools, teachers decide what goes in the gradebook. Make this non-negotiable. Institutional standardization is cheaper than pedagogical quality, but you can’t have both.
Accept lower adoption on compliance features. If teachers route around your LMS’s discussion forum because they find real learning happens in live dialogue, that’s not a failure. That’s information. It means your infrastructure isn’t serving teaching.
None of this requires a different LMS. Canvas, Blackboard, Moodle, D2L—the platform matters less than the orientation. You can have a control-focused infrastructure on any platform. And you can have a teaching-focused one too.
The question is which one your institution actually wants.