ºÚÁϳԹÏÍø

Use Focus views to analyse processes in Ardoq ShiftX

Updated on: 6 April 2026

Learn how to use Focus views to analyse processes and spot patterns or problems.


Before you start

You must be viewing or editing a process in the process editor. Focus works only if roles, people or systems have already been added to steps using components. If not, add these first.

See Create and update processes in Ardoq ShiftX for more details.


What Focus is

Focus lets you centre the process view on:

  • roles
  • teams
  • University groups
  • applications
  • information objects

When you apply Focus, only the steps linked to that item are highlighted. The full process is still there, but easier to read.

Focus changes how the process is viewed, not how it is built.


Why Focus is useful

Focus helps people understand responsibility without making the diagram messy.

It is useful for:

  • reviews and workshops
  • talking through a process with different teams
  • checking who is involved at each stage

You can switch Focus on and off without changing the process.


Focus compared to swimlanes

Focus and swimlanes both show responsibility, but they work differently.

Swimlanes:

  • split the process into fixed lanes
  • change the structure of the diagram
  • can become crowded in complex processes

Focus:

  • filters the view instead of changing the structure
  • works for different roles or systems without redesign
  • keeps the process simple and clear

Why Focus is often better than swimlanes

Focus has some clear advantages:

  • one process can support many views
  • no need to redraw the process when roles change
  • easier for non‑technical users to understand
  • faster to use in discussions and reviews

This makes Focus well suited to early drafts and ongoing improvement work.


How to use Focus

To use Focus:

  1. open the process
  2. select Focus from the bottom panel
  3. choose the role, person, team or system
  4. the view updates to highlight the relevant steps

You can change or remove Focus at any time.


Good practice

When using Focus:

  • use it for discussion and analysis, not structure
  • make sure roles and systems are clearly added to steps
  • avoid mixing heavy swimlane designs with Focus
  • use Focus in reviews to confirm responsibilities

You can also use Focus with drafts to compare current and future responsibilities.