Case log
Field studies from teams who argued with their dashboards
Each vignette is generalized from multiple engagements. Outcomes describe meeting dynamics and review habits, not revenue promises.
Regional grocer: nightly margin drift
Client industry: Retail
Challenge: Category managers saw different margin numbers in email, the warehouse, and finance packs every Tuesday morning.
Solution: We rebuilt the conformed product dimension, added reconciliation queries, and paired Metabase pulses with annotated footnotes.
Outcome: Tuesday reviews shortened from two hours to forty minutes; disputes now cite query IDs instead of screenshots.
SaaS billing: cohorts that disagreed with finance
Client industry: Software
Challenge: Product analytics counted trials differently from revenue operations, so renewal forecasts wobbled each sprint.
Solution: A shared cohort contract in dbt tests, plus a Looker Studio layer that exposes the definition beside every chart.
Outcome: Forecast variance tightened materially quarter over quarter; teams still debate strategy, not arithmetic.
Hospital network: access logs nobody trusted
Client industry: Healthcare
Challenge: Compliance needed row-level evidence, but clinicians complained dashboards slowed during peak ward rounds.
Solution: Selective secure views, warm aggregates for common cuts, and a documented escalation path for break-glass access.
Outcome: Audit evidence arrived in one bundle; clinical leaders reported stable load times during morning peaks.
Logistics partner: Excel islands before BigQuery
Client industry: Logistics
Challenge: Operations lived in Power Query while headquarters stood up BigQuery, causing duplicated logic and fragile refreshes.
Solution: A staged promotion checklist, paired office hours, and mirrored tests between Excel and warehouse models.
Outcome: Handoffs became predictable; the operations team now proposes schema tweaks with example queries attached.
Education nonprofit: donor reporting lag
Client industry: Nonprofit
Challenge: Donor reports mixed semester dates with fiscal calendars, producing awkward clarifications every funding cycle.
Solution: Calendar spine modeling workshop, explicit semester keys, and a narrative template for donor PDFs.
Outcome: Reports ship on schedule; program leads spend review calls on impact stories instead of date definitions.