LensReading which lens this session carries.
The catalogueMarketingDigital & WebAnalytical

Service MK6B

Conversion Experiment

Runs analytical. Starts when the reporting period closes. It runs 34 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 2 of them on the shared spine.

Runs a week

34

168 in flight right now.

Stations

6

1 person · 3 agent · 2 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Digital Experience.

Touchless

68%

Share of runs that complete without anybody opening them.

Timetable against actual

85.2h

Actual 67.2h, 18.0h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 39% of the dwellAgent3 stations and 41% of the dwellShared spine2 stations and 21% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Marketing Automation
Customer Relationship Management
Digital Analytics
Customer Relationship Management
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

Hypothesize

AgentSite Performance Agentworkflow7h 8m13h 59m44Customer Relationship Management
2

Design test

AgentConversion Path Agentworkflow9h 53m15h 36m10Marketing Automation
3

Launch

GBSSite Performance Agentgbs6h 6m11h 17m42Customer Relationship Management
4

Read result

AgentExperiment Design Agentworkflow9h 14m16h 34m33Digital Analytics
5

Decide

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

HumanDirector, Digital Experiencepolicy24h 53m48h 14m7Customer Relationship Management
6

Roll out

GBSSite Performance Agentgbs7h 7m12h 42m32Customer 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%
34 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 gates25 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
846h
34 items at 1,493 minutes of decision each.
Agent time a week
1,341.9h
2,368 minutes an item, which does not compete for a person.
Gate load
97%
Inside capacity, with 29h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
39% waiting on a person
61% in the agent lane
An item now takes 3,861 minutes of worked time end to end against 3,861 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 Conversion Experiment

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.

6 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

6 stations, nothing waiting, nothing sent back

0 min of 2.7 days

now Hypothesize · Site Performance Agent · 7.1 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 4.4 days

now Hypothesize · Site Performance Agent · 7.1 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.

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

4 of 6 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

1 of 6 stations attributed here · would write back

Digital Analytics

Adobe Analytics · marketing · inbound · medium

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Digital Orchestrator
That orchestrator’s remit
Owns web change work end to end inside Marketing. Runs 3 lines across 19 stations, drains the repeatable share into the A2L tower, and holds 3 human gates.
Accountable person
Director, Digital Experience
Sub-function
Digital & Web
Shared spine tower
a2l
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Web Change ReleaseMK6ASite Health WatchMK6C

What this page is and is not

This is a catalogue of the modeled estate.