Skip to content
Mini-Project

Ops Diagnostic: Two-Day Rescue for a Broken Looker Dashboard

A mid-size manufacturing supplier watched their Looker dashboards crumble after a dataset migration. In 48 hours, Ironhide found the failure points, fixed the joins and refresh chain, and restored trust in the numbers.

Two days. Zero drama. Dashboards they can actually run the week from.

2 days
End-to-end diagnostic and fix
0
Refresh failures post-fix (first 30 days)
1 source of truth
Finance, Ops, and Floor aligned

What went wrong

After an internal migration, dashboards started failing: broken joins, mismatched time zones, and totals that didn’t match the ERP. The ops team lost confidence and slipped back to manual Excel exports.

  • 🧩 Join keys changed — Looker models didn’t
  • ⏱️ Refreshes timed out due to heavy transforms
  • 🧮 KPIs drifted from finance’s numbers

Why a Mini-Project

They didn’t need a rebuild. They needed a surgical rescue: diagnose the failure points, fix the math, and harden the refresh chain — all without blowing up the week.

  • 🔧 Targeted fixes, not a full rewrite
  • 🧪 Side-by-side checks against ERP and prior exports
  • 🔔 Alerts re-enabled so issues don’t pile up

How we fixed it in 48 hours

We traced the failure path from source to dashboard, corrected the schema and time handling, and rebuilt the most brittle transforms in SQL. Then we verified totals against the ERP and restored notifications so problems surface immediately.

  • ✅ Repaired joins and casts causing row inflation
  • ✅ Moved heavy logic into SQL; simplified LookML
  • ✅ Reconciled KPIs to ERP and last trusted exports
  • ✅ Re-enabled refresh and error alerts via email/Slack

Visual Showcase

Five frames that tell the story: the restored dashboard, the before→after, the control room, the SQL fix, and the team back in sync.

What changed

  • ⏱️ Dashboards refresh on time — no manual exports
  • 🧭 Finance and Ops totals match — one version of truth
  • 🧪 Production metrics verified back to the ERP
  • 🔔 Alerts surface problems instantly instead of silently failing

Tools — and the role each one played

Looker (front-end dashboards)

Repaired model references and simplified LookML so visuals load quickly and reflect the corrected data model.

SQL (data shaping & reconciliation)

Moved heavy transforms to SQL, fixed joins and timestamp casts, and added reconciliation queries to validate totals against ERP exports.

Excel (baseline checks)

Used prior “last trusted” exports to confirm KPI math before turning dashboards back on.

Email / Slack Alerts

Re-enabled notifications so refresh failures or data drift trigger immediate action — not a week of bad decisions.

Client ERP (system of record)

Ground truth for jobs, runtime, and postings; the source we reconcile to so Finance and Ops stay aligned.

Dashboards wobbling after a change? You don’t need a rebuild — you need a rescue.

Book a 2-day diagnostic →