LensReading which lens this session carries.
The catalogueMarketingProduct MarketingAnalytical

Service MK7C

Adoption Diagnostic

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

Runs a week

14

50 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

Autonomy on this service is set at 65% against a ceiling of 70%.

Decisions a person makes

1

Held by VP Product Marketing.

Touchless

46%

Share of runs that complete without anybody opening them.

Timetable against actual

153.8h

Actual 129.7h, 24.1h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 30% of the dwellAgent4 stations and 70% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Marketing Automation
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

Read usage

AgentLaunch Readiness Agentworkflow3h 50m4h 51m34Customer Relationship Management
2

Segment

AgentValue Proposition Agentworkflow13h 34m30h 24m1Marketing Automation
3

Diagnose friction

AgentPersona Research Agentworkflow1h 41m2h 30m1Digital Analytics
4

Draft actions

AgentSales Collateral Agentworkflow8h 4m11h 25m8Customer Relationship Management
5

Owner review

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

HumanVP Product Marketingpolicy11h 22m14h 48m6Customer 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%
14 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 gates5 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
159.1h
14 items at 682 minutes of decision each.
Agent time a week
380.1h
1,629 minutes an item, which does not compete for a person.
Gate load
91%
Inside capacity, with 15.9h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
30% waiting on a person
70% in the agent lane
An item now takes 2,311 minutes of worked time end to end against 2,311 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 Adoption Diagnostic

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 39 hrs

now Read usage · Launch Readiness Agent · 3.8 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 44 hrs

now Read usage · Launch Readiness Agent · 3.8 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

3 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

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
Product Marketing Orchestrator
That orchestrator’s remit
Owns launch work end to end inside Marketing. Runs 3 lines across 19 stations, drains the repeatable share into the C2L tower, and holds 4 human gates.
Accountable person
VP Product Marketing
Sub-function
Product Marketing
Shared spine tower
Not on the shared spine
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Product LaunchMK7APortfolio Investment PositionMK7B

What this page is and is not

This is a catalogue of the modeled estate.