The Smartest Thing You’ll Do Before Building Your LMS: Ask for Feedback (Seriously!)
So, you’re ready to take the plunge and build your own Learning Management System (LMS). That’s exciting! It means you’re committed to enhancing learning, streamlining processes, and maybe even shaking things up a bit. But hold on just a moment before you dive headfirst into coding or signing contracts. There’s one crucial, often underestimated step that can make the difference between an LMS that truly rocks and one that just… well, rocks the boat: asking for feedback.
Think about it. You’re potentially investing significant time, money, and energy into this platform. It will become the digital heart of your learning environment, whether it’s for your company, school, university, or training organisation. Doesn’t it make sense to ensure it actually works for the people who will use it day in and day out? Skipping this step is like designing a car without talking to drivers – you might end up with something sleek, but completely unusable on the roads they actually travel.
Why “Just Building It” is a Risky Shortcut
We get it. The pressure to deliver can be immense. Stakeholders want results, budgets need using, and the allure of a shiny new system is strong. Jumping straight into development seems efficient. But here’s the reality check:
1. You’re Not Your User (Probably): Unless you’ll be the only person using every single feature of the LMS, your perspective is limited. Instructors have different needs than learners. Administrators have different concerns than content creators. What seems intuitive to the tech team might be baffling for a busy teacher.
2. Unseen Problems Lurk: You might have brilliant ideas about workflows or features, but existing users know the real pain points. They know where the current system (even if it’s just email and shared drives) causes friction, wastes time, or creates unnecessary complexity. They know the workarounds they’ve invented – valuable clues about where your new system needs to excel.
3. Avoiding Expensive “Oops” Moments: Discovering major usability issues or missing critical functionality after the system is built is incredibly costly. Fixing architecture flaws post-launch is orders of magnitude harder and more expensive than adjusting plans during the design phase. Feedback upfront helps you build it right the first time.
4. Building Buy-In is Half the Battle: People are naturally wary of change, especially big tech changes that impact their daily work. By asking for their input before you build, you’re sending a powerful message: “Your experience matters. We value your expertise.” This fosters ownership and makes users far more likely to embrace the new system when it launches, rather than resisting it.
Asking the Right Questions (to the Right People)
“Can I have some feedback?” is too vague. You need targeted questions directed at specific stakeholder groups. Here’s how to break it down:
For Learners (Students, Trainees, Employees):
“What’s the most frustrating part of accessing learning materials or courses right now?”
“How do you prefer to track your progress? What motivates you?”
“What features do you wish existed to make learning easier or more engaging?”
“What devices do you primarily use for learning?”
“What do you dislike about other online learning platforms you’ve used?”
For Instructors/Trainers/Facilitators:
“What tasks related to teaching/training take up the most unnecessary time?”
“How do you currently communicate with learners? What works/doesn’t work?”
“What kind of reporting or analytics would be most valuable for you to understand learner progress?”
“What features are absolutely essential for you to deliver effective learning? What would be ‘nice to have’?”
“What are your biggest challenges with grading, feedback, or managing assignments online?”
“How do you prefer to structure and deliver content?”
For Administrators/IT/Support Staff:
“What are our biggest technical headaches related to learning tech right now?”
“What integration points are non-negotiable? (e.g., HRIS, SIS, SSO, CRM)”
“What are our key security and compliance requirements?”
“What level of support burden is acceptable? What features could reduce it?”
“What reporting capabilities are needed for leadership and compliance?”
For Leadership/Decision Makers:
“What are the top 3 business/educational goals this new LMS must support?”
“How will we measure the success of this investment? (e.g., increased completion rates, reduced training costs, improved skill proficiency)”
“What are the budget and timeline constraints we absolutely must work within?”
How to Gather Feedback Effectively (Without Overwhelming Anyone)
Don’t just blast out a massive, generic survey. Be strategic:
1. Mix Your Methods:
Short, Focused Surveys: Use these for quantitative questions or quick polls (e.g., ranking features). Keep them very concise.
Targeted Interviews: Schedule 30-45 minute interviews with key representatives from each stakeholder group (e.g., 2-3 super users, 2 new instructors, 2 administrators). Dive deep into their workflows and pain points. These are goldmines.
Focus Groups: Bring together small groups of similar stakeholders (e.g., learners, instructors) for guided discussions. Group dynamics can spark valuable insights you might not get individually.
Observation (If Possible): Watch people interact with current systems. Where do they hesitate? What workarounds do they use? This reveals unspoken frustrations.
2. Frame it Right: Explain why you’re asking (“We’re building something new and want it to work brilliantly for YOU”) and how their input will be used (“This feedback will directly shape our requirements and design”). Assure anonymity where appropriate to get honest answers.
3. Make it Easy: Choose accessible tools and keep surveys short. Respect people’s time. Offer incentives if feasible (coffee vouchers, small gift cards).
4. Listen More Than You Talk: In interviews and focus groups, ask open-ended questions (“Tell me about…”, “Describe a time when…”) and then listen. Avoid leading questions that hint at the answer you want.
5. Look for Patterns: Don’t build based on one person’s pet feature request. Analyze the feedback across all sources. What are the recurring themes? What are the critical pain points mentioned by multiple people? What are the common goals?
Turning Feedback into LMS Gold
Collecting feedback is step one. The magic happens in the analysis and application:
1. Synthesize: Organize the feedback into clear categories: Pain Points, Desired Features, Technical Requirements, Success Metrics, Usability Concerns.
2. Prioritize Ruthlessly: Not all feedback is created equal. Use a framework like MoSCoW:
Must Have: Critical for launch. Non-negotiable for core functionality or compliance.
Should Have: Important but not vital for launch. High value.
Could Have: Desirable but lower impact. Nice if feasible.
Won’t Have (this time): Acknowledge it, but set it aside for future phases.
3. Translate into Requirements: Turn the “Must Haves” and key “Should Haves” into clear, actionable requirements for your development team or vendor selection process. E.g., “The system MUST allow instructors to provide audio feedback on assignments” or “Learners MUST be able to track completion progress visually on their dashboard.”
4. Inform Design & Workflow: Use learner and instructor feedback to map out intuitive user journeys. Where should key features live? How can complex tasks be simplified? Feedback often reveals where simplicity trumps fancy features.
5. Set Realistic Expectations: Share back a summary of what you heard and how you’re prioritizing it. Be transparent about what won’t make it into the initial build and why. This shows you listened and manages expectations. “We heard loud and clear that X is a major pain point, so it’s a top priority. Feature Y was requested but is lower priority right now due to Z.”
6. Keep the Loop Open: Feedback isn’t a one-and-done task. Continue gathering input during development (e.g., usability testing prototypes) and after launch. It’s an ongoing conversation for continuous improvement.
The Ultimate Payoff: An LMS That Works (For Everyone)
Taking the time to genuinely ask, listen, and act on feedback before you build your LMS isn’t a delay; it’s an investment. An investment in:
User Adoption: People are more likely to use and champion a system they helped shape.
Effectiveness: A platform that directly addresses real needs drives better learning outcomes and operational efficiency.
ROI: Avoiding costly rebuilds and feature bloat ensures your money is spent wisely.
Smoother Implementation: Knowing the requirements upfront leads to a more focused and predictable development process.
Reduced Support Burden: An intuitive system based on user workflows means fewer confused helpdesk tickets.
Building an LMS is a significant undertaking. By starting with feedback, you’re not just building software; you’re building a solution tailored to the people who matter most – the ones who will use it to learn, teach, and grow. You’re building a foundation for success. So, take a deep breath, pause the coding frenzy for a moment, and start asking those crucial questions. Your future LMS – and its grateful users – will thank you for it. What’s the first question you’ll ask?
Please indicate: Thinking In Educating » The Smartest Thing You’ll Do Before Building Your LMS: Ask for Feedback (Seriously