TINY TALES
OVERVIEW
Designed to allow busy parents and their children easy access to the books and stories they love, making bedtime a more seamless experience.
This is a personal and conceptual project I completed as a part of my coursework for Springboard utilizing Google’s Design Sprint methodology.
ROLE
Product Designer
Product Strategy, User Research, Interaction, Wireframing, Visual Design, Prototyping & Testing
DURATION
5 Day Design Sprint
DAY 1: Understand & Map
THE PROMPT
Tiny Tales is an application for parents who want to quickly and easily choose stories to read with their children that allows them to read to any or all of their children age and reading level appropriate stories without spending too much time browsing at bedtime.
Interviews + Problem Discovery
Interviews were conducted with 5 end users - parents with young children under 10 - where participants were asked about how they choose stories to read to their children.
Parents who read to their children often have little time at bedtime to make a quick story choice that is age/ reading level appropriate. Parents may be reading to multiple children at different reading levels at once and finding a book that is suitable to both age ranges can be challenging.
I honed in on the most commonly mentioned problems parents had and identified the three areas that I would design for in the final product.
Problem 1
Parents want to spend less time looking for a book to read and more time reading to their children
Problem 2
Parents want to be able to quickly find books on topics that their children are specifically interested in
Problem 3
Parents like getting recommendations from friends or family members on books they should read to their kids.
User Map & Journey
It was important for me throughout the design process to keep in mind that my user was going to be the parent choosing stories to read to their children and not the children themselves. I created a user journey to map out all the thoughts, feelings, and tasks our user (Claire) would be performing at each stage. This helped me to determine what actions I would be designing for when it came to the ideation phase.
DAY 2: SKETCH
DAY 3: DECIDE
WIREFRAMES
I used my sketches to create some quick wireframes that would become the basis for high fidelity designs. This is a way for me to quickly make decisions about hierarchy and layout as well as verify that my ideas were working.
PROBLEM SOLVING
DAY 4: PROTOTYPE
Branding & Visual Language
For the logo, I wanted to reflect the whimsicality of a children’s reading app as well as capture the wonder of an exciting story. Imagery and colors are usable for the parent but still energizing enough to keep children engaged with the content. Tones of blue and green are calming for bedtime but can also be brightened up to stand out during daytime use.
DAY 5: TEST
I tested the prototype using Adobe XD with 5 participants who have young children. Feedback about the interface included that the scrolling feature on the book page was not easily identifiable. I adjusted the scrolling feature as below:
Final Overview
In working on this project, I became familiar with the design sprint process. It put into context the need for quick research, ideation and prototyping abilities especially for organizations that utilize the Lean UX model of UX design. From over a decade working in the fashion and consumer product industries, I am very comfortable in having to create designs in a fast paced environment where I have to come up with my own research methodologies and even do some of my own guerrilla product testing for feedback. This was an extremely fun project and in the end I solved for a few problems facing modern parents.
NEXT PROJECT: SSEMBLE
A social media platform for social justice