TinyTales is a new startup where parents can find books to read to their children. As children have grown their library, parents expressed it’s been difficult and time-consuming to find the right stories to read to their children.
TinyTales wants to make it easier for parents to find a great story to read to their children. They’ve brought me on board to run a design sprint to quickly test out a possible solution.
The goal was the understand the challenge goals. The problem statement is clear—parents want to be able to find a book quickly according to the following preferences:
Length
Entertainment value
Educational value
Relevant to specific topics of interest
Age-appropriate reading level
As such, I’ve developed a user flow for how a TinyTales tablet app may look.
Initially, I explored a variety of children's book-reading apps, but noticed their design pattern to discover books were all very similar.
As such, I opted to quickly analyze three of the most popular entertainment apps (indirect competitors), rather than book-reading apps, for my lightning demo. The lightning demo is an exercise where I spend 30 minutes to find one feature from each of three apps to inspire TinyTales.
In order to ideate possible critical screens, I used Crazy 8s, an exercise that challenges people to sketch eight different ideas in eight minutes to brainstorm ideas for a critical screen. It is clear that the critical screen must be the dashboard from which parents can select books.
Then I generated a solution sketch (a three-panel board of the screen that comes before the critical screen, the critical screen itself, and the screen that comes after).
The storyboard was then uploaded to Marvel as a low-fidelity prototype, connecting the individual UI components from my storyboard.
With this interactive prototype, I conducted five user interviews to test usability. The key findings are as follows:
💡 Finding: Users wanted to see TinyTales' recommended books upfront, rather than what their social network was reading.
🛠️ Recommendation: De-prioritize social aspect of book discovery, unless you can connect with relevant groups such as your child's class or other same-aged social groups.
💡 Finding: Users were confused by the purposes of "Bookmark" and "Pause" functions of the reading page.
🛠️ Recommendation: Re-assess if "Bookmark" function would be used often and requires a brief tutorial, else remove. Remove "Pause" since users already assume that the page last read would be saved.
💡 Finding: "Democracy" tools allowing children to choose a book may not be needed, and parents don't want to manually select 2-3 books every night to allow child to pick.
🛠️ Recommendation: Provide an option to turn off or customize this tool, allowing parents to have 2-3 curated books randomly selected from a list, library, or topic.
This project taught me to work efficiently on a short 5-day timeframe. It was nice to be given the research data and problem statement from the TinyTales startup. Parents clearly expressed their desires, which informed the features I designed: easy product discoverability by certain filters (ex: age and topic) and the option to share preferences.
The themes were easy to find, but I found in my interviews that there are likely many use cases that the business premise of TinyTales itself does not accommodate. It goes to show that cross-collaboration between product managers, marketing, and other stakeholders in a company is essential during any UX process.