Catherine Hicks
User Experience and Product Design Professional

NetBase

NetBase delivers the social intelligence that global brands and agencies use to publish, monitor, analyze and engage with customers in real time. Using a high-precision natural language processing (NLP) engine, our platform processes billions of social media posts to extract structured insights delivered via customizable dashboards. Our solutions enable digital marketing, public relations, brand management, customer service, sales, and product innovation leaders to craft winning strategies faster.

Role & Project Summary

  • Allows the users to see large spikes in data and easily analyze them

  • Users need to gain quick insight into large fluctuations in data in order to address issues - both good and bad - that may came up
  • Users are able to see large fluctuations clearly in large amounts of data and will be able to dig in to see details
  • high spikes in data can be both good or bad, depending on what the spike is about. The analysis lets you dig into that data to fully understand the nature and details of the fluctuation
  • The idea of crisis management is a huge selling point for the enterprise product offering. The concept of this analysis came from the conversations had on the product team about how to expand the ideas we had of positive and negative sentiment on posts and allow users to identify spikes in data and deep dive into them to quickly gain and understanding of whats going on

Project Constraints

  • This feature must identify large fluctuations in data and allow the users to gain insight into what the data is telling them
  • We believe fluctuations in data need to be made visible in the platform and they need to be able to be dug into to be able to see the root cause of the fluctuation
  • We determined a spike of positive or negatives posts of a certain threshold would be considered a fluctuation - with the idea that down the road the user would be able to determine that threshold themselves
  • Project Goals: 
    •  Increased understanding of fluctuations and a way to immediate address them
    • We made assumptions on what the customers would determine to be a fluctuation in the data - we set those parameters, knowing that they may be different for different users

NetBase Enterprise: Fluctuation Analysis

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

NetBase Enterprise: Fluctuation Analysis

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

NetBase Enterprise: Fluctuation Analysis

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

NetBase Enterprise: Fluctuation Analysis

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

NetBase Enterprise: Fluctuation Analysis

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

NetBase Enterprise: Fluctuation Analysis

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

NetBase Enterprise: Fluctuation Analysis

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Summary

  • The overarching approach of product development came from our CTO and had three phases I still use to describe feature development: simple, sufficient and complete. The idea being that simple is your MVP, sufficient is enough to launch it with most functionality and complete is a complete feature.
  • We decided that allowing users to set their own thresholds was more towards the sufficient or complete phases, and beginning development of this feature with us setting those parameters was more of the MVP
  • The conversation about "what was a fluctuation" and what was the specific parameters that would be determined to be a large enough fluctuation to trigger the analysis was the hardest part to grasp for this feature, as we determined this could be different for each type of person
  • We determined that the fluctuation would at first be determined programmatically by our data analysts and then in subsequent versions of the feature we may give the user more granular control over determining what that is
  • I learned in depth how highcharts, our visualization framework, worked and how we could push the limits of that