Most EdTech companies now understand the importance of UX research in developing products that meet the needs of students, instructors, and administrators. But the thing about UX research is that it’s actually only the first half of the equation. Without thoughtfully prepared reporting, your UX research is really just a pool of data. By adopting effective presentation strategies for reporting research results you can ensure your findings are carried through the rest of the development process.
Over the past few years, the UX of EdTech products has improved by leaps and bounds. That’s true at the individual application level, anyway. But it’s a whole different story when you look at the user experience of product integrations that bridge two or more applications. It’s hard enough to integrate platforms in situations where you have complete control, but it can be incredibly difficult to integrate third-party platforms in a meaningful, seamless fashion.
EdTech companies are increasingly recognizing the importance of UX research in successful product development. The numbers bear this out, with industry surveys showing an uptick in companies who identify the need to conduct more in-depth customer research as digital products continue to revolutionize the marketplace. That’s a step in the right direction, for sure. But the reality is that many product teams remain uncertain about when and how to incorporate UX research.
Your EdTech company is thriving. Your product is growing and so too must your team. It’s a good problem to have, of course. But for companies considering working with an outside UX agency, it can be hard to know exactly how to gauge their value. It’s easy to see why this can feel like such a challenging decision. The idea of spinning up an internal team is daunting, but the idea of working with an agency brings its own set of concerns and unknowns that can lead to misinformed buying decisions.
The launch of a new product represents a huge leap, but it’s really just the first big step in a series of many. Over the course of a healthy product’s lifespan, your team will continue to work inside the product for years to come, fixing bugs, pushing out updates, making UX improvements, and adding new features. New features require efforts from UX, engineering, and product teams with each leading at different times.
