type: workstream slug: dashboard-factory name: dashboard factory description: Quickstarts, examples, and repeatable dashboard template production. owner: data-analysis-evangelist-ai-training status: active milestones: m0-prototype: |- A runnable prototype path exists for repeatable process for producing, reviewing, and publishing quickstarts/examples, with concrete artifacts that prove the flow works end-to-end in the current codebase. Core assumptions are documented, known constraints are explicit, and the team can explain what is real versus mocked without ambiguity. m1-ft-analytics-analyst-pilot: |- Internal analysts can execute at least one weekly real workflow that depends on repeatable process for producing, reviewing, and publishing quickstarts/examples in the 5T Analytics environment, without bespoke engineering intervention for every run. Instrumentation and feedback capture are in place so failures, friction points, and adoption gaps are visible and triaged with owners. m2-internal-adoption-design-partners: |- repeatable process for producing, reviewing, and publishing quickstarts/examples is hardened enough for regular use by multiple internal teams and initial design partners, with a predictable response loop for issues and requests. Quality expectations are documented, and prioritized improvements from real usage are actively incorporated into delivery. m3-public-launch: |- Launch scope for repeatable process for producing, reviewing, and publishing quickstarts/examples is complete, externally explainable, and supportable: user-facing behavior is stable, documentation is publishable, and operational ownership is explicit. Remaining gaps are non-blocking, risk-assessed, and tracked as post-launch follow-up rather than unresolved launch debt. m4-v1-0-launch: |- Post-launch stabilization is complete for repeatable process for producing, reviewing, and publishing quickstarts/examples: recurring incidents are reduced, support burden is lower, and quality gates are enforced consistently before release. The team has a repeatable operating model for maintenance, regression prevention, and measured reliability improvements. m5-v1-2-launch: |- v1.2 delivers meaningful depth improvements in repeatable process for producing, reviewing, and publishing quickstarts/examples based on observed usage and retention signals, not just roadmap intent. Enhancements improve real customer outcomes, and release readiness is demonstrated through metrics, regression coverage, and clear migration guidance where relevant. mx-far-future-ideas: |- Long-horizon opportunities for repeatable process for producing, reviewing, and publishing quickstarts/examples are captured as concrete hypotheses with user impact, prerequisites, and evaluation criteria. Ideas are ranked by strategic value and feasibility so future investment decisions can be made quickly with less rediscovery.
Quickstarts, examples, template patterns, and dashboard production standards. This workstream owns the process and tooling for producing dashboards at scale — the "factory line" that turns connector schemas into polished dashboard packs efficiently. Includes the quickstart/tutorial authoring pipeline, the docs-as-code rendering system, template quality rubrics, and the operational cadence for dashboard production throughput. This is the how of dashboard production — distinct from ft-dash-packs, which is the what (the actual connector-specific dashboard catalog). Adjacent to ft-dash-packs (which is the output), graph-library (which sets the visual quality bar), and mcp-analyst-agent (which may automate parts of the production process).
{{ workstream_milestone_rollup("dashboard-factory") }}