ReportManager

A remote design sprint

Project overview

The current application was first designed and built in 2012, to replace static PDF reports which existed before then. At the time, it offered a higher level of flexibility and access to data, and so was very well received.

However, since then, a lot of additional data and capabilities have been added to the tool. While this has made the tool more powerful, it has also become more complex. This complexity has resulted in a lower satisfaction score for the capability, especially in comparison to the collective score for all capabilities on the platform.

It has been prioritized for updating, as part of the suite of applications offered by the company. The design team used the design sprint format to help identify the right opportunities to target, and what the future of ReportManager might look like.

Process snapshot

Objective selection

Planning & logistics

Research details

Ideation workshop

Prototyping

Concepts are processed to group those with a similar value proposition. Each proposition point is mapped to the stage of the user journey. At this stage, it becomes possible to plan the prototype screens needed to visualize each proposition point for concept testing.

Collaborative storyboarding by the research, facilitation and design team to think about how to express each value proposition point within the context of the workflow and tool. This includes multiple reviews with the product team to make sure the “hard points” of the product are not missed.

The final prototype contains 6 points of value proposition, each represented by a single screen. This format maps to the concept testing method selected for the project, which is targeted single-concept testing (vs the conventional 2-3 fully interactive prototypes).

Concept validation

A qualitative study with 6-8 users distributed across the report-using personas, as in-depth interviews as well as forced ranking of each concept.