Executive Reporting
A weekly leadership deck built by hand from 6+ sources, and the reporting errors that came with it. The errors traced back to the handoffs.
- Weekly deck build
- 3+ hours → Under 5 min
- Critical reporting errors
- ~90% fewer
- Sources reconciled
- 6+
Tech Stack
The Problem
On Mosaic’s retail field-sales program for Google’s Pixel NAMER division, leadership got an 11-slide deck every week. Someone built it by hand from 6+ sources: BigQuery, Sheets and internal databases. The build took 3+ hours, and the same kinds of mistakes kept showing up in it.
The Diagnosis
The mistakes weren’t carelessness. They came from unguarded handoffs. The sources named the same records differently and never fully agreed. Nothing checked the data as it moved from one system to the next, so an error made upstream arrived in the deck looking like a fact.
The Build
Two pieces, built so the team could run them without me:
- The deck builds itself. Apps Script pulls from all 6+ sources and generates the 11-slide leadership deck in under 5 minutes.
- A six-layer verification protocol checks the reporting data across all 6+ sources: format, business logic, historical outliers, cross-source agreement, automated reconciliation, and a human-review queue for anything the rules can’t settle.
Every build writes raw data only and leaves the math in visible in-cell formulas, so a non-technical reviewer can audit any number by clicking the cell. Each one shipped with an SOP, and I trained the team on it at handoff.
The Outcome
The weekly build went from 3+ hours to under 5 minutes, and critical reporting errors dropped about 90%.
Guard the handoffs as carefully as the report they feed.
Want to talk about this work, a role, or a build for your team?
Let's Talk