interaction-research
User experience research (UXR), usability testing protocols, qualitative/quantitative metrics (SUS, SEQ, Task Completion Rate), think-aloud facilitation, and thematic insight synthesis.
- License 许可
- MIT
- 最近更新
- 2026-10-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- interaction-research
- description
- User experience research (UXR), usability testing protocols, qualitative/quantitative metrics (SUS, SEQ, Task Completion Rate), think-aloud facilitation, and thematic insight synthesis.
02 资源文件 6
- 参考文档checks/interaction-research-checklist.md1.9 KB
- 参考文档examples/usability_test_study.md2.3 KB
- 参考文档manifest.json1.8 KB
- 参考文档references/interaction-research-guide.md2.8 KB
- 脚本scripts/verify.sh1.9 KB
- 参考文档templates/user-research-protocol.md2.5 KB
03 SKILL.md 正文
Interaction & User Experience Research (UXR) Contract
1. Purpose
Plan, conduct, analyze, and synthesize empirical user experience research (UXR) and usability testing studies. Formulate non-leading task scenarios, administer standardized metrics (System Usability Scale - SUS, Single Ease Question - SEQ, Task Completion Rate - TCR), extract behavioral friction points, and deliver data-driven recommendations that guide product architecture.
2. Use When
- Formulating usability testing protocols and interview scripts for prototype or feature evaluation.
- Benchmarking software usability before and after major redesigns or architecture migrations.
- Measuring user task completion efficiency, error rates, and cognitive friction in core funnels.
- Synthesizing qualitative feedback from user testing sessions into prioritized product insights.
3. Do Not Use When
- Designing visual layout tokens or component styling (use
design-tokensorui-implementation). - Conducting automated headless pixel comparison (use
visual-regression). - Writing production application code.
4. Required Context
Before formulating a research study, verify:
- Research Objectives & Hypotheses: What specific behaviors, assumptions, or risks is this study designed to test?
- Target User Cohorts: Screener criteria, domain expertise level, customer segment.
- Stimulus Material: Figma prototype, staging deployment, production interface, or wireframe.
- Study Format: Moderated synchronous (remote/in-person) vs Unmoderated asynchronous (UserTesting, Maze).
5. Procedure
Step 1: Study Design & Participant Screening
- Define primary research questions and falsifiable hypotheses.
- Draft a screening survey selecting 5 to 8 participants per distinct user segment (Nielsen's rule: 5 users uncover 85% of usability issues).
- Ensure participant diversity and exclude internal stakeholders or biased individuals.
Step 2: Task Scenario & Protocol Authoring
- Design realistic, goal-oriented scenarios that avoid leading phrasing:
- Good: "You need to find out how much you spent on compute in August. Show me how you'd find that."
- Bad (Leading): "Go to the Billing tab and click on the August invoice button."
- Define explicit success criteria, maximum time allotment, and allowed assistance thresholds for each task.
Step 3: Session Facilitation & Think-Aloud Execution
- Obtain informed consent and record permissions (GDPR/privacy compliance).
- Facilitate sessions using the Think-Aloud Protocol: encourage participants to verbalize their thoughts, expectations, hesitations, and surprises in real time.
- Maintain neutral facilitation: never defend the design, explain the UI, or instruct the user unless they are irrecoverably blocked.
Step 4: Quantitative Metrics Collection
Administer standardized post-task and post-study questionnaires:
- Single Ease Question (SEQ): 1-item 7-point scale administered immediately after each task: "Overall, how easy or difficult was it to complete this task?" (1 = Very Difficult, 7 = Very Easy; target: $\ge 5.5$).
- Task Completion Rate (TCR): Binary measure (0 = Failed/Abandoned, 1 = Succeeded). Target: $\ge 80%$.
- System Usability Scale (SUS): 10-item standard questionnaire administered at the conclusion of the study, scored from 0 to 100 (industry benchmark average: 68; target: $\ge 75$ for high satisfaction).
Step 5: Thematic Synthesis & Insight Prioritization
- Group observed behavioral friction into thematic clusters using affinity mapping.
- Quantify issue severity by frequency (how many users struggled) and impact (blocking vs minor delay).
- Deliver clear, actionable design and engineering recommendations.
6. Decision Rules
- Zero Leading Prompts: Prompts must describe user goals, never UI mechanisms or specific menu names.
- Observe Behavior Over Stated Preference: What users do is authoritative over what users say. If a user states a task was "easy" but took 8 minutes and 3 errors, record it as a high-friction task.
- Standardized SUS Scoring: The System Usability Scale must be calculated using the exact standard odd/even normalization formula; ad-hoc modifications invalidate benchmarks.
- Privacy & Data Redaction: User PII, credentials, or sensitive organizational data must be scrubbed from transcripts and video clips.
7. Evidence Required
- Research Protocol Document: Complete test plan with screeners, task scenarios, and metrics.
- Raw Observations & Metric Logs: Task completion matrix, ToT, SEQ scores, and SUS score calculations.
- Synthesized Findings Report: Thematic findings linked to timestamped/recorded behavioral evidence.
8. Output Contract
A production UXR deliverable must contain:
- User Research Protocol & Plan (
templates/user-research-protocol.md). - Quantitative scorecard (TCR, SEQ, SUS).
- Key insights matrix with prioritized design/engineering recommendations.
9. Stop Conditions
- Required participant cohort sessions completed.
- All task scenarios scored for TCR and SEQ.
- Overall SUS score computed with standard deviation.
10. Escalation Rules
- Escalate to Product Management if usability testing reveals fundamental mismatch between user mental models and core product value proposition.
- Escalate to Compliance/Legal if session recordings capture unauthorized customer data or PII.
04 同仓库更多 Skills
zoom-reflow
暂无简介
wireframe-styleguide
暂无简介
visual-regression
Pixel-by-pixel snapshot testing, Playwright integration, dynamic content masking, deterministic font rendering, and cross-browser CI gates
ui-implementation
Component-driven UI implementation, multi-state matrix (default, hover, focus-visible, active, disabled, loading, empty, error), DTCG design tokens, responsive layout contracts, and accessibility tree mapping.
tui-editor-engine
Text buffer and editing semantics for a terminal code editor — index conversion, transaction-first editing, multi-cursor invariants, undo grouping, and large-file behaviour.
tree-sitter-context-indexing
暂无简介