Monitoring Your Most Important Data

My Role

UX Designer

UX Researcher

Team

Brett Wakefield - Design Manager

Ori Nevares - UX Designer

Ian Booth - Product Manager

Vikas Kumar Sign - Product Expert

Skills

UX/UI Design

Mobile Design

Responsive Prototyping

Cross team collaboration

Results

• e2e design of brand new feature for both mobile and desktop.


• Responded to acute customer feedback and product analytics with novel watchlist feature.


• Development support for building of initial MVP concept.

Timeline

Dec 2019 - April 2020 (4 mos)

Preview

One place for users to monitor and understand their business's most important data points.

1

App Wide Integration

Users can add data points from stories, analytic apps, and explorations to their watchlist.

2

Single Point of Entry

One place for users to view and monitor all their most important data points.

3

Contextual Exploration

Data exploration tools and AI powered insights to provide context of data point changes.

The Design Process

Background

SAP Analytics Cloud was trying to improve on its low NPS score due to poor usability. A key business goal was to support less experienced users with their daily needs such as monitoring their company's key data points.

The Problem

Currently, business users need to navigate through multiple files, pages, and charts to access data points they want to monitor regularly.

Click 1

Access File Browser

Click 2

Open File

Click 3

Navigate Pages

Click 4

Locate data point + refine

The Goal

Create one place for users to collect, monitor, and understand their business's most important data points.

Our Approach

Leveraging customer insights and stakeholder interviews informing a rapid iteration cycle and MVP development.

Stakeholder Interviews

30 minute semi-structured interviews were conducted to understand the problem space and establish design requirements.

Product Management

Why

Knowledgable about customer feedback, industry trends, and overall product strategy.

Goal

To better understand customer experience using SAC and how to align feature development with future of data analytics, and product positioning.

Key Takeaways

• Analytics is moving towards an ad hoc service and needs to prioritize non advanced users.

• SAC is needs to become more cloud native and move away from file based structures.

• Data point monitoring is primarily for executive suit users and requires a simple and intuitive user experience.

Design

Why

Knowledgable about UI standards, customer personas, and known pain points.

Goal

Better understand past design work done, known user pain points, and user personas.

Key Takeaways

• An existing high storyboard had been established and can be used as starting point.

Development

Why

Knowledgable about system architecture, technical constraints, and development costing.

Goal

Better understand system constraints, MVP development timelines, and investment cost.

Key Takeaways

• Project should take a mobile first development path with desktop to follow.

• Initial Beta release for mobile can inform next phase of development for both mobile and desktop.

Customer Insights

Feedback was gathered from product analytics, community forums, and NPS score reports to understand user pain points and requests.

Key Insights

Data was synthesized and analyzed to generate 5 key insights informing the design direction.

Created by Yudhi Restu Pebriyanto

from the Noun Project

Business User Centric

The feature should be developed with the business user in mind. They are the least technical and therefore should be a seamless user experience.

Created by sumarni

from the Noun Project

Data Exploration + Insights

The feature should seamlessly integrate data exploration and smart insight features to allow for the exploration of data point fluctuations.

Mobile First

The feature will be developed for mobile first as it is the primary use case. After beta testing the feature will be refined and released for desktop.

Created by Reza Nur

from the Noun Project

Ubiquitous

Users should be able to add data points from all areas of SAP Analytics Cloud and all data visualizations.

No Files

The feature should not make use of files and should exist in a ubiquitous way throughout SAP Analytics Cloud.

Concept Ideation

Card display of all pinned data points with time charts to display changes.

Concept Ideation

List display of data points with contextual information for selected item.

Mid Fidelity

Stakeholder reviews were conducted and the leading ideas were taken forward into mid fidelity mockups with the following changes.

Design Solution

From another round of stakeholder feedback, the designs were refined into high fidelity mockups and prepared for development handoff.

Development

Handoff specs were created to support development of a mobile MVP.

Reflections

Finding the right model for design and development collaboration is key.

Development Support

The development support process went very well for this project. A key part of this was to establish a framework on JIRA to log design bugs that were uncovered in design reviews, a consistent bug logging structure, and establish bi-weekly design/development calls. This is something I carried forward and built upon in other projects.

Research Triangulation

Like any product, its vital to analyze customer feedback and usage analytics. However, no source of data is complete on its own. Combining three different sources of analytics with stakeholder interviews provided the necessary depth to understand the core use case and features that needed to be built into the watchlist.

Company North Star

SAP Analytics Cloud is a massive product with many teams simultaneously working on feature development guided by a product wide north star to become more cloud native. Earlier alignment and consideration of how this feature fits into the bigger product roadmap would have helped avoid unnecessary iteration cycles and easier senior management buy-in for investment.

Website design and content by Ori Nevares