About rob_marshall

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

If the chart has a filtered axis, set the filter such that all items are shown, then publish the chart. Then set the filter criteria back as desired; the chart will then respect the filter

rob_marshall · ‎08-24-2020

Educate the users to use the Refresh option in the toolbar rather than action "refresh" buttons to open dashboards

rob_marshall · ‎08-24-2020

Use the contents page for navigation rather than clutter the dashboards with buttons Exceptions: 4.02-07a Iterative processes: When the user needs to toggle back and forth between dashboards, it is acceptable to have navigation buttons (old UX)

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

Show the page selector is appropriate but try and drive the selection from a general page selector Related to Rule: 4.02-04 Add Page Selectors rather than module selectors

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-24-2020

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

rob_marshall · ‎08-20-2020

@1454884 Only bring in the data at the level (granularity) you need into the spoke models. So, if you have transactional (daily level) data in the hub but only use Monthly level data in the spoke model, only bring that into the spoke model. Understand what data you really need for that model and what granularity and only bring that in. Rob

rob_marshall · ‎08-19-2020

@Srivaths123 , Understood about that piece, but why have an additional data hub? Why not keep the data in the initial data hub and have views within that data hub feed the spoke model?

rob_marshall · ‎08-19-2020

@Srivaths123 , Yes, you can do that by setting up a view in the data hub and have the other models call that view. But, I am curious, why have a data hub feeding another data hub? Rob

rob_marshall · ‎08-19-2020

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

rob_marshall · ‎08-19-2020

Check in after Go-Live to make sure everything is working well for them

rob_marshall · ‎08-19-2020

Check in with them during your building process to ensure you are on the right track

rob_marshall · ‎08-19-2020

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

rob_marshall · ‎08-19-2020

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

rob_marshall · ‎08-19-2020

Speak the users' language, with words, phrases and concepts familiar to the user

rob_marshall · ‎08-19-2020

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

rob_marshall · ‎08-19-2020

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

rob_marshall · ‎08-19-2020

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: Waterfall Charts