Design is working when a team makes better decisions, moves with less friction, and learns faster because design is involved.
Reach, satisfaction, and NPS matter, but they often arrive after the team has made many decisions. Operating signals appear earlier—in planning conversations, technical tradeoffs, and the way insight changes a roadmap.
Look beyond output
A team can ship polished screens on time without letting design shape the product. In that model, design decorates decisions made elsewhere.
The difference appears in how people work together:
- A product manager asks for a design perspective because the decision needs it, not as a courtesy.
- Engineering involves design before the architecture is locked so intent can shape the approach.
- The team includes design in tradeoff discussions without waiting for a formal invitation.
Those moments are difficult to place on a dashboard, but they show whether the team trusts design to improve the work.
Three signals to watch
Decision quality
The first signal is whether the team makes better decisions with design involved.
Look for specific evidence. Did design surface an edge case before engineering reached it? Did the team consider user impact while choosing a technical approach? Did experience priorities shape the scope?
A team that sees design improve decisions does not need design to defend its existence. Four Ways Designers Earn Influence on Product Teams describes the behaviors behind this signal: reduce ambiguity, name tradeoffs, make reasoning visible, and help the team move.
Friction reduction
The second signal is whether design makes the team faster by answering questions before they become blockers.
The practical test is simple: can product and engineering make progress while the designer is unavailable? If the team stalls, the work still depends on an artifact or a person. If the team can move with confidence, design has created shared understanding.
Design can add states, requirements, and edge cases. Strong design also removes ambiguity and prevents rework.
Learning velocity
The third signal is whether the team learns faster with design involved.
Research findings, usability tests, and competitive analysis matter only when they reach decision-makers in time to change what happens next. A thorough report that arrives after the decision does not improve the product.
Learning velocity depends on trust, timing, and framing. The team must trust the evidence, receive it before the decision, and understand what action it supports.
Treat the signals as leading indicators
These signals are qualitative. They require attention to how the team interacts, not only what it produces.
Dependencies, throughput, satisfaction, and NPS still matter. They are lagging indicators: they tell you what already happened. Decision quality, friction reduction, and learning velocity show whether the operating model is likely to produce a strong result.
Watch the conversations, the team's speed, and the quality of decisions people can make without the designer in the room. Those patterns will tell you whether design is working before the quarterly report arrives.
The standard that matters
Design is working when the team makes better decisions, moves faster with less friction, and learns more quickly than it would without design.
That is the standard I care about most.