Kargo Reporting Platform (SaaS)

The Kargo SaaS reporting platform is a product that provides ad campaign performance reporting to clients in one easy-to-use interface. The client is able to sign in themselves and check-in on the statuses of their campaigns without having to reach out to their respective Kargo client service managers. This product was brand new while I was on the team and was one that I led from the conception to its current state. The following work describes the current work and steps we’ve went through so far with the product.

Methods applied:

  1. Research Plan

  2. User Interviews

  3. Affinity Mapping

  4. Competitor Analysis

  5. Feature Prioritization / Effort Vs. Impact

  6. High-Fidelity Designs

  7. Stakeholder Feedback

 

Research Plan

 

User Interviews

GOAL

Identify the needs and challenges our users when it comes to access reporting at Kargo.

METHODOLOGY

Held 6 user interviews which consisted of 4 internal Kargo team members as well as 2 external clients. Created a script of questions prior to the interviews that was reviewed and approved by other members working on the product such as the Product Manager.

INTERVIEW script template

 

Affinity Mapping

GOAL

Analyze and synthesize the data gathered during the user interviews

METHODOLOGY

Transferred notes from all user interviews over to FigJam. Color coded notes by user. Worked with Product Manager and other team stakeholders to sort the notes into themes across all users that were interviewed. Identified reoccurring themes.

Summary Document

 

Feature Prioritization / Effort Vs. Impact Matrix

GOAL

Determine which features should be included in the MVP.

METHODOLOGY

Collaborate with product and engineering teams to plot the needs and feature requests from our users that we gathered from our interviews on an effort vs. impact diagram. Prioritize high impact, low effort features.

summary

Because our engineering team chose to use Looker to power most of the features of our platform, we were able to mark several features as low effort since they will not need to be custom built. Now designs can begin based on the prioritized list of features.

 

High-Fidelity Designs

 

Requirements

  • We must use looker embedding to power the bulk of the UI for the MVP due to timeline and engineering restrictions

  • The navigation UI must be built around looker’s embed UI

  • Different client user persona’s need access to different dashboards and explore

  • Client direct users need to only see their brand’s data while agency users need to see every brands data that is within their agency. Kargo users needs to see all data for all client direct and agency accounts.

 

Client Direct User

 

Agency User & Kargo User

 

Stakeholder Feedback

  • More Data Visualizations

  • Higher Level Data Overview

I partnered with the Analytics Team to make sure that our looker dashboards were using more data visualizations while also following brand guidelines and layout best practices. Here is where it is at now: