lolivingobjects
The transformation journey

Five phases, one gate at a time,
until your teams lead.

One team, from level 3 to level 4.

M0M1M2M3M4M5M61 · FRAME2 · MAP3 · ADAPT4 · EARN TRUST5 · EXTENDscenario 1scenario 2scenario 3zones, domainsgateshadowaskallow
Indicative durations for one operator entity. Each scenario climbs on its own: shadow, then ask, then allow. The next one starts before the previous one finishes, and your teams carry the third one past month six.
Weeks 1–3

Frame: the ambition, in figures

Leave week three with a target the executive committee has signed.

People
CTO, domain heads, sponsor, programme lead. With us: engagement lead, senior network expert.
Workstreams
  1. Ambition. Set the target autonomy level at two, five and seven years.
  2. Baseline. Rate every activity on the TM Forum autonomy scale.
  3. Indicators. Build one indicator tree, from executive committee to scenario team.
  4. Governance. Name the sponsor, the programme lead and the steering committee.
Deliverables
Signed ambition · baseline · indicator tree · governance charter · confidential business case.
GateExecutive committee sign-off.
Weeks 3–8

Map: where the time goes

Pick the three scenarios worth starting with.

People
Working groups from every domain, the future core team. With us: facilitators, network and data engineers.
Workstreams
  1. Listen. Collect each team's expectations and pain points.
  2. Activities. Measure where time is spent and where it waits, by value stream mapping.
  3. Data. Rank every source by value and by cost of access.
  4. Scenarios. Rank candidates against b.lo's standard scenarios by volume, risk and data readiness.
Deliverables
Activity map · value stream maps · data source map · ranked backlog.
GateThree scenarios chosen, core team named.
Months 2–4

Adapt: from the b.lo base to your know-how

Start from the multi-vendor base, then capture your own expertise, case by case.

People
Core team, domain experts. With us: network engineers, platform integrators.
Workstreams
  1. Need. Align the team on what it wants, through user stories.
  2. Processes. Adapt the standard BPMN processes to your organisation.
  3. Diagnosis. Grow the base tree with your own causes, markers and remediations.
  4. Bench. Freeze the historical cases that prove the tree on your network.
Deliverables
Sources connected · your processes · your diagnostic tree · bench.
GateThe tree meets its precision target on the bench.
From month 3

Earn trust: from shadow to allow

Delegate a scenario once it has proven itself on your network.

People
Zone analysts, experts who write the policies, steering committee. With us: scenario lead.
Levels
  • shadowAgents propose, analysts decide, agreement is measured.
  • askThe agent prepares, an analyst validates.
  • allowThe action runs within your experts' policy, logged and re-measured.
Criteria
Shadow to ask: target agreement reached, no regression on the bench.
Ask to allow: policy approved, thirty days of operations replayed.
Deliverables
Per scenario: level · policy · replay report.
GateThe steering committee approves each promotion.
Months 5–6

Extend: your teams take the lead

By month six your teams take the lead: they run the proven scenarios on their own and extend them to new zones, new domains and new scenarios.

Request a demo