Three Workspaces. Same Measure. Three Definitions

Finance has Net Revenue in the corporate workspace. Sales has Net Revenue in the pipeline app. Ops has Net Revenue in the plant pack.

All three tiles are green, and all three disagree by enough to ruin a Monday. It is the same label with three DAX definitions, and the meeting will spend itself on archaeology instead of action.

Duplicate measures are a portfolio failure

This is not a story about one messy pbix. It is what happens when every team builds “their” model and reuses English words without reusing the logic.

Every team built their own model describes the pattern, and why Power BI reports show different numbers describes the meeting. This post is the measure-level version: identical names, incompatible math, distributed with confidence.

Measures nobody can explain is the cousin inside a single model. Across workspaces the unexplained measure multiplies, and each copy drifts on its own calendar of patches and tribal fixes. Executives hear one language while the estate speaks three dialects and hopes nobody runs a crosswalk.

Why the same measure multiplies

Self-service has no shared product boundary. Teams are rewarded for shipping a local app, not for consuming a certified definition.

Delivery runs on copy and paste. A working measure gets duplicated into a new workspace “just for now,” and now never ends. The copies diverge on the first edge case.

Different source grains pretend to be the same KPI: booked versus shipped, gross versus net, customer versus invoice. The labels stay friendly while the logic does not.

Nobody owns the name. If you cannot govern what you cannot name, you also cannot stop three authors from minting Net_Revenue_Final_v3.

Certification is local. Each workspace certifies its own dataset, and cross-workspace consistency never gets a steward. Certified datasets versus wild west still applies, because certification without a shared definition catalog is a sticker collection.

The costs of three definitions for one word

1. Meetings become reconciliation workshops. Leaders spend the first half hour comparing extracts, and decisions wait for the crosswalk.

2. Trust collapses asymmetrically. One bad collision teaches executives that “Power BI numbers” are optional. Winning that trust back takes longer than building the shared measure.

3. Patches fork forever. A returns fix lands in finance’s model. Sales never hears about it and ops hears late. The same bug gets solved three times, incompletely.

4. Incentives misalign. A sales leader and a plant leader can both “hit Net Revenue” under different math. The scoreboard becomes a negotiation, not a fact.

5. Who can change a measure becomes unanswerable. There are three change paths, three silent edits, and no single approval gate.

6. Sprawl taxes every enhancement. A new product hierarchy must be rebuilt everywhere, and delivery slows while the estate pretends it has one KPI language.

7. Exports amplify the mess. Three definitions leave the apps for Excel and the screenshot pack. The forks spread faster than any center-of-excellence newsletter.

8. You fund parallel truth systems. Capacity and licenses pay for several machines that argue with each other in public.

How to fix it: one definition, many consumers

1. Inventory the collisions. Search for identically named measures across production workspaces, starting with revenue, margin, inventory, and on-time. Publish the hit list without blame.

2. Pick a system of record for each metric family. One semantic model owns Net Revenue, and other apps connect to it or go away. The semantic model is the product, so treat definition ownership like product ownership.

3. Rename honest differences. If ops needs “Net Revenue Shipped,” call it that. Stop overloading “Net Revenue” until the meeting explodes. Clarity beats forced sameness.

4. Stand up a thin definition catalog executives can read. List the name, plain-English logic, grain, owner role, workspace of record, and last change date. Link it from the app and keep it short.

5. Gate new measures that reuse reserved names. If the name exists in the certified model, new workspaces consume it instead of redefining it. Enforcement beats reminders.

6. Migrate consumers before you delete copies. Point sales and ops reports at the shared model and validate totals. Then retire the local twins on a date, with the discipline in how to retire a dashboard.

7. Put change control on the shared measures. Propose, assess impact, approve, release. Local heroes editing production DAX overnight is how forks restart.

8. Certify the shared layer. Certify the model that owns the definition, and stop certifying contradictory copies just because each workspace has a steward.

9. Review collisions quarterly in the steering forum. Show the remaining duplicate names and their retirement dates. Make consistency a management metric, not an IT hygiene chore.

A hard rule that saves months

If two production measures share a business name and differ in logic, one of them is misnamed or unauthorized. There is no third option called “both are fine for now.” “For now” is how estates wake up with twelve revenues and a leadership team that stopped believing the portal.

You do not need a perfect enterprise glossary on day one. Start with the five measure names that already cause arguments: revenue, margin, inventory, backlog, and on-time. For each word, force a single definition of record or an honest rename, and publish the decision. Then stop the estate from minting quiet duplicates under the same English label. Once those five are clean, expand. Most mid-market collision pain lives in a short list, not in a thousand obscure measures.

What good looks like in the first quarter

Finance, sales, and ops can open different apps and still land on the same Net Revenue math. Pages may show different cuts and layouts, but they do not invent different formulas.

When a definition must change, one proposal reaches one owner, and downstream reports inherit the change on a known release. The Monday crosswalk shrinks, and analysts spend their time on new questions instead of re-implementing last year’s margin logic in yet another workspace.

New workspace requests get a simple question: which certified measures will you consume, and which new names are you proposing? If the answer is “we’ll recreate revenue,” the request is not ready.

Executive takeaway

Three workspaces with three Net Revenues are not a self-service success story. They are a naming and ownership failure with a DAX accent. Consolidate the definition, rename honest differences, and retire the twins. Then the meeting can argue about the business again instead of which tile to trust.

Want a collision inventory and a consolidation path for your critical KPIs? Book a session with Alluvium. We will map duplicate measures, the system of record, and the retirement sequence that ends the Monday crosswalk. To check the model’s overall condition, request a free Model Health check.