Who can create what?
← All services
Power BI Governance Starter
You need governance. You probably do not need a 70-page governance document.
A lightweight governance framework designed to be used in day-to-day decisions, not filed away after the project ends.
DOES THIS SOUND FAMILIAR?
Start with what is actually happening.
- Nobody is sure who owns a workspace or semantic model.
- Naming is inconsistent and environments are difficult to distinguish.
- Production and experimentation live side by side.
- Reports remain active long after their owners leave.
- Governance conversations produce documents but few behavioural changes.
WHAT WE NEED TO ANSWER
Good work starts with better questions.
Who owns what after it goes live?
How should content move into production?
What genuinely needs standardisation — and what can remain flexible?
WHAT WE DEFINE
The scope follows the problem.
I do not force every engagement through the same checklist. These are the areas that may matter; the agreed scope determines how deep we go.
Workspace strategy
Roles and ownership
Naming conventions
Endorsement and certification
Content lifecycle
Sensitivity and access responsibilities
RLS ownership
Publishing and documentation expectations
WHAT YOU GET
Something you can use after the conversation ends.
The output should help you make a decision, change a practice or move the work forward. It should not exist simply to prove that work happened.
Governance Principles
A small set of principles that make recurring platform decisions easier.
Role & Ownership Model
Clear accountability for platform, data products and business content.
Workspace Rules
Practical guidance for creation, naming, ownership and lifecycle.
Publishing Guidance
What “ready for production” should mean in your environment.
Governance Checklist
A lightweight tool teams can actually use.
HOW IT WORKS
Enough structure to make the work clear. Not so much process that the process becomes the work.
Context
We start with a short conversation about what is happening, what matters and what has already been tried.
Review
I analyse the relevant parts of the solution or operating model at the depth agreed for the engagement.
Prioritise
I organise observations around impact, risk and usefulness — not around how many issues I can find.
Walkthrough
We go through the findings together, challenge assumptions and discuss trade-offs.
Next step
You decide what happens next: implement internally, continue together or stop because the focused engagement was enough.
YOUR TIME COMMITMENT
I keep the client-side time demand deliberately light. A focused assessment usually needs a kickoff conversation, access or materials, and a final review session. We agree the exact involvement before we start.
A GOOD FIT WHEN
This is likely to help if...
- Power BI usage has grown beyond informal conventions.
- You need more consistency without centralising every decision.
- You want governance that supports self-service rather than blocks it.
IT MAY NOT BE THE RIGHT FIT IF
- You need enterprise-wide information-governance policy across all systems.
- You want a purely compliance-driven control framework.
If the problem is real but the format is wrong, that is useful to know early. I would rather redirect the conversation than force the challenge into the wrong service.
POWER BI GOVERNANCE STARTER
You need governance. You probably do not need a 70-page governance document.
Bring me the problem, not a polished brief. A few sentences about what is happening and what you would like to change are enough to start.
Tell me what's happeningPREFER TO WRITE?
Send me a message.
You do not need a polished brief. Whether the topic is Power BI, Fabric, AI, team training, mentoring, coaching or simply a challenge that needs untangling, leave a few details and we can start from there.
SIGNALMESSAGECONVERSATION