Rooster — Mind Map & Content Architecture

# SyF Glossary — Terms Rooster Needs to Know
Last Updated: [TODAY'S DATE]

Quick Reference:
- This page defines Synchrony-specific terms so Rooster understands context
- Update this page whenever a new term comes up in your work
- ROVO will reference this page when interpreting any SyF-related request

---

## Card Types

Cobrand
  Definition: A credit card issued under a retail brand in partnership with Synchrony
  Examples: Amazon Synchrony card, Lowe's Synchrony card
  Works in: everywhere Visa/Mastercard is accepted

Dual Card
  Definition: A card that functions as both a store card AND a network card (Visa/Mastercard)
  Works in: both the issuing retailer AND everywhere the network is accepted
  My trains: Emerging Payments serves dual card and cobrand accounts

Private Label
  Definition: A store-only credit card — cannot be used outside that retailer
  Examples: A retailer-branded card that only works at their stores
  My trains: EHS/UniFi serves private label (Emerging Payments does not)

---

## Wallet & Provisioning Terms

Provisioning
  Definition: The process of adding a payment card to a digital wallet (Apple Pay, Google Pay)
  Who does it: Leanne P's team (Tokenization) + Christopher M's team (paperwork/config)
  External parties involved: Fiserv (processor), Apple, Google

Tokenization
  Definition: Replacing a card's actual number with a secure token for digital wallet transactions
  Who owns it: Leanne P (Tokenization + Digital Wallet Services)
  How it works: Fiserv ↔ Google/Apple APIs — all backend, no front end

Card Access
  Definition: SyF's homegrown provisioning platform
  What it does: QR code or SMS short-code → user authenticates → landing page to add card to Apple Wallet or Google Pay
  Also handles: Temporary shopping pass (in-store checkout without a wallet)
  Who owns it: Pat B

DWAM (Digital Wallet Access Manager)
  Definition: Post-authentication wallet management platform
  What it does: Lets users add, remove, rename, or freeze cards in their digital wallets after initial setup
  Who owns it: Julian W
  Relationship to Card Access: Downstream of Card Access — Card Access provisions the card; DWAM manages it afterward

---

## Platforms

UniFi
  Definition: Synchrony's private-label ecommerce checkout platform
  What it does: Powers the checkout experience for 200+ merchant ecommerce sites (private label only)
  Challenge: Integrations are tightly coupled — changes for one merchant can break another
  Who leads: Christina Berry (Train Leader, EHS/UniFi train)
  Future state: Being repositioned as "Synchrony Pay" — see Synchrony Pay Context page

Synchrony Pay
  Definition: Proposed rebrand and expansion of UniFi into a multi-channel checkout product
  Channels: In-store, phone, chat (expands beyond ecom-only)
  Why it matters: Extends UniFi value to dual card and cobrand merchants (not just private label)
  Status: Vision in progress — see Synchrony Pay Context page

---

## SAFe / Agile Terms

Train
  Definition: A group of Agile teams working toward shared business outcomes (SAFe term)
  My trains: Emerging Payments (primary) + EHS/UniFi (oversight)

RTE (Run Train Engineer)
  Definition: Manages the Agile Release Train's cadence, ceremonies, and coordination
  My RTE: Suri M (Emerging Payments)

PI Planning
  Definition: Program Increment Planning — quarterly ceremony where all teams plan the next 10-12 weeks
  My role: Bookend with business context + thank-yous; Suri M quarterbacks

SAFe
  Definition: Scaled Agile Framework — the methodology Synchrony uses across its product org

Steering Committee
  Definition: Biweekly meeting where each team presents status
  Format: One slide per team (~6 teams) + demo/analytics variable
  My role: POs build slides; I assemble, present, email deck to broader audience after

---

## Org Terms

Octane
  Definition: Synchrony's project/portfolio tracking tool (separate from Jira)
  Used for: Bijayta monthly accountability deck data — ROI, initiative status
  Pain point: Data is in Octane AND Jira AND prior decks — no single pull point

[ADD MORE TERMS HERE AS YOU ENCOUNTER THEM]

# Active Initiatives — Current State
Last Updated: [TODAY'S DATE — UPDATE MONTHLY]

Quick Reference:
- This page tracks what's actually in flight across both trains
- Update after every PI Planning cycle and when major status changes occur
- ROVO uses this page to answer "what are we working on" questions

---

## Emerging Payments — Active Initiatives

[INITIATIVE NAME]
  Status: [Green / Yellow / Red]
  Owner: [PO name]
  What it is: [one sentence]
  Current phase: [where in delivery]
  Next milestone: [date — what]
  Blocker (if any): [what's blocking + who owns the unblock]

[INITIATIVE NAME]
  Status: [Green / Yellow / Red]
  Owner: [PO name]
  What it is: [one sentence]
  Current phase: [where in delivery]
  Next milestone: [date — what]
  Blocker (if any): [none]

---

## EHS / UniFi — Active Initiatives

[INITIATIVE NAME]
  Status: [Green / Yellow / Red]
  Owner: [Christina Berry / PO name]
  What it is: [one sentence]
  Current phase: [where in delivery]
  Next milestone: [date — what]
  Blocker (if any): [what + who]

---

## Agentic Commerce Team — Status

Status: Red (as of [date])
Issue: Team funded and stood up but no roadmap or backlog defined
PM accountability: Patrick B / Tasha M / Rachel M
Topher's stance: Stepped back — this is a PM org problem to solve
What would change this: PM org defines backlog and direction

---

## Synchrony Pay — Moonshot Status

Status: In progress (vision deck not yet complete)
What it is: Rebrand UniFi → Synchrony Pay as multi-channel checkout (in-store / phone / chat)
Target audience: Rachel M, Mike S, Bijayta B — need a polished vision deck
Exit framing: Capstone, not gate — exits regardless of outcome
Blocker: Vision deck not yet pitch-ready
Next step: Draft vision deck using Rooster (see Synchrony Pay Context page)

# My Document Standards — Formats Rooster Should Always Use
Last Updated: [TODAY'S DATE]

Quick Reference:
- This page defines the exact format expected for recurring outputs
- Rooster should reference this page when building any deck or document content
- Do NOT invent formats — use these

---

## Bijayta Monthly Accountability Deck

Audience: Bijayta B (skip) + ~22 train leaders
Cadence: Monthly
Format: One section per train team, then a summary slide

Per-team section format:
  Team: [Name] | Owner: [PO name]
  Status: [Green / Yellow / Red] [emoji: 🟢 🟡 🔴]
  Shipped this month: [2-3 bullet points of what closed]
  In progress: [1-2 bullets of what's active]
  Blocked: [1 bullet OR "None"]
  Key metric: [one number with context — e.g., "Sprint velocity: 42 pts (up from 38)"]

Summary slide format:
  Train health: [overall Green/Yellow/Red]
  Wins: [top 2 outcomes]
  Risks: [top 1-2 concerns]
  Asks: [anything I need from Bijayta or her org]

IMPORTANT: Keep language neutral and factual. No candid political commentary.

---

## Steering Committee Deck

Audience: 4 POs + Christina Berry + extended stakeholders (emailed after)
Cadence: Biweekly
Format: One slide per team, built by POs, assembled by me

My assembly checklist:
  - Title slide (train name, date)
  - One slide per team (PO-built)
  - Analytics / metrics slide (variable)
  - Demo slide (if applicable)
  - Parking lot (open questions / decisions needed)

When asking Rooster to help with Steering Committee content:
  - Ask for one talking-point section per team
  - Max 3 bullets per team
  - Lead with what's most interesting to stakeholders (not process)

---

## Status Email to Taylor Y

Audience: Taylor Y (my manager)
Cadence: As needed (after major events or on request)
Format:
  Subject: [Train Name] — Status Update [Date]

  Body:
  [2-3 sentence summary of overall health]

  What moved:
  - [bullet 1]
  - [bullet 2]

  Watch items:
  - [anything yellow or red]

  No action needed from you / OR / One ask: [specific ask]

  Length: Under 200 words. Taylor reads fast, keep it tight.

---

## 1:1 Coaching Prep (Per PO)

Format for Rooster coaching prep requests:

  === [PO Name] — [Date] 1:1 Prep ===

  Recent Jira activity (last 2 weeks):
  [What they closed, what they started, what's been sitting]

  Patterns I'm seeing:
  [2-3 observations — factual, not evaluative]

  Suggested coaching questions:
  1. [Open-ended question based on pattern 1]
  2. [Open-ended question based on pattern 2]
  3. [Forward-looking question]

  IMPORTANT: Keep all coaching prep on this page ONLY.
  Do not include in any output that goes to Confluence team spaces.