← Back to case studies

The organization needed planning, close, and board reporting to reference one set of definitions—without asking finance analysts to abandon rigor or velocity while the lakehouse path matured.

What leadership was trying to fix

Credible numbers in steering and close

Critical metrics lived in spreadsheets passed between teams. Each version was defensible in isolation, but steering committees could not trace a single “revenue” or “margin” story from source through to presentation. When upstream systems changed, spreadsheet logic broke quietly until someone noticed in reconciliation. The cost was not only time in close; it was credibility when numbers did not match across rooms.

Friction in the data estate

Tribal spreadsheet logic and social “official” cuts

Upstream systems fed overlapping extracts; dimensions for stores, products, and time did not always align between operational feeds and finance adjustments. Analysts protected quality with manual checks and tribal knowledge. Promoting a number to “official” status was a social process rather than a published contract, so new reports often started from the most convenient file rather than a certified layer.

Design of the response

Bronze through Gold for finance semantics

We anchored the program on a medallion layout: Bronze for immutable landing from agreed upstream feeds with replay when sources changed; Silver for conformed keys, hierarchies, and shared dimensions across planning and close; Gold for certified measures, named cuts for board and operational packs, and interfaces to self-service BI.

Spreadsheets did not disappear overnight—they were bounded. New official cuts came from promoted datasets; exploratory work stayed clearly labeled and outside the certified path until definitions passed governance.

How we ran delivery

Metric families in thin vertical slices

We sequenced vertical slices: one metric family and one consumer community at a time, end-to-end from landing through a thin Gold mart. Finance and data owners reviewed semantic changes; platform engineers owned pipelines and tests. The same conformed dimensions fed planning models and close reporting where the retailer chose to align them—reducing duplicate mapping in analyst spreadsheets.

This pattern—contracts, tests-at-promotion, explicit ownership—is how we repeat similar foundations without turning every engagement into a custom science project.

Impact

Close and board on shared definitions

Board and operational reporting increasingly start from shared definitions and promoted datasets instead of shadow Excel chains. Reconciliation scope and calendar pressure around close improved materially. Internal platform teams operate steady-state pipelines with documentation and escalation paths transferred during the program.

Identifying details are omitted under client confidentiality.