AB InBev - Data Analytics Lead, Logistics
Jun 2024 – Jun 2025
First holder of a new regional role bringing three countries' logistics data teams into one operation. Responsible for what got built, in what order, by whom, and whether the operation actually used it.
AB InBev - Data Analytics Lead, Logistics
Jun 2024 – Jun 2025
-
I designed the operating model for a three-market Agile data team that had just been centralized and had no methodology yet: discovery, prioritization, the quarterly roadmap cycle, and the ceremonies themselves. I validated each piece with the three product owners.
- Discovery ran per market because a process like warehouse picking carried different business rules in each one, so a combined session would have lost those differences
- I extended weighted shortest job first scoring with multipliers for product type and market reach, which put the regional strategy directly into how initiatives were ranked
- Result: each quarter the regional logistics director and the three market directors chose between two or three costed scenarios, each with a named resource plan by month. 91% of the committed roadmap delivered across the year
-
I redesigned how dashboard usage was measured, interviewing sub-area managers to establish who should be using each report, at what frequency, and in which routine.
- Every dashboard came out with an action attached: decommission, promote, fix, or leave. Low usage got investigated rather than assumed, and usually traced to something specific, like a source file owner who had stopped uploading
- Result: over 85% usage in H2 2024. In 2025 I extended it across all three markets and built a portfolio rationalization method, presented to the regional logistics director, which identified the unused long tail for decommissioning
-
I expanded the team's NPS survey from a small group of managers to the wider operation, building the form with conditional logic so questions adapted by market, sub-area, and which team the respondent worked with.
- The wider base made the score meaningful, and the analysis could be read by market, by sub-area and by logistics pillar rather than only in aggregate
- Result: 65.8 against a target of 60. For 2025 I unified the survey with the sister projects team and led the design for both areas
-
I attended all three markets' daily stand-ups, which the role did not require, because most blockers raised there were organizational rather than technical: an unanswered question to a business partner, a missing permission, a file nobody had shared.
- Sitting between the visualization analysts, the engineers and the business meant I could take those to the person who could actually clear them, instead of leaving them stuck inside one squad with no one who had the standing to move them
- Result: the three squads started solving problems for each other. An engineer hitting something in one market got connected to whoever had already solved it in another, and I set up cross-market chat groups by role so that contact outlasted the stand-up