Design Metrics and Product Thinking

"How do you know your design worked?" is one of the harder senior-interview questions precisely because the honest answer requires fluency in two languages most designers only speak one of: the language of user experience (was it usable, did it feel right, did it reduce friction) and the language of the business (did it move a number leadership tracks). A candidate who can only answer in the first language sounds like they design in a vacuum. A candidate who can only answer in the second sounds like they'd ship a manipulative dark pattern if it moved the number. The strong answer moves fluidly between both — naming a specific UX metric, connecting it to a specific business metric, and being explicit about where that connection could go wrong.

This subject is about that fluency: the frameworks for defining UX metrics in the first place (HEART, Goals-Signals-Metrics), the business vocabulary that makes a design rationale legible to a PM or exec (funnels, activation, retention, North Star metrics), the judgment calls interviewers probe for (quality vs. velocity, how to argue for a change before you have data), and the guardrail that keeps metrics-driven design from curdling into manipulation.

It builds directly on earlier subjects in this track — usability-testing-and-evaluation's task-success metrics feed straight into HEART's "Task success" category, and personas-journey-maps-and-jtbd's journey maps are where funnel drop-off gets diagnosed — and sets up design-ethics-and-dark-patterns, where the over-optimization risk covered here becomes the central topic. It also complements design-critique-and-portfolio-presentation: a portfolio case study that names the metric a decision was meant to move, and what actually happened, reads as far more credible than one that stops at "and here's the final screen."