Landing pages and hotspots

Build a landing page to link to your documentation; processes & URL links

Ksawery Lisinski avatar
Written by Ksawery Lisinski
Updated over a week ago

Elements process mapping brings structure and interconnected network of competencies, allows you to have a deep insight and analysis at the top of your hand.

Article outline

  • Prerequisites

  • Elements mapping overview

  • Option 1. Top Level operational diagram

  • Option 2. Catalog of "End to End" processes

  • Option 3. Using an existing folder structure

  • Useful techniques

  • You might be also interested in


  • Registered and verified Elements account

  • Editors right in Space

Elements mapping overview

The power of the hierarchical mapping approach is that you can build just ONE map and EVERY process diagram is a child diagram.

There are advantages to this rather than having lots of discrete diagrams. You are only managing one map, therefore managing access rights, governance, version control, reporting and branding is far simpler.

The top level diagram is a top-level landing page - a graphical folder structure if you like - where you can put ALL the different process diagrams and data models you will be drawing over time as you document more and more of your Org. 

We’ve seen different approaches for landing pages 

  • An overall company end-to-end process or value stream. This sometimes takes a while to get agreement on if it doesn’t already exist. However, it is very valuable because every process in the company hangs off it somewhere.

  • A series of activity boxes, each of which is a mini end-to-end process, e.g.: “issue to resolution”, “recruit to retire”, “quote to cash”.

  • A simple set of activity boxes for each lower level process diagram, so it is essentially a set of menus or shortcuts

Below are examples of each type of landing page.

Option 1. Top Level operational diagram

This is the flow of high-level activities showing the core value stream of the operation, with individual boxes housing the support processes. If you have this kind of view available - or have the right stakeholders to help you create it - it's our recommended approach. If you can't start with this picture, at least keep it in mind, as it's where you would hope to end up if you use this approach in the longer term.

Option 2. Catalog of "End to End" processes

This is a common way of describing processes in an "IT project" context - “issue to resolution”, “recruit to retire”, “quote to cash”, etc. This is really useful when you do not have the time to agree on how option 1 should look. The example below shows using "Image mode" for the activity box theme. This makes it more visual and when you hover over the image - the text underneath becomes visible. But you could just as easily write "Develop and Close Sales" or "Develop new product" as the text in the activity box. The inputs/outputs in this context are optional. Whatever works for you. It's about communication, context and getting everyone on the same page.

Option 3. Using an existing folder structure

You may have existing documentation and process content in a set of folders. We get asked "how can I save my Elements maps in folders". We would recommend moving to a process focused structure (like Option 1 or 2). If that's not an option, simply create a top-level diagram that replicates your file folder structure for content. While it re-enforces functional silos and misses out on delivering the value of cross-functional visibility, if you absolutely have to stick with it it's no worse than where you are today.

Useful techniques

You might be also interested in

  • Analyze Salesforce help usage - useful, powerful and insightful, this support article tells you all about how your users adopt, use and provide help

Did this answer your question?