PortfolioEL-10

Engagement Leadership · Control room

Executive Communication Studio

SIMULATEDVerified Jul 2, 2026

The same delivery data, turned into the artifact the moment needs — and reframed for who's in the room. Juniors report status; seniors force decisions. Every draft here ends in an ask.

Portfolio

Artifact

Audience

Data in →RAID from EL-04· 1G / 2A / 1R· Adoption 63%· Burn +6% vs plan

Steering pre-read · Card & payments portfolio

For CIO. Risk posture and delivery health, decisions front and center.

Status

Talk track — Open with the red and the gaps — don't bury the decisions.

Portfolio health 61/100 — 1 red, 2 amber, 1 green, with 1 reported-vs-actual gap. 3 decisions need this forum.

1 on track2 at risk1 off track1 reported-vs-actual gapAdoption 63%Burn +6% vs plan

Decisions needed

Talk track — Name the decision, the options, and the date — don't leave without a call.

  1. DecisionCard-member servicing assist

    Approve a 2-agent floor-champion backfill before the ramp — decision needed by Friday.

  2. DecisionDisputes automation

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

  3. DecisionKYC document intelligence

    Decide: narrow scope to the top-5 document types for launch, or extend timeline 6 weeks — steering call today.

Risks & mitigations

Talk track — Pair every risk with the mitigation already in motion — show control, not alarm.

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

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

    Disputes automation · Disputes pod

  • highTimeline slips again if scope isn't cut

    Mitigation: Decide: narrow scope to the top-5 document types for launch, or extend timeline 6 weeks — steering call today.

    KYC document intelligence · KYC pod

Asks

Talk track — Restate each ask as a yes/no with an owner and a date.

  • DecisionApprove a 2-agent floor-champion backfill before the ramp — decision needed by Friday.
  • DecisionFund a 1-sprint eval-hardening spike and pause the category expansion — decision needed at this steering.
  • FYIGreen-light the drift-monitor automation in next sprint — no steering decision required, FYI.
  • DecisionDecide: narrow scope to the top-5 document types for launch, or extend timeline 6 weeks — steering call today.

Steering-committee takeaway: An exec update that contains no decision request is a diary entry. Every pre-read I send asks for something.

Resume echo — weekly leadership updates and QBRs across multiple AMEX portfolios.

How this is built

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

Input: the same authored portfolio data EL-04 reads (RAID + trend + adoption + burn) — a single source, so this genuinely consumes the delivery instrument rather than restating it.

Generation: deterministic. Decisions are extracted from each workstream's ask; risks pull the high-severity items and pair each with the mitigation already in motion; the status headline and section order rewrite by audience.

The per-section talk track is templated here; a LIVE variant can generate it via LIVE_MODEL without changing the Status → Decisions → Risks → Asks discipline.

Limitations: sample data is illustrative, not a live feed; audience reframing changes emphasis and ordering, not the underlying facts. In production this reads from the delivery tracker, adoption telemetry, and the financials.