Making Research Stick

Making Research Stick

Your work doesn’t end when research is delivered. It ends when it’s used. When research becomes a constant in conversations, decision-making, and roadmaps, that’s when it truly sticks.

You’ve just wrapped up a research study. The insights are clear, the findings are solid, and you’re excited to share them.

Fast-forward a few weeks: The team is deep in decision-making… and no one is referencing the research.

Fast-forward a few months: Someone else asks you to do the same research again—because they don’t even know it exists.

Sound familiar?

Research doesn’t drive impact just because it exists. It sticks when it’s socialised, acted upon, and integrated into decision-making.

Over the years, I’ve seen research ignored, skimmed, and—worst of all—forgotten. I’ve also seen what makes it land. And trust me, it’s not just about writing a better report or having a well-organised repository.

Here’s how you make research stick:


1. Be Proactive

The best way to ensure research gets used? Start before anyone even asks for it.

  • Pair up with data, product, and design to spot gaps early. What’s on their mind? What’s keeping them up at night?
  • Don’t wait for a research brief - embed yourself in product and design meetings (e.g. sprint planning, roadmap reviews) so you can flag problems before they become urgent.
  • Being proactive doesn’t have to mean launching a massive study. You can:

💡 Pro Tip: A 20-minute chat with a product manager and a data analyst can reveal more research gaps than waiting for a formal request.


2. Build Strong Partnerships

You can’t carry research impact alone. Find allies who can amplify insights when you’re not in the room.

  • Designers can push for research-backed decisions in design critiques.
  • Product managers can champion insights in roadmap discussions.
  • Data teams can strengthen findings with quant validation.

The trick? Involve them early. Co-create research questions. Let them hear users firsthand. Make them feel like research is theirs, not just yours.

💡 Pro Tip: After every study, send a quick Slack update with a key takeaway. Keeping research visible means keeping it relevant.


3. Speak The Business Language

Stakeholders love insights - but they love insights that tie to business impact even more.

A usability issue is frustrating, sure - but how does it hurt conversion, revenue, or retention? And why should foundational insights matter?

  • Conversion Rates: If filters are hard to find, users get stuck. Better visibility = smoother browsing = more purchases.
  • Average Order Value: If people need help choosing, show them dishes similar to what they like. A well-designed menu (and an easy checkout) increases basket size.
  • Retention: A smooth first-time experience increases repeat customers - so post-order experience isn’t just a ‘nice to have’.

Think beyond “Participants struggled.” Instead, say: “Participants struggled to find the right meal, leading to drop-offs. A clearer search and category layout could increase conversions.”

💡 Pro Tip: Before presenting insights, ask yourself: “So what?” If you can’t answer how it impacts business goals, refine your message.


4. Deliver In The Right Format

Not everyone wants a deck. (In fact, most don’t.)

  • Some teams need a one-pager.
  • Leadership may only have time for a 30-second Slack message.
  • Others might engage best with a five-minute video summary.

💡 Pro Tip:Meet people where they are (not where we wish they were). Experiment with different formats to see what sticks.


5. Help Turn Insights Into Action

Insights don’t magically turn into solutions. Facilitate action.

  • Run a short insights-to-action session - bring the right people together, help them pick their top three takeaways, and commit to next steps.
  • Check in a few weeks later: “What’s changed? What’s still blocking action?”
  • Track impact. If an insight led to another iteration, experiment, or product change, share the success story - people remember research that drives results.

💡 Pro tip: A “Research in Action” Slack update showcases real impact - building credibility and keeping teams engaged. If you send newsletters, consider adding a “Research Impact” highlight.


🎯 Bonus: For Research Leaders

As a leader, your job isn’t just about ensuring good research happens—it’s about making sure it drives action.

Here’s how you can help make your team’s research stick:

  • Get 'Research' a seat at the table – And take that seat! Advocate for researchers to be in roadmap planning, leadership meetings, and product strategy discussions. If research is invited after decisions are made, it’s too late.
  • Make research a habit, not an event – Encourage continuous discovery, not just reactive studies. Build rolling research programs that surface insights before teams realise they need them.
  • Give your team visibility – Help them present insights in leadership forums, all-hands, or company updates. Stakeholders should see the faces behind the research.
  • Celebrate impact – Track research outcomes and highlight wins. When insights lead to real changes, share it - whether in leadership meetings, Slack, or an internal newsletter.

💡 Pro tip: If you’re a leader, ask yourself - “Does my team’s research influence decisions, or does it just get delivered?” If it’s the latter, step in and amplify their voice.


Final thought: research that sticks, stays

Your work doesn’t end when research is delivered. It ends when it’s used.

When research becomes a constant in conversations, decision-making, and roadmaps, that’s when it truly sticks.

And if you’re doing this well? Soon, you won’t be the only one bringing research into discussions - your cross-functional team will be doing it for you.

That’s when you know research is no longer just a function. It’s a habit.

And that’s where the magic happens.


💬 I'll now wrap up this longer Swetha Spiel (thanks for reading till the end!). What’s worked for you in making research stick? Drop your best tip in the comments!

To view or add a comment, sign in

More articles by Swetha Sethu-Jones

Insights from the community

Others also viewed

Explore topics