User-Centred Performance
User-centred performance is Judd Antin‘s term for customer obsession or user-centred practice that is symbolic rather than learning-driven — work done to signal how customer-obsessed a team is, not to change a decision.
Definition and tells
The defining characteristic is that no one expects to be wrong. User-centred performance can be distinguished from genuine user research by checking: Is the team open to a result that changes the plan, or are they looking for confirmation that the plan is sound?
Explicit forms include:
- Validation studies commissioned after a product decision is effectively made
- Executive listening sessions where the PM controls the questions and framing
- ‘Quick user studies’ requested at the end of a development cycle to check a box before launch
Implicit forms include confirmation-seeking that is rationalised as open-minded inquiry, and post-hoc attribution of insights to user research when the decision was driven by intuition.
Root causes
Three groups generate user-centred performance, per Antin’s analysis:
Product managers use middle-range research to justify decisions they are reluctant to make on their own. The research provides cover, not input.
Designers request middle-range research because it fits their process model of what rigorous design looks like — not because it will alter the outcome.
Executives commission it to perform user-centricity without investing in the process changes that would actually produce it. They will, in most cases, decide on the basis of their own judgment regardless.
Antidote: falsify, do not validate
Antin’s formulation: ‘We don’t validate, we falsify. We are looking to be wrong.’
A research process oriented toward falsification:
- Defines upfront what would constitute evidence against the current hypothesis
- Includes the researcher in the decision conversation from the start — not at the end
- Counts ‘we were wrong’ as a success, not a failure
Structural condition
User-centred performance is not primarily a character flaw. It is the predictable output of research organised as a service function rather than an integrated partner. When researchers are called in late, excluded from the framing of questions, and measured on output volume rather than decision impact, performing user-centricity becomes rational behaviour.
The structural fix is consistent researcher integration from the beginning of the product process — not periodic engagements on predetermined questions.
See also
- Judd Antin
- Judd Antin on the User Research Reckoning, Middle-Range Research, and User-Centred Performance
- Product Operations — related: the systems that determine whether research reaches decisions