A Work Mode answers one narrow question: how should a manager approach this interaction so the confirmed management work has a better chance of reaching closure? It does not answer who a person is, whether they are a risk, or whether a Management Loop should exist.
The order matters
The evidence comes first. If configured Work Evidence suggests that management work may be open, Clio can create a Possible Loop. A manager must confirm or dismiss it. Only then does the Loop become management work.
The Loop type determines the closure requirement and the Management Skill — the intervention needed to move the work. Work Mode comes later and changes the way that intervention is framed.
Skill = what. Work Mode = how.
What Work Modes never do
- They do not create a Possible Loop.
- They do not determine Loop priority.
- They do not label a person as decisive, avoidant, high-risk, low-risk or any other identity.
- They do not prove that a manager should take employment or performance action.
- They do not replace the evidence required to close the Loop.
Where the context comes from
Where the feature is enabled, Clio may use an optional individual self-assessment and prior interaction context to calibrate how an intervention is presented. That context is secondary to the work evidence. If the context is unavailable, Clio can fall back to a neutral intervention instead of inventing a profile.
Clio follows work, not people. Work Evidence determines what may be open. Work Mode only helps determine how to approach the interaction.
A concrete example
Suppose a KPI recovery Loop is confirmed because a KPI is below target and there is additional operational evidence that related commitments remain open. The Management Skill might be Prepare KPI recovery 1:1. The manager still has to approve the intervention. Work Mode can then change the opening and sequence of that 1:1 — without changing why the Loop exists or what would count as closure.
The Loop closes only when its required Closure Evidence exists. A better KPI is observed separately as a business outcome; it does not retroactively prove that the management work closed.
The product boundary
Work Evidence → Loop → Skill → Work Mode → Action → Closure Evidence. Keeping those objects separate is what lets Clio personalize management without turning personalization into employee profiling.
In short
Work Modes are interaction context. They make a confirmed intervention land better, but they never decide that a problem exists. The Management Loop remains the operational object; the Skill defines what needs to happen; Closure Evidence decides whether it is done.