Skip to Content
Use casesUX research

UX research

Skyelight ties research findings to the screen they’re about, so the team sees them where it builds and can turn them into fixes.


The problem

You run five sessions. People hesitate on the same step. Two of them miss the same button. One says something sharp about the onboarding that the whole team needs to hear.

Then it goes into a synthesis doc. The doc becomes a deck, and the deck gets presented once. The finding “people don’t see the save button on mobile” is now three steps removed from the save button.

Research loses most of its value between “we learned this” and “we fixed this.”

Where Skyelight fits

Pin observations on the page you tested. During or after a session, click the element where someone got stuck and write what happened. The thread stays on that element, with page context captured at that moment.

The finding and the element it’s about are in the same place. Anyone in the workspace who opens that page sees what research found there. Participants and stakeholders can join as reviewers, which are free on every plan.

Tip: Write observations rather than opinions. “P3 scrolled past the CTA twice before finding it” is a finding. “The CTA is bad” starts a debate.

Last updated on