LINKEDIN
EMAIL
I didn't study data. I walked into it. As order orchestrator at KPN ÉÉN I was the single point of contact for business customers — every delivery was mine to land, and our team needed operational insight nobody could give us. There was a forgotten BI tool sitting in the corner: Spotfire. Nobody knew how it worked. I said I'd try.
YouTube and stubbornness taught me the business logic, then how to change it, then how to rebuild the entire dashboard. That got me the analyst job — and with one colleague I built a full ETL and data model in Power BI. I didn't know Power BI either. Same method: figure it out, ship it, improve it.
The pattern repeated at HR. After the BRIDGE migration there was a hole in our reporting. Oracle gave us OTBI — and again, YouTube and I taught ourselves to build reports in it. OTBI wasn't great, so we built Power BI dashboards on top of it to fill the gaps.
Ten years later I'm a BI developer in a scrum team of five. GBS adopted our team from HR, so its main products are finance while I own the HR side. What I bring isn't only DAX: it's HR domain knowledge and a UX perspective most BI teams don't have.
Microsoft CertifiedPower BI Data Analyst AssociateVerify at Microsoft
Hearing the decision, not the request
Stakeholders ask for a report. I listen for the decision behind it. Eight years of retail conversations teach you the difference.
Numbers for non-numbers people
I've explained targets to part-timers on a shop floor and models to directors. It's the same skill, and most BI work fails on it.
UX, inside BI
A complex model makes a horrible pivot table. I design the way in — what users see first, what they never have to touch.
I've carried a target
Manager of a team of four or five, measured monthly. I build for the person who has a number to hit and an escalation to handle.
