If you’re an advocate for user research in an organization that doesn’t value it, you might feel like you’re shouting into the wind sometimes. Too often, stakeholders (and we’re talking about executive leadership and even designer/developers) consider research an obstacle to rapidly launching a product or update. Recruiting users to interview, analyzing results and reporting on findings takes time, and in a quick-turn release cycle it may be too late by the time you get the answers you need.
From administrative tasks like taking attendance and grading quizzes to features that enable students to learn and succeed, EdTech products have become more and more powerful. But that power can make these tools more complicated for users. Learn how to align tools with common mental models from search, retail, and gaming.
Improving the on-ramp to your product makes users confident in their choice and increases their satisfaction. The bottom-line benefit of a better onboarding experience comes from both greater customer retention and reduced customer service.
Often, design systems are treated as “one and done” initiatives — drafted, agreed upon and set in stone. Many a design team has embarked on a fool’s errand, thinking they could anticipate every design need that may arise in the future. If you instead adopt a continuous release approach for ongoing improvements to guidelines, you essentially mirror the product development process itself.
Remember that you’re creating products for two audiences with distinct but overlapping needs. Instructors select the tools for their classrooms, so tech companies often develop products with them in mind. But for every one instructor there may be 600 student users, and if something goes wrong with the app, instructors get 600 emails about the problem.
