Research methods

Choose the research method based on the decision risk.

Fred helps teams choose between moderated interviews, moderated and unmoderated usability tests, information architecture validation, concept comparison, surveys, and AI-assisted synthesis, then keeps the evidence connected through findings, reports, and product decisions.

  • Method coverage across moderated and unmoderated research
  • Decision-led guidance for discovery, usability, IA, concept, and feedback work
  • Source-linked findings and reports after evidence is collected

Method fit

Usability and task validation

Use this group before committing design or engineering time to a task flow.

Qualitative discovery and interviews

Use this group when the question starts with why, how, or what matters.

Information architecture

Use this group before a navigation, content model, or taxonomy decision hardens.

Concept and design direction

Use this group when multiple plausible directions need evidence before prioritization.

Structured feedback and prioritization

Use this group to quantify patterns, priorities, or preferences alongside qualitative evidence.

Analysis and decision output

Use this workflow after collection to decide what the evidence supports and what the team should do next.

Method coverage

A methods hub for the question behind the work.

Collection methods, moderated sessions, and synthesis workflows produce different kinds of evidence. Fred keeps those differences clear so teams can choose the right path for the decision in front of them.

Use task-based methods when the team needs to understand what people do.

Use UserSphere when live context, follow-up questions, and session evidence matter.

Use surveys and structured tests when consistent feedback across a segment is needed.

Use synthesis and reporting when evidence needs to become a decision record.

Research workflows

What each method helps your team decide.

Start with the product question, then choose the workflow that produces the evidence your team can actually use.

Usability and task validation

Unmoderated usability testing

Can participants complete the task, and where do they hesitate, misclick, abandon, or misunderstand?

Use when

Use it when a live researcher is not required and the team needs task evidence from participants moving through a product, prototype, website, or flow.

Evidence

  • task outcomes
  • click paths
  • session recordings where available
  • friction points
  • gaze or attention signals where available
  • source-linked findings

Inside Fred: Review task evidence, cluster friction patterns, and turn the strongest finding into a report section.

Usability and task validation

Moderated usability testing through UserSphere

What happens when a researcher observes a participant completing tasks, reacting to a screen, or working through a prototype?

Use when

Use UserSphere when the team needs live session context, follow-up questions, observed friction, and moderated task evidence.

Evidence

  • session recording
  • transcript
  • task context
  • observed friction
  • participant reactions
  • AI-assisted reaction cues
  • prosody context
  • source-linked moments

Inside Fred: Connect the moderated session moments to themes, quotes, clips, and stakeholder-ready findings.

Qualitative discovery and interviews

User interviews through UserSphere

Why do people behave this way, and what motivations, objections, needs, expectations, or decision criteria shape the experience?

Use when

Use interviews for discovery research, customer interviews, problem exploration, concept exploration, qualitative validation, and research reviews.

Evidence

  • transcripts
  • quotes
  • participant context
  • key moments
  • AI-assisted reaction cues
  • prosody context
  • source-linked findings

Inside Fred: Group recurring language, motivations, objections, and mental models into reviewable themes.

Usability and task validation

First-click testing

Does the first action match the intended path, and do people know where to start?

Use when

Use it before committing to a page, dashboard, landing page, onboarding step, checkout path, or feature entry point.

Evidence

  • first-click evidence
  • start-path success
  • misclick patterns
  • label comprehension signals
  • task context

Inside Fred: Compare intended paths against participant starts, then flag labels, hierarchy, or layout choices that need revision.

Usability and task validation

Prototype usability testing

Does the prototype or product flow create friction before engineering work is committed?

Use when

Use it when the team wants early evidence on an interactive prototype or product flow before build decisions harden.

Evidence

  • task outcomes
  • click behavior
  • observed friction
  • participant comments
  • source-linked findings

Inside Fred: Turn prototype friction into design priorities before handoff or sprint commitment.

Information architecture

Card sorting

How do users group information, features, content, or concepts?

Use when

Use it when labels, content groupings, product categories, or feature organization are still open.

Evidence

  • grouping patterns
  • category models
  • participant rationale
  • mental model signals

Inside Fred: Use the grouping evidence to shape navigation, taxonomy, content structure, or product packaging.

Information architecture

Tree testing

Can users find the right path in the navigation before the interface is redesigned?

Use when

Use it when a proposed structure needs validation without visual design influencing the result.

Evidence

  • navigation success or failure
  • path evidence
  • label comprehension signals
  • findability patterns

Inside Fred: Identify broken labels, unclear hierarchy, and paths that need restructured before launch.

Concept and design direction

Preference tests

Which design, message, layout, or concept is clearer or more convincing for the intended decision?

Use when

Use it when the team needs comparative evidence before choosing a direction.

Evidence

  • preference distribution
  • comparison evidence
  • qualitative explanations where collected
  • segment-level differences

Inside Fred: Connect preference evidence to the decision the team needs to make, not just the option that won.

Concept and design direction

5-second tests

What do people understand, remember, or miss after first exposure?

Use when

Use it to test first impressions, message recall, visual hierarchy, and immediate comprehension.

Evidence

  • first-impression feedback
  • recall responses
  • comprehension signals
  • message clarity evidence

Inside Fred: Use recall and comprehension evidence to adjust message hierarchy, concept framing, or landing-page direction.

Structured feedback and prioritization

Surveys and questionnaires

How common is a pattern, need, pain point, or preference across a target segment?

Use when

Use surveys and questionnaires when the team needs structured responses that complement interviews, usability sessions, or concept work.

Evidence

  • structured responses
  • rating data
  • open-text responses
  • prioritization input
  • segment-level feedback

Inside Fred: Combine structured feedback with qualitative evidence before deciding which pattern is strong enough to act on.

Decision-risk matrix

Group the method by the risk it reduces.

Discovery, usability, information architecture, concept direction, structured feedback, and decision output each need a different evidence shape.

Usability and task validation

Reduce the risk that a flow, prototype, website, dashboard, or feature cannot be understood or completed.

  • Unmoderated usability testing
  • Moderated usability testing through UserSphere
  • First-click testing
  • Prototype usability testing

Use this group before committing design or engineering time to a task flow.

Qualitative discovery and interviews

Reduce the risk that the team misunderstands user motivations, objections, mental models, needs, or buying criteria.

  • User interviews through UserSphere
  • Discovery sessions

Use this group when the question starts with why, how, or what matters.

Information architecture

Reduce the risk that users cannot understand labels, categories, paths, or navigation structure.

  • Card sorting
  • Tree testing

Use this group before a navigation, content model, or taxonomy decision hardens.

Concept and design direction

Reduce the risk of choosing a design, message, layout, or value proposition that does not land.

  • Preference tests
  • 5-second tests

Use this group when multiple plausible directions need evidence before prioritization.

Structured feedback and prioritization

Reduce the risk of over-weighting one conversation when the team needs structured input across a segment.

  • Surveys
  • Questionnaires

Use this group to quantify patterns, priorities, or preferences alongside qualitative evidence.

Analysis and decision output

Reduce the risk that method output becomes disconnected notes, exports, or claims without evidence.

  • AI-assisted thematic analysis
  • Insight signals
  • Source-linked findings
  • Stakeholder-ready reports
  • Reusable decision records

Use this workflow after collection to decide what the evidence supports and what the team should do next.

What you can run

Concrete workflows, not a generic method list.

Fred is strongest when the team can name the decision, choose the evidence shape, and keep the source material attached after collection.

Observe a checkout, onboarding, dashboard, or prototype flow

Run a moderated usability test through UserSphere when a researcher needs to watch a participant complete tasks, ask follow-up questions, and preserve session evidence.

Collect task evidence without a live researcher in the room

Run an unmoderated usability test when the team needs completion, click, friction, and attention evidence from participants on their own time.

Explore needs, motivations, objections, and mental models

Run a user interview through UserSphere when discovery work needs transcript, quotes, participant context, and source-linked moments.

Validate where users start

Use first-click testing when the team needs to know whether people begin in the expected place on a page, prototype, or flow.

Shape and validate information architecture

Use card sorting to understand how people group content, then tree testing to check whether the proposed navigation paths work.

Compare design, messaging, layout, or concept alternatives

Use preference tests and 5-second tests when the team needs first-impression, recall, comprehension, and comparison evidence.

Collect structured input from a target segment

Use surveys and questionnaires to measure priorities, ratings, open-text feedback, and segment-level patterns.

Turn research activity into decisions

Use AI-assisted synthesis and evidence-linked reports to connect method output to reviewable findings, recommendations, and reusable decision records.

Evidence chain

The method matters because the evidence has somewhere to go.

Fred's value is not just method coverage. It is the connected workflow from research activity to participant evidence, behavioral or session context where available, AI-assisted synthesis, source-linked findings, reports, and decision records.

  1. 01Method setup
  2. 02Participant evidence
  3. 03Behavioral or session signals where available
  4. 04AI-assisted synthesis
  5. 05Source-linked findings
  6. 06Stakeholder-ready report
  7. 07Decision record

Method guidance

Match the method to the kind of evidence the decision needs.

Some questions need discovery interviews, some need usability testing, some need information architecture validation, and some need structured survey research. Fred helps teams connect each user research method to AI-assisted analysis, research reporting, and the product decision that follows.

Use moderated usability testing when live observation and follow-up questions matter. Use unmoderated usability testing when the team needs task evidence from participants without a researcher in the room. Use user interviews for discovery, motivations, objections, needs, expectations, language, and decision criteria.

Use card sorting and tree testing for information architecture. Use first-click testing to validate where people start. Use 5-second testing and preference testing to compare concepts, design directions, message clarity, and first impressions. Use survey and questionnaire research when structured responses can complement qualitative evidence.

After collection, Fred helps teams use AI-assisted research analysis, insight signals, source-linked findings, and stakeholder-ready research reporting to make the decision case reviewable.

Common questions

Practical details before choosing a research workflow.

Short answers for teams comparing methods, moderated workflows, AI-assisted synthesis, and evidence-linked reports.

Decision-led research

Run the workflow that fits the question.

Start with the decision risk, collect the right evidence, and keep every finding connected to source material before the team acts on it.

Choose the method
Preserve the evidence
Synthesize with review
Report the decision