A live Tableau dashboard project for course attendance and booking data, framed as an implemented analytics project rather than a notebook exercise. The strongest proof point is external feedback from the Digital Skills Lab context describing the dashboard as a tool relied on weekly.
Context
Course attendance and booking data can become operationally useful only when the team can see patterns clearly and return to the same reliable view over time.
The project was not just about producing a chart. It was about building a usable reporting workflow that helped a busy team monitor activity, understand demand and make weekly sense of course engagement.
What I did
- Prepared and structured course attendance and booking data for analysis.
- Built an iterative Tableau dashboard and reporting view around the team’s operational questions.
- Worked through technical roadblocks and project-management constraints until the dashboard became usable in practice.
- Connected the public technical portfolio to the real work through the related Tableau repository and Tableau Public demo where appropriate.
Outcomes
The dashboard created a repeatable way to inspect course activity instead of relying only on ad hoc analysis.
Feedback describes the tool as something relied on weekly, which is the signal that the work moved beyond a prototype.
The testimonial highlights technical challenges and roadblocks, making delivery itself part of the evidence.
Evidence base
This case study is supported by testimonial evidence from Jeni Brown, Head of Digital Skills Lab at LSE.
- The testimonial describes the dashboard as extremely useful for analysing and visualising course attendance and booking data.
- It states that the tool is relied on weekly by the team.
- It also notes that earlier attempts had not succeeded and that this version was delivered despite technical challenges.
How this translates
This project is the clearest bridge between the real-world work and the GitHub portfolio. On the site, it should lead the analytics story, while the related GitHub/Tableau material should sit underneath as supporting proof.
A natural next development would be to add screenshots, a short data-flow diagram and a before/after description of the reporting workflow.