PortfolioEL-04

Engagement Leadership · Control room

Delivery Health & RAID Radar

SIMULATEDVerified Jul 2, 2026

A steering board should report trajectory, not snapshots. Each workstream pairs its reported RAG with the health it actually has once the trend is priced in — so the one that reads green but is sinking can't hide.

Card-member servicing, disputes, fraud, KYC — finserv, anonymized, illustrative.
Portfolio health
61/100

Actual health, trend priced in

Workstreams at risk
3/4

Actual amber or red

Reported-vs-actual gaps
1

Green on paper, worse in reality

This period
Week 6

Trend window: last 3 weeks

Health × trajectory

improving ↑↓ deterioratingworsebetter

Dot color = reported status; position = actual health × trend. A green dot in the shaded corner is the trap.

Disputes automation

Amber-14pt

Reported green, but eval pass-rate slipped 14 pts and agent adoption stalled at 41%.

Risks · 1

  • highQuality slide reaches production before it's caught in review

Issues · 2

  • highGolden-set pass-rate 77% vs 90% gate
  • medAdoption stalled at 41% of agents

Dependencies · 1

  • highLabeled data for new categories (Ops)

Assumptions · 1

  • New dispute categories reuse the existing eval harness — proving false

Auto-drafted leadership status

Status. Disputes automation is at risk (green as reported, amber on trajectory, deteriorating).

What changed. Golden-set pass-rate fell from 91% to 77% after the new dispute categories landed; adoption flat at 41%.

Watch. The status is reported green on delivery milestones, but quality and adoption are both trending down — the milestone view is hiding it.

Ask. Fund a 1-sprint eval-hardening spike and pause the category expansion — decision needed at this steering.

The reported-vs-actual gap

1 workstream reports healthier than reality. A green status with a downward arrow is a yellow that hasn't surfaced yet — the milestone view rewards "on schedule" and stays silent on quality and adoption.

Steering-committee takeaway: Green with a downward arrow is yellow. Report trajectory or get surprised.

Resume echo — the weekly reality of multi-portfolio EM work at AMEX.

How this is built

Stack: Next.js (static) + the shared design system; client-side state only.

Data: authored sample portfolios (finserv + telecom), each workstream carrying reported vs actual RAG, a 3-week trend, and RAID items — shared with EL-10.

Health index = mean of actual-health scores (green 100 / amber 60 / red 25); the radar plots actual-health × trend with reported status as dot color, so a green dot in the deteriorating-but-looks-better corner is the trap.

Narrative: deterministic template over the workstream's authored brief, disciplined into Status → What changed → Watch → Ask. A LIVE variant can generate the prose via LIVE_MODEL without changing the structure.

Limitations: sample data is illustrative, not a live feed; the reported-vs-actual gap is engineered into the data to teach the pattern. In production this reads from the delivery tracker and the eval/adoption telemetry.