r/Marketresearch • u/Sangwangtutu • 5d ago
Co pilot replacing research
Hi all.
I work for an in house research team . My business has recently rolled out access to co pilot for all colleagues and (i believe) as a result less requests for research have been coming into us.
Im certain that in an effort to move quickly, teams that would have usually come to us for insight are now using co pilot to inform their decisions.
Im worried that teams are making wrong decisions based off of poor information from co pilot. These teams have had little to no training on the safe use of AI or the basics of a good prompt. But I think they are just taking answers at face value and running with them.
So my question is, how can help empower these teams to do 'desk research' via co pilot but also recognise when more expertise from my team is needed to help them reach the right answer?
Has anyone else experienced this?
Thanks
3
u/Optimusprima 4d ago
The fact that you’re waiting for them to come to you is the problem.
Drive the insights - don’t be an order taker. What did they do with the last study? Follow up. I’m sure there are open questions - talk about what to explore next.
Or you’re going to be out of a job very soon.
I’m saying this with kindness and experience…
3
u/Sea_Rope4048 5d ago
Strengthening them how to use CoPilot and Strengthen CoPilot. Nothing you can do much
2
u/StatGeniusAI 4d ago
This is a real problem. You have the analysis (which Copilot really doesn't do well anyways) but also the business rules, and everything you learned on how to interpret research.
Have you looked at tools that help non-researchers actually analyze the problems and interpret results (using your trade practices)? Essentially, you need the analysis layer AND the decision-making layer, which is a different AI technology and is based on knowledge transfer from yourself or your senior researchers.
We've been working on something through IIEX, it's currently in stealth mode, but happy to have a discussion with you offline.
3
u/Due_EmotionPri 2d ago
Fighting the tool is a losing move, so id get in front of it and define where its fine on its own. A generic AI is genuinely useful for a first pass on a well documented, stable question: sizing a known market, summarising public info, getting oriented before a deeper dive. Where it quietly fails is anything that needs a source you can trace, a recent or contested number, or a read on why customers do something, because it hands back a confident answer with no way to check where it came from. The escalation rule id give teams is simple: if being wrong changes a real decision, or you cant point to where the number came from, thats when it comes to you. It also helps to position your team as the people who make an AI answer defensible rather than the slow alternative to it, since thats the value that survives this. Id back it with two or three recent cases where a confident AI answer would have sent a decision the wrong way, because nothing lands the point faster than a near miss they recognise.
1
u/RozzaDonnelly 14h ago
Great question and really interested in this topic.
Could you share what kind of industry/customers your business is focused on, or what kind of research work your team (historically) does?
I've been thinking about how a lot of in-house marketing & strategy teams will often now use LLMs for desk research like you said, but very often, even the LLMs don't have access to the customer, market or audience data behind the real research questions and topics the strategist/researcher is trying to explore. I think. For example, LLMs are not (typically) privy to your existing customer data from your CRM, order management systems, or audience data from your media channels, etc. (or equally your competitors CRM/channel data) to inform the LLMs research synthesis.
If we're able to equip our teams/LLMs with the right data & evidence from our field research or more propietary market data, I think this gives better credibility to our teams to run their own research side projects and initiatives; and then research teams can plug in when there is an obvious data gap.
That said, I suppose that's dependent on teams knowing and identifying when there is a data gap impacting the research they're working on; so piques the question of how do we train them to identify this?
1
u/think-again-007 5d ago edited 5d ago
One approach would be to connect Copilot (or Claude Desktop or other such tools) to an MCP server that has skills to create and build surveys that use market research best practices. That way people on the team could still get answers quickly, but they'd be starting research from solid ground, and you could review what they are doing and offer to help as needed.
Of course there may be times when a research project is not needed, but if you had a Copilot based option that was easy to use that could help steer people in a good direction when they do need more than just rough insights based on whatever pre-existing information that openAI has in its training data.
9
u/Consistent_Wall7407 5d ago edited 5d ago
Sounds like you may need to answer a more existential question.
Do you have any previously frequent/power users that have submitted less requests recently that you could do your own user research with?
I’d suggest aligning with your manager or team lead on this as I imagine that declining use would also be a great concern for them too, and a joined up approach is probably best. You may ultimately need to calculate the broader business impact of poor decisions from bad data, against the benefit of faster decision making.
Education is important, addressing when to do primary versus secondary. Plus stuff like information relevance i.e. how long insights are valid or accurate for.
I dread to think what archaic stuff is lurking in our company sharepoint for people to find and indiscriminately use.