AI Executive Office — CXO Assistant Platform  ·  View 03 of 30  ·  2 · People and journeys

Actors and Their Core Journeys

Who the platform is for, in their own words, and the named things each of them gets to do with it.

Editable source SVG draw.io All views
The executive office — the people the platform is for CXO 3–8 per tenant Goal — Tell me what changed overnight and settle the decisions that need me, before my first meeting. Core journeys Morning brief to approval daily Ask across every system Weigh an option set Chief of staff 1–3 per CXO Goal — Have the investigation already done, with the numbers reconciled, before my principal asks. Core journeys Delegated investigation Prepare the option set Chase an executed action Business unit head 20–200 per tenant Goal — See the exception in my area before it reaches the CEO, and be the one who fixes it. Core journeys Own an escalation Respond to a variance Assurance and operation Governance officer risk and compliance Goal — Show a regulator exactly how the platform reached a decision that moved money. Core journeys Reconstruct a decision on demand Review the abstention log Implementation lead M+ delivery Goal — Stand a new ministry up on the platform in six weeks without writing product code. Core journeys Onboard a tenant 6 weeks Map a source to canon Publish a KPI pack Tenant administrator customer side Goal — Change a threshold or an approval limit myself, on a Tuesday, without raising a ticket. Core journeys Set approval thresholds Grant and revoke access Platform SRE M+ run team Goal — Know which tenant is degraded and why, without opening tenant data to find out. Core journeys Triage a degraded tenant Drain a region Machines that act without being asked Detection sweep hourly + on event Goal — Find the exception worth an executive's attention, and nothing else. Core journeys Score signals against baselines Raise a situation Ingestion pipelines per source contract Goal — Land every source inside its freshness contract, or say loudly that I did not. Core journeys Land and reconcile a source Publish a staleness flag Outcome monitor per executed action Goal — Close the loop: prove the intervention worked, or reopen the decision. Core journeys Track a KPI after an action Reopen a failed intervention Source systems 12 classes Goal — Be read on a schedule I can sustain, and written to only through my own front door. Core journeys Serve a governed read Accept an approved write Actors and Their Core Journeys Person or role Journey / task Security / platform External / third party v 1.0 · owner Data & AI Global Practice · date 2026-09

Why these actors

  • The chief of staff is the platform's real competitor and its best advocate. Designing for the CXO alone produces a demo; designing for the delegate produces a system that gets used on a Tuesday
  • The implementation lead is an actor because the product is multi-tenant. If onboarding needs product code, the commercial model fails — and no CXO journey will reveal that
  • Three machines are actors with goals and failure paths: the detection sweep, the ingestion pipelines and the outcome monitor. Each has an SLA and an owner

What this rules out

  • No goal here is "chat with our data". Every goal names a decision, a deadline or an obligation, which is what makes them arguable at a sign-off
  • The platform SRE's goal — know which tenant is degraded without opening tenant data — is a hard constraint on observability, and it is why view 23 separates platform telemetry from tenant content

Assumptions

  • Executives will not learn a query language, a filter panel or a dashboard hierarchy. Anything that requires training is treated as a design failure
  • Business-unit heads are the volume users. The CXO is the sponsor; the tier below is the load
◀  High-Level Architecture All views Journey — CXO, Morning Brief to Approved Intervention  ▶
Solution Architecture v1.0 · Azure-native, multi-tenant, sovereign-capable · Data & AI Global Practice · 2026-0903-actors-and-journeys