Launch operations and reliability readiness

ID	M3_PUBLIC_LAUNCH-FT_DASH_PACKS-03
Status	not_started
Priority	p0
Milestone	m3-public-launch
Owner	data-analysis-evangelist-ai-training

Problem

Fivetran dashboard packs ship connector-native dashboards to end users, but the pack publishing workflow has no operational instrumentation. There is no telemetry on pack install success rates, no alerting when a published pack fails to compile against a user's warehouse schema, and no visibility into which connector sources are producing broken packs. Support ownership for "I installed the Stripe pack and it shows errors" is unassigned. Without an incident playbook, a bad pack release for a popular connector like Salesforce or Stripe could generate a flood of support tickets with no established triage process.

Context

Public launch for connector-specific dashboard packs and KPI narratives for Fivetran sources needs more than feature completeness; it also needs clear ownership, monitoring, support routing, and a practiced response to failures.
Without explicit launch operations, the team will discover gaps in alerts, escalation, rollback, or user communication during the most visible part of the release.
Expected touchpoints include dashboard pack YAML, dbt/example assets, connector fixtures, and quickstart docs, runbooks, monitoring or review surfaces, and any launch-day coordination artifacts.

Possible Solutions

A - Handle launch ops informally through the people closest to the code: workable for small releases, but too fragile for public launch.
B - Recommended: define an explicit launch operations package: owners, dashboards/checks, escalation paths, rollback steps, and user/support communication rules.
C - Delay launch until a broader platform-operations program exists: safest, but likely more process than this specific launch needs.

Plan

List the launch-day risks for connector-specific dashboard packs and KPI narratives for Fivetran sources, including failure modes, ownership gaps, and dependencies on adjacent teams or systems.
Write the required runbooks and operating checklists covering monitoring, escalation, rollback, and communication.
Confirm the launch support model with named owners and the minimal dashboards, logs, or review artifacts they need to do the job.
Run a tabletop or rehearsal pass and update the plan anywhere the team still relies on tribal knowledge instead of written procedure.

Implementation Progress

Review Feedback

[ ] Review cleared