Certified Models vs the Wild West Workspace

If everything is blessed, nothing is. If nothing is blessed, every team workspace becomes 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, a shared enterprise product versus a clone per org chart, is covered in when every team builds their own semantic model. This post is about the status of a given dataset: promoted or not.

A shared model can still be uncertified if it has no steward and 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 a decision about who may publish the company’s word, and certification is how you enforce that decision in the workspace list. The semantic model is still the product. A brochure can be messy. The product leadership argues from cannot.

Uncertified twins in executive channels are how you schedule the symptom in why Power BI reports show different numbers.

What certified actually promises

Steward. A named 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. Otherwise you get measures nobody can explain.

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

Promotion path. A sandbox can become certified and a certified model can be demoted, and the path is written down. “We use it a lot” is not a path.

Uncertified work is allowed. It is for exploration, kaizen slices, what-if analysis, and campaign cuts. It must look uncertified, it must not reuse the English word the certified product owns, and it must stay out of the Monday pack.

The junk drawer needs a lid: a sandbox workspace, a naming rule, an expiry, and a ban on executive channels. No lid is the wild west. No drawer is how files end up hiding in Downloads.

The costs of no promotion path

1. Five Revenues with equal confidence. Each workspace ships a tile named Revenue, and 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 and nobody audits the sentence. The catalog fills with stamps and consumers learn to ignore them.

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

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

5. Security and capacity hide in the uncertified pile. Datasets that “aren’t official” still hold customer and plant grain, still refresh, and still get shared. The access review only looked at certified models, and 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 work into the ELT channel and dare you to object in the meeting. You will lose that dare.

The broader cost lives in hidden costs of poor Power BI governance. If two models both claim the company number and only one of them (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, and they should.

Do not treat certified as “we like this author.” The contract is the number.

Do not ban sandboxes either. A lid is not a lock, and exploration that cannot happen legally will happen illegally.

How to fix it

1. Inventory status, not just names. For each dataset that can reach a leader, record its status (certified, candidate, sandbox, or retire), its owner, the English words it publishes, and its last refresh. If you cannot produce that list, you do not have certification. You have folklore.

2. Write the promotion bar on one page. A named steward, a signed sentence, refresh in the window, row-level rules where plants must not see each other, and at least one meeting that will consume it. No bar, no badge.

3. Build the junk drawer on purpose. Give it a sandbox workspace, a prefix in the name, no executive app, and an expiry or review date. Use composite reads of the certified kernel where possible so experiments do not fork the ledger. Promote what the meeting needs and delete what expired.

4. Fence the rooms. The board pack, the ELT, and the company-level plant scorecard use the 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 let the app do the fencing.

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

6. Make promotion a backlog item, not a favor. A promotion request gets a date and an owner like any other product change. It should be fast enough that people use it and slow enough that the sentence gets written. A Quickstart can get one domain over the bar, and managed advisory covers ongoing stewardship if you do not have the bench.

Start with one word leadership already fights about. Promote one product, put a lid on its cousins, then move to the next word.

What good looks like

The Monday app is boring because it holds certified models only.

Analysts still have a place to try cuts, but those cuts are not named Revenue and stay out of the pack until they earn their way in.

The catalog is short, and 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 the 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 if it gets renamed so it no longer claims the company word. A local model and a certified company model do different jobs.

Get started

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

Want to know which datasets are actually certified and which are merely familiar? Book a session. We will map the promotion path and the lid on the junk drawer, not a sticker campaign. Or start with a free Model Health check.