The Business-Fluency Scalpel for Researchers
Learn the company's financial language so your insights land in the funnel, not in a deck.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 92%
Antin's most contested claim: researchers must become explicitly profit-focused, hunting the overlap between what users need and what the business needs. The mechanism is concrete — read the quarterly report, listen to the shareholder call, scour the internal strategy folder, memorize the OKRs and the conversion funnel — so that when a research question arrives you can point it at a specific business opportunity instead of accepting the blob version.
Origin
Judd Antin, from 'The UX Research Reckoning is Here.' The section drew the sharpest pushback he received — from what he calls the 'anti-capitalist crew' who felt profit focus was not research's job.
Core principles
- 01There is an overlapping Venn of user need and business profit; the researcher's job is to be explicit about finding it.
- 02Empathy and user-centeredness are not abandoned — they are aimed.
- 03The strategy documents, the earnings call, and the funnel are the language you must speak to be in the room.
- 04Insights should be used like a scalpel: pointed at one spot, not spread over a topic.
- 05Fewer things done better beats ten projects across seven PMs and twenty designers.
How to run it
- 1
Read the financial primary sources
If the company is public, read the last quarterly report and listen to the shareholder call. The unfamiliar language in them is precisely the language you need to learn.
Pro tip Note the metrics executives repeat under analyst pressure — those are the metrics your research must move.
- 2
Scour the internal strategy corpus
Go through the internal drive for every document about this quarter's, this half's, and next half's strategy. Extract the OKRs, the metrics, and the conversion funnel and know them back and forward.
Pro tip Also read the competitive reports — 'that competitor is eating our lunch with this group of users' is a research proposal, not a complaint.
- 3
Convert every incoming request into a funnel-anchored proposal
Answer requests in the form: 'I hear the question you're asking; I've identified the exact spot in the funnel where I think the opportunity is, and here's what we'd learn there.' This is what turns a blob middle-range ask into a pointed, worth-the-time study.
Pro tip Bring evidence of a metric trend to the framing conversation — it converts you from order-taker to proposer.
Watch out This only works if you are in the conversation early. Business fluency without a seat in the room just makes you a better-informed order-taker.
- 4
Ruthlessly prioritize with your partners
Antin's load rule: a full plate for a researcher is about three things — two big projects and one small side project. More than that and the researcher is doing none of them well. Partner with the PM to say no.
Pro tip A project can take 48 hours; size is not the constraint, count is.
Watch out Most researchers today are the lone researcher across many PMs and designers — without an explicit prioritization pact, they default to the reactive queue.
In the wild
Instead of accepting the request as posed, the business-fluent researcher responds by naming the exact funnel step where the opportunity sits or the competitor threat that a specific user group represents — because they have read the competitive report and understand it deeply.
→ The conversation shifts from 'run this study' to 'here is the question worth answering,' which is where research impact actually comes from.
The same middle-range question ('how do hosts feel about payments') becomes legitimate once the researcher can say: I have studied the business plan, I have seen the metric trend, I know exactly where this is going.
→ The middle-range study still runs — but pointed, and the time is now worth it.
Common mistakes
Treating profit focus as a betrayal of the user
Antin's response to the critique: 'what are we doing then if we're not helping businesses succeed?' The user lens is not dropped; it is intersected with the business lens.
Saying yes to everything
A lone researcher spread across seven PMs, twenty designers, and ten projects will do a bad job on all of them, which is then read as research being low-impact.
Is it for you?
Best for
UX researchers and insights people who feel sidelined, unheard, or vulnerable in a layoff cycle
Not ideal for
Academic or pure-discovery research contexts where commercial outcomes are explicitly not the objective
From the transcript
“like did you read the last quarterly report if it's a public company did you listen to the shareholder call”
“what are the okrs understand the metrics and the funnel the conversion funnel”
“understanding exactly how to use your insights like a scalpel”
“I used to say that a full plate for a researcher was probably three things two big projects and a small project”
From the episode
The UX research reckoning is here
Judd Antin (Airbnb, Meta)