Certified Models vs the Wild West Workspace

Promotion to certified is how you stop five Revenues. Workspaces still need a junk drawer with a lid.

If everything is blessed, nothing is. If nothing is blessed, every team workspace is a ledger. Certification is a promotion path, not a sticker you put on last quarter’s file because the author asked.

Certified versus uncertified—not a model per team

When every team builds a production semantic model, you industrialize five closes. That architecture problem is when every team builds their own semantic model. Shared enterprise product versus a clone per org chart. This post is the status on a given dataset: promoted, or not.

A shared model can still be uncertified: no steward, no sentence. Sandboxes can be healthy because they cannot feed the board pack. The wild west is not exploration. It is uncertified numbers in certified rooms.

Single source of truth is the decision about who may publish the company word: SSOT is a decision, not a slogan. Certification is how you enforce that decision in the workspace list. The model is still the product: the semantic model is the product. A brochure can be messy. The product that leadership will argue from cannot.

Conflicting tiles in a meeting are the symptom: why Power BI reports show different numbers. Uncertified twins in exec channels are how you schedule that symptom.

What certified actually promises

Not a badge. A contract.

Steward. A role who will defend the measure in the room and who can change it. Not “the analyst who published.”

Sentence. What the number includes and excludes, at what grain, on what calendar. If nobody can say it, do not certify it. That is measures nobody can explain.

Refresh and access. It lands in the window the meeting needs. The right plants see the right rows. A certified model that fails on Monday morning is a close risk wearing a ribbon.

Promotion path. Sandbox can become certified. Certified can be demoted. The path is written. “We use it a lot” is not a path.

Uncertified is allowed. It is for exploration, kaizen slices, what-if, a campaign cut. It must look uncertified. It must not reuse the English word the certified product owns. It must not sit in the Monday pack.

The junk drawer needs a lid: sandbox workspace, naming rule, expiry, ban on exec channels. No lid is the wild west. No drawer is how files hide in downloads.

The costs of no promotion path

1. Five Revenues with equal confidence. Each workspace ships a tile named Revenue. None is wrong in its own story. The meeting cannot tell which one was promoted. Trust dies in the comparison, not in the DAX.

2. Certification becomes a popularity contest. Authors request the badge. Nobody audits the sentence. The catalog fills with stamps. Consumers learn to ignore the stamp. You spent governance effort on wallpaper.

3. The junk drawer becomes the house. With no sanctioned sandbox, exploration happens in production workspaces—or in Excel. You either freeze publishing and recreate the ticket queue, or you bless every experiment by inaction.

4. Demotion never happens. A certified model rots: grain wrong, steward left, refresh flaky. It keeps the badge. New work forks beside it because nobody will pull the ribbon. Now you have a certified ghost and an uncertified live twin. The worst of both.

5. Security and capacity hide in the uncertified pile. Open datasets that “aren’t official” still hold customer and plant grain. They still refresh. They still get shared. The access review looked at certified only. The leak was in the drawer with no lid.

6. Promotion takes forever, so people stop asking. If the path to certified is a six-month committee, the business will ship uncertified into the ELT channel and dare you to object in the meeting. You will lose that dare.

Broader cost lives in hidden costs of poor Power BI governance. This article is the badge versus the drawer. If two models both claim the company number and only one (or neither) is promoted, you are in it.

What not to do

Do not certify reports instead of models. A pretty page on a wild dataset is still wild.

Do not certify everything in a workspace because the workspace is “finance.” Finance sandboxes exist. They should.

Do not treat certified as “we like this author.” The contract is the number. Do not ban sandboxes. A lid is not a lock. Exploration that cannot exist legally will exist illegally.

How to fix it

1. Inventory status, not just names. For each dataset that can reach a leader: certified, candidate, sandbox, or retire. Owner. Which English words it publishes. Last refresh. If you cannot produce that list, you do not have certification. You have folklore.

2. Write the promotion bar in one page. Steward named. Sentence signed. Refresh in the window. Row-level rules where plants must not see each other. At least one meeting that will consume it. No bar, no badge.

3. Build the junk drawer on purpose. Sandbox workspace. Prefix in the name. No exec app. Expiry or review date. Composite reads of the certified kernel where possible, so experiments do not fork the ledger. Promote what the meeting needs. Delete what expired.

4. Fence the rooms. Board pack, ELT, plant scorecard at company level: certified kernel only. If someone pastes an uncertified tile into those rooms, that is a process miss, not a creative workaround. Say so once. Then the app does the fencing for you.

5. Demote in public. When a certified product no longer meets the bar, pull the badge and say where people should go instead. Ghosts with ribbons are how five Revenues return while the catalog still looks clean.

6. Make promotion a backlog item, not a favor. The path is a request with a date, owned like any other product change. Fast enough that people will use it. Slow enough that the sentence gets written. A Quickstart can get one domain over the bar. Ongoing stewardship is managed advisory if you do not have the bench.

Start with one word leadership already fights about. Promote one product. Lid on the cousins. Then the next word.

What good looks like

The app for Monday is boring: certified models only.

Analysts still have a place to try cuts. Those cuts are not named Revenue. They do not appear in the pack until they earn it.

The catalog is short. Demotions are as visible as promotions.

A new hire can tell, from the name and the badge, what they may argue from and what they may only explore.

FAQ

Isn’t certification just Microsoft’s endorsement feature? The feature is a flag. The promise is the contract. A flag without a steward is still wild west with a nicer icon.

Can we certify a team model if it is the only one they have? Only if it is willing to become the enterprise product for that word—or it is renamed so it does not claim the company word. Local and certified-company are different jobs.

Get started

Stop putting ribbons on files. Write the bar, the drawer, and the one product you will promote this month.

Need a 30-minute look at which datasets are actually certified versus merely familiar? Contact Alluvium. We will map the promotion path and the lid on the junk drawer—not a sticker campaign.

Book a 30-minute consult.