Red Bull — DP Evolution

The problem

Red Bull's Distribution Evolution programme needed to assess distributor performance consistently across a large partner network — and then turn that assessment into action, rather than into a report nobody opens.

Consistency is the hard requirement. If scoring drifts between assessors or between regions, benchmarking becomes noise and every conclusion drawn from it is wrong in a way that's difficult to detect.

What I built

A distributor survey system with automated scoring, analytics, reporting, and cross-distributor benchmarking. A DPM interface for tracking the action plans that came out of each assessment. And a scorecard reporting on the programme's own effectiveness — measuring whether the initiative was working, not just whether distributors were.

That last piece is the one I'd argue for again. A system that scores other people should be willing to be scored.

Beyond the code

I presented technical plans directly to senior Red Bull stakeholders — the part of engineering where you find out whether you actually understand your own design, or have just been close enough to it for long enough. I also owned the amChart and PHPExcel integrations and post-launch fixes.

Stack

CakePHP · jQuery · AJAX · amChart · PHPExcel