Kebbi can play, chat, tell stories or dance, and much more. Kebbi has facial recognition and object recognition features to make interactions more playful.
Our research found the onboarding tutorial was not engaging. The problems included:
Attract people by telling a background story of a robot world through an interesting interaction:
So, why weren't users satisfied with the previous onboarding process?
Based on the survey results of previous customer satisfaction, we analyzed the data that was related to onboarding and tutorial. Furthermore, I searched the forums and unboxing articles/videos of users.
Insights:
Tutorials included 7 sections: Sensor Tutorial, Listening Tutorial, Wake up Tutorial, Recap, Object Recognition Tutorial, Accessory Tutorial, and Menu Tutorial. I would like to take the Wake up Tutorial as an example.
.png)
Insights:
We conducted 3 semi-structured interviews with teachers and parents to understand the conversational habits of children. Also, we visited an elementary school to observe how children interact with the robot.
.png)
Identified key insights from the research activities with affinity diagramming
Based on the results of the secondary studies, observations, and interviews, we identified 4 key takeaways for our onboarding redesign:
How might we provide an engaging multimodel experience for children with a story?
As the project owner, I was involved in the story workshop with the screenwriter and the animation to built a robot world and Kebbi’s persona. With the persona, we, the onboarding team, started to brainstorm how Kebbi meets with humans for the first time and how Kebbi may behave in this situation.
I mapped out the original settings and onboarding process and decided on the key interactions. Other functions in the previous rituals will be teached separately in each app’s onboarding.
Based on the storyboard, we discussed how the robot presents itself. Quickly drawing the interaction on papers and conducting the Wizard of Oz testing on the utterance, we took into account all the interfaces of the robot, including screen, sound, dialogue, body movement, and light.
“If you want to know more about what I can do, you can open the function list to guide you.”
“I'm good at many things. Let me perform them for you. For example, I can tell you stories! WOOOOO~ I can also sing and dance with you. I also have a lot of games. Now, let's play together!”
The engineer provided ideas based on his technical background and help us make the design implementable. Here are some examples:
WiFi setup came before updates, so animations could show properly.
We only updated the UI to match the story, keeping functionality unchanged due to limited development time.
Throughout the process, we discussed how the robot presents itself from large pictures to specific performances. Quickly drawing the interaction on papers, conducting the Wizard of Oz testing on the utterance, and building the high-fi prototypes.
What I have learned?
Children are creative and imaginative, which would have helped us come up with more interesting stories. Furthermore, Participatory design using different techniques, such as workshops and interviews, could have helped users understand the needs and involve them in the design.
Due to the limitation of time to meet the date of product release, we only had about 3 weeks for the interaction design. Therefore, I only tested the process internally and asked for feedback from an elementary school teacher. However, children’s interests and cognitive skills varied in different stages. Testing with child users would allow us to discover how they interact with the robot.
I involved members from different functions in the decision-making processes, broke the project into manageable tasks, and assigned them based on members’ strengths. Therefore, we coordinated but conducted defined tasks independently of each other with crystal-clear goals and expectations. It also gave us a mutual understanding of each other.
As the researcher, conversation designer, and project owner, I needed to quickly switch between the different roles. Collaborating with stakeholders of the animation team and engineering team, I identified the story settings and development feasibility then brought the takeaways back to the onboarding team. These experiences strongly improved my task management, time management, and communication skills.
Crafted with love and a touch of matcha magic ❣️ 🍵