Explore ways to increase the adoption of CTAT, a tutor-writing software, in higher education settings.
The design and build (demo) of a new landing page and site map for CTAT.
Role UX designer
Team Grace Guo (researcher), Chris Feng (project manager), Siting Jin (developer)
The Cognitive Tutor Authoring Tools (CTAT) allow instructors to create intelligent tutors, which are powerful for their ability to provide contextual feedback as students work through problems. However, we found that potential users find the software difficult to understand, much less use.
For students, fresh course material and feedback are both crucial to their learning, yet immensely time consuming for instructors. CTAT could alleviate many of these issues by providing contextual feedback at scale. However, many instructors push back against adopting yet another education management tool.
Faculty are busy...if they’re going to put in time to learn new software, it better be worth it.
Through competitive analysis and interviews, we learned about common useful features of educational technologies, and CTAT's competitive edge. However, CTAT is also more complicated and faces 3 major barriers to adoption:
Of the 3, we ruled #1 as out of scope, as it would involve altering CTAT’s code base.
Based on our research findings, we decided to aim to help instructors better understand how CTAT can help them in order to increase interest and adoption.
Current User Journey
Desired User Journey
For deliverables, we identified marketing and onboarding as entry points to make users excited about CTAT.
The existing site had little to no material, so we spent time talking to existing users and researching the education technologies field to find CTAT's competitive edge.
We found that the layout of exploration B worked best to deliver information to users. I iterated on ways to improve engagement, reduce cognitive load, and improve visual appeal.
I like that there are images to quickly give me a sense of the product, but I can also scroll to easily see more information.
Beyond the home page, the team brainstormed other content that would be helpful. Among our final features were a tutor demo gallery, tutorials, and complete software documentation.
The gallery would showcase live interactive tutors made by CTAT users. In other products like Principle and Unity, we found that concrete demos quickly helped people understand the product's purpose and got them excited about the possibilities before them.
We envisioned sorting the tutorials with clear hierarchy, so users can easily find relevant topics. We also would like to have reformatted the existing content to make it easier to consume.
The behavior graph looks super useful. If that’s a basic topic, I want to know what else [CTAT] can do!
Though users showed better learning and understanding of CTAT in our quick A/B testing, we did not track the effectiveness of our design on CTAT adoption over time. Next steps might include: