Transaction List × Search Alignment

Architectural Reassessment for Transaction List & Search Integration

Executive briefing to align Cross-Product, Search, Utilities, and Digital Channels on a single path forward that balances user workflows, SLA expectations, and platform constraints.

TL

Compressed Signal Burst

Decision Trigger

Deep coupling of transaction list & search means siloed fixes fail → demand integrated architecture workshop 10/1.

Timeline Risk

Option B (search orchestration) still unsized; Q1 delivery jeopardized until SLA + effort locked.

Core Blocker

SOR may reject new MQ load; requires escalation to CDP + clear problem statement this week.

User Lens

Single vs. multi-account, view-all, and clear-search flows must work seamlessly across all options.

Decision Matrix Snapshot

Use this as the framing device for Wednesday’s working session—each row expands with progressive disclosure for rapid triage.

A SOR Integration via MQ

Cross-Product API adds direct MQ connections into SOR.

Risk: CDP blocking MQ load

Timeline: Extends beyond Q1

Sizing: Large (integration + migration + regression)

Work Required

  • Stand up new MQ integration layer with hardened failover.
  • Refactor Cross-Product API contracts; cutover traffic from DDA history.
  • Requalify downstream consumers for new payload schema.

Key Questions

  • Can SOR absorb additional MQ load without jeopardizing DDA Primary initiative?
  • What SLA would SOR commit to during batch hours?
  • How do we mitigate regression risk across multi-channel clients?
B Search Orchestration

Search team orchestrates list vs. search responses.

Risk: Undefined SLA & unsized effort

Timeline: Q1 jeopardized until sizing complete

Sizing: Medium-High (pending discovery)

Work Required

  • Build bifurcated orchestration: DDA History for list, Cross-Product for search.
  • Update swagger contracts & search ranking logic.
  • Utilities deliver problem statements, flows, and SLA expectations.

Open Questions

  • What latency budget do we have during nightly batch windows?
  • How do we ensure consistent UX between search results and default list?
  • Does Search own monitoring & failover logic or share with Cross-Product?
C Cross-Product Calls DDA History

Cross-Product invokes DDA Transaction History API directly.

Risk: Additional latency & upstream ripple

Timeline: Extends beyond Q1

Sizing: Medium (logic + perf optimization)

Work Required

  • Add conditional routing + caching in Cross-Product services.
  • Normalize payloads for single & multi-account contexts.
  • Run latency testing; optimize for <= target SLA.

Key Questions

  • What is the acceptable additive latency (current estimate ~50ms)?
  • How does this impact upstream batching and analytics feeds?
  • Can we reuse monitoring from DDA history or do we duplicate?

Problem Statement & Urgency

Why we paused execution and what must be true before we resume.

Expand brief

The transaction list is the canonical experience customers rely on for daily money movement monitoring. Embedding search inside the list reshapes navigation patterns, caching assumptions, and real-time data freshness. Any misalignment introduces inconsistent workflows, duplicate latency, and the potential to violate channel SLAs.

Why Now

  • Q4 planning locks next week; we need a single architectural bet.
  • Q1 commitments assumed reusing Cross-Product API pipelines—no longer viable.
  • SOR scalability questions unresolved; risk accumulates daily.

Success Criteria

  • Approved SLA for transaction list load (baseline & peak).
  • Aligned ownership for orchestration, monitoring, and failover.
  • Documented user workflows and parity expectations across channels.

Architectural Flows & Touchpoints

Visualize the coupling across systems to inform trade-offs.

Show / Hide flows

Current-State Interaction Map

  1. User launches transaction list → Cross-Product API fetches DDA history cache.
  2. Search queries route to Search service → indexes rely on Cross-Product payloads.
  3. Utilities supply orchestration metadata → ensures workflow parity across channels.

Impact Radar by Option

Option A

Shifts orchestration to Cross-Product + SOR; reduces Search complexity but raises infra debt and MQ load.

Option B

Search becomes orchestrator; adds logic for stateful list/search blending; risk concentrated in SLA clarity.

Option C

Cross-Product handles dual data sources; moderate latency hit; ensures API consistency across channels.

SLA Dependencies

  • Define acceptable list load time (baseline < 1.5s? peak?).
  • Clarify search-to-list switch cost & caching policy.
  • Document batch-hour degradation envelope & failback triggers.

Priority User Workflows & Use Cases

Each scenario must be represented in architectural sizing.

Toggle workflows

List-Centric Journeys

  • Default account view → infinite scroll reliability.
  • Multi-account toggle → consistent filters & totals.
  • View all transactions → caching + pagination alignment.

Search-Centric Journeys

  • Inline search with instant suggestions & results parity.
  • Clear search → revert to cached list without flicker.
  • Scoped search (single vs. multi-account) → consistent filtering.

Edge Considerations

  • Accessibility: maintain keyboard-first navigation + screen reader context when transitioning between list and search results.
  • Offline / degraded mode: define messaging + retry logic when MQ or Search experiences latency.
  • Analytics continuity: ensure instrumentation persists across views for conversion tracking.

Risk Register & Mitigations

Highlight blockers that require executive escalation.

Show risk plan

SOR MQ Capacity

Formalize problem statement to CDP; request capacity assessment & mitigation options.

Owner: Cross-Product

SLA Ambiguity

Define baseline/peak targets in workshop; add measurement plan + instrumentation updates.

Owner: Utilities

Search Ownership

Clarify if Search assumes orchestration or remains index provider; align support model.

Owner: Search

Wednesday 10/1 Working Session Agenda (60 min)

Designed for rapid decision enablement.

Review flow
  1. 5 min – Reconfirm problem statement, urgency, and success criteria.
  2. 10 min – Walk the decision matrix; capture delta questions per option.
  3. 15 min – Deep dive on SLA expectations (baseline, peak, degraded modes).
  4. 15 min – Map architectural flows with user workflows (single, multi-account, view-all, clear search).
  5. 10 min – Assign action owners, escalation paths, and re-baseline timeline.
  6. 5 min – Confirm next checkpoints & communication plan to executives.

Pre-Read Package

  • Revised executive email framing urgency + decision matrix.
  • Option-specific architecture diagrams (drafted prior to session).
  • User workflow storyboards for search/list transitions.

Single-Slide Executive Narrative

Design + content outline to summarize options, problem, flows, and use cases.

View slide plan

Slide Layout

  • Title Bar: “Decision Needed: Transaction List × Search Architecture” with date + logos.
  • Left Column (40% width): Problem statement + urgency bullets.
  • Center Band (35% width): Mini swimlane diagram showing user journey → system touchpoints → SLA guardrails.
  • Right Column (25% width): Decision matrix heatmap (Options A/B/C) with risk colors.
  • Footer: Use case icons (single account, multi-account, clear search) + Wednesday session CTA.

Content Checklist

  • Problem statement highlighting coupling & Q1 risk.
  • Icons representing Options A, B, C with one-line implication each.
  • Journey arrows: User → Cross-Product → Search/SOR → Channels.
  • Use case badges (“Single Account,” “Multi-Account,” “View All,” “Clear Search”).
  • Action footer: “Decide path on 10/1 – owners: Cross-Product, Search, Utilities, Digital Channels.”

Design Guidance

  • Color palette: Indigo for Cross-Product, Amber for Search, Emerald for DDA History, Rose for risks.
  • Use thin separators and iconography to keep slide readable; avoid dense paragraphs.
  • Highlight the unsized SLA risk in amber pill with “Action: Quantify before committing Q1 plan.”
  • Annotate swimlane with latency budget callouts (baseline vs. peak).
  • Include meeting QR or short link for quick calendar access.