My Knovel ToGo
About the project
My Knovel ToGo is the companion native mobile app to Knovel, an online library of science and engineering textbooks and other materials. The previous version of the app was rather barebones, and the Knovel team wanted guidance on what to include in the next version.
We set out to gather insights from user research, and user testing of prototypes, but ultimately we'd have to make the case for our findings in such a way that they would actually influence the app's development.
- Led workshops with client stakeholders to gather and prioritize ideas for product features
- Interviewed users of the current app to assess their needs, compared to client priorities
- Created wireframes integrating stakeholder and user feedback
- Review those wireframes with users in order to further refine key proposed features
My first step was to understand the client's vision for the next version of the app.
Later on, we'd have only a limited amount of time to do research and testing with users, so we had to be sure the project focused on features we thought would have the most impact, as well as those we needed to flesh out the most. For example, implementing fingerprint-based authentication in the app was likely to have only a small impact on user satisfaction, and would have a straightforward implementation on both iOS or Android.
Over a series of in-person workshops, I worked with a team of stakeholders from across the Knovel organization to:
- Generate ideas for features for the next version of the app
- Work together to develop a shared understanding of those feature ideas
- Prioritize those feature ideas according to how important we thought they would be to users
Next, it was time to hear what users wanted from the app.
The Knovel team put in touch with several users of the existing app, who we interviewed to learn more about the app fit into their workflow. The client wanted to be sure we would leave this phase of the project with a clear “yes or no” to each of the features we had defined previously, but I did my best to balance that with understanding more broadly what was important to each of the interviewees.
During the research phase, I also looked at other mobile apps, especially other e-readers, to understand what they were doing that potential users of My Knovel ToGo have come to expect from this type of app.
Once we heard from stakeholders and users what they wanted, it was time to bring that to life.
Again, due to the limited time we'd have to test wireframes with users, we chose to focus on some key elements of the future app:
- Logging in: Surprising complex, given all of the ways one can access their company's or university's Knovel subscription
- Browsing materials: Users said they sometimes wanted a more curated experience, like other e-readers or online bookstores.
- Searching materials: There were a lot of advanced search features on desktop that needed to make their way to the app.
- Taking notes within materials: Again, previously only on desktop, but a key feature of any e-reader.
- Clearly and simply syncing user activity between desktop and mobile
We walked users through wireframed versions of these key flows, and made notes of the parts that were confusing, or missing features they expected to see. These findings then made their way into our final research report.
Finally, I put it all together into one last report.
Over the course of a few months, I learned what the client and their customers wanted to see in the next version of My Knovel ToGo, and took a shot at meeting the needs of both groups, at least in wireframes. Now that those wireframes had been put in front of users, it was time to make one last set of recommendations as to how these wireframes could be further refined, and what to focus on next when the full app was designed and built.
Unfortunately, due to budget constraints, this project hasn't gone any further just yet, but the agency where I did this work has continued to do work with the Knovel team, which suggests they were happy with what they learned. Looking forward to seeing where the app goes next.