Skip to content

vt-c-kw-user-test

Comprehensive user research workflow including interview script creation, interview analysis, and usability test design.

Plugin: core-standards
Category: Knowledge Work Workflow
Command: /vt-c-kw-user-test

Knowledge Work: User Research

Comprehensive user research workflow for creating interview scripts, analyzing interviews, and designing usability tests.

Workflow Position

/vt-c-kw-prd → /vt-c-kw-prototype → /vt-c-kw-user-test → /vt-c-kw-specs
                              │
                              ├── script    (before user interviews)
                              ├── analyze   (after interviews)
                              └── usability (test prototype)

Invocation

/vt-c-kw-user-test script              # Create interview script
/vt-c-kw-user-test analyze FILE        # Analyze interview transcript
/vt-c-kw-user-test usability           # Create usability test plan

Configuration

# Project paths
prd_path: "03-PRD/PRD.md"
personas_path: "02-Knowledge/02-Zielgruppen-Personas/"
output_path: "02-Knowledge/04-Dokumente/"
prototype_path: "04-prototyp/"

Agents Used

This skill leverages three specialized research agents: - interview-script-writer - Creates semi-structured interview guides - interview-analyzer - Extracts insights from transcripts - usability-test-designer - Designs prototype test plans

Mode 1: Interview Script Creation

Invocation

/vt-c-kw-user-test script

Execution Instructions

Step 1: Load Context

  1. Read PRD for research objectives
  2. Read personas from 02-Knowledge/02-Zielgruppen-Personas/
  3. Identify key assumptions to validate
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Interview Script Generator
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Project: [name]
PRD: 03-PRD/PRD.md

Target Persona: [Select or specify]
─────────────────────────────────────────────────────────────────
1. [Persona 1] - [description]
2. [Persona 2] - [description]
3. [Other] - Specify custom persona

Research Objectives:
─────────────────────────────────────────────────────────────────
• Validate problem statement
• Understand current workflows
• Test value proposition
• Identify unmet needs
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 2: Gather Research Focus

Ask user for: - Primary research questions (what do we want to learn?) - Specific features to explore - Known assumptions to validate - Interview duration (30/45/60 minutes)

Step 3: Generate Interview Script

Create structured interview guide:

# Interview Script: [Project Name]

## Interview Information
- **Target Persona**: [Persona name]
- **Duration**: [X] minutes
- **Research Objectives**:
  1. [Objective 1]
  2. [Objective 2]
  3. [Objective 3]

---

## Before the Interview

### Setup Checklist
- [ ] Recording consent form
- [ ] Recording device tested
- [ ] Interview guide printed
- [ ] Note-taking materials ready
- [ ] Prototype URL available (if needed)

### Consent Script
> "Thank you for participating in this interview. We're researching
> [topic] to improve [product/service]. The interview will take about
> [X] minutes. With your permission, I'd like to record this session
> for note-taking purposes. The recording will be kept confidential
> and used only for research purposes. Is that okay with you?"

---

## Part 1: Warm-Up (5 minutes)

### Introduction
> "Let's start with some background questions to understand your
> context better."

### Questions
1. **Tell me about your role at [company/context].**
   - Probe: Daily responsibilities?
   - Probe: Team structure?

2. **How long have you been in this role?**

3. **What tools do you currently use for [relevant task]?**

---

## Part 2: Current State Exploration (15 minutes)

### Context Setting
> "Now I'd like to understand how you currently handle [process/task]."

### Questions
4. **Walk me through how you typically [do task].**
   - Probe: What triggers this activity?
   - Probe: Who else is involved?
   - Probe: What tools do you use?

5. **What's the most challenging part of [task]?**
   - Probe: Why is that challenging?
   - Probe: How often does this happen?
   - Probe: What have you tried to solve it?

6. **Tell me about a recent time when [problem situation].**
   - Probe: What happened next?
   - Probe: How did you feel about that?
   - Probe: What would have made it better?

---

## Part 3: Feature Exploration (15 minutes)

### Transition
> "Now I'd like to share some ideas we're exploring and get your
> feedback."

### Questions
7. **[Describe feature concept]. What's your initial reaction?**
   - Probe: What would be most useful?
   - Probe: What concerns do you have?
   - Probe: How would this fit into your workflow?

8. **If this existed, how would you use it?**
   - Probe: Who else would need access?
   - Probe: How often would you use it?

9. **What would make or break this for you?**
   - Probe: Must-have features?
   - Probe: Deal-breakers?

---

## Part 4: Prioritization (5 minutes)

### Questions
10. **Of everything we discussed, what's most important to you?**

11. **What would you be willing to give up to get [key feature]?**

---

## Part 5: Wrap-Up (5 minutes)

### Closing Questions
12. **Is there anything we didn't discuss that you think is important?**

13. **Do you know anyone else who might be good to talk to about this?**

### Thank You Script
> "Thank you so much for your time today. Your insights are incredibly
> valuable and will help us build something that truly meets your needs.
> If you have any additional thoughts later, please feel free to reach
> out. We may follow up with a brief survey or to share what we've
> learned."

---

## Interviewer Notes

### Key Areas to Probe
- [Area 1]
- [Area 2]
- [Area 3]

### Watch For
- Emotional reactions
- Workarounds and hacks
- Unmet needs mentioned in passing
- Contradictions between stated and actual behavior

### Don't Forget
- Ask "Why?" at least 3 times
- Let silence work for you
- Note non-verbal cues
- Follow unexpected threads

Step 4: Save and Display Summary

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Interview Script Created
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

File: 02-Knowledge/04-Dokumente/interview-script-[date].md

Script Summary:
─────────────────────────────────────────────────────────────────
• Duration: [X] minutes
• Target persona: [Persona]
• Questions: N total (Y warm-up, Z core, W wrap-up)

Sections:
1. Warm-Up (5 min)
2. Current State Exploration (15 min)
3. Feature Exploration (15 min)
4. Prioritization (5 min)
5. Wrap-Up (5 min)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NEXT STEPS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Review and customize the script
2. Schedule interviews with target users
3. Conduct interviews and record (with consent)
4. Analyze transcripts: /vt-c-kw-user-test analyze [file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Mode 2: Interview Analysis

Invocation

/vt-c-kw-user-test analyze [transcript-file]

Execution Instructions

Step 1: Read Transcript

  1. Read the provided transcript file (PDF or Markdown)
  2. Load original interview script for context
  3. Load PRD for research objectives
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Interview Analysis
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Transcript: [file]
Interview Script: [detected or specify]
PRD: 03-PRD/PRD.md

Analyzing...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 2: Extract Insights

Analyze transcript for: - Key quotes (verbatim, with timestamps if available) - Themes and patterns - Pain points mentioned - Feature reactions - Unmet needs - Contradictions

Step 3: Generate Analysis Report

# Interview Analysis: [Participant ID/Name]

## Interview Metadata
- **Date**: [date]
- **Duration**: [X] minutes
- **Participant**: [role/persona]
- **Analyst**: [name]

---

## Executive Summary

[2-3 sentences summarizing key takeaways]

---

## Key Findings

### Finding 1: [Theme]
**Insight**: [Description of finding]

**Supporting Quotes**:
> "[Exact quote from transcript]" - [timestamp if available]
> "[Another quote]" - [timestamp]

**Implications for PRD**:
- [How this affects requirements]

### Finding 2: [Theme]
[Same structure]

---

## Pain Points Identified

| Pain Point | Severity | Frequency | Quote |
|------------|----------|-----------|-------|
| [Pain 1] | High/Med/Low | [how often mentioned] | "[quote]" |
| [Pain 2] | High/Med/Low | [frequency] | "[quote]" |

---

## Feature Reactions

### Feature: [Feature from PRD]
- **Reaction**: Positive/Neutral/Negative
- **Quote**: "[exact reaction]"
- **Concerns**: [any concerns raised]
- **Suggestions**: [improvements suggested]

---

## Unmet Needs

1. **[Need 1]**: [description]
   - Quote: "[supporting quote]"
   - Priority indicator: [high/med/low]

2. **[Need 2]**: [description]
   - Quote: "[supporting quote]"
   - Priority indicator: [high/med/low]

---

## Recommendations

### For PRD Update
- [ ] [Specific recommendation]
- [ ] [Specific recommendation]

### For Prototype
- [ ] [Specific recommendation]
- [ ] [Specific recommendation]

### For Further Research
- [ ] [Topic to explore more]
- [ ] [Topic to explore more]

---

## Quote Library

### On [Topic 1]
> "[Quote]" - [context]
> "[Quote]" - [context]

### On [Topic 2]
> "[Quote]" - [context]

---

## Appendix

### Full Transcript Reference
[Link to transcript file]

### Analysis Notes
[Any additional observations]

Step 4: Save and Display Summary

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Interview Analysis Complete
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

File: 02-Knowledge/04-Dokumente/interview-analysis-[date].md

Analysis Summary:
─────────────────────────────────────────────────────────────────
• Key findings: N
• Pain points: X
• Feature reactions: Y
• Recommendations: Z

Top Finding:
[Brief description of most important insight]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NEXT STEPS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Review analysis with team
2. Update PRD with insights
3. Conduct more interviews (recommended: 5-8 total)
4. Run usability test: /vt-c-kw-user-test usability
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Mode 3: Usability Test Design

Invocation

/vt-c-kw-user-test usability

Execution Instructions

Step 1: Load Prototype Context

  1. Scan 04-prototyp/ for available screens
  2. Read PRD for key user journeys
  3. Identify critical tasks to test
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Usability Test Designer
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Prototype: 04-prototyp/
PRD: 03-PRD/PRD.md

Detected Screens:
─────────────────────────────────────────────────────────────────
1. /login - Login page
2. /dashboard - Main dashboard
3. /profile - Profile management
4. [other screens...]

Select user journeys to test:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 2: Define Test Parameters

Ask user for: - Target number of participants (recommended: 5) - Test duration per session - Key tasks to test - Success metrics

Step 3: Generate Usability Test Plan

# Usability Test Plan: [Project Name]

## Test Overview
- **Prototype URL**: [URL or local path]
- **Test Duration**: [X] minutes per participant
- **Participants**: [N] target
- **Test Period**: [dates]

---

## Research Questions

1. Can users complete [key task] successfully?
2. Where do users struggle in [workflow]?
3. How intuitive is [feature]?
4. What improvements would increase satisfaction?

---

## Participant Recruitment

### Screener Criteria
- [Criterion 1]: [requirement]
- [Criterion 2]: [requirement]
- [Criterion 3]: [requirement]

### Disqualification Criteria
- [Criterion]: [reason]

### Sample Screener Questions
1. [Question about role/experience]
2. [Question about relevant behavior]
3. [Question about tools used]

---

## Test Tasks

### Task 1: [Task Name]
**Scenario**: "[Narrative setting the context]"

**Instructions to Participant**:
> "Using this prototype, please [specific task]. Think aloud as you
> work through it."

**Success Criteria**:
- [ ] Completed without assistance
- [ ] Completed with minor assistance
- [ ] Required significant assistance
- [ ] Unable to complete

**Metrics**:
- Time to complete: [target]
- Error count: [expected max]
- Satisfaction rating: [scale]

**Observation Points**:
- [ ] Did they find the starting point?
- [ ] Did they understand the labels?
- [ ] Did they hesitate anywhere?
- [ ] Did they use expected path?

### Task 2: [Task Name]
[Same structure]

### Task 3: [Task Name]
[Same structure]

---

## Moderator Script

### Introduction (5 minutes)
> "Thank you for participating today. We're testing a prototype of
> [product], not testing you. There are no wrong answers - we want
> to learn what works and what doesn't.
>
> I'll ask you to complete some tasks using this prototype. Please
> think aloud as you work - tell me what you're looking for, what
> you expect to happen, and any confusion you experience.
>
> The prototype has limited functionality, so some things won't
> work. Just tell me what you'd expect to happen.
>
> Do you have any questions before we begin?"

### Task Transitions
> "Great, thank you. Now let's move on to the next task..."

### Probing Questions
- "What were you looking for there?"
- "What did you expect to happen?"
- "What would you do next in real life?"
- "How did that compare to what you expected?"

### Closing (5 minutes)
> "Thank you! Before we finish:
> - Overall, how would you rate this experience? (1-5)
> - What was most confusing?
> - What was most useful?
> - Any other feedback?"

---

## Observation Template

### Participant: [ID]
**Date**: [date]
**Duration**: [actual time]

#### Task Completion

| Task | Complete? | Time | Errors | Notes |
|------|-----------|------|--------|-------|
| Task 1 | Y/N | [mm:ss] | [count] | [notes] |
| Task 2 | Y/N | [mm:ss] | [count] | [notes] |
| Task 3 | Y/N | [mm:ss] | [count] | [notes] |

#### Key Observations
- [Observation 1]
- [Observation 2]

#### Notable Quotes
> "[Quote]" - [context]

#### Satisfaction Ratings
- Overall: [1-5]
- Ease of use: [1-5]
- Would recommend: [1-5]

---

## Analysis Framework

### Quantitative Metrics
| Metric | Target | Actual (avg) | Notes |
|--------|--------|--------------|-------|
| Task 1 completion rate | 90% | [%] | |
| Task 1 avg time | [sec] | [sec] | |
| Overall satisfaction | 4.0+ | [score] | |

### Issue Severity Rating
- **Critical**: Prevents task completion
- **Major**: Significant delay or confusion
- **Minor**: Noticed but didn't impede progress
- **Cosmetic**: Aesthetic or preference issue

### Issue Tracking Template
| Issue | Severity | Frequency | Task | Recommendation |
|-------|----------|-----------|------|----------------|
| [Issue] | [level] | [N/5 users] | [task] | [fix] |

---

## Deliverables

After testing complete:
1. [ ] Findings summary report
2. [ ] Issue list with severity ratings
3. [ ] Recommendations for prototype updates
4. [ ] Video highlights (if recorded)
5. [ ] Updated PRD requirements (if needed)

Step 4: Save and Display Summary

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Usability Test Plan Created
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

File: 02-Knowledge/04-Dokumente/usability-test-plan-[date].md

Test Summary:
─────────────────────────────────────────────────────────────────
• Tasks: N defined
• Duration: X minutes per session
• Participants needed: Y
• Key metrics defined: Z

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NEXT STEPS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Recruit participants using screener criteria
2. Deploy prototype: /vt-c-kw-prototype --deploy
3. Conduct test sessions
4. Analyze results and update prototype
5. Update PRD with validated requirements
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Integration with Research Agents

The skill delegates to specialized agents: - /vt-c-kw-user-test script → interview-script-writer agent - /vt-c-kw-user-test analyze → interview-analyzer agent - /vt-c-kw-user-test usability → usability-test-designer agent

Output Files

All outputs are saved to 02-Knowledge/04-Dokumente/: - interview-script-YYYY-MM-DD.md - interview-analysis-YYYY-MM-DD.md - usability-test-plan-YYYY-MM-DD.md