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

  • Built upon Instant Search to complete a more robust platform

  • When starting out building the new NetBase Pro platform, we first needed to come up with the page where all the data would sit - the dashboard
  • Users will have an easy to understand and utilize main application page
  • The tabular dashboard structure along, built for Pro with the search and filtering options which were brought in and enhanced from enterprise platform, allow users to have more streamlined data and allows ease of growth of the platform
  • The dashboard structure came from many brainstorming sessions. We first started out with using the existing ideas of the enterprise product to
  • The dashboard is the landing page for this new product. In being so, this page must show relevant data and be set up to allow the users to move through the other features of the product seamlessly

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: 1. 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 Pro: Dashboard Structure

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 Pro: Dashboard Structure

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 Pro: Dashboard Structure

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 Pro: Dashboard Structure

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 Pro: Dashboard Structure

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 Pro: Dashboard Structure

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

  • We believe a concise and clear dashboard with up to date visualizations will make this platform easily usable for all users
  • The dashboard structure came from many iterations and working sessions alongside the product team. We decided the dashboard structure was similar to our competitors via competitive analysis and we also decided it allowed ease of future grow and customization, two things we knew we needed to worry about moving forward
  • After competitive research, we made the assumption that the card and tabular based system we built our dashboard with was widely used by our competitors and would be easy for our users to grasp and understand with minimal assistance
  • The approach to the dashboard design was the following: what is the easiest way to show a lot of data in a manner that would allow us to easily add features as we continue to build out the product feature set
  • We came to tabs and cards after many days of brainstorming as a product t team (the 2 Product Managers, me and occasionally our CTO)
  • Project was successfully launched and within the first month brought an additional 7 figures of profit into the company with companion license purchases