What Gets Measured

3 other 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.

Healthcare benchmarking sits under HIPAA-era data-sensitivity constraints. The interface had to make physician-identifiable data legible to authorized reviewers while keeping every public demo fully de-identified. That discipline carries over into any domain where data visualization and clinical analytics touch protected information.

Faculty performance at an academic medical center 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.

The design principle that unified the entire interface was this: every visualization answers exactly one 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.

Before, a single continuous brush. The core interaction is the parallel coordinates brush filter, showing every physician as an individual polyline crossing 6 clinical 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 analysis at the precision of a continuous brush, not the coarseness of a dropdown. Brush any axis below.

After, compound brush composition. The current case study extends the brush into compound cohort definition: OR within an axis, AND across axes, with a readable audit trail after overlaps resolve. Multiple ranges can live on one axis, colliding ranges merge automatically, and brushes across axes combine into a single cohort definition. Try the scenes below.

The current case study carries the same design philosophy forward as a modern exception-led command center for clinical benchmarking.

The domain model covers care quality, access reliability, equity gap closure, workload pressure, value realization, and team support. Each metric answers a reviewer question instead of becoming one blended score.

The interface is exception-led. Ranked alerts, selected exception context, and burnout-risk signals appear first because exploration should follow the signal.

Burnout risk and patient equity are first-class signals. They are treated as operational risk indicators, not secondary annotations.

The parallel coordinates survived and deepened. The Benchmark Comparison Engine is the same analytical operation, hold one axis and observe all others, rebuilt in D3.js v7 with 6 clinical dimensions, overlaid reference lines for the review target and scoped service mean, and 4 scenario lenses: Quarterly Benchmark Review, Capacity Strain Watch, Access Parity Review, Quality Drift Watch.

The metrics chosen for any performance dashboard are not neutral. They are an institutional statement about what gets valued. What gets measured defines what gets managed. A well-designed interface makes that argument legible rather than hiding it in a formula.

The interface is not 5 disconnected charts. It is 1 loop: benchmark, compare, surface the exception, rank it, review the cohort, and commit a decision that feeds the next cycle.

A senior decision is usually a trade-off made on purpose. Here are 3 made on this build, and what each one bought.

Canvas polylines are not screen-reader readable. A production version owes keyboard filters, a semantic summary table, focusable controls, color-independent severity, and reduced-motion support. This page is a prototype, designed to WCAG AA principles but not VPAT-certified. Naming the gap is more useful than overclaiming a compliance the prototype has not been audited against.

The choice of what to measure, how to visualize it, and how to make it interactive are all the same decision made at different levels of abstraction. A parallel coordinates brush is the claim that holding one dimension constant while observing all others is the right analytical operation for this kind of comparison, and that a decision-maker under time pressure deserves that capability at the precision of a continuous brush, not the coarseness of a dropdown.

More than a decade of practice in this domain, from Protovis to D3, from reporting tools to command centers, from financial metrics to equity signals, produced a point of view. In pilot review of the rebuilt interface, reviewers used the compound brush to define a physician cohort in one move where the prior dashboard needed three separate filter steps, observed in walkthrough, not a timed study.

Behavior shift the case study is designed for: before, reviewers navigated view → chart → filter to find outliers; after, exceptions surface ranked on load and the brush defines a cohort in one gesture. This is the intended behavior of the design, not a measured result.

My starting assumption was that the composite score was the enemy, and better charts would beat it. Building the brush broke it: the real opponent is premature ranking anywhere in the flow, including chart defaults. The rule I carry forward: no view ranks candidates before the reviewer defines the comparison.