Purpose of Level 3
Level 3 converts opportunity and readiness inputs into an executable, risk-aware transformation roadmap. It helps leadership decide what to implement first, what needs preparation, and what should not be scaled yet.
Core philosophy
Outcome automation first. Conversational AI second.
The dashboard intentionally prioritizes deterministic workflow automation before Conversational AI expansion. If workflow, API, telemetry, or production readiness is weak, the model suppresses aggressive AI rollout.
TPS — Transformation Priority Score
TPS ranks use cases for roadmap sequencing. It balances value, feasibility, workflow maturity, strategic leverage, and risk posture.
TPS = Business Value 25% + Delivery Feasibility 25% + Workflow Maturity 20% + Strategic Leverage 15% + Risk Posture 15%
TCI — Transformation Confidence Index
TCI estimates the likelihood that a use case can succeed sustainably. It considers TPS, workflow maturity, technology readiness, operational readiness, organisational readiness, and inverse risk.
Business Value
Indicates whether the use case is worth doing. It considers volume, automation opportunity, CX impact, and cost impact.
Delivery Feasibility
Indicates whether the use case can realistically be implemented. It considers operational readiness, organisational readiness, technology readiness, API readiness, and implementation effort.
Workflow Maturity Pillar
Measures whether the servicing workflow is stable and deterministic enough for automation. It considers workflow maturity, orchestration readiness, telemetry readiness, and exception complexity.
Telemetry
Telemetry means the ability to continuously observe, measure, track, and diagnose what is happening inside automated workflows and AI journeys in production.
Telemetry = operational visibility + workflow observability + production diagnostics
Examples include workflow completion %, API failures, customer drop-offs, AI fallback rates, escalation rates, retries, latency, production errors, and abandonment points.
Weak telemetry means leadership cannot reliably understand whether automation is succeeding, failing silently, or creating operational leakage. Therefore weak telemetry suppresses aggressive AI rollout in this framework.
Strategic Leverage
Measures whether the use case unlocks future scale through reusable platforms, shared dependencies, cross-channel applicability, or modernization value.
Risk Posture
Measures how safe the use case is to pursue. It considers compliance risk, dependency risk, vendor dependency, change resistance, and production risk. Higher risk reduces roadmap priority.
TRI — Transformation Risk Index
TRI indicates implementation risk. High TRI means the use case needs executive review, mitigation, or stabilization before scale-up.
MVP Candidate
A use case is considered an MVP candidate when it has strong readiness, manageable risk, clear workflow maturity, acceptable dependencies, and faster time-to-value.
Wave meanings
- Wave 0: Foundation stabilization — workflow, API, telemetry, governance, or technology readiness gaps must be fixed first.
- Wave 1: Deterministic workflow automation — controlled mobile/web/form-based automation of proven service journeys.
- Wave 2: AI-assisted servicing — human-in-the-loop or agent-assisted automation where full automation is not yet safe.
- Wave 3: Conversational AI overlay — bot/chat/voice layer on top of proven workflows.
- Wave 4: Predictive intelligence — proactive service, predictive triggers, and analytics-driven interventions.
- Wave 5: Autonomous servicing — highly mature, governed, low-risk automation with minimal human intervention.
Workflow-first gate
The workflow-first gate checks whether the use case has enough workflow maturity, API readiness, telemetry, and AI suitability. Weakness here means Conversational AI should not be scaled yet.
Expected Benefit
Directional risk-adjusted benefit estimate calculated using annual benefit potential, confidence, and wave realization factor. It must be validated with Finance during benefits realization.
Dependency Bottleneck
A shared API, platform, workflow engine, data source, vendor system, or operational capability that blocks or enables multiple use cases. High bottleneck dependencies should be addressed early.
Executive usage
Use this dashboard to identify MVPs, sequence waves, explain why certain use cases must wait, identify technology and workflow blockers, and prepare CEO/COO/CTO roadmap discussions.