Identifying Key Roles

Last modified: August 09, 2021

group of people

In a dashboard design project, multiple people are involved in making it a success. Key stakeholders need to be defined from the start to facilitate optimal collaboration and communication during the appropriate steps of the process. There are four key stakeholders with corresponding responsibilities in a typical dashboard project.

These roles may be fulfilled by the same person, but typically they are not.

Key Stakeholders

1. Designer

Define > Prototype > Build > Deploy process

This is the person that is responsible for creating the dashboard and managing the project. As you are the one reading this book this is likely you. Since you will be involved in all steps, you should be in charge of coordinating all efforts of the project.

Designer responsibilities:

  • Define the stakeholders
  • Metric calculation
  • SQL queries
  • Chart determination
  • Dashboard build
  • Point Person approval

2. Audience

Highlighting the deploy phase to find the audience

This stakeholder group is the most passive in the creation of the dashboard, but the most active once the dashboard is finalized.

Audience responsibilities:

  • Provide feedback on whether or not the dashboard is useful

There are no direct responsibilities for this role during the design and build phase. However, all design decisions should take into account how the audience will interact with the dashboard. Pretty much every decision that is made in this project should be made with the audience in mind. Their product or business knowledge, business role, and any cultural or other sensitivities NEED to be considered when completing almost every step of the dashboard project.

Questions to keep in mind about audience:

  • What devices will they use to view this dashboard?
  • How much context is needed for each metric?
  • How often will they be referring to this dashboard?

These questions will help guide your design decisions so that the dashboard is most effective for the consumers.

However there is one audience member who is very involved in the process, we will call this individual the Point Person.

3. Point Person

Highlighting Define, Prototype, and depoynnpw

The Point Person is the one that is requesting the dashboard. This is the person who has the business need for creating the dashboard, such as wanting to understand the marketing funnel or how users are engaging with the product over time. They should be involved in all of the decision points since they have the most context to ensure the dashboard is useful.

Point Person’s responsibilities:

  • Provide the decisions this dashboard will inform
  • Identify the key metrics
  • Identify the audience of this dashboard
  • Provide approval on the dashboard design

4. Data Gatekeeper

Highlight the build phase

This is a member of the data team that understands the data source, schema, and any other library that will be used to create the metrics. In some cases, the Data Gatekeeper and Designer roles will be the same person.

Data Gatekeeper’s main responsibilities include:

  • Setting up permissions and access to the data
  • Helping others understand the data source schema
  • Helping with SQL queries

Figuring out which columns to use in a visualization and in a dashboard can be challenging since many databases are not well documented and the data is not modeled appropriately. Data Gatekeepers can make this much easier since they will be familiar with the schema and can grant you permission to tables that you may not have access to. They may also write the SQL queries themselves or help you optimize queries that you have written.


  • Creating a great dashboard is a team effort, and all roles are vital in its completion.
  • Designers coordinate the project and create the dashboard
  • Consumers are the audience, and the design should meet their needs
  • Point People define the central decisions that a dashboard needs to support
  • Data Gatekeepers help find the relevant data in the database

Written by: Matt David
Reviewed by: Mike Yi , Dave Fowler