CSAT & Experience reporting: data model, ETL and dashboard
I designed the database, built the ETL and designed the dashboard in Google Looker Studio for a customer-satisfaction reporting product, taking survey responses all the way to something stakeholders can act on.
- Survey dataPlatform survey, one cycle per half-year
- ETLPrepare each cycle for reporting
- Data modelCycle · category · sentiment · theme
- Looker StudioScorecard, insights, trends
Database design
- Structured the data around the questions the dashboard has to answer: score by category, by survey cycle, against target.
- Made category, sentiment and theme first-class dimensions, so any view can be sliced and compared without reprocessing.
ETL
- Built the pipeline that takes each survey cycle from raw responses to reporting-ready tables.
- Produces what the dashboard reads: category CSAT scores, the positive / neutral / negative split, and counted themes.
Dashboard design
- Built in Google Looker Studio, leading with one number, overall CSAT against the OKR, so status reads in a second.
- Filters for date range, category and half-year, then an insights panel written as Observation → Trend → Action.
- Charts with the target drawn in, then ranked themes per category so every score has a visible driver.