Work V — Making the Numbers Legible

pbe 2.0

Building on an inherited design system, not around it.

Analytics design is a discipline of restraint: expert users, dense data, and the constant temptation to decorate. For DRG's Pharmacy Benefit Evaluator 2.0, I worked deliberately inside the existing design system — reusing and extending it rather than replacing it — so the product gained coherence with every screen shipped instead of drifting into a second visual language.

PBE before and after redesign — Fig. 1PBE, before and after 2.0.

Whiteboard working through the drill-down problem — three interdependent data buckets, why a parent-child tree doesn't apply, and three candidate interaction patterns — Fig. 2The full working board — the system thinking behind the screens.

PBE 2.0 final screen — trending overview — Fig. 3Final: trending overview.

PBE 2.0 final screen — comparison view — Fig. 4Final: comparative analysis.

PBE 2.0 final screen — detail drill-down — Fig. 5Final: drill-down detail.

PBE 2.0 final screen — multi-parent trending — Fig. 6Final: multi-parent trending.

PBE 2.0 final screen — summary view — Fig. 7Final: summary (sensitive data boxed out).

eyereturn

Campaign analytics for people who live in the numbers.

At Eyereturn, the users were advertising operators watching live campaign performance — people who open the same screens dozens of times a day. The design goal was less 'insight' theatre and more operational trust: the number you need, where your eye already is, at the density a professional can actually use.

Eyereturn campaign analytics interface — Fig. 8Eyereturn campaign analytics.