Summary
Designing an improved AAC platform for kids with speech impediments
Tools + Processes
UXR, product strategy, interaction design
Duration
September 2020 to February 2021
SUMMARY
The Opportunity
CBoard allows kids with speech issues to communicate their daily thoughts. However, CBoard is unable to support kids in developing new communication + learning styles as they get older.
Solution
CBoard can adopt features (like text-to-speech) that allow for personalization and customization tailored to each child's unique communication style.
PROJECT BEGINNINGS
CBoard is an Augmentative and Alternative Communication (AAC) web application funded by UNICEF that helps children with speech impediments communicate.
After launching CBoard through a pilot program, the creators approached our team and tasked us with creating a native, mobile version of the app.
We thought we could do one better and help improve the app as well. Here are our findings and what it led to:
Younger kids want to express themselves and develop confidence in their ability to communicate
User Needs:
Getting feedback and encouragement to aid learning
Variety in communication tools as they develop preferences
Older kids want to improve their fluency in communication and express more complex thoughts
User Needs:
Ability to personalize their communication experience
Require tools that allow for more nuanced and expressive communication, including predictive text and customizable phrases
HMW honor different learning styles and age groups?
HMW make customization easy?
HMW cater to different learning styles?
THE PROBLEM
HMW help kids with speech impediments develop their learning and communication styles over time as they age?
1
HMW honor different learning styles and age groups?
2
HMW make customization and personalization easy?
3
HMW cater to different learning styles?
Since this was our team’s first time designing an AAC platform, we started, we wanted to gain a better understanding of the UX considerations that would be front and center for such applications.
These became our defining principles as we ideated and made decisions:
Easy customization is essential so the app can foster a sense of ownership and engagement in a users’ journey.
Building multiple access methods ensures inclusivity and accessibility for users w/ diverse styles.
Learning from a user’s action so the app is tailored to their needs can enhance efficiency and user satisfaction.
Saved Phrases
Letting users save and personalize common patterns to make them quicker.
Predictive Text
Having the app predict and smart-populate phrases so users can be more efficient and explore new phrases.
Text to Speech
Giving users a new method of communicating especially for more advanced phrases.
I primarily focused on designing the Text-to-Speech feature.
I wrestled with where the entry point for TTS should be and how it should be treated.
Option 1
Entry Point: Tap on text bar to begin typing
Treatment: Plain text
Option 2
Entry Point: First tile in grid
Treatment: Tile
We ultimately landed on a decision that was a compromise between the two. These were a few things I weighed in making my decision.
Ease of Access
Users should navigate the feature without potentially interrupting their workflow.
Consistent Position
It should be a consistent element where users can easily predict its behavior and location.
Integration with Current Mental Models
We want to leverage the existing design language, maintaining consistency and familiarity for users.
Text-to-speech (TTS) is a different style of AAC that goes beyond CBoard’s current functionalities.
Instead of clicking on pre-made symbols, kids have the option of typing words.
Those words then save as tiles.
TTS solves the design problem by encouraging higher-level learning that exceeds symbols and is suitable for kids as they get older.
Divide and Conquer
In a larger team of designers, effectively dividing and tackling design work is crucial for maintaining productivity and cohesion, particularly in a virtual setting.
Breaking down complex design tasks into smaller, manageable components allows for parallel workstreams and ensures steady progress towards project goals. Ultimately, fostering a culture of trust, transparency, and accountability empowers team members to collaborate effectively.
Building for AAC users
Empathizing with users was essential in this project, as it allowed us to gain insights into the unique experiences of those who rely on AAC technologies. By listening attentively and observing how users interact with existing solutions, we were able to address functional requirements but also resonate emotionally with users, fostering a sense of empowerment, dignity, and inclusion.
LEARNINGS