Mister Intel best practices

PURPOSE

This document provides an overview of the data contained in Mister Intel as well as best practices to follow when building a dashboard.

PROCESS

Core Datasets

The Core Datasets Dashboard displays a comprehensive list of available datasets
- Includes the following:
  - designated usage
  - current status
  - descriptions of the fields included within each dataset.
Review the Core Datasets Dashboard to learn about which datasets are available.

Personalized Data Permissions (PDP)

To keep user information private, personalized data permissions are applied to sensitive datasets limiting the data an employee can access.
- NOTE: Cards, Downstream datasets and views inherit the permissions from the top level.
PDP is currently applied regionally.
- This means that employees can see data for all stores and/or members who fall into the regions they are assigned to.
Employees on the material non-public information (MNPI) list can see data for all regions.

Certification of Cards and Datasets

The certification of content in Mister Intel is crucial as it enables users to distinguish between draft and certified content.
Certified cards and datasets serve as a reliable source of information that users can trust, knowing that it has undergone validation.
Reference Certifying Cards and Datasets in Mister Intel to learn how to certify cards and datasets.
- MISTER INTEL - HOW TO CERTIFY CARDS AND DATASETS

BEST PRACTICES

Copy the Dashboard Template
- The Dashboard Template includes a Production Header, space for ten cards, and a footer.
- You can copy the template and add cards to it instead of building a dashboard from scratch.
Enter Field Names
- Use descriptive names for fields. Use full words instead of abbreviations whenever possible.
- Follow the Pascal case format: capitalize the first letter of each word and lowercase the rest of the word.
  - DO NOT add spaces or symbols between words.
- For example, MonthlyActive is correct; monthlyActive, monthly_active, and Monthly Active are all incorrect.
Choose Dashboard Header
1. Review the Header Choices Dashboard for branded headers that can be used when you build a dashboard.
2. The color of the dashboard header indicates its status:
  - Purple = Development (DEV)
  - Orange = User Acceptance Testing (UAT)
  - Branded Color (Mister-approved gray, blue) = Production
3. If your dashboard will be visible to the field or multiple departments
  - Recommend pushing the dashboard from Development, then User Acceptance Testing, and finally to Production.
  - Share the dashboard with the following groups:
    - UAT: When a dashboard is being pushed to User Acceptance Testing, it should only be shared with team members who are participating in UAT and providing feedback.
    - Production: When a dashboard is being pushed to Production, you can share it with specific users or with all employees.
Build Cards
1. Business data is represented by cards.
2. When building a card, enter a short title in the Card title field.
3. Use the Description field to enter additional information.
4. When viewing dashboards on mobile, the Description field will be hidden.
5. In general, dashboards should contain a minimum of two cards and a maximum of ten cards.
6. This ensures that users who regularly access the dashboard are not overwhelmed by content.
Customize Graph Dates
1. We use a standard format for graphs. Abbreviate months and only display the year at the beginning and when the year changes.
  - The example below starts in February 2023 and goes through January 2024.
2. To have your dates display this way:
3. Under the Chart Properties section, select “Category Scale (X)”.
4. Find “Never Use Time Scale” and change the dropdown to “False”.
Add Dashboard Footer and FAQ Section
1. Use the standard footer (see below), at the bottom of each dashboard to direct users to share feedback and report bugs.
2. If you believe users will have additional questions about the dashboard, an FAQ section can be added to the footer of the dashboard.
Verify Mobile View
1. To optimize the mobile experience for users, follow these best practices:
2. Remove dashboard headers as they take up unnecessary space on mobile.
3. Extend small or difficult to read graphs on cards.
4. Adjust numbers on cards to be larger and easier to read.