macbook-3macbook-3

Reimagined a childcare management app.

 

The app is a childcare management application based in Australia. The app helps users to record complex data series of children for the business’ records, parent‘s and Government’s references. The users would be able to record data, set a reminder and submit data.

The Challenge

 

The app has tons of features, from set a reminder, view and generate reports, check in and out children, create rooms, generate price per hour for the educator, submit reports, send notifications via email and SMS, and even multi-tabbing. Though, this feature may increase the experience since one doesn’t need to use any other apps to achieve their goal and to get their work done, however, the construction and arrangement of the features and information seem to be overwhelming for first-time users.

My Role

 

On this project, I was the UX/UI Designer - team of one. That being said I was responsible for the whole UX journey: strategy, remote user research, market comparison, requirement gathering, wireframing, prototyping, remote user testing, UI and visual design. I collaborated closely with the developers and the team in Australia for remote user research and user testing.

The process

 

Immersion to the project

Due to tons of feature and complex information and requirements, I immersed myself to the application itself for 1 week. I tried myself using the app to know the process from data recording till submitting the data. I also interviewed the stakeholders to better understand the goals and objectives of the project as well as the business.

Gathering existing feedbacks

The first thing that I did after I was comfortable with the application was to look into the user feedbacks from the customer support records. These feedbacks were great insights to know and pin the pain points, interaction gaps, and content gaps. These are the main insights from support record.

 

  • Navigation bar is too cluttered making one couldn’t identify which one which.
  • Lack of information and guidance while editing a child’s data.
  • Overwhelming data in operating hours

User research

I also interviewed the stakeholders to find out more about who their users are. I developed a survey and with the help of the team in Australia gathering some insights about the users, what their motivations are, what they care about the most, what frustrates them, are there any of their goals that aren’t being achieved, their usual environment and interactions.

Developed few personas based on findings to really know who my users are

Developed new information architecture

With the help of the team in Australia, the users and I collaboratively worked to develop a new navigation structure that was much more easy to scan and identify. I used Trello to help me conducting the card sorting method so that the users easily move cards around and group them into lists.

Competitor comparison review

I spent time looking through a series of similar applications - indirect and direct competitors and industry. Since this is a management app which records tons yet useful data, The App is basically a CRM app. I looked into a couple of competitors app as well to find any design opportunity (new features).

User testing

I gathered all of the insights and created wireframes. For remote testing, I prototyped the design on MarvelApp. The team in Australia asked users to test it, some face to face and some via call. These testings are to find as many pain points as possible.

Frustrations and Motivations

We’ve iterated the prototype twice and the majority of the user mentioned about the left navigation seemed to be confusing. Some stated the reason because they were accustomed to the current top navigation. Other than that these were the pain points from users

 

  • Navigation bar is too cluttered making one couldn’t identify which one which.
  • Lack of information and guidance while editing a child’s data.
  • Overwhelming data in operating hours

The neat new UI and generous white space were however helped a lot.

Designs and Outcomes

 

Once I’ve learned what the users expect to see, and how they interacted with the prototypes, I took my time to create the UI design based on the grey wireframes. Here’s the small selection of designs in high fidelity that I’ve created during various iterations.

Above/

The first thing that the user would do for the first time is to record children’s data. Since there are a lot of things to be recorded this has taken too much time of the user. I incorporated the findings from card sorting and grouped personal data into one. This way, the user would have a much larger overview of the child and himself/herself.

 

A progressive disclosure is being used here so the users will get the information they need first and would click more if they want to know more.

 

I also incorporated tags and mini info in necessary data so the more important data are easy to be identified.

 

I also developed a new tone of voice instead of using Educator’s Profile, I changed it to My Profile to create a sense of ownership.

Above/

Operating hours were designed much simpler and easy to understand. In lieu of combining different type of dates, I separated them into 3 section based on its behaviour: regular, custom, and holiday. This way, the information is much clearer and easy to scan and identify.

Above/

Reminder is now clearer. I used conventional colour to identify alerts and notification. This is to enable and familiar users with the reminder app that they use perhaps daily on their phone.

Above/

Children page will look similar but will have a much detailed information. I also added shortcut for users to contact children’s parents/guardians or to call them. In Case of Emergency contact is visible and easy to identify.

Above/

Designing a table could be tricky. However, I managed to identify what information is important for the users. I also identified that majority of users expected to see a report button on this page due to the common additional buttons found in most list like this one.

Above/

I grouped email from similar type of communnication, email notification from business owner & parent portalinto, into one communication centre page. On this page, the user would be able to view the email they sent to their centre as well as the communications sent to the parents.

Looking back

 

After various of iterations, big amount of coffee each morning, and Google hangout sessions with team in Australia, I managed to created the User Interface, complete with the visual design. I wanted to keep the interface simple and minimal, yet colourful as well as playful as well. Though, the app won’t be used by the children, it is nice to have colours as they can quickly inform the users what he/she can interact which and where the important piece of information can be found.

Entering data should be fun and easy

Educators in childminder would use most of their time attending the children, and the application should allow them to do their work, as opposed to being stress and might affect the work quality and the children. There are some data that make the design cluttered but it can’t be avoided because it is part of the requirements.

 

My overall goal was to make this application useful and aesthetically pleasant.

Position
Senior Designer

Responsibilities
UX/UI, Prototype, Research, Visual Design

For
Kidsoft