The Client

Aurelius tools serve UX designers, user researchers, marketing professionals and other product teams with a platform to make sense of their research findings. Currently, the tool allows users to easily add notes, tag and organize them in ways to make sense of the feedback and resurface it all in one place when needed.

The Challenge

The next goal for Aurelius is to expand their platform to create a new tool for users on the site. Aurelius users can already organize their data into what is called, a key insight, that highlights important research information. The next step is for Aurelius to create a way for users to pull key insights from various projects into one cohesive report; Aurelius Collections.

Understanding the users and their product

To get a better idea of how using Aurelius as a tool would impact a business, a customer journey map was created. The diagram highlights key points where users come into contact with the product, as well as their perceived experience  with the tool.

Looking at what Aurelius' competitors were doing provided more of an understanding of what tools were currently offered to users using platforms for research, ways in which they were currently executed, and what tools may be desired, but lacking.

- Make it easy to upload data
- Some platforms are social--allowing the creator to get feedback and share

- The ability to import data in bulk is preferred

Since Aurelius has an internal development team, part of this project involved working within their technical and time constraints. This was considered when developing the scope of the project. Feature cards, a series of possible product solutions and functionalities, were presented to the internal development team to determine the feasibility.

The most feasible and interesting feature cards were then passed along to Aurelius users to gain insights on what product expansions and functionalities mattered most to them. 

-  Users were concerned about scalability of the product, and the ease of locating key insights from multiple projects.
-  Users wanted to be able to add/edit descriptions in the Collections

-  The ability to export and share the Collection was important

Following this research, each functionality was ranked using a Kano Analysis system, and the top features were taken into account for Phase 1 Development.

Phase 1 Development

In order to execute the following recommendations for the initial process of development, the current system model (site structure and patterns) was maintained.  The following features were implemented into the design:

-  Create Aurelius Collections
-  Add descriptions to Collections
-  Revise notes to show or hide dates

-  Build Collections from notes, key insights

-  Share Collections, or export as a PDF

WIreframes + Interactive Prototype

Wireframes that are consistent with the other components of the platform were created in low-fidelity sketches before mocking them up in Sketch.