LensReading which lens this session carries.
The catalogueSalesSales EnablementTransactional

Service SL10B

Playbook Refresh

Runs transactional. Starts when a scheduled window opens. It runs 2,205 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

2,205

82 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Sales Enablement.

Touchless

82%

Share of runs that complete without anybody opening them.

Timetable against actual

20.1h

Actual 15.0h, 5.1h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 42% of the dwellAgent3 stations and 35% of the dwellShared spine1 station and 23% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Contract Lifecycle Management
Configure, Price and Quote
Contract Lifecycle 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

Mine wins

AgentSkill Gap Agentworkflow2h 55m6h 36m38Customer Relationship Management
2

Draft play

AgentContent Assembly Agentworkflow1h 42m3h 5m26Contract Lifecycle Management
3

Field test

AgentCertification Trackerworkflow10m18m5Configure, Price and Quote
4

Leader approve

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

HumanDirector, Sales Enablementpolicy5h 39m11h 39m1Contract Lifecycle Management
5

Publish

GBSCall Coaching Agentgbs3h 9m4h 53m12Customer 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%
2,205 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 gates356 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
12,458.3h
2,205 items at 339 minutes of decision each.
Agent time a week
17,493h
476 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 1.8h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
42% waiting on a person
58% in the agent lane
An item now takes 815 minutes of worked time end to end against 815 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 Playbook Refresh

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

now Mine wins · Skill Gap Agent · 2.9 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 19 hrs

now Mine wins · Skill Gap Agent · 2.9 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

2 of 5 stations attributed here · would write back

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

2 of 5 stations attributed here · would write back

Configure, Price and Quote

Salesforce CPQ · crm · inbound · high

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
Enablement Orchestrator
That orchestrator’s remit
Owns enablement asset work end to end inside Sales. Runs 3 lines across 14 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person
Director, Sales Enablement
Sub-function
Sales Enablement
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

Seller RampSL10ACall Coaching LoopSL10C

What this page is and is not

This is a catalogue of the modeled estate.