Self-Service That Doesn’t Create Five Revenues

Self-service without certified measures is how you get five Revenues. Guardrails first.

Explore is not the enemy. Forking the company word is. A workspace that lets people slice a trusted kernel is enablement. A workspace that lets everyone publish a new definition of Revenue is a second close.

This is not the IT queue, and it is not sprawl counted as files

Waiting weeks for a variance cut is the request bottleneck: the hidden cost of waiting on IT. That article is lock-down versus wide-open as an operating model. This post is narrower: how people are allowed to explore without forking the words leadership already fights about.

Fifty reports is a tax on refresh and meetings: dashboard sprawl is not self-service. Sprawl is inventory of pages. Five Revenues is inventory of definitions. You can retire twenty unused reports and still have three live measures named Revenue. You can also have a short catalog and still fork the kernel every time an analyst “just needed a tweak.”

Certified versus sandbox is the promotion path: certified models vs the wild west. Read that for badges and junk drawers. Here the job is the explore layer: live connection, thin reports, banned local measures on company words, and a place to try a cut that cannot enter the pack until it earns a name of its own.

[Judgment:] if explore requires a copy of the model, you did not enable self-service. You franchised the ledger.

What “explore” is allowed to mean

Analysts should filter, slice, and assemble pages on the certified kernel. They should not redefine Revenue, Margin, or Bookings in a local measure because the meeting wanted a slightly different bag.

A new question is often a new cut, not a new word. Customer, plant, channel, week. Those are dimensions. If the answer requires a different include/exclude, that is a candidate measure with a new English name—not a silent edit of the company one.

The model is still the product: the semantic model is the product. Self-service that works treats reports as brochures on one product. Self-service that fails treats every brochure as a license to change the product.

Single source of truth is the decision about who may publish the company word: SSOT is a decision. Guardrails are how explore respects that decision without a ticket for every slicer.

The costs of explore-by-fork

1. Five Revenues with equal confidence. Each explorer meant well. Each published a tile. The meeting cannot tell which one is the kernel. Trust dies in the comparison, not in curiosity.

2. The certified measure becomes optional. Once a local twin exists, people use the twin that matches the story they brought into the room. Stewardship is theater. The kernel is a suggestion.

3. IT swings back to lock-down. After one bad ELT meeting, platform owners revoke publish rights. You recreate the queue. Shadow Excel returns. You paid for licenses and bought the wait you were trying to kill.

4. Capacity and refresh multiply. Forked models refresh as if they were products. You fund five pipelines for one word. Failures scatter. Nobody knows which twin the pack used last Monday.

5. Onboarding teaches the wrong skill. New analysts learn “copy dataset, tweak DAX” because that is how the last person shipped a cut. You industrialize forks. Training will not fix an architecture that rewards them.

6. Audit cannot answer who changed Revenue. Local measures have no steward. If anyone can edit the company word, you have a wiki with DAX—the cousin in who is allowed to change a measure. This article is the explore path that makes that control necessary.

If two tiles already disagree in the room, you are in different numbers. Five Revenues is how self-service scheduled it.

What not to do

Do not equate self-service with “everyone gets build on the production model.” Build on the kernel is how Revenue forks. Explore on the kernel is a live connection and a thin report.

Do not ban sandboxes. A lid is not a lock. Exploration that cannot exist legally will exist in downloads.

Do not let sandbox files reuse the English word the certified product owns. Call it Working Revenue Cut, or better, do not call it Revenue at all until it is promoted.

Do not certify a report that sits on a forked model. A pretty page on a twin is still a twin.

How to allow explore without five Revenues

1. Fence the words. List the company measures nobody may redefine locally: Revenue, Bookings, Margin, On-hand, Scrap, whatever you will argue in ELT. Publish the list. A sandbox measure with the same name is a process miss, not creativity.

2. Live connection or composite on the kernel. Explorers build thin reports against the certified model. They do not download a copy “for speed.” If they need a new dimension, that is a model request, not a fork. Composite for a local fact is allowed when it cannot change the kernel measures.

3. A junk drawer with a lid. Sandbox workspace. Prefix in the name. No exec app. Expiry. Promote what the meeting needs through the same bar as any other product change. Delete what expired. The drawer is certified vs wild west applied to explore, not a second catalog of Revenues.

4. Cuts are free. Definitions are a ticket. Slicers, bookmarks, personal pages: self-serve. A new include/exclude: named request, steward, sentence. Fast enough that people will use it. Slow enough that the sentence gets written. That is the middle the queue article asked for, implemented on measures.

5. Name the promotion path in one page. How a useful cut becomes a certified measure. Who signs. How the old local file dies. If promotion is a six-month committee, explorers will keep shipping twins into the ELT channel.

6. Watch for twins, not just unused reports. Usage logs catch museums. Definition drift needs a catalog of measure names across datasets. Two measures named Revenue is the smell. A Quickstart can put one domain on a kernel. Stewardship is managed advisory if you do not have the bench.

Start with one word leadership already fights about. Put explore on that kernel. Ban the local twin. Then the next word.

What good looks like

Analysts ship a new cut the same day. They do not ship a new Revenue.

The pack and the sandbox cannot be confused by name, workspace, or badge.

A new hire can tell what they may argue from and what they may only explore.

When someone needs a different bag, they request a named measure. They do not quietly edit the kernel in a copy.

Frequently asked questions

Isn’t this just lock-down with nicer slides? No. Filters and pages are free on the kernel. The lock is on redefining the company word. The queue is what happens when even a slicer is a ticket.

Can teams have their own models? Not for words the company already certified. A local grain with a local name is a different product. A clone of Revenue is a second close: when every team builds their own semantic model.

What if the certified measure is wrong? Change it in the kernel, with a steward and a sentence. Do not “fix” it in a fork. Forks never reconverge.

Get started

Stop treating copy-dataset as enablement. Fence the words, connect live, and give explore a drawer that cannot enter the pack by accident.

Need a 30-minute look at where self-service is already forking Revenue? Contact Alluvium. We’ll map the kernel, the banned names, and the path a cut uses to get promoted.

Book a 30-minute consult.