> ## Documentation Index
> Fetch the complete documentation index at: https://irisdocs.prescientlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Interpretation

> Interpret Iris workflow evidence as a consultant: identify material patterns, validate them and connect them to business consequences.

A workflow visual is useful only when it improves understanding of the client problem.

## Analyse four layers

### Structure

What are the main activities, stages, branches and loops?

### Behaviour

Where do variants, exceptions and rework occur?

### Friction

Where are handoffs, queues, manual effort, duplicate entry or unclear ownership concentrated?

### Consequence

What does that friction cause commercially or operationally?

## Avoid over-reading the visual

A busy-looking map is not automatically a bad process. A simple-looking map may hide a costly bottleneck. Use stakeholder evidence, operational data and client context.

## Validate interpretation

Ask process owners and practitioners whether:

* the main path is representative;
* important variants are missing;
* loops are occasional or systemic;
* identified friction has a meaningful consequence;
* the proposed root cause is correct.

## Move from pattern to recommendation

Do not recommend “automate bottleneck X” until you know why X is a bottleneck. The cause may be technical, policy, ownership, incentives, staffing or upstream data quality.

\[SCREENSHOT REQUIRED: Iris process map showing a validated bottleneck and rework loop]