Personalizing the intervention process for child disability specialists
NeuroLeap Corp • Feb 2025 - May 2025 • Sole Designer and Researcher
Background
Buy, use, and sell intervention activities that are effectively tailored for children with disabilities.
Child specialists need tailored, engaging, and community-driven intervention activities for their children with disabilities. NLONE Cloud is a one-stop platform where specialists are able to buy, use, and create personalized activities for their children.
The Problem:
The current interface lacked real-life applicability and was mired with failed interactions.
Discovery
Understanding + uncovering key usability problems
I conducted usability testing with specialists on the 3 central tasks of the app, tracking the number of errors users made and their user rating (1-10).
Findings
Tasks were unfamiliar, overwhelming, and misaligned with their workflow.
After testing, I mapped out the user errors, identifying “hotspots” of confusion.
A Hidden Checkout Process
Users could not find prices/checkout process, which were hidden in unfamiliar icons.
An overwhelming interface
Child specialists could not understand the grading buttons for activities, which was cluttered with buttons and images with no visual hierarchy or grouping.
Lack of workflow similarity
When specialists were making their own activities, the process felt constrained and limited in customisability because of the required pre-categorization fields, preventing specialists from organizing questions in their own mental models.
Design goals
The new experience should be...
Low-friction
Primary tasks should be intuitive, easily discoverable, and broken down in to steps.
Workflow-aligned
Product’s experience and capabilities should parallel the complex workflow needs of child disability specialists.
Decision 1
Using activities should feel simple and focused
Pushing for clarity over complexity
As I refined my understanding of the product with the team and received their feedback, I was able to push towards the best layout possible, which often meant deprioritizing minor functionalities to highlight important ones.
Show Previous Design
An iterative process
It took me several tries to find a layout that the team and I were happy with. However, as I refined my understanding of the product with the team it was easier to come to this conclusion once more.
Decision 2
Buying an activity should feel familiar
Leveraging familiar user design patterns
Similar to popular ecommerce sites such as Amazon, shop.com, and eBay, users understand that clicking on product cards leads to a product page with a checkout option.
Decision 3
Making activity questions should be flexible and workflow-aligned
More customization, without added complexity
A step-by-step process progressively discloses information to users without overwhelming them. By switching to a multi-page layout, we are able to fit in more questions and customization without sacrificing usability.
Show Previous Design
Categorization is optional
A step-by-step process progressively discloses information to users without overwhelming them. By switching to a multi-page layout, we are able to fit in more questions and customization without sacrificing usability.
Show Previous Design
User test validation
Usability testing #2 showed improvements, but activity-making was hard to find...
Categorization is optional
A step-by-step process progressively discloses information to users without overwhelming them. By switching to a multi-page layout, we are able to fit in more questions and customization without sacrificing usability.
Show Previous Design
Final Design
Buying an activity, 91% less user errors.
Using an activity, 95% less user errors.
Making activities, 65% less user errors.