LensReading which lens this session carries.

Operate · the run state

Every queue, one day, one canvas

This is the operation as it stood at the close of Sun, Nov 23. 36 queues across 12 towers, ranked not by how large they are but by how fast they are changing …

The documents behind it
Day on screen
Sun, Nov 23
Sun, Aug 17365 modeled daysSun, Aug 16
Back to the last modeled day

Health

What the day did to the operation

Arrival against service is the only pair that tells you whether tomorrow is worse than today.

The binding constraint on this day
Order desk in Order-to-Cash — 65,824 items standing and draining by 160 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 9.1% of everything standing, and it is not growing, so the ranking is driven by the standing depth alone. At the day service rate of 2,218 items, and only if nothing else arrived, what is already standing in it is 29.7 days of work; work does keep arriving, and at the rate it is actually falling it takes 411 days to empty. Its oldest item has been waiting 11.5 d, and 390 of the 2,218 items it did serve cleared outside commitment.

The name recorded against most of the work in this queue in the sampled ledger week is Chidi Obi. That is who this constraint belongs to.

65,824
Standing
9.1%
Share of all standing work
2,058
Arrived on the day
2,218
Served on the day
+43%
Against its own normal
11.5 d
Oldest item

Detail on the record

The blockage map

Every queue in the operation, grouped by tower.

All queues at the close of the day

36 queues · 725,947 items standing · deepest is 65,824

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay117,104 standing · 16.1% of the operation
Buying desk
49,326+34014.9 d
Invoice processing
42,620-2877.2 d
Supplier operations
25,158+2044.2 d
H2RHire-to-Retire96,834 standing · 13.3% of the operation
Payroll operations
58,894-44421.7 d
Time and claims
32,409+4959.7 d
Employee lifecycle
5,531-9439.6 h
ITSIT Service84,441 standing · 11.6% of the operation
Service requests
29,452+7294.6 d
Incident desk
28,183+49120.7 d
Change and access
26,806+8227.3 d
O2COrder-to-Cash84,289 standing · 11.6% of the operation
Order desk
65,824-16011.5 d
Billing and credit
18,254+4828.4 d
Cash and collections
211+21116.7 h
AIOAI Operations81,902 standing · 11.3% of the operation
Agent run desk
34,799+1,1629.2 d
Model routing
31,671+21710.7 d
Prompt and policy
15,432+25811.9 d
M2DMake-to-Deliver79,061 standing · 10.9% of the operation
Make and release
41,943+5296.5 d
Move and deliver
34,449+84611.5 d
Quality control
2,669+1226.9 d
C2LConcept-to-Launch61,544 standing · 8.5% of the operation
Formulation
26,974-28021.7 d
Artwork studio
26,962+50112.2 d
Launch gates
7,608+1233.7 d
R2RRecord-to-Report41,798 standing · 5.8% of the operation
Postings desk
36,149-19912.7 d
Close management
4,884+793.1 d
Reconciliation
765+6418.4 h
P2PPlan-to-Perform21,516 standing · 3.0% of the operation
Replenishment
7,885-6214.5 d
Sales and operations planning
7,519+16711.7 d
Forecast desk
6,112+8812.8 d
A2LAwareness-to-Lead21,023 standing · 2.9% of the operation
Media operations
9,675+1836.5 d
Trade promotion
8,323+558.1 d
Campaign briefing
3,025+47241.5 h
LGLLegal Operations20,084 standing · 2.8% of the operation
Contract desk
12,208+4547.1 d
Obligation management
6,700+6210.5 d
Matter management
1,176-403.7 d
D&AData and Analytics16,351 standing · 2.3% of the operation
Metric governance
5,887+857.4 d
Report certification
5,382-13011.1 d
Data quality
5,082-2025.3 d

Three numbers follow each bar: items standing at the close, the day net change, and the age of the oldest item in the queue. The bars are an exhaustive map of the operation — all 36 queues appear, and their standing depths sum to the 725,947 on the tile above. A queue opens the series with work already in it, so standing depth is not arrivals minus service.

What to pick up

Flow rather than stock

Ranked by how much work releasing the queue would free — standing depth plus five days of the rate at which it is falling behind.

Every queue, ranked by what releasing it frees

26 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Order deskO2C2,0582,218-16065,82445,945+43%29.782%11.5 d
2Payroll operationsH2R2,2192,663-44458,89442,836+37%22.189%21.7 d
3Buying deskS2P2,3001,960+34049,32645,294+9%25.262%14.9 d
4Make and releaseM2D2,2001,671+52941,94331,002+35%25.187%6.5 d
5Invoice processingS2P3,0013,288-28742,62037,662+13%13.064%7.2 d
6Agent run deskAIO2,082920+1,16234,79924,683+41%37.891%9.2 d
7Move and deliverM2D2,3151,469+84634,44924,861+39%23.568%11.5 d
8Postings deskR2R2,5432,742-19936,14931,085+16%13.296%12.7 d
9Time and claimsH2R2,8652,370+49532,40932,079+1%13.766%9.7 d
10Service requestsITS1,8091,080+72929,45221,135+39%27.389%4.6 d
11Model routingAIO1,004787+21731,67120,794+52%40.280%10.7 d
12Change and accessITS2,0141,192+82226,80616,721+60%22.593%7.3 d
13Incident deskITS1,430939+49128,18324,353+16%30.062%20.7 d
14Artwork studioC2L1,092591+50126,96217,362+55%45.688%12.2 d
15FormulationC2L9641,244-28026,97418,167+48%21.773%21.7 d
16Supplier operationsS2P2,0411,837+20425,15820,541+22%13.787%4.2 d
17Billing and creditO2C2,3821,900+48218,25413,529+35%9.682%8.4 d
18Prompt and policyAIO1,243985+25815,43210,309+50%15.764%11.9 d
19Contract deskLGL1,246792+45412,2085,071+141%15.487%7.1 d
20Media operationsA2L584401+1839,6757,456+30%24.183%6.5 d
21Trade promotionA2L659604+558,3234,043+106%13.891%8.1 d
22Sales and operations planningP2P479312+1677,5194,873+54%24.168%11.7 d
23Launch gatesC2L626503+1237,6085,255+45%15.165%3.7 d
24ReplenishmentP2P376438-627,8855,047+56%18.093%14.5 d
25Obligation managementLGL734672+626,7005,432+23%10.087%10.5 d
26Forecast deskP2P456368+886,1125,461+12%16.664%12.8 d
27Metric governanceD&A547462+855,8875,139+15%12.782%7.4 d
28Employee lifecycleH2R1,6111,705-945,5317,631-28%3.293%39.6 h
29Campaign briefingA2L1,6261,154+4723,0255,807-48%2.680%41.5 h
30Report certificationD&A533663-1305,3825,631-4%8.177%11.1 d
31Close managementR2R832753+794,8842,604+88%6.594%3.1 d
32Data qualityD&A8221,024-2025,0826,699-24%5.063%5.3 d
33Quality controlM2D345223+1222,6691,078+148%12.071%6.9 d
34Cash and collectionsO2C834623+211211167+26%0.374%16.7 h
35Matter managementLGL279319-401,1761,061+11%3.787%3.7 d
36ReconciliationR2R1,3981,334+64765808-5%0.690%18.4 h

"Normal" is the mean standing depth for that same queue over the 27 modeled days before the one on screen, so it is a comparison of a queue with itself rather than with any other queue. "Days of work" divides what is standing by what was served on the day. Both are unavailable at the start of the series, where there are no prior days to average.

Now versus normal

29 queues are more than ten percent above their own 27 day mean

M2DQuality control2,669 standing against a normal of 1,078 · +148%
LGLContract desk12,208 standing against a normal of 5,071 · +141%
A2LTrade promotion8,323 standing against a normal of 4,043 · +106%
R2RClose management4,884 standing against a normal of 2,604 · +88%
ITSChange and access26,806 standing against a normal of 16,721 · +60%
P2PReplenishment7,885 standing against a normal of 5,047 · +56%
C2LArtwork studio26,962 standing against a normal of 17,362 · +55%
P2PSales and operations planning7,519 standing against a normal of 4,873 · +54%
AIOModel routing31,671 standing against a normal of 20,794 · +52%
AIOPrompt and policy15,432 standing against a normal of 10,309 · +50%
C2LFormulation26,974 standing against a normal of 18,167 · +48%
C2LLaunch gates7,608 standing against a normal of 5,255 · +45%

The first 12 of 29 are shown, deepest departure from normal first.

The commitment on the day
33,695 of 42,206 items served cleared inside commitment — 79.8%.

8,511 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Invoice processing with 1,186. Commitment here is measured against what was served on the day; items still standing have not yet been judged against it.

900,433
Documents a week
36
Queues on the canvas
365
Days you can travel

Actions

What is waiting on a person

A queue is worth acting on when it is growing, not when it is large.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

This page can rank every queue by depth, by growth and against its own prior distribution, and name the one whose release frees the most work.

Live observability

What the record shows right now

Direction of travel on the day on screen, an exhaustive partition of all 36 queues: each queue either grew, drained or held level.

Current distribution

36 queues

Growing2569%
Draining822%
Level38%

Is policy and strategy coming to fruition

Whether the written intent is holding here

79.6% of what was served on the day cleared inside commitment, with 1,636,528 items left standing.

Nothing on the record settles this

The written position is that work is managed by flow rather than by backlog size, and that a commitment is a promise about each item rather than an average.

What this page is, and what it is not

This page animates a modeled series. The 365 days between Sun, Aug 17 and Sun, Aug 16 were generated from a fixed seed for Brightvale, an invented company, and nothing on this canvas is attached to a running queue in any real system. Moving the day changes which generated row is being read. It does not replay anything that happened.

Brightvale Consumer Group is an invented company.

Two conventions matter for reading it. Queues open the series carrying work, so standing depth is not the running total of arrivals minus service, and the two should not be reconciled against each other. And unlike the ledger, none of this is sampled: arrival, service and depth are full population counts, so multiplying them by fifty to match the ledger sample would be wrong in both directions.

The binding constraint is computed, not chosen. It is the queue with the highest standing depth plus five times the rate at which it is falling behind — a deliberate weighting that puts growth ahead of size. A different weighting names a different queue, and the ranking below it changes with the day on screen.