LensReading which lens this session carries.
The catalogueMarketingAttribution & AnalyticsAnalytical

Service MK11B

Incrementality Test

Runs analytical. Starts when the cycle calendar fires. It runs 28 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

28

78 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 60% against a ceiling of 84%.

Decisions a person makes

1

Held by Director, Marketing Analytics.

Touchless

69%

Share of runs that complete without anybody opening them.

Timetable against actual

77.9h

Actual 92.1h, 14.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 40% of the dwellAgent3 stations and 38% of the dwellShared spine1 station and 23% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Marketing Automation
Digital Analytics
Customer Relationship Management
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Design holdout

AgentAttribution Model Agentworkflow11h 29m23h 6m17Customer Relationship Management
2

Run

GBSAttribution Model Agentgbs13h 53m30h 36m10Customer Relationship Management
3

Measure lift

AgentAnomaly Detection Agentworkflow1h 40m3h 15m33Marketing Automation
4

Draft finding

AgentReporting Automation Agentworkflow9h 48m22h 27m16Digital Analytics
5

Ratify

Held for a named human when the unit exceeds the analysis decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

HumanDirector, Marketing Analyticspolicy24h 17m52h 23m2Customer Relationship Management

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through.

Move something
Demand100%
28 a week is what the estate records.
Decisions handed to agents0 of 0
This service has at most one gate, so there is nothing to hand over without removing the last human decision.
People on the gates20 people
Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.
Agent speed100%
100% is the dwell the estate records today.
Person time a week
679.9h
28 items at 1,457 minutes of decision each.
Agent time a week
1,031.3h
2,210 minutes an item, which does not compete for a person.
Gate load
97%
Inside capacity, with 20.1h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
40% waiting on a person
60% in the agent lane
An item now takes 3,667 minutes of worked time end to end against 3,667 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.
What this model is, on Incrementality Test

The simulation is arithmetic on the estate, not a queueing model.

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking.

5 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

5 stations, nothing waiting, nothing sent back

0 min of 2.5 days

now Design holdout · Attribution Model Agent · 11 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 4.5 days

now Design holdout · Attribution Model Agent · 11 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

4 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

3 systems attributed

0 of 3 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

3 of 5 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

1 of 5 stations attributed here · would write back

Digital Analytics

Adobe Analytics · marketing · inbound · medium

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Marketing Analytics Orchestrator
That orchestrator’s remit
Owns analysis work end to end inside Marketing. Runs 3 lines across 16 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 3 human gates.
Accountable person
Director, Marketing Analytics
Sub-function
Attribution & Analytics
Shared spine tower
data-analytics
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Monthly Performance ReadMK11AMix Reallocation PositionMK11C

What this page is and is not

This is a catalogue of the modeled estate.