Dashboard design best practices
Recommendation
Improve navigation and visualization within your Collibra environment by using dashboards as your landing page. Dashboards provide out-of-the-box widgets to customize your pages.
Impact
Boost usage and adoption across diverse user communities by improving the user experience. Dashboards can offer direct access to critical information and capabilities, making your environment more appealing and user-friendly.
Best practice recommendations
Begin designing your new dashboards using the following example of a typical design process:
- Home page design: Start with a home page concept that helps users understand and navigate the various functionalities.
- Community or domain hierarchy: Normalize the community or domain hierarchy to make it easily consumable for specific roles or groups.
- Role-specific dashboards: Design dashboards tailored for specific roles, focusing on visual data representation.
- KPI and metric dashboards: Design dashboards showing KPIs and metrics for all Collibra content with filters. This allows managers to assess the progress of data governance programs within a given community.
- Embedded BI reporting: Use the Insights widget for operational reporting and executive dashboards, instead of building them natively within Collibra.
Do's and Don'ts
Do's
- Always keep your users’ goals in mind.
- Prioritize ease of navigation and user ergonomics in your design.
- Use a consistent color scheme or palette.
- Design the page with as few objects as possible, whose purpose is clear and most used.
- Instantly answer essential questions from your visitors.
- Highlight the main features.
Don'ts
- Avoid bright or conflicting colors.
- Avoid cluttering with excessive text or overly busy graphics.
- Avoid unclear navigational structures.
- Avoid including irrelevant information.
Validation criteria
Use monitoring tools and gather user feedback to track monthly or quarterly usage and adoption.
More information
For more information, go to the following resources (Collibra sign-in required):