Who should build what?
← All services
Self-Service BI Reset
You wanted self-service analytics. Did you accidentally create self-service report chaos instead?
A focused reset of how business users, BI specialists and platform teams work together around Power BI.
DOES THIS SOUND FAMILIAR?
Start with what is actually happening.
- Hundreds of reports exist but trusted answers are still difficult to find.
- Different teams calculate the same KPI differently.
- Business users have Power BI access but still depend heavily on BI developers.
- Nobody agrees where self-service ends and governed BI begins.
- Training exists, but support and ownership after training are unclear.
WHAT WE NEED TO ANSWER
Good work starts with better questions.
Which semantic models should be centralised?
Where does business ownership sit?
What support does self-service actually require?
How much freedom is useful before it becomes fragmentation?
WHAT I REVIEW
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.
Current self-service adoption
User personas and capability levels
Semantic-model ownership
Workspace model and publishing patterns
Training and enablement
Support and office-hours model
Governance and endorsement
Community and BI-team responsibilities
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.
Current-State Diagnosis
Where self-service is helping and where it is creating avoidable friction.
Self-Service Operating Model
A practical definition of governed, managed and user-owned BI.
Role Boundaries
Clear responsibilities for business users, creators, BI teams and administrators.
Enablement Plan
Training, support and community mechanisms matched to user needs.
90-Day Priorities
A realistic starting plan rather than a multi-year transformation deck.
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 has scaled beyond one central team.
- Self-service exists but trust, reuse or ownership are inconsistent.
- You want to reduce the “report factory” pattern without blocking the business.
IT MAY NOT BE THE RIGHT FIT IF
- You only need introductory Power BI training for a small group.
- Your main issue is technical performance rather than operating model.
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.
SELF-SERVICE BI RESET
You wanted self-service analytics. Did you accidentally create self-service report chaos instead?
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