Architecture Decision-Governance Recovery Leader

The mandate

A network-cloud outage crossed virtualisation, identity, orchestration and service-assurance boundaries that separate design councils had approved independently. Investigators found expired waivers, supplier-authored reference patterns and no durable record of who accepted combined failure risk. The group disbanded its architecture council and removed its chair, opening a nine-month executive seat before major radio and digital-service releases depend on the same shared platform.

The interim leader must establish decision governance around material choices rather than presentation review. Work includes architecture domains, decision classes, evidence thresholds, accountable authors and deciders, independent challenge, waiver expiry, supplier participation and a searchable rationale record. The model must connect enterprise, network, security, data and country authorities while preserving the rapid operational choices required during incidents and time-bound spectrum or market commitments.

By month five, the group will identify a permanent architecture executive and country deputies. Those leaders must jointly run the final two councils, adjudicate a cross-domain network-cloud choice and close or renew critical waivers before transfer. Handover includes the decision corpus, reference-pattern ownership, supplier boundaries, skills assessment and unfinished design controversies, with a formal competence review before the interim leader’s fixed departure.

The seat can reject incomplete architecture submissions, halt a release within delegated resilience thresholds, retire obsolete standards, require waiver owners, determine council agendas and commission proof for cross-domain risks. It cannot accept regulatory non-compliance, decide spectrum investment, sign vendor architecture commitments, waive cybersecurity control, approve country capital or command live network incidents unless separately appointed by the accountable officer.

The remit excludes serving as permanent enterprise architect, operating the network-cloud platform, procuring vendors or writing every solution design. Completion requires faster traceable decisions, closed legacy waivers, supplier-independent reference ownership and permanent leaders who can resolve conflict without escalating routine design to the group chief technology officer. The nine-month limit is intended to prevent governance recovery from becoming a central approval bureaucracy.

Why this seat is open

The former council reviewed artefacts but did not own the combined decisions that created a shared outage path, and its chair lost executive confidence. Country teams now risk creating local alternatives while the permanent leadership design is unsettled. A time-bound executive can rebuild authority from the incident evidence, exercise it through current releases and hand it to credible successors before temporary centralisation hardens into another bottleneck.

What you will own

• Reconstruct the outage-related decisions across network cloud, identity, orchestration, observability, service assurance and country implementation.
• Define architecture decision classes, accountable deciders, required evidence, challenge roles, escalation thresholds and review timing.
• Replace open-ended exceptions with waivers carrying rationale, consequence, compensating controls, named owners and expiry decisions.
• Establish supplier participation boundaries that invite technical evidence without ceding standards, risk acceptance or roadmap authority.
• Build reference-pattern ownership and conformance tests spanning enterprise, network, cyber, data and operational resilience domains.
• Chair councils around live decisions, publish dissent and measure time to decision, reversals, exception ageing and downstream rework.
• Qualify permanent group and country leaders through observed cross-domain choices and transfer the complete rationale corpus.

Candidate qualifications

• Has rebuilt enterprise and network architecture governance after a material telecom outage or comparable cross-domain failure.
• Understands network cloud, OSS, BSS, identity, orchestration, observability and country operating dependencies at decision depth.
• Has converted standards councils from presentation forums into accountable decision bodies without slowing incident or market action.
• Can govern influential equipment and software suppliers while keeping architecture rationale and risk acceptance inside the operator.
• Has retired waivers and local patterns through evidence, ownership and expiry rather than an unenforced compliance campaign.
• Demonstrates succession across group and country architecture leaders who exercised authority before the temporary mandate closed.

Non-negotiables

• Will operate onsite in Dubai and attend monthly country councils and both planned supplier-design summits.
• Must disclose relationships with telecom operators, network vendors, cloud providers, integrators and architecture-assurance firms.
• Brings cross-domain telecom architecture decision authority; repository administration or solution review alone does not qualify.
• Will not permit suppliers to author the operator’s risk acceptance or retain exclusive custody of design rationale.

1. 49 words maximum. Which cross-domain decision record would you reconstruct first after a network-cloud outage?
2. 49 words maximum. How would you admit supplier expertise without transferring architecture authority to that supplier?
3. 49 words maximum. What observed council decision would qualify the permanent group and country leaders?