Dataface Tasks

Future opportunity research

IDMX_FAR_FUTURE_IDEAS-FT_DASH_PACKS-01
Statusnot_started
Priorityp3
Milestonemx-far-future-ideas
Ownerdata-analysis-evangelist-ai-training

Problem

Ideas for extending connector dashboard packs beyond the current roadmap—cross-connector dashboards, AI-generated KPI narratives, embedded alerting, community-contributed packs, real-time streaming dashboards—are scattered across Slack threads, meeting notes, and individual heads. Without a structured capture of long-horizon opportunities with explicit user impact hypotheses and strategic fit assessments, the team will repeatedly rediscover and re-debate the same ideas. When future investment decisions need to be made quickly, the lack of a curated opportunity backlog means starting from scratch each time.

Context

  • There are plausible future bets for connector-specific dashboard packs and KPI narratives for Fivetran sources, but they should be captured as concrete opportunities with user value and strategic fit rather than as loose brainstorming.
  • This task should separate genuinely promising directions from attractive-but-vague ideas and tie each candidate to the product or platform outcomes it could improve.
  • Expected touchpoints include dashboard pack YAML, dbt/example assets, connector fixtures, and quickstart docs, roadmap notes, adjacent workstream dependencies, and any evidence from users that points toward a longer-horizon opportunity.

Possible Solutions

  • A - Keep future ideas as an unstructured backlog list: easy to collect, but hard to prioritize or revisit intelligently.
  • B - Recommended: turn future ideas into structured opportunity notes: describe user value, strategic rationale, dependencies, and why each idea is worth considering later.
  • C - Skip future opportunity work until all near-term milestones are complete: lowers distraction, but loses useful strategic context.

Plan

  1. Gather the strongest future ideas for connector-specific dashboard packs and KPI narratives for Fivetran sources from roadmap discussions, usage feedback, and adjacent workstream needs.
  2. Write a structured note for each opportunity covering user value, likely scope, dependencies, and the signals that would justify investment.
  3. Rank the opportunities relative to each other and explicitly note which ones are interesting but not yet credible.
  4. Link the top opportunities to prerequisite or experiment tasks so they can mature without being mistaken for near-term commitments.

Implementation Progress

Review Feedback

  • [ ] Review cleared