One Metric That Matters

What it is. One Metric That Matters is the single measurable outcome that decides whether a design project delivered value or just delivered pixels. It is the last of the six questions in the brief but it shapes every answer that comes before it. The metric must be observable from outside the team. It must tie directly to business results. It must be measurable with tools the client already uses such as Google Analytics, Mixpanel, or Stripe dashboards. In the one page constraints sheet it sits at the bottom where the decider signs because it is the clause that ends the relationship if the number does not move. The decider owns it. The done state describes exactly when and where the metric gets measured. The out of scope list keeps the team from doing work that would distract from it. The budget kill and timeline kill prevent the project from limping along after it becomes clear the metric will not budge. This creates a closed loop system where every decision either serves the number or gets rejected without debate. The team reviews it every two weeks in the same room as the decider. No slides. Just the number and the work. If the number moves the project succeeds. If it does not the team has concrete proof that the approach failed and the kill criteria kick in without emotion. The metric retroactively dictates the entire brief. Pick it first even though it appears last.

What it is not. One Metric That Matters is not a balanced set of KPIs. It is not brand awareness or user satisfaction or any metric that takes a survey team three weeks to calculate. It is not the five things leadership wants to track so no one feels left out. It is not a vanity number like total visitors or social mentions or Figma files completed. The anti dashboard exists because teams love hiding behind walls of green dots while the one number that pays salaries stays flat. One Metric That Matters removes the hiding spots. It forces the team to pick one hill and ignore the rest. Most agencies resist this because it makes their decorative work accountable to data instead of taste. The best teams demand it because it gives them permission to kill beautiful but useless ideas without a long debate. It is not something added at the end of the brief like an afterthought or a slide no one reads. It is chosen first then used to audit every other line in the constraints sheet. It rejects any answer that cannot be tracked from production data next week.

Concrete example. Linear used One Metric That Matters for their Q1 2024 command bar and issue view redesign. The number was percentage of weekly active teams completing four or more cycles inside the product. They pinned the exact target to their project channel in Notion and every design critique started with the same question. Will this change move that number. Two beautiful but slow loading states got cut in the final week because they dropped the metric by six points in internal dogfooding. The shipped version looked plain in isolation but lifted the metric from 39 percent to 48 percent in the first month after launch. Stripe ran their 2023 checkout redesign against first month revenue from new users who saw the new flow. They deleted three illustration heavy states the design team had spent weeks perfecting because data showed those states reduced completion rates by 11 percent. The metric won and revenue followed. Vercel targeted paid conversion from preview deployments within 14 days for their 2025 dashboard refresh. They removed popular but distracting status indicators that lowered the conversion rate in A B tests even though those indicators tested well in brand workshops. Anthropic applied the same logic to their Claude interface updates with prompt completion rate for users above 50 messages per week. Every color contrast change and button placement got tested against that number before it reached production. These companies do not launch beautiful work and hope the market likes it. They launch work that moves the number they wrote down before the first pixel left Figma.

When to use. Use One Metric That Matters on every commercial design project that has a budget and a shipping date. Write it in the brief before any design work begins. Put it in the contract next to the payment terms. Pin it to the Slack channel and the wall. Review it every two weeks with the named decider present. Use it to kill scope creep that does not serve the number. Use it for marketing sites that live or die by qualified leads per month. Use it for product features measured by activated accounts in the first 30 days. Use it for brand projects judged by measurable changes in inbound deal quality or sales cycle length instead of vague sentiment scores. It pairs perfectly with value based pricing because the metric becomes the trigger for the final payment and removes arguments about whether the work was worth it. It works with kill criteria by giving the team an objective trigger for ending the project instead of hurt feelings or endless revisions.

When not to use. Do not use One Metric That Matters for pure exploratory work or speculative concepts with no attached commercial outcome. Do not use it when the client cannot or will not name a single decider who owns the number. Do not use it if the metric requires new tracking infrastructure that takes longer to build than the project itself. Do not write the number then ignore it when the data looks bad in week three. That creates worse theater than never writing it at all. The kill criteria in the brief exist to handle exactly those cases where the metric reveals the work is not working. Trigger them mechanically on the dates written in the sheet. The number does not negotiate with opinions or sunk costs.

One Metric That Matters turns every design conversation into math instead of opinion.