Insights

When you think of inclusivity in EdTech product design, your mind probably jumps to accessible design principles. But truly inclusive design starts long before UX designers put pixels to prototypes. In fact, the seeds of inclusivity are planted in the earliest UX research stages. And it all begins with how you recruit and relate to test users. 

The discovery phase sets the stage for the successful launch of your EdTech product. Our latest resource guides you through the process and the tools to maximize this first step in the UX process. The result? Stronger alignment among your team and a better experience for your users.

In the world of EdTech product development, accumulating some degree of debt is acceptable. Minimal levels of design debt (design-related inconsistencies that occur within a product over time) or technical debt (shortcuts in development that prioritize speed over perfect code) are a reflection that you’re constantly evolving and updating your product. What happens, though, when multiple debts mount over time and cause increased user frustration? The result is trust debt — an increasing lack of confidence in your product and your brand.

Sure, it would be ideal if you could sit in on all your EdTech product’s test sessions. But as a product owner, it probably feels like there are never enough hours in the day. You simply can’t be present every time users test your product. But you also don’t have to wait until testing is complete to get up to date. When you access this Early Research Recap Worksheet, you can squeeze the most value out of each round of UX research. It provides a thorough report of what’s happening, as it’s happening — and the answers to your most pressing questions.

A speedier design process and a better end-product are possible when your UX designers and researchers work in lockstep. And that requires their continuous communication at all points of your product’s development process — especially in user testing. Download this free user testing worksheet that our UX designers and researchers created together in order to: track important user testing dates and links, describe users and research goals, and provide a list of research questions, tasks, and subtasks.