Before selecting collection methods, understand what type of data you need:

- Likert scale ratings (1-5 satisfaction scores)

- Yes/No responses

- Task completion times

- Error counts

- Success/failure rates

- User opinions and experiences

- Explanations of problems encountered

- Suggestions for improvements

- Behavioral observations

**Purpose**: Collect standardised, quantifiable feedback from multiple testers simultaneously

**When to Use**: When you need measurable data to compare across users and identify trends

**Types of Questions**:

- _Rating Scale_: "Rate the user interface design: Very Poor (1) to Excellent (5)"

- _Multiple Choice_: "Which feature was most difficult to use? A) Login process B) Main navigation C) Search function D) Settings menu"

- _Yes/No_: "Were you able to complete the task without assistance?"

- _Experience-based_: "Describe any moment when the interface caused you to pause or feel uncertain"

- _Problem-focused_: "What was the most challenging aspect of using this software?"

- _Improvement-focused_: "What changes would make this software easier to use?"

**Advantages**: Efficient for large groups, standardized responses, easy to analyze statistically

**Best For**: Measuring satisfaction, ease of use, feature preferences

---

**Purpose**: Record actual user behavior without relying on self-reported data

**When to Use**: When you need objective evidence of how users actually interact with your software

**Observation Techniques**:

- **Screen recording** during testing sessions

- **Task completion monitoring** (time-on-task measurements)

- **Error frequency tracking** and navigation patterns

- **Behavioral notes** (hesitation, confusion, workarounds)

**Example Observation Tasks**:

- Record how long it takes users to complete core workflows

- Observe navigation patterns and identify common user pathways

- Note frequency and types of errors made during typical tasks

- Document where users pause or show confusion

**Advantages**: Objective data, reveals actual vs. reported behavior, identifies usability issues

**Best For**: Workflow efficiency, interface design problems, actual vs. perceived performance

---

**Purpose**: Explore the "why" behind user behaviors and gather detailed feedback

**When to Use**: When you need to understand user motivations, clarify survey responses, or explore unexpected findings

**Interview Structure**:

- "Walk me through how you typically use this software"

- "What was your initial reaction to the main interface?"

- "Describe your experience with the most important features"

- "Can you tell me more about that challenge?"

- "How did that make you feel as a user?"

- "What would have made that process easier?"

- "Why do you think that happened?"

**Advantages**: Rich detailed feedback, clarifies confusing survey responses, uncovers unexpected issues

**Best For**: Understanding user emotions, complex workflows, training and support needs

---

**Purpose**: Systematically compile and analyse all collected data into actionable insights

**When to Use**: To synthesise findings from multiple methods and present recommendations

**Key Components**: Combine quantitative data (scores, statistics) with qualitative insights (themes, quotes) to create comprehensive findings and prioritized recommendations.

**Advantages**: Provides comprehensive overview, supports decision-making, documents test outcomes

**Best For**: Final assessment, stakeholder communication, future development planning

**For Closed Survey Questions**:

- Calculate average scores and percentages

- Create charts showing satisfaction trends

- Identify lowest-scoring areas for improvement focus

**For Open Survey Responses and Interview Data**:

- Use thematic analysis to identify common issues

- Code responses into categories (usability, functionality, performance)

- Extract representative quotes for reporting

**For Observation Data**:

- Compile task completion statistics

- Map common error patterns

- Document workflow efficiency metrics

**Best Practice**: Use multiple methods to triangulate findings

**Recommended Combination Approach**:

1. **Survey** to measure overall satisfaction and identify problem areas

2. **Observation** to objectively measure task performance in those problem areas

3. **Interview** to understand why those problems occur and how users work around them

4. **Report** to synthesize quantitative metrics with qualitative insights

This approach ensures you capture both the "what" (quantitative metrics) and the "why" (qualitative insights) of user experience.

---