Episode Details

Back to Episodes

Semantic layers: one revenue number for the board

Episode 96 Published 1 month ago
Description

What happens when finance, sales and product each compute revenue their own way? The episode opens on a board meeting where three presenters defend three different quarterly numbers, and argues that the cost is not bad data but frozen decisions while teams re-litigate whose spreadsheet counts. Finance recognizes revenue on fulfillment, sales on signature, product on ship date, and each team's bonus depends on its version.

You come away with a build sequence for a semantic layer: inventory the 12 to 15 metrics that appear in board decks and budget fights, lock each to one written formula with finance and sales signing off together, then choose tooling. The discussion weighs a dbt Labs vendor claim against MIT Sloan Management Review's work on trust in shared numbers, and covers churn, customer acquisition cost, and the CDO's refereeing role.

Key takeaways

  • Inventory only the 12 to 15 metrics that show up in board decks and budget fights, not all 400.
  • Lock each metric to a single written formula and make finance and sales leads sign off in the same room.
  • Define the five metrics in your next board meeting, ship those, and use the momentum for the rest.
  • Treat the dbt Labs figure on conflicting metric definitions as vendor marketing, not evidence.
  • Email each department head before the next board meeting asking for their exact formula in one sentence, then compare the replies.

Chapters
0:00 Three revenue numbers in one board deck
0:47 Why finance, sales and product disagree
1:24 What a semantic layer actually is
2:03 Inventory metrics and lock the formulas
2:40 dbt Labs claims and the trust problem
3:20 Shipping five metrics before committee kills it

Go deeper, free lessons

Sources

Full article and transcript: https://www.mba-training.com/blog/semantic-layer-metric-consistency-playbook

MBA Training, mba-training.com

Listen Now

Love PodBriefly?

If you like Podbriefly.com, please consider donating to support the ongoing development.

Support Us