Skills Journey
Child mental health provider
User research, MVP, information architecture, visual design, design system
About Skills Journey
Skills Journey is a web system that helps specialists of the Child Development Centre create and manage treatment plans for their clients. I was responsible for conducting user research, exploring journey maps and designing the MVP.
The owner wanted a web system because she used a legacy system, the onboarding process for new staff was difficult and the experienced specialists' knowledge were non-transferrable to new staff. The owner needed new effective workflow.
User research
I conducted qualitative research using remote observation and interviews.
Remote observation allowed me to identify the pain points and challenges that specialists faced with the current technology and process.
Interviews helped me to understand the specialists’ emotions and motivations during specific activities.
I analysed the research data using thematic analysis and developed a set of themes that captured the users’ problems. I've created a board with users' quotes to remember why we design the new system:
“Assessment reports take up too much of my time”
“Writing emails with treatment plans and instructions for parents requires a lot of focus”
“I often forget to monitor the exercises’ progress”
“It’s a hassle to find and analyse past data”
“I don’t get enough feedback from my peers”
“It’s hard to review my teammate’s work without knowing their context”
Main problems
Routine tasks (like tracking progress, writing instructions and filling out assessment forms) take too long
The review process is inefficient and doesn't scale to a larger team
Automation
The main design idea was about automation. If the specialist creates a child’s health profile, the system suggests treatment plans, sends instructions to parents, generates reports and helps with tracking.
Information architecture
Then I created the structure and navigation of the new system. I enjoyed doing this because it helped me visualise and understand the product, and it helped to avoid rework later on.
In collaboration with developers I created a simple document that described the functionality, data structure (objects and relationships) and navigation of the system. This document made it possible for everyone to understand the product’s scope and vision.
Navigation and examples of some objects:
Solution
My main goals for designing the solution were:
Create a smooth and continuous flow so that the user knows what step they need to take at every moment
Support all the required functionality
Make the system easy to use
Exercises stats screen
Pain points solved:
Specialists were able to easily track exercises.
Specialists were able to effectively navigate through the stats.
Specialists were able to effectively navigate through their notes.
Specialists were able to easily update the exercise plan.
Assessment screen
Pain points solved:
Specialists had one simple page to fill out instead of different distributed forms and papers.
Reviewers had a page to glance over the overall child’s conditions.
Specialists were able to easily recall the overall child’s conditions.
Results
In 7 weeks, I designed the first version of a new product with desirable functionality, thoughtful navigation, scalable structure and user-friendly interfaces. I also created a design system to support consistency and effectiveness. During usability testing sessions specialists were excited about using the new system.
The key factors for a successful start were: the prioritization of requirements, the iterative design process, collaboration with the developers and close contact with the owner.
The expected business outcomes are:
Increased overall efficiency
Reduced costs for training new staff
Established streamlined processes
Next steps
The project is still ongoing and there are many features and improvements that I would like to work on next. Some of them are:
Creating knowledge base for this system
Implementing a notification system for reminders and feedback
I learned a lot from this project and I’m looking forward to seeing it grow and evolve. I’m grateful for the opportunity to work with such a passionate and dedicated team.
Skills Journey
Child mental health provider
User research, MVP, information architecture, visual design, design system
About Skills Journey
Skills Journey is a web system that helps specialists of the Child Development Centre create and manage treatment plans for their clients. I was responsible for conducting user research, exploring journey maps and designing the MVP.
The owner wanted a web system because she used a legacy system, the onboarding process for new staff was difficult and the experienced specialists' knowledge were non-transferrable to new staff. The owner needed new effective workflow.
User research
I conducted qualitative research using remote observation and interviews.
Remote observation allowed me to identify the pain points and challenges that specialists faced with the current technology and process.
Interviews helped me to understand the specialists’ emotions and motivations during specific activities.
I analysed the research data using thematic analysis and developed a set of themes that captured the users’ problems. I've created a board with users' quotes to remember why we design the new system:
“Assessment reports take up too much of my time”
“Writing emails with treatment plans and instructions for parents requires a lot of focus”
“I often forget to monitor the exercises’ progress”
“It’s a hassle to find and analyse past data”
“I don’t get enough feedback from my peers”
“It’s hard to review my teammate’s work without knowing their context”
Main problems
Routine tasks (like tracking progress, writing instructions and filling out assessment forms) take too long
The review process is inefficient and doesn't scale to a larger team
Automation
The main design idea was about automation. If the specialist creates a child’s health profile, the system suggests treatment plans, sends instructions to parents, generates reports and helps with tracking.
Information architecture
Then I created the structure and navigation of the new system. I enjoyed doing this because it helped me visualise and understand the product, and it helped to avoid rework later on.
In collaboration with developers I created a simple document that described the functionality, data structure (objects and relationships) and navigation of the system. This document made it possible for everyone to understand the product’s scope and vision.
Navigation and examples of some objects:
Solution
My main goals for designing the solution were:
Create a smooth and continuous flow so that the user knows what step they need to take at every moment
Support all the required functionality
Make the system easy to use
Exercises stats screen
Pain points solved:
Specialists were able to easily track exercises.
Specialists were able to effectively navigate through the stats.
Specialists were able to effectively navigate through their notes.
Specialists were able to easily update the exercise plan.
Assessment screen
Pain points solved:
Specialists had one simple page to fill out instead of different distributed forms and papers.
Reviewers had a page to glance over the overall child’s conditions.
Specialists were able to easily recall the overall child’s conditions.
Results
In 7 weeks, I designed the first version of a new product with desirable functionality, thoughtful navigation, scalable structure and user-friendly interfaces. I also created a design system to support consistency and effectiveness. During usability testing sessions specialists were excited about using the new system.
The key factors for a successful start were: the prioritization of requirements, the iterative design process, collaboration with the developers and close contact with the owner.
The expected business outcomes are:
Increased overall efficiency
Reduced costs for training new staff
Established streamlined processes
Next steps
The project is still ongoing and there are many features and improvements that I would like to work on next. Some of them are:
Creating knowledge base for this system
Implementing a notification system for reminders and feedback
I learned a lot from this project and I’m looking forward to seeing it grow and evolve. I’m grateful for the opportunity to work with such a passionate and dedicated team.
Skills Journey
Child mental health provider
User research, MVP, information architecture, visual design, design system
About Skills Journey
Skills Journey is a web system that helps specialists of the Child Development Centre create and manage treatment plans for their clients. I was responsible for conducting user research, exploring journey maps and designing the MVP.
The owner wanted a web system because she used a legacy system, the onboarding process for new staff was difficult and the experienced specialists' knowledge were non-transferrable to new staff. The owner needed new effective workflow.
User research
I conducted qualitative research using remote observation and interviews.
Remote observation allowed me to identify the pain points and challenges that specialists faced with the current technology and process.
Interviews helped me to understand the specialists’ emotions and motivations during specific activities.
I analysed the research data using thematic analysis and developed a set of themes that captured the users’ problems. I've created a board with users' quotes to remember why we design the new system:
“Assessment reports take up too much of my time”
“Writing emails with treatment plans and instructions for parents requires a lot of focus”
“I often forget to monitor the exercises’ progress”
“It’s a hassle to find and analyse past data”
“I don’t get enough feedback from my peers”
“It’s hard to review my teammate’s work without knowing their context”
Main problems
Routine tasks (like tracking progress, writing instructions and filling out assessment forms) take too long
The review process is inefficient and doesn't scale to a larger team
Automation
The main design idea was about automation. If the specialist creates a child’s health profile, the system suggests treatment plans, sends instructions to parents, generates reports and helps with tracking.
Information architecture
Then I created the structure and navigation of the new system. I enjoyed doing this because it helped me visualise and understand the product, and it helped to avoid rework later on.
In collaboration with developers I created a simple document that described the functionality, data structure (objects and relationships) and navigation of the system. This document made it possible for everyone to understand the product’s scope and vision.
Navigation and examples of some objects:
Solution
My main goals for designing the solution were:
Create a smooth and continuous flow so that the user knows what step they need to take at every moment
Support all the required functionality
Make the system easy to use
Exercises stats screen
Pain points solved:
Specialists were able to easily track exercises.
Specialists were able to effectively navigate through the stats.
Specialists were able to effectively navigate through their notes.
Specialists were able to easily update the exercise plan.
Assessment screen
Pain points solved:
Specialists had one simple page to fill out instead of different distributed forms and papers.
Reviewers had a page to glance over the overall child’s conditions.
Specialists were able to easily recall the overall child’s conditions.
Results
In 7 weeks, I designed the first version of a new product with desirable functionality, thoughtful navigation, scalable structure and user-friendly interfaces. I also created a design system to support consistency and effectiveness. During usability testing sessions specialists were excited about using the new system.
The key factors for a successful start were: the prioritization of requirements, the iterative design process, collaboration with the developers and close contact with the owner.
The expected business outcomes are:
Increased overall efficiency
Reduced costs for training new staff
Established streamlined processes
Next steps
The project is still ongoing and there are many features and improvements that I would like to work on next. Some of them are:
Creating knowledge base for this system
Implementing a notification system for reminders and feedback
I learned a lot from this project and I’m looking forward to seeing it grow and evolve. I’m grateful for the opportunity to work with such a passionate and dedicated team.
