-
5.01-01 Naming Convention
Use numeric prefixes to signify the order within the process (e.g. 1.1 Import Products, 1.2 Import Product details). There is no need to include the technical module name in the description Related to Rule: 5.02-01 Naming Convention Best Practice article: Naming Convention
-
4.03-06 Avoid filtering on Nested Dimensions
If possible, try and avoid filtering on nested dimensions. Try and pivot the view differently. If this is not possible, ensure the filters are efficient Related to Rule: 4.02-01 Use efficient filters Best Practice article: Filter Best Practice
-
4.03-05 Use User filters to provide dynamic reporting
Create filter modules dimensioned by the users list to support dynamic filtering of module data Related to Rule: 1.03-02 Performance and size can be dependent Users list Best Practice article: Increase end user adoption with smart filters
-
4.03-04 Filter Selections in order of size
If using multiple conditions in a filter, include the conditions in order of list size with numeric conditions last
-
4.03-03 Use time filters on all dashboards
Do not use show/hide function for time; these are static. Using the Time Settings module makes the filtering dynamic when the model calendar changes Related to Rule: 2.01-07 Time Settings Module
-
4.03-02 Keep Filters in separate modules
Try and keep filters in separate System modules. They can then be reused for different modules Relate to Rule: 2.01-15 Filters in separate modules
-
4.03-01 Use efficient filters
For most efficient performance resolve filters to a single Boolean condition for each axis Related to Rule: 4.03-06 Avoid filtering on Nested Dimensions Best Practice article: Filter Best Practice
-
4.02-15 Limit modules with many formatted list line items
Too many list formatted line items displayed on a dashboard can adversely affect performance especially if the lists are large. Try and limit the number of displayed line items in a single module; split them into separate modules if necessary
-
4.02-14 Enable Personal Dashboards
Use Personal Dashboards to enable users to personalize the views of the data Related to Rule: 6.04-03 Master Dashboards Best Practice article: Personal Dashboards - Tips and Tricks
-
4.02-13 Store image URLs in a separate module
Keep all of the image URLs for a list in a separate System module. Be mindful of the correct dimensionality Related to Rule: 2.01-04 Use the D.I.S.C.O. Methodology for Module Design
-
4.02-12 Avoid using Delete action buttons on dashboards for end users
End users could potentially delete historical data, so keep the list element maintenance separate as part of the administration process Related to Rule: 4.02-11 Publish Process Actions instead of Import/Export Actions
-
4.02-11 Publish Process Actions instead of Import/Export Actions
Import and Export actions need to be republished if modified or replaced, whereas Process Actions are always consistent with whatever is held within the Process, making management easier Relate to Rule: 5.01-02 User Facing Actions in a process
-
4.02-10 Turn off the Module name
Use dashboard text to describe the grid, rather than display technical module names Related to Rule: 2.01-01 Naming Convention Exception: 4.02-10a Space Saving: If screen space is at a premium, heading text can take up more space than desired, but do consider the overall user experience and don't clutter up the dashboard
-
4.02-06 Deep Level hierarchies
Create a separate dashboard with selection modules to keep the main dashboards clean. This also allows for more efficiency navigation up and down the hierarchy tree
-
4.02-04 Add Page Selectors rather than module selectors
Use separate page selectors rather than module page selectors, especially if the dimensions are repeated in multiple dashboard elements Related to Rule: 4.02-05 Turn off module page selectors
-
4.02-03 Consider the screen size of the end users
Don't build based on your screen size. Consider the smallest size that users will be viewing the dashboard and build to that size. You should change the screen resolution to double check how the dashboards will look for the end users Related to Rule: 4.02-02 Avoid horizontal scrolling
-
4.02-02 Avoid horizontal scrolling
Try and avoid the screen scrolling horizontally. It is better to fix the grid and scroll within the grid Related to Rule: 4.02-03 Consider the screen size of the end users
-
4.02-01 Back to front design
At the beginning of the design process, take the user stories and the UX Principles. Start with the end in mind Best Practices article: Designing Dashboards
-
3.10-04 User Feedback
Interview users for the initial check in, talk them through your ideas and pages during your building process. Afterwards, you can interview them, or have them use the system and watch them as they do. See where they get stuck or are having troubles and make adjustments to suit their needs
-
3.10-03 After Go-live
Check in after Go-Live to make sure everything is working well for them
-
3.10-02 During the build
Check in with them during your building process to ensure you are on the right track
-
3.10-01 During the design
Put users at the heart of the design. Check in with them during the design to learn what their needs are and help define what and how you build your instance
-
3.09-02 Consider the Business Process
It may be helpful to map out the process. Then in Anaplan, follow the real-world conventions and follow the real-world process when deciding which information to place where, so that it appears in a natural and logical order
-
3.09-01 Use familiar language
Speak the users' language, with words, phrases and concepts familiar to the user
-
3.08-01 Provide Feedback
Ideally, the pages should always keep users informed about what is going on, through appropriate feedback within reasonable time. Being informed about the current status helps users decide what to do next in order to accomplish their goals, and figure out if their actions were effective or if they made a mistake
-
3.07-10 Combination Charts
Combination charts are useful where you want to validate the relationship between two variables that have different magnitudes and scales of measurement but are related in a meaningful way Best Practices article: Combination Charts
-
3.07-09 Waterfall Charts
A waterfall chart can be used for analytical purposes, especially for understanding or explaining the gradual transition in the value of an entity which is subjected to an increase or decrease in value. Often, a waterfall chart is used to show changes in revenue or profit between two time periods Best Practice article:…
-
3.07-08 Timeline charts
A timeline chart is an effective way to visualize a process using chronological order. Since details are displayed graphically, important points in time can be easily seen and understood. They are often used for managing a project’s schedule, timeline charts function as a sort of calendar of events within a specific period…
-
3.07-07 Funnel Charts
Funnel charts are often used to represent stages in a sales process and show the amount of potential revenue for each stage. This type of chart can also be useful in identifying potential problem areas in an organization's sales processes. A funnel chart is similar to a stacked percent bar chart Best Practice article:…
-
3.07-06 Pie Charts
Pie charts are best to use when you are trying to compare parts of a whole. They do not show changes over time Best Practices article: Pie Charts
