Problem Statement
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.
Steps
Ingest stakeholder materials
INGESTCollect key reports, spreadsheets, data sources, and descriptions of current workflows and pain points. Parse and summarize what exists today with an empathetic understanding of current processes.
Retrieve and categorize reports for prioritization
EXECUTEGroup reports by stakeholder, purpose, and frequency. Identify high-value, high-friction reports that would benefit most from dashboard migration.
Generate prioritized dashboard list and metric definitions
EXECUTEProduce a clear ranking of dashboards to build first, along with metric definitions, governance rules, and a recommended data model approach.
Validate alignment with stakeholders
EXECUTECheck proposed dashboards, definitions, and model plans against stakeholder needs and highlight any gaps before build. Ensure tone stays supportive and transition-aware.
Generate training and adoption plan
EXECUTECreate a structured stakeholder training plan, onboarding materials, and adoption KPIs including transition-period recommendations.
Prompt Configurations
BI migration synthesis prompt
You are assisting a BI lead who is transitioning stakeholders from ad-hoc spreadsheets to trusted dashboards. Using the provided inputs (stakeholder reports, spreadsheet workflows, pain points, and data sources), produce the following: (1) prioritized dashboard list, (2) clear metric definitions and governance notes, (3) proposed data model approach, (4) stakeholder training and transition plan, (5) adoption metrics. Your tone must be supportive, systematic, and adoption-oriented. Do not invent data; only use what is provided and reasonable domain inferences. Ensure the output uses public-safe language and respects existing workflows by offering empathetic transition guidance.
Example Inputs/Outputs
Stakeholder reports: weekly revenue spreadsheet, marketing spend tracker, manual customer churn file. Pain points: inconsistent revenue formulas, manual VLOOKUPs, unclear churn definition. Data sources: CRM export, finance SQL table. Need prioritized dashboards and training plan.
Prioritized dashboards: (1) Executive Revenue Dashboard, (2) Marketing Spend Efficiency Dashboard, (3) Customer Churn Insights. Metric definitions: standardized revenue formula with source-of-truth finance SQL table; churn defined as customers inactive for 30 days. Data model approach: star schema with revenue facts and customer dimensions. Training plan: weekly sessions for marketing and finance, plus guided walkthroughs. Adoption metrics: dashboard views per team, reduction in spreadsheet usage, and consistency of metric usage across teams.