product design case study
2019-2020

10 years ago, e-book readers looked out to be a thing of the future. When we got it, they seemed clunky and impersonal, but with time, little by little, they got better. 10 years forward, we have them in our phones, stringing along with us while commuting, before going to sleep or even during short coffee breaks.
Here is my experience on the next story, where we take a book reader made for all and made it for a few, so that those few could enjoy it reading even more. It’s how we localize the Kobo e-book reader app –made for readers around the globe– to the readers in Japan.
Note: to comply with my non-disclosure agreement, I have blurred and obmitted confidential information to comply with my non-disclosure. The information in this case study reflects my personal view and experience and does not necessarily reflect Rakuten Kobo’s viewpoint.
Kobo is an e-book leading company that was founded in Canada in the late 2000s, expanded to the Americas, Europe and is now available in most of Asian Markets as well. The company was bought by the Japanese e-commerce giant Rakuten and is now a core part of its ecosystem.
The initial business goal was to integrate the product in the Japanese market, as well as Rakuten values and their core technology. The next step as a Designer was to completely understand the market, customers and their needs as users.
I led a team of UX & UI Designers for this project, whose focus was to understand the local market and audience, rebuild and redesign the mobile & tablet apps. I worked alongside the Product Manager, Product Owner and 4 Developers.
The project execution started late 2018 and finished early 2020 for iOS. The project is yet to be launched for Android.
1. Gathering early Market & Customers Insights
2. Ideation & Leading Workshops
3. Planning and Scope Definition
4. Team Leading, Management and Coordination within different departments and overseas design teams
5. Create the User Experience & First Interfaces
Localizing a service presents very different challenges than creating a new service or preparing it to scale.
The Kobo app already had a solution that was working for “everybody” –a global standard user– but it wasn't working as well for the new Japanese market. Despite that, it became the number 1 selling market in the platform in a matter of months. Even so, for these new users, the product wasn't fulfilling their needs & expectations. They were accustomed to a different experience: they read different content than overseas users and the target demographic was extremely different as well. At this point, Kobo Japan already knew that they needed to localize the product and there were already too many hints on what we needed to do in order to maximize the users satisfaction and enhance the business local growth.
In a country that creates so much literature and manga content and with more than 70 competitors in the market, we needed to differentiate ourselves by changing the experience and service. In comparison to the rest of Kobo users, the Japanese users in average:
I also had a personal challenge: to understand a new culture.
When I joined the company, I needed to quickly onboard on a new culture and market. Not knowing the language was just the first of the hurdles. Understanding the Culture was going to be the most challenging one. I didn't have a lot of time to onboard, so I focused on figuring out what were the specific points in which the users read, use their books differently and how their habits differ.
I summarized from different internet sources and with the great help of the Product Manager and the UX Designer in my team. The next are the key differences that gave shape to the new platform.
Traditional wood paintings or Ukiyo-e have represented daily lives from the 16th up until the end of the 19th century and are one of the main reasons why visual tradition has been well conserved and was a big part of the culture that ended up inspiring other tipes of visual communication including Shin-hanga (or new prints), manga (or comics) among others. Kanegafuchi no Yurai (History of Kanegafuchi), c. 1848 From the play Kaidan Sumidagawa.
3. Longer commute in highly dense areas and public transportation


The word ‘hanami’ (fireworks) in the 3 different script systems. In order from left to right, Kanji, Hiragana and Katakana.
To check more information about the Japanese writing systems, check Shoko Mugikura’s beautiful article Japanese, a beautifully complex writing system.
Nightlife in Shibuya, Tokyo. The streets are busy where signs compete ferociously for the walkers’ attention.
After I had a better idea of the culture and market, I created the roadmap and laid out the blueprint of how we would tackle the project.
Now that we understood where the big problem relies, I worked with the product and project management teams to update the roadmap and prioritize user research where we needed. This was going to be a more than a year project –rebuilding the whole app took its time– so it was vital to reduce complexity and invest in specific pain points and substantial opportunities of improvement.
After 2 prioritization workshops and further work from the product management side this was the final roadmap:
In this use case, I’ll address the improvements and processes in while redesigning the library.
This is an evolution from the 5D Product Design process refined by Altuit that I adjusted to the needs of the project.
User research can take a lot of time and resources. It was key that we identified where our needs were in order to prioritize correctly.
Right after understanding the market and cultural differences better, I needed to verify the assumptions that we had collected to understand the current behavior of the product, pain points, goals and expectations from the users.
We divided the research into 3 different blocks:
6. user research
What can we offer to the users in the app other than reading?
Findings from usage data and major demographics to the Product and Business teams in Kobo Japan.
That is a more profound redefinition of what I mentioned previously as app usage outside of reading. To understand more, me and the UX Designer in the team summarized quantitative data and crossed it with qualitative data via interviews and finished with a user activity.
About 50% of the content are manga books compared to less than 10% overseas
A small amount of users have thousands of books and they made up for a large part of the purchases
From the Collections feature (users could create one personal collection and add books to it), people were creating collections just for their names. Besides from that, they were barely being created
Search was mostly used to find books directly, rather than searching by authors, genres or other related content
More than 90% of the users were using the first tab of the library: Books. Others, such as author views were barely used in Japan: we assumed that it was more suited for Novel and Business books rather than comics
Continue reading and Recently added were the most used lists in the app
Libraries that had a lot of manga books were really heavy and could slow the app performance
Other library usage data related to tab structure access and filtering
We interviewed 7 users to understand which issues would they find in their book libraries and if there were any trends or insights that could help us to improve the current experience. These were some of their findings:
Users had a hard time to find their favorite genres. It was easy to find the books in the store than in their library
Users identify books by their covers rather than by their names. This could be due to a culture that has a higher visual recognition or because the titles can be written with different writing systems ("or alphabets") which makes finding these titles more difficult and less recognizable
Authors are not as relevant to recognize a title, especially considering as representative for manga books
Users didn't find easy to continue reading different books in the same series
In order to gain a deeper understanding of how the users search and organize their content, we laid out a card sorting activity. The cards contained different actions and categories of books and content. We proposed different scenarios and asked the participants how would they locate a book, organize their content to begin reading.
Before starting the activity, we asked the users if they knew how large their library was, the type of content they usually read and if they were using other readers or library managing apps. That would help us understand their mindset behind their decision making.
Cart sorting activity was done with 7 users where they had to organize first their book library as what they’d do in their bookshelf, how would they improve it and then we’d specify some cases they’d have to portray to understand how they would build their libraries based on them
Users expected to read as soon as purchased and expected to find their books without any steps in between
Users wanted to continue reading manga series as soon as the next volume is available and expected to browse the content grouped by series
We verified that searching by title, filtering by "on device" or "downloaded", and browsing by author had less impact on how the users would access their content
Filtering/browsing by sub-genre seems rarely used, despite it was one of the requests found in the interviews. Only users with large libraries would use filtering often and they would probably need a more advanced or a detailed version of how we had it
Fewer predefined categories might help users find their content more quickly
Once the session was over, we had an initial idea of which categories and actions are more useful to improve the Information Architecture of the app.

The current library had quick filters. These didn’t work well for users who had a large library who are the ones using it. We needed to optimize it for different personas.
7. reshaping the vision
The larger the library becomes, the more complex problems users inherit. Every user will have a more enjoyable reading experience by simplifying the library for all users and providing specific tools for the expert ones.
8. solving problems
To provide unique solutions for the different users that were using our app, I reframed the problems as challenges and created hypothesis to test and implement them. These are some of the major solutions that introduced game-changing improvements.
How Might We help users finding content in their series as fast as possible?
We believe that grouping and optimizing the current library structure will provide a more intuitive way to find and access their content easily.
We created 3 different versions that organized the library in a different way:
We ran a Usability Testing session with 7 active users in which we found:
Through another round of iteration and feedback, it was clear that we needed the business model version in the top level navigation, but still needed an extra navigation level to grant access to different content types.
Up until this point, we had figured out how the users could access and add content, which worked great for most users.
What about those who had thousands of books?
Those that read one book after another, one comic after another, non-stop? These were our most loyal users. After these changes, we still had not solved the largest issue for them: the libraries were too heavy (a comic book is about 20x as large in size as a text book with the same pages) and looking for content in a large library was still painful.
Aside from that, some manga books have with similar covers, and users can forget their names and some titles have a lot of characters, and were not as easy to search for.
How Might We help users with large libraries finding their content?
Creating an advanced filter will give users with a large library a better way to refine and find their content.
We wanted to facilitate the work for the heavy users and not hurt the middle and novice user. By creating and advanced filter, we were giving more control to the heavy users but we didn't know how the others one would react, considering that we didn't have usage data, just opinions from our previous interviews and customer care.
The current control version had all the filters in one sheet in which the user could select only 1 option at a time. I ideated an advanced filter version that split them into 2 sections or steps and gave more control for advanced users.
After the testing session and interviewing the users we found:
In the end, the 2 steps filter was successful for large library users and didn’t take anything away from the rest of users. Likewise, having a separate sort option helped the rest of the users focusing on sort options and omitting seeing filtering options that were not relevant for them.
How Might We show other suggestions or results aside from books while searching?
Dividing search suggestions by categories will help users to identify their content faster and provide multiple category results when searching.
The premise was simple: adding different categories to the search prediction and on the page results as well. The initial order came from top search usage, starting by history searched term (users may book the same book more than once), series, books, authors, collections and uploaded books. Also as a result of separating the Library search experience from the Store search experience, we were able to target the search better and provide better contextualized results.
After the usability test sessions we found out that:
These were the initial 2 big changes and many more came. After all, changing the structure of your library can mean that the shelves can break or the books fall flat. I needed to make sure that the changes made a big impact.
The main structure of the library was working well now, but in the new library, the visualization and grouping options didn’t match 1-to-1 as they did previously. Here’s a quick view mapping of these options:

Sort and filters (filters would have grouping inside)

Sort, grouping and filters

Filters, sort and visualization options. This was the final version
Changed the default book grid from 2 columns to 3 columns on smartphone to show 150% of the original content:
Aiming to improve recognition while keeping the library as simple as possible, we made some small improvements, aimed to have visibility of the status of the book progress, ownership and download state
This is the final representation of the states over the book main information.

This is the final structure that shows the minimal information that a book needs to be recognised, download, read states, progress and actions access.
We started working in the local design first, and half way through, we started working with the other 2 reader services and design teams overseas. We synchronized and started working in different features that the others would optimize and implement and vice-versa.
We put a lot of effort and emphasis towards standardizing UX and UI creation processes. We had a Designer in charge of creating the main components in a centralized library using Figma. Each one of the teams used these components to customize them and apply their styles to fit each service brand and needs.
In the end, we created components, mockups and user journeys by customizing the Shared Basic Library. We also discussed and added components back to that library for the other teams to use.
This is a quick mock of how we build our libraries:
Examples of the library customization:


Customization of the Top bar and Bottom navigation bar from the Shared Basic to the Kobo Japan Library.
The biggest initial challenge was to be able to dive in deep into another culture that represented so many changes on how the users behave and what would be the best User Experience for them.
It was also challenging to lead multiple Designers working with different features, sometimes by themselves, sometimes in squads while designing at the same time.
Another big challenge was coordinating 3 different products that were sharing design and development core despite having different user needs. This represented a lot of going back and forth despite time zone differences. Creating a common scalable design system was challenging to say the least.
Some of my major learnings was how to set different UX approaches while leading a team into one direction. It took a multiple team effort, lots of trials and errors, redefining and refining processes.
Creating a multi-scalable design system was very interesting and required major coordination between stakeholders overseas and also implementation inside the team. It also forced me to plan ahead of schedule for possible changes and I had to be able to mitigate some of the issues that it entangled. In the end, it helped us create a more consistent and escalable project that would serve not only us, but other teams and companies.
At the time I was also directing other projects from different companies, which made time management critical and made me plan and make accountable my time investment and resource management from the different Designers in my team.
This was my main personal work in progress for most part of the project. I was both a Designer for the project and a Team Lead and Manager of a group of 5 Designers –for this and other projects– working for different companies. It was extremely difficult at times to manage between the 2 different worlds of designing and managing. There is a different mindset that these positions require and, again, time management is a key factor.
After a while, I got a better handle on it but the periods of time or allocation between the tasks that I would require to do fluctuated and it was tiring at times, but definitely a learning experience and an enriching one in terms of not just being able to do one thing but forcing myself to watching issues from different points of view. Being able to talk and emphatize with different stakeholders from different worlds and cultures was an experience that I will treasure.
There is still a lot of work to be done. Currently, the iOS app is about to be released and the Android will come in the next few months. Some of the next improvements might be:
Copyright © Jaime Zamorano. 2020
Legal details