LensReading which lens this session carries.

The work elsewhere

What this platform can actually see

Across every function the platform observes 77.9% of the work, reconstructs 14.3% by rule or cohort, and knows that 7.8% happens where it cannot read it.

Every function, and how much of it the platform reads

Ordered as the estate is ordered, not by score.

Sales
Source system count · plus or minus 14% · Chief Revenue Officer
50.0%observed of 4,820 a week
observed 2,410inferred 1,204unseen 1,206
Field negotiation held in email and in the account team’s own spreadsheets before anything reaches the quote system.
Marketing
Source system count · plus or minus 18% · Chief Marketing Officer
60.0%observed of 6,140 a week
observed 3,684inferred 1,535unseen 921
Agency work and campaign approvals that never enter the automation platform.
Revenue Growth Management
Source system count · plus or minus 9% · SVP Revenue Growth Management
73.0%observed of 11,240 a week
observed 8,206inferred 2,135unseen 899
Manual reconciliation of quote and order data in analyst workbooks.
Legal
Interview with the function · plus or minus 26% · General Counsel
40.0%observed of 2,140 a week
observed 856inferred 428unseen 8561 attestation
Advice given verbally or by email that never becomes a matter record.
Procurement & Source-to-Pay
Source system count · plus or minus 11% · Chief Procurement Officer
70.0%observed of 8,940 a week
observed 6,258inferred 1,788unseen 894
Off-contract buying settled on a corporate card and reconciled later.
Supply Chain
Source system count · plus or minus 13% · Chief Supply Chain Officer
65.0%observed of 9,620 a week
observed 6,253inferred 2,405unseen 962
Carrier and 3PL exception handling conducted on the carrier’s portal.
Engineering
Source system count · plus or minus 12% · Chief Technology Officer
70.0%observed of 3,140 a week
observed 2,198inferred 628unseen 314
Design decisions taken in chat and recorded only in a commit message.
Research & Development
Declared gap against a disconnected system · plus or minus 31% · Chief Scientific Officer
30.0%observed of 1,420 a week
observed 426inferred 284unseen 7101 attestation
Bench work recorded in the research notebook, which is not connected.
Finance
Source system count · plus or minus 8% · Chief Financial Officer
70.0%observed of 12,480 a week
observed 8,736inferred 2,496unseen 1,248
Close adjustments prepared in workbooks and posted as a single journal.
Human Resources
Interview with the function · plus or minus 22% · Chief Human Resources Officer
60.0%observed of 6,240 a week
observed 3,744inferred 1,560unseen 936
Employee relations conversations that are deliberately not systematized.
Information Technology
Source system count · plus or minus 10% · Chief Information Officer
80.0%observed of 18,640 a week
observed 14,912inferred 2,796unseen 932
Desk-side fixes done without a ticket being raised.
Administration
Interview with the function · plus or minus 24% · Chief Administrative Officer
50.0%observed of 8,420 a week
observed 4,210inferred 2,526unseen 1,6841 attestation
Facilities and travel requests raised by email or in person.
Customer Service
Source system count · plus or minus 7% · Chief Customer Officer
85.0%observed of 42,800 a week
observed 36,380inferred 4,280unseen 2,140
Escalations handled by an account manager outside the contact center.
AI GBS & Global Business Services
Source system count · plus or minus 6% · Head of Global Business Services
90.0%observed of 64,200 a week
observed 57,780inferred 4,494unseen 1,926
Requester follow-ups taken by a service desk agent over chat and closed verbally.

Every outcome chain, and how its links were joined

Here observed means a stage link joined on a shared key.

Requisition to receipt
Stage link provenance · plus or minus 17% · Diego Fuentes
29.4%observed of 326 links
observed 96inferred 189unseen 41
Requisitions raised verbally to a buyer and entered later under the buyer’s own name.
Invoice to payment
Stage link provenance · plus or minus 29% · Sofia Kalogeropoulou
0.0%observed of 352 links
observed 0inferred 289unseen 63
Paper and PDF invoices received directly by a business unit and forwarded weeks later.
Order to cash
Stage link provenance · plus or minus 21% · Beatriz Salgado
17.0%observed of 88 links
observed 15inferred 55unseen 18
Orders taken by phone by the field team and keyed the next day.
Deduction to settlement
Stage link provenance · plus or minus 33% · Rafael Duarte
0.0%observed of 65 links
observed 0inferred 43unseen 22
Trade claims agreed in a customer meeting and confirmed by email.
Hire to productive
Stage link provenance · plus or minus 35% · Grace Mutiso
0.0%observed of 385 links
observed 0inferred 311unseen 74
Interview feedback given verbally and summarized by the recruiter.
Close to report
Stage link provenance · plus or minus 9% · Nils Andersen
51.3%observed of 624 links
observed 320inferred 256unseen 48
Close tasks tracked on the controller’s own checklist.
Query to resolution
Stage link provenance · plus or minus 15% · Wei Lin Tan
46.2%observed of 455 links
observed 210inferred 190unseen 55
Queries answered in the same call without a case being opened.
Concept to shelf
Stage link provenance · plus or minus 27% · Yasmin Chaudhry
35.2%observed of 301 links
observed 106inferred 129unseen 66
Concept work carried in the research notebook, which is not connected.

How each figure was produced

A method is the thing to argue with.

Source system count10
Observed comes straight from what the connected systems return. The remainder is split between what the platform can reconstruct and what it is told exists.
45% of statements
Stage link provenance8
Observed is the count of stage links joined on a shared key. Inferred is joined by rule or by cohort. Unseen is the residual against the declared instance count.
36% of statements
Interview with the function3
The unseen share was given by the function rather than computed. It is the weakest method here and is labeled as such wherever the figure appears.
14% of statements
Declared gap against a disconnected system1
The unseen share is anchored on a named source system in a not-connected state, so the gap has a cause on the record rather than an estimate behind it.
5% of statements

Actions

What is waiting on a person

A coverage statement is only as good as the method behind it.

6

statements carrying an uncertainty band of a quarter or more

The widest is Hire to productive at plus or minus 35%. A band this wide means the figure should be read as a range …

3

functions whose unseen share came from an interview, not a count

Legal · Human Resources · Administration.

3

outcome chains with no keyed link at all

Invoice to payment · Deduction to settlement · Hire to productive.

1

function estimate nobody has put their name to

Human Resources. An attestation would not make the figure measured. It would put a person behind the estimate …

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

This surface publishes a coverage statement and lets anybody dispute the method behind it.

Live observability

What the record shows right now

Work items a week across every function, split 3 ways by how the platform knows about them.

Current distribution

200,240 items a week

Observed156,05378%
Inferred28,55914%
Unseen15,6288%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Yes on saying it.

Holding on the record

The written intent is that the platform says what it cannot see rather than reporting a clean estate.

How to disagree with a number on this page

Coverage can only ever be estimated from the outside.

A coverage statement is disputable by design.

3 statements rest on an interview rather than a count. Those are the ones to challenge first, and the function head named on each one is the person who gave the figure. 3 statements carry an attestation, and every one of them is signed by an office rather than by an individual, which is the weaker of the two.

File work the platform could not see