1.03-03 Set a landing dashboard by role
Different roles should require a different entry point. Avoid a generic landing page if possible and create a specific dashboard tailored for each role
Comments
-
Rule 1.03-03 Set a Landing Dashboard by Role. Different roles should require a different entry point. Avoid a generic landing page if possible and create a specific dashboard tailored for each role. It goes against NECESSARY elements of PLANS if you wish to go against this rule
Here is how it was done in Pre Planual Era: We used to have only one Landing Dashboard for the entire Anaplan User base.
Let’s say there are two roles in a model i.e., Sales Reps and Sales Managers. There in one specific dashboard for each role. Sales Managers need to have access to both the dashboards whereas Sales Reps need to have access to only one i.e., Sales Rep Dashboard
This is how it looks for Sales Reps when creating only one Landing Dashboard for both the roles
What is wrong with this method? Look and feel gets compromised. Users may get confused
Here is how it should be done in Planual Way: Create separate landing dashboards for each role that you have in the model. After creating separate landing dashboards this is how the dashboards looks
Landing Dashboard for Sales Reps:
Landing Dashboard for Sales Managers
0
Title
- Preface
- PLANS
- Planual Conventions
- Zen of Anaplan
- Chapter 1 - Central Library
- Time
- Versions
- Users and Roles
- Contents
- Lists
- Subsets
- Line Item Subsets
- Emojis
- Chapter 2 - Engine
- Modules
- Formulas
- Line Items
- Saved Views
- Chapter 3 - UX Principles
- Hierarchy of Information
- Smart Grouping
- Reduce Visual Load
- Progressive Disclosure
- Use Consistency and Standards
- Provide Help and Guidance
- Use The Correct Data Type
- Give Users Visibility Into Status
- Match With Real World Scenarios
- Check In With End Uses Frequently
- Chapter 4 - UX Build
- Apps
- Dashboards
- Filters
- Chapter 5 - Integration
- Actions
- Processes
- Source Models
- Imports
- Exports
- Import Data Sources
- Data Hub
- Chapter 6 - Application Lifecycle Management
- Revision Tags
- Production Lists
- Architecture
- Deployed Mode
- Managing Changes During Development
- Chapter 7 - Extensions
- Excel
- PowerPoint