3 earlier showcases in this portfolio, Uncertainty as Signal, North Bridge, and HR as DJ, deal with the same underlying problem: when dense information is misread, the resulting decision becomes expensive to reverse. Uncertainty as Signal keeps probabilistic climate risk legible for capital allocation. North Bridge keeps workflow signal tied to company context and follow-through. HR as DJ turns staffing uncertainty into actionable allocation moves. This showcase brings that same design problem into clinical operations, where missed exception patterns create care quality risk.

This showcase goes further back, and further forward at the same time.

Faculty performance at an academic medical center is not a single number. It is the contested intersection of 4 incommensurable domains: clinical productivity, research output, financial contribution, and educational impact. A high-volume surgeon fills OR hours and trains fellows. A principal investigator on 3 grants earns the institution funding and intellectual standing that no collection ratio can capture. A primary care physician who sees twice the patient volume of her colleagues but publishes nothing is, by different measures, both the most and least valuable person on the department’s roster.

I was brought in to design an interface that could show all of these dimensions simultaneously, compare any physician against any reference point, and support decisions about resource allocation, promotion, and strategic planning without pretending the underlying tensions had been resolved.

This was 2010 to 2012. D3.js did not yet exist. We built the Faculty Information Database on Protovis, the library that would become D3, developed by Mike Bostock and Jeff Heer at Stanford. The framework was early AngularJS, pre-1.0. That constraint forced a kind of clarity that is harder to achieve today. When you cannot reach for a charting library that hands you a parallel coordinates implementation, you have to think from fundamentals about what each visual encoding is actually for. The answers end up in the design.

The design principle that unified the entire interface was this: every visualization answers exactly 1 comparison question.

5 visualizations. 5 comparison questions. No chart that answered more than 1, because a chart that tries to answer 2 usually answers neither cleanly.

The most sophisticated interaction in the original work was the parallel coordinates brush filter, showing all 101 physicians as individual polylines crossing 8 axes simultaneously. The brush let users hold 1 dimension constant while immediately observing whether that dimension correlated with others or was entirely orthogonal. That is not filtering. That is analysis. The interface should support it at the precision of a continuous brush, not the coarseness of a dropdown.