The consensus in edtech right now feels settled: Learning management systems need better features, sleeker interfaces, more integrations. Universities shop for platforms the way they shop for enterprise software anywhere else. Does it have the bells and whistles? Can it sync with our other tools? Will adoption numbers look respectable in the first semester?
The better question is this: What does our obsession with LMS feature-building break about how we actually think about teaching?
Let's be honest about what's happening. The instructional design community has spent years documenting that LMS success depends on far more than platform capabilities. Yet institutions continue treating the platform as the variable that matters most. We pour resources into choosing between Blackboard and Canvas iterations, debating whether the grade book interface is intuitive enough, arguing about whether a new mapping feature justifies the cost.
Meanwhile, the actual teaching and learning happening inside these systems receives a fraction of that attention.
There's a real risk baked into this approach. When you elevate platform features as the primary lever for educational improvement, you subtly shift responsibility away from the harder work: faculty development, instructional design support, rethinking how syllabi communicate course purpose, or building meaningful professional networks that help educators learn from each other.
A syllabus tells a story. An interactive campus map creates belonging. A robot in a classroom raises questions about what teaching actually requires. These aren't small considerations. Yet they tend to get treated as secondary concerns, nice-to-haves after you've locked down your LMS contract.
The feature-first framing also creates a problem for smaller institutions or those with limited budgets. It suggests that educational quality is proportional to platform sophistication. That's demonstrably false, but it's a message the market reinforces constantly. The result: schools stretch budgets for enterprise features they'll never fully use, while missing opportunities to invest in the human infrastructure that actually drives learning outcomes.
This matters because infrastructure shapes what becomes possible next. When your primary investment is in platform features, your next iteration naturally focuses on more features. When your primary investment is in how faculty think about course design or how students experience community, your next iteration focuses on those human elements. The path you choose now constrains what you can build later.
There's nothing wrong with wanting better LMS tools. Interface design matters. Integrations save time. But there's a difference between treating these as tools that serve a larger educational vision and treating them as the vision itself.
The uncomfortable truth is that the harder problems in edtech don't have feature solutions. How do you create genuine community in online learning? How do you help students understand the narrative arc of a course before they click into it? How do you build professional networks that actually change how educators approach their work? These questions require different thinking entirely.
The industry consensus wants to stay comfortable in the world of platform capabilities because that's familiar, measurable, and comes with clear vendors and purchase cycles. It's business. It makes sense.
But it also means we're optimizing for the wrong variable. We're treating LMS features as the primary driver of educational success when they're really just infrastructure. Important infrastructure, sure. But infrastructure nonetheless.
The institutions making real progress aren't the ones shopping for the next platform generation. They're the ones asking what their current system enables them to do differently with faculty, with course design, with student experience. They're working backward from learning outcomes instead of forward from feature lists.
That's harder. It's also where the real work begins.