Analytics Platform Presentation Runbook

Recommended Reading and Presentation Order

PROBLEM STATEMENT

• https://mdview.io/s/d2c12473
• https://mdview.io/s/1325775b
• https://mdview.io/s/94a9c98c
• https://mdview.io/s/96456f40

1. EXECUTIVE-SUMMARY.md

• Explains the business problem and value in leadership language.
• Clarifies risk, mitigation, and the approval decision needed.
• Link placeholder: EXECUTIVE-SUMMARY link

2. ANALYTICS-PLATFORM-SIMPLIFIED-HLD.md

• Defines the target architecture: app-owned analytics logic with thin shared runtime SDK.
• Establishes hard boundaries, versioning rules, and fail-safe behavior.
• Link placeholder: ANALYTICS-PLATFORM-SIMPLIFIED-HLD link

3. ANALYTICS-AGENT-WORKFLOW.md

• Shows operational automation flow: prompt -> clarify -> generate -> validate -> PR -> rollout/rollback.
• Makes the model practical with concrete generated artifacts and release checks.
• Link placeholder: ANALYTICS-AGENT-WORKFLOW link

4. IMPLEMENTATION-ROADMAP.md

• Provides phased delivery plan with owners, timelines, and measurable checkpoints.
• Documents enforcement gates: dependency boundaries, semver checks, compatibility, rollback.
• Link placeholder: IMPLEMENTATION-ROADMAP link

5. analytics-platform-HLD.md

• Serves as deep technical reference for architecture and design review questions.
• Covers extended patterns and tradeoff analysis for engineering follow-ups.
• Link placeholder: analytics-platform-HLD link

---

Meeting Flow

In-Room Flow (Primary)

1. EXECUTIVE-SUMMARY.md
2. ANALYTICS-PLATFORM-SIMPLIFIED-HLD.md
3. ANALYTICS-AGENT-WORKFLOW.md

Backup / Q&A Flow

4. IMPLEMENTATION-ROADMAP.md
5. analytics-platform-HLD.md

---

Suggested Talk Track

Opening (2-3 minutes)

• We have multiple analytics implementation patterns across teams.
• This creates regressions, slower onboarding for new markets, and high manual effort.

Target State (5-7 minutes)

• Business/event logic is app-owned.
• Shared analytics remains runtime-only and app-agnostic.
• Versioned contracts and fail-safe release gates prevent unsafe changes.

Automation Demo Narrative (5-7 minutes)

• User gives one simple analytics prompt.
• Agent asks short clarification questions only if needed.
• Agent generates app-level contracts, app implementation, tests, and PR.
• CI gates and canary checks enforce safe rollout and rollback.

Delivery and Confidence (3-5 minutes)

• Roadmap phases and timeline are clear.
• Ownership and governance model are explicit.
• Safety controls are built-in for every change.

---

Key Messages to Repeat

1. App owns business meaning. Shared SDK owns only core runtime mechanics.
2. No shared dependency on app logic or app types.
3. Every change is versioned, validated, and rollback-safe.
4. Automation reduces manual work while improving reliability.

---

Expected Questions and Short Answers

Q: Are we replacing Adobe Launch?

A: No. We keep Adobe Launch and standardize how events reach it.

Q: How do we avoid breaking existing markets?

A: Semver + compatibility gates + canary rollout + auto rollback.

Q: Who owns event logic?

A: App teams own event semantics and payload shaping.

Q: What does shared analytics own?

A: Runtime-only responsibilities: validate, route, dispatch, observe.

Q: What if generated code is wrong?

A: CI gates block unsafe output; manual approval remains for risk classes.