UX research

Find the moments where users struggle.

UX researchers use Hymetry to spot friction signals, choose sessions worth reviewing, trace product paths, and turn repeated activity into research questions with source context close at hand.

Friction signals Sessions worth reviewing Product paths Research questions Source context
Session research

Friction signal workspace

Observed behavior with source context available

Source linked
SessionVisit 8m 42s
UserNew admin
CompanyNorthstar Labs
Page pathSetup to Dashboard

Repeated activity before workflow shift.

Dense event cluster, three setup returns, long pause, then the path changed from Setup to Dashboard to Boards.

Review first
Setup Integrations Setup Dashboard Boards
00:48 Dense event clusterRepeated setup actions around integration state.
02:16 Returned to SetupUser moved back after reaching Dashboard.
03:04 Long pauseNo meaningful action for 51 seconds.
04:12 Path changed directionSession shifted from Setup to Dashboard to Boards.
Replay/context availableSource visit can be inspected before forming a conclusion.
Suggested research question Why did users return to setup after reaching the dashboard?

Observed behavior

Start with what users actually do.

Hymetry turns product activity into inspectable sessions, paths, and friction signals, so researchers can decide what is worth investigating next.

See real product paths Identify repeated behavior Find shallow or interrupted workflows Connect sessions to users and accounts
1Raw product activity

Clicks, page changes, and interaction events.

2Visits

Sessions grouped into inspectable behavior.

3Page paths

How users moved through the product.

4Friction signals

Repeated actions, long pauses, path changes.

5Research questions

What should the team investigate next?

Session prioritization

Find sessions worth watching.

Instead of scanning random recordings, filter for sessions that may indicate friction: repeated actions, dense event clusters, unusual path changes, low interaction, or drop-off behavior.

Session User Company Product area Friction signal Evidence Replay/context Next step
Repeated setup activity New admin Northstar Labs Setup Repeated returns
Dense event clusterReturned to Integrations 3 times
Available Open timeline
Workflow shift after pause Team lead Atlas Works Dashboard Path changed
Long pauseMoved from Setup to Dashboard
Available Review path
High adoption, low interaction Power user Brightline Health Reports Shallow use
Page opened oftenFew meaningful actions
Source context Compare similar sessions
Repeated clicks before exit First-time user Harbor Ops Boards Exit after cluster
Multiple repeated actionsShort visit
Available Inspect replay context

Session inspection

Open the session behind the signal.

Every signal connects back to the underlying visit, so researchers can inspect the path, timing, events, and context before deciding what the behavior may indicate.

Session timeline

New admin returned to setup after reaching Dashboard.

Northstar Labs, 8m 42s visit, replay/context available

Inspect
User levelNew admin
Account levelExpansion account
Page pathSetup, Dashboard, Boards
Project setup Integrations Dashboard Setup Boards
00:14 Project setup openedUser began from the admin checklist.
01:31 Integration state repeatedSeveral repeated actions around connection status.
03:02 Dashboard reachedNo completion event was recorded before the next page change.
03:47 Returned to setupWorkflow moved back to setup after a pause.
06:40 Opened BoardsSession changed direction instead of completing setup.
Research note Why did users return to setup after reaching the dashboard?

Journey paths

Understand the path before and after friction.

See the sequence around a signal: what users did before friction appeared, where they paused or returned, and what happened after the path changed.

00:00Project setupChecklist opened from onboarding.
01:12IntegrationsReturned to connection state twice.
02:44SettingsDense event cluster around permissions.
04:08DashboardLong pause, then no completion event.
05:31BoardsWorkflow changed direction.
06:24ExitSession ended without setup completion.
Returned to Settings after reaching Dashboard. Dense event cluster before the workflow changed. Long pause before the next product area opened. No completion event before exit; compare with successful setup paths.

User and account comparison

Compare behavior across users and accounts.

Separate one-off confusion from repeated experience problems by comparing paths across companies, roles, user health states, and product areas.

Completed vs abandoned New users vs power users Healthy vs at-risk accounts Adopted vs skipped workflow
SegmentNew users

31 users across 12 companies

Common pathSetup -> Dashboard -> Setup
Friction patternRepeated setup returns

May indicate unclear required steps.

Affected sessions42 sessions
Review setup returns
SegmentPower users

49 users across 18 companies

Common pathProjects -> Boards -> Reports
Friction patternHigh interaction, few drop-offs

Use as successful path contrast.

Affected sessions88 sessions
Compare completed paths
SegmentPassive users

26 users across 9 companies

Common pathDashboard -> Exit
Friction patternLow interaction

Opened often with few meaningful actions.

Affected sessions31 sessions
Inspect shallow visits
SegmentAt-risk accounts

17 users across 6 companies

Common pathReports -> Settings -> Exit
Friction patternInterrupted reporting workflow

Path changes before report completion.

Affected sessions24 sessions
Review at-risk paths

Research planning

Turn behavior patterns into better research questions.

Hymetry helps teams move from "something looks wrong" to a specific question grounded in observed behavior, source sessions, and product context.

Observed patternUsers return to setup after reaching Dashboard.
Research questionDo users understand what setup is required before using Dashboard?
Observed basis36 sessions, repeated setup visits, long pause
Where to inspectOpen visit timelines
High
Observed patternReporting is visited but not interacted with.
Research questionIs Reporting discoverable but unclear?
Observed basisHigh page adoption, low interaction
Where to inspectCompare successful vs shallow sessions
Medium
Observed patternNew admins repeat integration actions.
Research questionAre integration states and next steps clear?
Observed basisDense event clusters, multiple returns
Where to inspectReview replay context
High

AI-assisted summaries

Summaries that keep the evidence visible.

Hymetry can summarize repeated behavior patterns, but every insight keeps source sessions, pages, users, and underlying events available for review.

AI-assisted pattern summary

Several new users repeat setup actions before changing workflows.

Across similar sessions, new admins repeat setup actions, pause, then shift to Dashboard or Boards before completing setup. The summary helps researchers choose what to inspect; it does not decide why users struggled.

36 similar sessions Repeated Integration setup actions Long pauses before path change Most affected users are new admins Replay/context available
Suggested next step: Review representative sessions and compare successful setup paths.
Representative sessions5 visits marked for review
Affected usersMostly new admins
Product areasSetup, Integrations, Dashboard
Similar patternsSetup returns, pauses, path changes
Source visitsTimeline, path, replay/context, user and company details
Research questionWhich setup step is unclear before users move to Dashboard?

Responsible research

Research from behavior without unnecessary exposure.

Hymetry helps teams inspect product behavior while privacy controls help filter sensitive fields, configure what not to capture, and keep source context reviewable.

Privacy controls help filter sensitive fields Teams can configure what not to capture Ignored selectors and pages can be excluded Replay context can be inspected with controls in place Source views remain reviewable

Find the evidence behind better product experiences.

See where users may struggle, open the sessions behind the pattern, and bring observed behavior into every research conversation.

Explore a demo project first, then create your workspace when you're ready.