Dataface Tasks

M2 Internal Adoption + Design Partners

Due Apr 30, 2026

Planned25 / 120 (21%)
Exit criteria (0/4)
  • Multiple internal teams using product weekly.
  • 3-5 influencer companies active as design partners.
  • Weekly feedback loop closes top blockers quickly.
  • Pricing/packaging tested with real buyer conversations.
KPI targets (0/3)
  • Activation trend improving week-over-week.
  • Internal + design partner WAU stable or growing.
  • Reliability metrics within pre-launch thresholds.

Tasks by Workstream

Show

dft core (Sr Engineer Architect)

the YAML contract, compiler/normalizer, execution adapters, and release/versioning 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.

cloud suite (UI Design and Frontend Dev)

hosted user experience for onboarding, sharing, collaboration, and account/project flows 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.

inspect profiler (Sr Engineer Architect)

warehouse profiling, semantic inference, and analyst-facing data context surfaces 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.

mcp analyst agent (Data AI Engineer Architect)

AI agent tool interfaces, execution workflows, and eval-driven behavior tuning 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.

ft dash packs (Data Analysis Evangelist and AI Training)

connector-specific dashboard packs and KPI narratives for Fivetran sources 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.

ide extension (Head of Engineering)

analyst authoring workflow in VS Code/Cursor with preview, diagnostics, and assist 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.

chart library (rj)

The chart library has distinct style packages, evaluation ownership, reusable design assertions, semantic-type-aware behaviors, exposed and documented chart properties, and a good table chart baseline. The system is coherent enough for regular use by multiple internal teams and initial design partners, with a predictable response loop for issues and requests.

context catalog nimble (Data AI Engineer Architect)

context schema/catalog contracts and Nimble enrichment flows across product surfaces 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.

dashboard factory (Data Analysis Evangelist and AI Training)

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.

infra tooling (Sr Engineer Architect)

developer tooling, local workflow reliability, and deployment execution safety 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.

integrations platform (Head of Engineering)

deployment, billing, 5T connectivity, and operational reliability/launch integration 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.