Mainframe Order-Journey Decomposition Leader

The mandate

Three modernisation programmes have built new channel and orchestration layers while the mainframe still decides whether consumer, small-business and wholesale orders can be fulfilled. Duplicate state, overnight corrections and product-specific activation rules make apparently simple changes hazardous. The transformation leader was removed after a fibre launch generated orders that appeared complete online but remained stranded between credit, inventory, provisioning and billing, creating both customer harm and regulatory escalation.

Across eighteen months, the interim executive must define bounded order journeys, expose authoritative state, establish event and reconciliation contracts, and direct progressive extraction through production slices rather than another wholesale rewrite. Priority journeys include new activation, address move, service modification, cancellation and number portability. Each release must prove commercial completion, network activation, bill initiation and recoverable exception handling before legacy logic is retired.

The permanent platform executive will be selected by month eleven and inherit the final two migration waves under observation. Handover requires that successor to chair a launch decision, resolve a cross-domain state dispute and present the retirement evidence for one mainframe component to the investment board. The interim leader must transfer architecture rationale, vendor dependencies, service economics, migration controls and the uncomfortable residual constraints—not merely a polished roadmap.

Within approved funding, the seat can stop unsafe releases, reset sequencing, require common order-state definitions, redirect programme capacity, approve journey boundaries, appoint migration owners and retire code after evidence gates pass. It cannot change regulated service terms, accept customer-remediation exposure, renegotiate network contracts, waive security or financial controls, or close the mainframe facility. Those decisions remain with authorised business and risk officers.

The remit excludes running retail channels, network field operations, billing operations or the permanent architecture function. Success is a demonstrably smaller legacy decision footprint, fewer stranded orders, controlled dual-running and a successor able to continue decomposition without dependence on a single vendor’s undocumented knowledge. Eighteen months is a fixed transformation window; scope must be shaped to leave completed retirements rather than an indefinitely expanding programme.

Why this seat is open

The former leader treated interface delivery as progress even when end-to-end order state remained ambiguous and legacy decisions multiplied. A fibre failure made the gap visible to customers and regulators, prompting the board to replace programme leadership before the next market launch. The company needs temporary authority capable of stopping releases, cutting through domain ownership disputes and preparing a successor around working migrations rather than inherited presentation material.

What you will own

• Map authoritative and duplicated order state across channels, mainframe modules, orchestration, inventory, provisioning and billing systems.
• Define bounded customer journeys with explicit entry conditions, events, compensations, control points and operational exception ownership.
• Sequence strangler releases that remove mainframe decisions while preserving number portability, credit, activation and billing integrity.
• Institute dual-run reconciliation across commercial completion, network fulfilment, charge creation, fallout queues and customer communications.
• Govern vendor knowledge extraction, code archaeology and dependency evidence needed before any component retirement is approved.
• Exercise release stop/go rights using journey-level evidence, quantified customer exposure, rollback capability and service-readiness proof.
• Induct the permanent executive through live migration decisions and transfer the retirement register, economics and residual architecture debt.

Candidate qualifications

• Has led decomposition of a mainframe-dependent telecommunications order or fulfilment estate through incremental production migration.
• Understands order capture, product qualification, inventory reservation, provisioning, portability, billing initiation and fallout operations end to end.
• Has resolved conflicting system-of-record claims using event lineage and reconciliation rather than adding another synchronisation layer.
• Can govern vendors holding undocumented legacy knowledge while building internal capability and evidence for safe component retirement.
• Has stopped or reshaped a commercially urgent release when activation and billing proof did not support the reported status.
• Demonstrates successful handover to a permanent leader who subsequently delivered migrations without retaining the interim executive’s personal network.

Non-negotiables

• Will maintain the Toronto hybrid commitment and attend monthly release command and scheduled Canadian market visits.
• Must disclose relationships with telecom operators, network equipment suppliers, billing vendors, integrators and modernisation product companies.
• Brings live legacy retirement in telecom fulfilment; greenfield architecture or channel redesign alone is not sufficient.
• Will not count wrappers, duplicated stores or dormant-but-required code as retired mainframe capability.

1. 49 words maximum. Which order state would you make authoritative first, and what evidence supports that choice?
2. 49 words maximum. Describe a legacy retirement you delayed because the dual-run reconciliation was misleading.
3. 49 words maximum. What must the permanent leader demonstrate before inheriting the final migration waves?