Before You Build That LMS: Why Asking for Feedback Isn’t Just Polite, It’s Essential
So, you’ve decided it’s time. Your institution needs a Learning Management System (LMS), or maybe it’s time to replace the clunky old one that everyone groans about. You’ve done your preliminary research, maybe even shortlisted a few vendors or sketched out some specs if you’re building custom. The urge to dive headfirst into development or procurement is strong. But hold on! Before you hit the “go” button, there’s a critical, often underestimated step: asking for feedback.
This isn’t about a quick, token survey sent to a handful of people. It’s about strategically gathering genuine, insightful input from the very people whose lives this new LMS will transform. Skipping this phase isn’t just impolite; it’s a recipe for wasted resources, low adoption, and a solution that misses the mark. Here’s why asking for feedback before you build is non-negotiable and how to do it right.
The High Cost of Building in a Vacuum
Imagine spending months (and significant budget) developing or implementing a shiny new LMS. Launch day arrives, excitement is high… only to be met with a collective shrug, confusion, or even outright resistance. Why? Because the system, however technically sound, doesn’t solve the real problems your users face daily.
Misaligned Priorities: What you think is the biggest pain point (say, complex gradebook setup) might rank low for instructors drowning in assignment submissions or students struggling to find course materials. Feedback reveals the actual priorities.
Ignored Workarounds: Users are incredibly resourceful. They’ve likely developed intricate, unofficial workarounds using shared drives, email chains, or even paper to bypass the limitations of the old system. Building without understanding these means you might automate a process no one uses or overlook a crucial gap your new LMS should fill.
Underestimated Needs: A department head might desperately need robust reporting you hadn’t considered. Faculty might crave specific integration capabilities with tools they love. Students might prioritize mobile accessibility above all else. Uncovering these needs early prevents costly rework later.
Eroded Trust & Buy-in: When users feel their input wasn’t sought, they feel unheard. This breeds skepticism and makes driving adoption after launch an uphill battle. Involving them upfront builds ownership and champions.
Who Really Needs a Voice? (Hint: It’s More Than Faculty!)
It’s easy to default to surveying instructors. They are primary users, after all. But an LMS ecosystem is complex. Cast your net wider:
1. Instructors/Faculty: Deep insights into course design needs, assessment workflows, communication preferences, grading complexities, and content management. What frustrates them most? What features would save them time?
2. Students: The ultimate end-users! What do they find confusing in the current system? What features make learning easier? What device do they primarily use? How do they prefer to receive announcements and feedback? Focus groups with diverse students are gold.
3. Teaching Assistants (TAs): Often power users navigating between instructor and student roles. They spot workflow inefficiencies and usability issues others might miss.
4. Instructional Designers & Technologists: Experts in pedagogy and tool integration. They understand learning objectives and what features genuinely support them. They also know the technical constraints and possibilities.
5. Department Chairs & Program Directors: Focused on program-level needs, reporting, consistency across courses, and resource allocation. What data do they need from the system?
6. Administrative Staff: Involved in enrollment, reporting, compliance, and potentially backend setup. What administrative burdens can the LMS alleviate?
7. IT Support: Understand infrastructure requirements, integration challenges (SIS, authentication), security, and long-term maintenance implications. Their early feedback prevents technical nightmares.
8. Librarians & Academic Support Staff: Often involved in resource linking and supporting students/faculty. How can the LMS better integrate library resources or support services?
Beyond Surveys: How to Gather Meaningful Feedback
A generic “What do you want in an LMS?” survey sent to a large list will yield generic, often unhelpful results. Aim for depth and context:
1. Targeted, Focused Surveys: Instead of one massive survey, design smaller ones for specific groups. Ask instructors about their teaching workflows. Ask students about their learning and navigation experiences. Use specific, scenario-based questions (“Describe your process for returning graded papers online…”).
2. Small Group Workshops/Focus Groups: Gather 5-8 people from a similar role (e.g., faculty from one department, a group of TAs, a mix of students). Facilitate discussions around pain points, wish lists, and specific features. The dynamic conversation sparks deeper insights than surveys alone.
3. Structured Interviews: Conduct 30-60 minute interviews with key stakeholders (seasoned faculty, tech-savvy students, lead IT staff). This uncovers nuanced needs, hidden challenges, and strategic perspectives.
4. “Day in the Life” Shadowing/Observation: Observe instructors and students using the current system (or workarounds) in real-time. You’ll see frustrations and inefficiencies they might not articulate verbally.
5. Feedback on Existing Systems (If Applicable): If replacing an LMS, mine its support tickets and help desk logs. What are the most common complaints and requests? Analyze usage data – what features are heavily used? Which are ignored?
6. Scenario Walkthroughs: Present potential workflows or feature ideas (low-fidelity mockups or simple descriptions) and ask for feedback. “How would you use this?” “What problems might this solve (or create) for you?”
7. Open Forums (Use Sparingly): Can be useful for broad awareness and gathering initial ideas, but often lack depth. Best combined with more targeted methods.
Turning Feedback into Your LMS Blueprint
Collecting feedback is only half the battle. The magic happens in synthesis and action:
1. Categorize & Analyze: Group feedback themes: Usability, Features, Integration, Reporting, Support, Accessibility, etc. Identify recurring pain points and frequently requested capabilities. Distinguish “must-haves” from “nice-to-haves.”
2. Prioritize Ruthlessly: Not all feedback can or should be implemented. Prioritize based on:
Impact: How many users does this affect? How significantly does it improve learning/teaching/efficiency?
Feasibility: What’s technically possible within budget and timeline?
Alignment: Does this support core institutional goals and learning objectives?
3. Define Clear Requirements: Transform prioritized feedback into concrete functional and non-functional requirements for your LMS. This becomes your core checklist for evaluating vendors or guiding custom development.
Example: Feedback: “Students constantly lose track of assignment deadlines scattered everywhere.” -> Requirement: “LMS must provide a centralized, personalized student dashboard displaying all upcoming deadlines across courses clearly.”
4. Communicate What You Heard (and What You Didn’t Do): Circle back! Share a summary of the key themes and priorities identified. Crucially, explain why certain popular requests might not be in the initial rollout (budget, complexity, lower priority). Transparency builds trust, even when you can’t deliver everything immediately.
5. Inform Implementation Strategy: Feedback doesn’t just shape what you build; it should inform how you roll it out. Did faculty express anxiety about change? Plan more robust training. Do students need simpler navigation? Prioritize intuitive design and onboarding resources.
The Bottom Line: Feedback is Fuel for Success
Asking for feedback before building your LMS isn’t about delaying progress. It’s about investing wisely. It’s the difference between delivering a tool that lands with a thud and delivering a solution that empowers your educators, engages your students, and genuinely enhances the learning experience. It uncovers hidden needs, prevents expensive mistakes, fosters crucial buy-in, and ultimately ensures your LMS project delivers real, measurable value. So, take a deep breath, pause before the build, and start asking those essential questions. The insights you gather will be the most valuable foundation your new learning platform can have.
Please indicate: Thinking In Educating » Before You Build That LMS: Why Asking for Feedback Isn’t Just Polite, It’s Essential