Transitioning to the New User Experience

Fwolf · July 2019

Anaplan provides a user with endless ways to build out a planning platform across a multitude of use cases. This also provides our model builders with the opportunity to get creative with how to build dashboards.

After implementing various use cases in Anaplan and building out the many dashboards to support them, I took a step back and reviewed all of these dashboards. I boiled it down to the activity that was occurring in each dashboard and created a list of the different types of dashboards one would typically build out in a planning application. Below, I've listed the different types of dashboards and thoughts on how to redesign them using Anaplan's new user experience platform.

One of the goals of the new user experience is to eventually transition all existing and new dashboards to it. While Anaplan is still developing this platform though, there are some things that will remain easier and more intuitive in classic Anaplan for the time being. As Anaplan continues to build out new features and functionality in the new user experience, we will be updating this page to highlight when a specific type of dashboard can be built in the new user experience.

Input and Action Dashboards

Most of these will fall in the category of worksheet pages in the new UX. Below we will discuss how to best use the new user experience features to design them.

Type of Dashboard

Recommended Approach

Top-down forecasting

Set a target at a top level of the hierarchy, review results and override as you walk down levels of the hierarchy

Worksheet Page: Choose the primary grid where the top down forecast starts as the main grid for the page. Use the related content to allow users to walk down the levels of the hierarchy.

Another option is to create a worksheet page for each level of the hierarchy and link the pages together through the side bar navigation.

Notes: Use Hierarchy Sync with the Hierarchy Filter to walk down the hierarchy

Bottom level planning (for specific items)

(ie. New products or top performers, etc). Most likely this would be driven by a filter of sorts

Worksheet Page: Choose the primary grid where data is input as the main grid page. Use grid cards in the context panel to show product attributes and filters

For driver-based planning you could choose the primary grid as the results of the drivers and have the grid where you choose drivers as related content.

Add a new item to a list and input related data for the new list item

Worksheet Page: use actions to add a new member. Then use the primary grid to fill out the details of the new member that has been added.

Form Page - (Coming soon!!) - the new UX will include Forms for inputting data when adding new members.

Scenario planning

Need the ability to add a new scenario, copy from existing or start with a blank scenario, input values

Worksheet Page: Use actions to add a new scenario. Then use the primary grid to provide a name for the scenario and any additional details. Link to pages to perform scenario planning using the context panel.

Excel-like input page

Type into multiple rows and then run an upload action. This would include actions for export template, import template, run action, clear form

Worksheet Page: Use actions for export template, import template, run action, clear form. The primary grid will show the Excel-like input page.

Notes: This may need to be done in classic UX if users are copy/pasting from Excel until copy/paste is available.

Review large data sets (base data)

Review transactional data

Worksheet Page: Choose the transactional data module as the main grid page. Use cards in the context panel to show user-based filters.

Input commentary on Module Data

Worksheet Page: Choose the module to comment on as the main grid page. Have users select a line and use a grid card in the side bar or separate view of the same module in the related views to input commentary.

Workflow Dashboards

Integration with Anaplan's workflow functionality is coming soon to the new User Experience. Until this is fully integrated we recommend the following approach:

Type of Dashboard

Recommended Approach

Approval Dashboard

Worksheet Page: Use the primary grid to show approval status. Use related content to show values of items being approved.

Board Page: Set up grid cards to show approval status and values of items being approved. Use a KPI card to enter commentary for specific approval lines

Lock or Snapshot Data

Worksheet Page: Use the primary grid to choose versions or scenarios to snapshot or lock. Use actions for running the lock process. Related grids or context panel can be used to show high-level view of data that will be copied.

Board Page: Use grid cards to choose versions or scenarios to snapshot or lock. Use action cards to run the lock process.

Additional grid cards or graphs can be added to show the data that is copied.

Menu or Task list Dashboards

Including directions and information for when to navigate to other dashboards

Board Page: Use text boxes and link to other board or worksheet pages using the title of the text box.

Notes: There will not be role-specific landing dashboards

Reporting, KPI, Executive Summary Dashboards

Most reporting dashboards should naturally migrate to Board Pages as they are meant for reporting.

Although worksheet pages are generally classified for action-driven work and user inputs, there is nothing stopping you from also using them for reporting purposes. Worksheet pages can also be very helpful for reporting as well especially in situations where the report is a large grid of data or where the end user needs to input a field that will drive the values in the report.

Type of Dashboard	Recommended Approach
Executive Summary Dashboard	Board Page: Use combination of KPI Cards, Charts, and Tables depending on what data you want to show.
Variance reporting	This dashboard could be built in both board and worksheet variations: Board Page: Use a board page to show high level variance reporting. A boards could be set up with both the table showing the variance and a graph to accompany it. Use KPI card to show high level totals. Worksheet Page: if you intend to show one primary grid and want the grid to take up the whole screen. If users are selecting what to compare for version 1 and version 2 or a MTD / YTD view use a card on the sidebar. The side bar can also be used to show trends or other graphical views of the variance View Designer (Coming soon!!): will allow a user to add a calculation (line item) on top of an existing table view. In this case they could add in a variance column when they need it.
Top X Report (ie. Top 10 Performers, or Top 10 Products)	Board Page: Use combination of KPI Cards, Charts, and Tables depending on what data you want to show.
Multiple module reports / graphs	Board Page: Use combination of KPI Cards, Charts and Tables depending on what data you want to show.
Data Validation	Worksheet Page: Use primary grid to show the full data set. Use cards in the context panel to show user-based filters. Use related content to show additional modules with data validation (ie. record counts, summary values by month, specific filtered views to show missing data, etc.).
Ad-Hoc Reporting	View Designer (Coming soon!!): will allow a user to add in ad-hoc calculations.

Admin and Maintenance Dashboards

Administrative dashboards do not fall into a natural category within the new user experience and depending on what the dashboard is used for it could work in both Board and Worksheet pages.

Type of Dashboard	Recommended Approach
Data import, map, and validate	Board Page: Add grid cards for data validation and action cards for imports Worksheet Page: If this is a large set of data and any additional input is needed from the end users this will be better suited to a worksheet page
Hierarchy maintenance Updating lists through running actions or manual adjustment	This will remain in Classic UX until actions are available and lists can be published onto dashboards.
Documentation	Board Page: Use text cards with details and directions on how to use the application. Use links from text card titles to other worksheet and board pages for navigation. Use KPI cards to show number of. Notes: Help tool tips are coming soon.
Landing Dashboards	Board Page: Use text cards with details and directions on how to use the application. Use links from text card titles to other worksheet and board pages for navigation. Notes: Currently there are not role specific landing dashboards. Use the dashboard name to identify it as a landing dashboard. Use classic Anaplan for the ability to use list properties to open different dashboards (currently you will not be able to link navigation of dashboards from classic and the new user experience with any actions).

andrewtye · July 2019

Nice overview. Think that it's 50/50 on the high-level forecasting between sheet and boards. Now that boards are editable if you're inputting in full-year numbers or adjustments and want to see the impact with graphs would lean towards there for that. Then move into the sheet for the lower level adjustments...

david.savarin · August 2020

Are there any hints as to when the Integration with Anaplan's workflow functionality will be available in new ux ?

We have use of new ux which is very good but it is a bit annoying for user to have to switch to classic ui to manage data completion lock and / or unlocking data.

vazqulu1 · July 2022

Thanks for compiling the information and providing the table.

Some screenshots of the Recommended Approach would be helpful too.

coraparks · August 2022

Thank you for this overview!

Currently I am using the strategy of all legacy dashboards are in the classic view, and new dashboards to be built will be done in the NewUX. Is that a typical COE response to the NewUX change for legacy customers, or do you see COEs changing all dashboards to the NewUX over time?