Intermediate Power BI (session 5)

Power BI
intermediate
Intermediate Power BI course
PQM
Published

February 26, 2026

This session is part of our intermediate-level Power BI desktop course. The course structure is as follows:

Previous attendees have said…

  • 22 previous attendees have left feedback
  • 95% would recommend this session to a colleague
  • 100% said that this session was pitched correctly

NoteThree random comments from previous attendees
  • Not a coding person, but very helpful. especially as NHS based. setup is good & very interactive sessions, compared to standard courses. Much easier to follow & learn.
  • I would call this session intermediate, but it follows on nicely from the previous sessions. Missing a previous session may make it more difficult to join in at this point. Really informative and eases gently into more difficult query building.
  • Complex subject well taught with examples
TipForthcoming session(s)
Booking link Date
Intermediate Power BI (session 5) 10:00-12:00 Tue 26th May 2026

Session aim

  • we’ve had four content-heavy training sessions so far
  • session five is about putting your new skills into practice in a collaborative environment
ImportantNote!

This is a collaborative session. You’ll be working in small groups to develop a dashboard. That means that you should expect to be an active contributor to that group throughout the session.

Session outline

  • an entirely practical build-a-dashboard session
  • we’ll use The Care Inspectorate’s public datastore, which contains a lot of rich data about Scotland’s care sector
  • you’ll be putting your Power BI skills to the test on this data: what can you show us?
  • you’ll be working in small groups, doing team programming

Setup

Personae

We’ll be working collaboratively to design a dashboard. More specifically, we’ll ask you to group programme. This means that every member of the group has an identified role and responsibility. These are:

  • the author, who is the person who actually writes the dashboard in Power BI. They’ll share their screen, they’ll make all the changes in Power BI, and everyone else will tell them what to do
  • the presenter, someone who keeps an overall eye on the work, and takes charge of presenting your work-in-progress dashboard to the whole group when we catch-up. That would ideally be someone with some subject-matter expertise
  • some data engineers to think about the raw data, understand what it means, and how to make it behave for your dashboard via e.g. PowerQuery
  • some front-end engineers - again, a couple of people to think about how the dashboard page itself should look, any DAX formulas etc you might need, and how the report page helps tell the story you want to tell

Schedule

We’ll work through a series of small- and whole-group sessions to develop the dashboard. The

  • 15 minutes: initial exploration of the data, and idea generation
  • 5-10 minutes: re-join for troubleshoot and chat
  • 15 minutes: data wrangling
  • 10 minutes: break
  • 20 minutes: report draft
  • 10 minutes: re-join for chat
  • 10 minute: polish and refine
  • until session end: showing off and suggestions

Telling a story

Good dashboards tell a specific story about the data. That usually means making some clear decisions about only exploring parts of the available data. In the first small-group session, you’ll have a look at the data, and try to develop a clear objective for your eventual dashboard. Some suggestions to help you do that:

  • do you want to talk about data that is national, regional, or local?
  • do you want to show a snapshot of something, or show change over time (e.g. inspection ratings)?
  • do you want this dashboard to be self-contained from the provided data, or would it help to bring in other sources of open data?
  • about care in general, or something more specific?
  • about inspections, service organisers, service users?

Conduct

  • be kind: we’re all here to learn
  • I’m here throughout: message me in case of any difficulties
  • nominate one person to share their screen, and work on the report
  • other people navigate, direct, suggest, and look up
  • start small and iterate