top of page

Transforming Support

Better error messaging means more time on task and less strain on customer service

Opportunity

Teacher interviews revealed that unclear error pop-ups during student assessments added stress for both students and proctors.

Screenshot 2024-09-06 at 10.09_edited.jp
existing error messages show varying designs

Research

Discovery: Alongside developers, audited all existing error messaging and used Heap to identify the most frequent.

Stakeholder Alignment: Audit and interviews with call center staff and teachers uncovered key issues:​

  • Off-brand designs

  • Unclear next actions for troubleshooting

  • Robotic, technical tone

  • Lack of student-friendly language

  • Spanish speakers in a Spanish test get English errors

 

KPIs: Improved comprehension, fewer call center queries, faster query resolution, full language availability

Challenges

Bringing these error messages into the design system is relatively straightforward.

The small challenge of defining a clear hierarchy of next steps to troubleshoot these errors is merely a matter of working through them one by one with our developers.


The main challenge is our wide range of users, each of  whom deserve messaging that communicates to them:

  • Varying literacy levels from pre-K to adults

  • Both Scored Tests (with proctors) and Practice Tests (no proctor guaranteed)

  • Two supported languages

How do we speak to all users where they are?

Strategy

Screenshot 2024-09-10 at 2.54.39 PM.png

We have the means to detect the language and type of test, so rather than work for a single universal design, we can best meet everyone's needs with inclusive design. ​The importance of reaching everyone warrants the small additional investment of Spanish translation and making alternate copy for students who may not have a proctor.​

Language support: Ensure all messaging is fully bilingual.

​​

Create dual set of messaging, one for Scored Tests and one for Practice Tests.

  • For Scored Tests, make the student's primary task to pull in the proctor for any non-basic trouble-shooting. Use design to differentiate the part of the message aimed at students and that aimed at proctors.

  • For Practice Tests, use visuals and the most basic language possible to maximize communication:​

    • ​​Pre-literate Students: Use iconography & visuals to supplement text.

    • Literate Students: Provide clear, actionable messages when applicable.

The Design

  • Language: Worked with Spanish copywriter for accurate translations with accessible wording for new readers.

  • Visual cues: A raised hand icon signals students of all reading levels to ask for help.

  • Clarity: Font size and placement differentiate student instructions from proctor guidance. With the copywriter to optimize for young readers

  • Proctor visibility: A full-screen color change to help proctors spot issues quickly.

  • Lastly, the idea of an error message code number to help users quickly identify the issue was very popular with the call center professionals.​

errorMessages_GrowthB.png
errorMessages_GrowthA_edited.jpg

Testing and Next Steps


Testing & Implementation
Some students felt the full-screen alert could make them worry about lost any progress made before the error.

A semi-opaque background where students could still see where they were lowered this apprehension.

Next Steps
Testing with a larger cohort of students, including those with disabilities, and redesigning based on that feedback was unfortunately put off until future iterations.

bottom of page