Mouhamad MalliAdvisory

Fictional illustrative engagement

CedarWave: deciding what to fund before committing to an AI platform

A fictional telecom scenario showing how fragmented initiatives, architecture assumptions, and a proposed platform investment can be converted into a governed executive decision.

Illustrative status

CedarWave is a fictional regional telecom operator created solely to illustrate the advisory method. It is not a real organization, client, or engagement. All situations, decisions, and portfolio classifications below are fictional.

Fictional operator context

Fourteen initiatives. Fragmented foundations. One consequential investment decision.

CedarWave’s leadership team was considering fourteen AI initiatives across network operations, customer workflows, and enterprise support. Data and architecture were fragmented across multi-vendor platforms, while a proposed $9.8 million platform investment was presented as the foundation for scale.

Evidence reviewed

Challenge the decision using the evidence available—not the confidence of the proposal.

  1. 01Business cases and delivery briefs for fourteen proposed AI initiatives
  2. 02Network, OSS/BSS, customer, and enterprise-data architecture views
  3. 03Event, telemetry, and data-pipeline inventories
  4. 04The proposed $9.8 million platform scope, sizing, licensing, and recurring-cost assumptions
  5. 05Selected vendor recommendations and integration dependencies
  6. 06Network-operations, incident, security, governance, and production-support workflows

Principal findings

The platform decision was ahead of the operating evidence.

  1. 01

    The fourteen initiatives had not been ranked through one value, feasibility, control, and execution logic.

  2. 02

    Operational data remained fragmented across RAN, Core, OSS/BSS, customer, and enterprise-platform boundaries.

  3. 03

    The proposed platform sizing preceded validated workload, adoption, and production-volume evidence.

  4. 04

    Several closed-loop concepts lacked explicit human approval, fallback, escalation, and operational ownership.

  5. 05

    Recurring cost and multi-vendor dependency were not sufficiently connected to initiative-level value hypotheses.

Illustrative portfolio outcome

Stop, continue, redesign, or fund.

The classification demonstrates the decision logic only. It is not a client result or a recommendation for another organization.

Stop

  1. General employee knowledge assistant
  2. Autonomous pricing recommendation agent
  3. Unowned customer chatbot expansion

Continue

  1. Network incident summarization
  2. Field operations briefing
  3. Alarm-enrichment pilot

Redesign

  1. Closed-loop remediation
  2. Customer churn intervention
  3. Fault-correlation workflow
  4. Contact-center agent assistance
  5. Capacity prediction workflow

Fund

  1. Service-impact correlation
  2. Controlled incident-triage copilot
  3. Operational event-data foundation

Recommended direction

Authorize a limited validation tranche—not the full platform commitment.

The fictional recommendation is to validate three priority operational outcomes, the required data and integration path, production controls, sizing assumptions, and recurring cost before expanding the investment.

Illustrative 90-day action plan

Turn the validation tranche into an executive decision sequence.

No confidential-looking register or full workbook is shown. The sequence summarizes the leadership gates that matter.

Days 0–30

Align evidence

Confirm outcomes, owners, baselines, data boundaries, workload assumptions, and validation criteria.

Days 31–60

Test viability and control

Validate integration, sizing, resilience, human control, security, operating cost, and support readiness.

Days 61–90

Return to the funding gate

Compare demonstrated evidence with the investment hypothesis and decide whether to stop, redesign, or authorize the next tranche.

Leadership decisions enabled

What leadership can confidently decide after the validation tranche

  1. 01Do not approve the full $9.8 million platform commitment on the current evidence.
  2. 02Authorize a limited validation tranche tied to three priority operational outcomes.
  3. 03Require workload, sizing, integration, and recurring-cost evidence before platform expansion.
  4. 04Retain human approval and fallback for incident and closed-loop workflows.
  5. 05Assign accountable business, operations, architecture, data, security, and delivery owners.
  6. 06Reassess the portfolio at the 90-day decision gate using validated evidence.

Independent perspective

A critical transformation decision should not depend on untested assumptions.

Request an executive conversation to determine whether a focused diagnostic, architecture review, workflow assessment or retained advisory engagement is appropriate.

Request an executive conversation