Durations

How long work sits between steps. Durations measures the wait between any two activities in the current cohort, shows the spread behind the average, and ranks every transition by how long objects typically wait to make it.

What Durations answers

The process map shows you that an edge is red. Durations tells you how long that wait really is, how consistent it is, and which transitions are worth your attention first. It measures waits: the gap between one activity and the next. An object's whole cycle time lives on Health.

A long wait is not automatically a bottleneck — a step that runs overnight by design has a long wait too — which is why the page is called Durations. It gives you the numbers; you decide which of them are problems.

Open it from Durations in the project sidebar. Like every page in the project, it answers to the active filters, and the count in the top-right says how many objects of the lens type are in view.

The page, top to bottom

Headline tiles

Slowest transition — the step-to-step move with the longest average wait, labelled as an average
Slow steps — how many step-to-step transitions average more than three days
Targets — when the project has SLA targets: how many are set, with the total number of objects currently over target underneath (summed across targets, so an object over two targets counts twice)

Analyze a span

Pick any two events — consecutive or not — and the page draws the distribution of the time between them: a histogram of waits, with the median and the spread. Either end of the span can also be a point on the timeline rather than a named event:

From → First event — measure from the start of each object's journey
To → Last event — measure to the end of it
To → Now (end of data) — measure to the latest point in the data, which is how you ask "how long have the unfinished ones been waiting?"

Spans between two named events count only the objects that reached the second one. If an event happens more than once on the same object, a First / Last switch appears beside that picker so you can say which occurrence you mean; the To side always means an occurrence after the From one.

Set target turns the span into an SLA target: a threshold, the number of objects that would breach it, and a rule that keeps counting from then on.

Picking bars

Clicking bars in the span chart does not filter straight away. Picks are one continuous run of bars — click outside the run to extend it, click an end bar to drop it, click inside to cut it, or drag across the bars you want — and the top bar shows how many objects the pick will keep. Press Apply to make it a filter that every page in the project answers to; Clear in the chart header removes it again.

Transitions by average wait

A table of the fifteen slowest step-to-step transitions: from, to, average wait, median wait, how many objects made the move, and the SLA target with its breach count where one exists. Click a row to load that transition into the span analyser above; click it again to clear. The From and To column headers carry the same First / Last switch as the span picker, and it applies to every row. The table downloads as CSV.

Reading the numbers

A wide spread matters more than a slow average. A step that always takes three days is a scheduling fact; one that takes anywhere from an hour to a month is a queue nobody is managing. Look at the histogram, not just the tile.
Median beats mean for waits. A handful of objects stuck for months drags the average up; the median tells you what usually happens.
Compare before you conclude. Filter to the slow objects — pick the right-hand bars and Apply — then open Compare to see what sets them apart from the rest.

Working with the rest of the product

From the map — a red edge is a wait; open Durations to see its distribution and rank it against the others
Into filters — every applied pick is an ordinary filter, visible in the Active Filters panel and carried in the URL
Into Rules — Set target stores the threshold as a rule, so breaches are counted over time on the Rules page
From the copilot — "which step has the longest wait?" answers with the same numbers, and can link you here with the cohort carried

Next steps

Health — the whole cycle time, and which steps repeat
Rules — turn a wait you will not accept into a target
Compare — find out what the slow objects have in common

Waits are where the time goes

Most of an object's cycle time is not work; it is waiting for the next step to start. Durations is the page that shows you where, and by how much.