Research that doesn’t impact anything is a waste of time and money. Doing “research just for the sake of research” is never a good idea. The most common problems here are:
Product development is about making decisions: business, product, design, marketing, and other decisions.
Each decision has a cost of implementation, expected impact, and implied risks.
Cost of implementation — is how much we will spend on developing particular feature and not others, entering a new market, etc. Expected impact — is what we anticipate to get in the result of the decision, usually expressed in improvement of relevant metrics: active users, conversion, retention, revenue, etc. Risk — is a level of uncertainty that given actions will lead to expected result and whether the resources will be spent reasonably.
Research is a tool for reducing the risks of decisions.
The cost of implementation and expected impact can be expressed in money. Research also has a price — how many resources we spend on designing, and conducting study, interpreting, and presenting data.
Therefore, the research makes sense only when its benefits outweigh the costs. This is the case, when:
I find this — “benefits should outweigh the costs” — to be a powerful mindset that helps me stay focused on the impact of the research, see the context that it exists in, and ultimately optimise the benefit-to-costs ratio of projects that I’m involved in.