The organization currently relies on ad-hoc spreadsheets for reporting, resulting in manual work, inconsistent metrics, and low trust in data. The goal is to transition stakeholders to reliable BI dashboards with clear metrics, governance, and sustainable workflows. The workflow prioritizes empathy for existing processes while guiding the shift to structured, scalable reporting.

The workflow aims to help a Data Team Lead transform raw source table schemas and business requirements into well‑structured semantic models for dbt projects. It ensures that metrics have a single source of truth, models follow medallion or Kimball principles, and documentation and testing standards are consistently applied. The output includes a semantic model diagram, dbt project structure, metric definitions, and documentation guidelines.

Teams across the organization rely on inconsistent metric definitions, causing confusion, duplicated work, and conflicting dashboards. The goal is to standardize disputed metrics into a single, trusted glossary with clear SQL definitions, filters, grain, and known caveats. The workflow must also define canonical dimensions, governance rules, and a stakeholder announcement to drive alignment.

Non-technical stakeholders often struggle to understand where a critical KPI originates, how it is calculated, and what its limitations are. This workflow produces a clear, friendly, and accessible KPI lineage explanation. It converts technical inputs into a narrative, a source/transform table, an FAQ, and ownership details—all while avoiding proprietary names and keeping the explanation concise.

The workflow converts unstructured program and meeting notes into clear, structured BI program management deliverables. It ensures milestone progress, risks, dependencies, and decisions are captured consistently and translated into stakeholder-ready updates. The goal is to reduce ambiguity and improve reporting accuracy across projects.

The workflow aims to assist applied data scientists in designing GenAI agent prototypes by producing an agent architecture blueprint, tool schemas, prompt scaffolding, evaluation plans, and failure-mode analyses. The system must convert a high-level task description into a structured, testable, and cost-aware prototype design. The output must be systematic, engineering-focused, and ready for iteration and versioning.

The goal is to take a list of data engineering tasks and transform it into a production-ready orchestration design. This includes defining a clear DAG blueprint, mapping explicit dependencies, and incorporating reliability mechanisms such as retries, backfills, logging, metrics, and cost controls. The workflow should help a Data Engineering Lead produce consistent, idempotent, and well-documented orchestration designs.

The goal is to transform raw charts, tables, and analytic outputs into clear, audience-tailored decision narratives. The workflow must interpret quantitative results, highlight what matters, and produce recommendations aligned with the decision context. It must also surface uncertainty, provide necessary caveats, and prepare the user for likely stakeholder questions.

The workflow analyzes weekly sales data to surface meaningful trends, anomalies, and performance insights for a sales analytics team. It identifies significant week-over-week and quarter-over-quarter changes, highlights rep-level outliers, and produces concise, actionable recommendations. The final output includes a short executive summary suitable for leadership review.