Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

User Research Methodologies

ASecurity

Systematic approaches for discovering user needs, behaviors, and pain points through interviews, testing, observation, and surveys

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
researchgotesting

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill user-research-methodologies --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of User Research Methodologies?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for User Research Methodologies
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-user-research-methodologies/badge)](https://www.skillsdirectory.com/skills/lev-os-user-research-methodologies)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: user-research-methodologies
description: Systematic approaches for discovering user needs, behaviors, and pain points through interviews, testing, observation, and surveys
---

# User Research Methodologies

## Overview

User research methodologies are systematic approaches to understanding user behaviors, needs, motivations, and contexts through various qualitative and quantitative techniques. As defined by Nielsen Norman Group, UX research can be positioned along three dimensions: Attitudinal vs. Behavioral (what people say vs. what they do), Qualitative vs. Quantitative (depth vs. scale), and Generative vs. Evaluative (discovery vs. validation). The goal is to inform design decisions with evidence rather than assumptions, using the right method at the right stage of product development.

## When to Use

- Beginning new product development to discover unmet user needs (generative)
- Validating design concepts before investing in full development (evaluative)
- Understanding why users behave in certain ways (qualitative)
- Measuring task success rates or satisfaction scores at scale (quantitative)
- Identifying usability problems in existing products
- Creating user personas, journey maps, or mental models
- Prioritizing features based on actual user needs rather than stakeholder opinions

## The Process

### Step 1: Define Research Questions and Choose Method Type

Articulate what you need to learn and select appropriate attitudinal/behavioral and qualitative/quantitative methods. **Example:** Question: "Why do users abandon checkout?" Choose Behavioral + Qualitative = Usability Testing and Session Recording Analysis.

### Step 2: Conduct User Interviews (Generative, Qualitative, Attitudinal)

Perform 1-on-1 conversations to explore user needs, pain points, and mental models. **Example:** 10 interviews with target users, 45-60 minutes each, semi-structured questions about current workflow pain points, recorded and transcribed for analysis.

### Step 3: Execute Usability Testing (Evaluative, Qualitative, Behavioral)

Observe users attempting realistic tasks with your product to identify usability issues. **Example:** 5 participants perform "find and purchase product" task while thinking aloud, facilitator notes friction points, measures task completion rate and time-on-task.

### Step 4: Deploy Surveys (Attitudinal, Quantitative)

Collect structured feedback from large sample sizes for statistical significance. **Example:** Post-purchase survey (n=500) using System Usability Scale (SUS) and Net Promoter Score (NPS), 5-point Likert scales, multiple-choice questions for demographics.

### Step 5: Perform Field Studies / Contextual Inquiry (Generative, Qualitative, Behavioral)

Observe users in their natural environment to understand context and workarounds. **Example:** Shadow 6 nurses during hospital shifts, observe EMR system usage in actual clinical context, identify interruptions and workarounds not visible in lab setting.

### Step 6: Conduct Card Sorting (Generative/Evaluative, Qualitative, Behavioral)

Understand user mental models for information organization and navigation. **Example:** Give 15 participants 50 content cards, ask them to group and name categories (open sort), validate proposed IA structure (closed sort), analyze with clustering software.

### Step 7: Analyze and Synthesize Findings

Identify patterns across research data, prioritize insights by frequency and severity, translate to actionable recommendations. **Example:** Affinity diagramming of interview notes reveals 3 major themes, usability test videos coded for error types, survey data analyzed for statistical significance, findings compiled into research report with prioritized recommendations.

## Example Application

**Situation:** Healthcare scheduling app has 2.1 star rating and declining usage, but team doesn't understand root causes.

**Application:**
- User Interviews (n=12): Discovered patients confused by medical terminology, feared scheduling wrong appointment type
- Usability Testing (n=8): 87% struggled to reschedule appointments, 62% couldn't find cancellation policy
- Field Study (n=4): Observed patients at clinic trying to use app while stressed, multi-tasking, interrupted by staff
- Survey (n=350): Quantified that 68% preferred phone scheduling despite app availability, SUS score of 48/100 (below average)
- Card Sort (n=15): Revealed users organized appointments by body system (cardiology, orthopedics) not by clinic location (current design)

**Synthesis:** Primary issues were (1) unclear appointment type selection, (2) hidden rescheduling function, (3) stressful usage contexts requiring simpler UI.

**Outcome Post-Redesign:** App rating increased to 4.3 stars, active users grew 140%, phone call volume decreased 35%, SUS score improved to 76/100.

## Anti-Patterns

- Testing with 1-2 users and treating findings as representative of all users
- Leading questions in interviews that bias responses ("Don't you think this design is intuitive?")
- Usability testing without realistic tasks in realistic contexts
- Confusing attitudinal data (what users say) with behavioral data (what users do)
- Running research without clear questions, resulting in unfocused findings
- Skipping synthesis and jumping directly from data collection to design solutions
- Using only quantitative methods without understanding the "why" behind numbers
- Recruiting participants who don't match target user profile (employees, friends)

## Related

- Nielsen Norman Group Research Framework - Dimensional classification of methods
- Jobs To Be Done - Understanding user motivations and goals
- User Personas - Research-derived user archetypes
- Journey Mapping - Visualizing user experience over time
- Affinity Diagramming - Synthesis technique for qualitative data
- System Usability Scale (SUS) - Standardized usability questionnaire
- Ethnographic Research - Deep observational studies in context
- A/B Testing - Quantitative method for comparing design variants

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Competitor Analysis

This skill provides comprehensive analysis of competitor SEO and GEO strategies, revealing what's working in your market and identifying opportunities to outperform the competition.

1823 votes

Deep Research

Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review...

452202 votes

Paperclip Distill

Use when an operation issue is a Paperclip cursor-window, distill, or backfill — `operationType: "distill"` or `"backfill"` and the body references a Paperclip source bundle for a project or root issue. Turn raw Paperclip activity into a wiki-insightful project page, decisions log, and history note. This skill exists specifically to replace the stiff, datestamp-heavy templated output that the deterministic distiller produces.

805541 votes

Academic Pipeline

Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publi...

452201 votes

Exa Search

Semantic search, similar content discovery, and structured research using Exa API

304951 votes
View all in research →