A room for UX researchers

Research Insight Relay

Help useful research reach the people who make product and engineering decisions.

Why this might help

Good research doesn't always reach the people who need it. Findings sit in decks, notes get buried, and decisions get made without them. This room is for UX researchers who want their work to actually land. You'll find honest signals that your insights aren't traveling far enough, a simple playbook for closing that gap, and a tool called the insight relay note that helps you hand off findings in a way product and engineering teams can actually use.

Does this feel familiar?

  • A product manager makes a decision you know your research already answered, but nobody looped you in.
  • Your findings deck got shared once in a meeting, then nobody mentioned it again.
  • An engineer asks a question in a sprint that you answered three months ago in a report.
  • You finish a study, write it up carefully, and then hear nothing back from the team for weeks.

Try this together

  1. Write one short summary for each study — think three sentences, not three pages — and share it the same week you finish.
  2. Find out how your product and engineering teams prefer to get information, then meet them there instead of asking them to come to you.
  3. Pick one finding per sprint that's directly relevant to what the team is building right now, and bring it up yourself.
  4. Keep a simple running list of your past studies so anyone can search it — even a shared doc works fine for this.
  5. After a decision gets made, check back in a few weeks to see whether your research played a role, so you can learn what's actually getting through.

Insight Relay Note

  1. Open a new work item in Tindlo and name it after the study or finding you want to relay — something specific, like 'Checkout flow confusion — July sessions'.
  2. Write a short brief inside the item: what you found, why it matters right now, and one clear thing you'd like the team to consider.
  3. Attach your research file or paste a link to the full report so anyone who wants more detail can find it without asking you.
  4. Tag the item with the relevant project or team so it shows up in the right layer when people are looking at their week.
  5. Schedule the item on the shared timeline for the week it's most relevant — for example, the week before a design review or a sprint kickoff.

Questions worth talking about

When was the last time a product or engineering decision clearly used something from your research — and what made that happen?

What usually gets in the way of your findings reaching the right person at the right time?

If a new engineer joined your team today, how would they find out what your research already knows?

A few common questions

How is an insight relay note different from just sending a Slack message or email?

A message disappears fast. An insight relay note stays attached to a point in time on your team's shared schedule, with the file and context right there. Someone planning next week's work can actually see it sitting alongside everything else, not buried in a thread.

What if my team doesn't read the notes I create?

That's worth exploring together. Sometimes the format is too long, sometimes the timing is off, sometimes people just don't know the habit exists yet. Start with one person you trust on the product side and ask them directly what would make it easier to read.

Can Tindlo help with this?

Tindlo lets you create work items with a brief, files, links, and a scheduled place on a shared timeline. That means your insight relay note lives where your team already plans their week, not in a separate tool. It won't do the research communication for you, but it gives the note a visible home.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?