LensReading which lens this session carries.
The catalogueMarketingProduct MarketingTransactional

Service MK7A

Product Launch

Runs transactional. Starts when an upstream system posts an event. It runs 2,484 times a week across 8 stations. 2 of those stations stop for a person and 6 are done by an agent, none of them on the shared spine.

Runs a week

2,484

155 in flight right now.

Stations

8

2 person · 6 agent · 0 spine

Agent share of steps

75%

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

Decisions a person makes

2

Held by VP Product Marketing.

Touchless

67%

Share of runs that complete without anybody opening them.

Timetable against actual

0.8h

Actual 0.9h, 0.1h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 58% of the dwellAgent6 stations and 42% of the dwellShared spine0 stations and 0% of the dwell2 crossings 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
Customer Relationship Management
Marketing Automation
Digital Analytics
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

Launch brief

AgentLaunch Readiness Agentworkflow1h 44m3h 37m37Customer Relationship Management
2

Build narrative

AgentValue Proposition Agentworkflow38m1h 24m32Marketing Automation
3

Assemble collateral

AgentPersona Research Agentworkflow1h 6m2h 15m7Digital Analytics
4

Enablement pack

Hands over at sales

AgentSales Collateral Agentworkflow8m16m25Customer Relationship Management
5

Readiness 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 Marketingpolicy4h 21m8h 19m0Customer Relationship Management
6

Go decision

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 Marketingpolicy5h 59m14h 14m9Customer Relationship Management
7

Launch

AgentPortfolio Strategy Agentworkflow51m1h 17m43Marketing Automation
8

Measure

AgentProduct Marketing Orchestratorworkflow3h 2m3h 59m2Digital Analytics

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%
2,484 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates734 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
25,668h
2,484 items at 620 minutes of decision each.
Agent time a week
18,588.6h
449 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 22h of headroom.
Stations without a person
75%
2 gates left on 8 stations.
Where an item spends its time
58% waiting on a person
42% in the agent lane
An item now takes 1,069 minutes of worked time end to end against 1,069 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 Product Launch

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.

8 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

8 stations, nothing waiting, nothing sent back

0 min of 18 hrs

now Launch brief · Launch Readiness Agent · 1.7 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 37 hrs

now Launch brief · Launch Readiness Agent · 1.7 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

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

4 of 8 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

2 of 8 stations attributed here · would write back

Digital Analytics

Adobe Analytics · marketing · inbound · medium

modeled

2 of 8 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
sales

Other services in this sub-function

2 alongside this one

What this page is and is not

This is a catalogue of the modeled estate.