<aside> ðĄ Project Title: Start Date: Target End Date: Project Members:
| Role | Email Address | Phone Number | |
|---|---|---|---|
| ðĐâð | UX Research Lead (Moderator) | [email protected] | (123) 456-7890 |
| ðĐðŧ | User Researcher (Notetaker) | [email protected] | (456) 789-0123 |
| ð§ | UX Designer | [email protected] | (789) 012-3456 |
| </aside> |
<aside> ð Objectives: State the overarching goal of the usability test, what you aim to achieve, and what insights you hope to gain.
Here are sample objectives you can check out
</aside>
<aside> ðĨ Methodology *State the overarching goal of the usability test, what you aim to achieve, and what insights you hope to gain.
Here are some of the most common methodologies:
Moderated Usability Testing*
| Description | Participants interact with the product while a moderator observes and asks questions. Can be conducted in-person or remotely, offering real-time feedback. |
|---|---|
| Sample Goals and Tasks | - Evaluate the ease of onboarding process - Complete the registration process - Find and add an item to the shopping cart |
| Sample Materials Needed | - Prototype or live product - Recording equipment (camera, screen recording) - Task scenarios - Consent forms |
| Enhanced Metrics to Measure | - Task completion time - Success rate - Error rate - User satisfaction (e.g., SUS Score) - Critical issues identified - Heatmaps of user interactions |
| Notes | Ensure participants understand the think-aloud process |
Unmoderated Usability Testing
| Description | Participants perform tasks and provide feedback independently, often using pre-recorded test scenarios. Offers scalability but lacks real-time interaction. |
|---|---|
| Sample Goals and Tasks | - Assess the navigation and menu structure - Find contact information on the website - Share a product on social media |
| Sample Materials Needed | - Usability testing tool (e.g., UserTesting) - Task scenarios - User demographics survey - Post-test survey |
| Enhanced Metrics to Measure | - Task completion time - Success rate - Usability issues reported - Heatmaps of user interactions |
| Notes | Set clear instructions for participants |
| </aside> |
<aside> ðĪš Participants:
Define the characteristics of the participants you want to recruit (e.g., age, gender, experience level, etc.). Consider diversity to get a well-rounded perspective.
Here's a sample recruitment criteria table**:
| Demographic Criteria | Requirements | Priority |
|---|---|---|
| Location | City/Area | Mandatory |
| Age Range | 20-50 (various age range) | Mandatory |
| Educational Background | Various educational backgrounds (not just university graduates) | Mandatory |
| Gender | Any (female/male is okay) | Nice to have |
| Language Proficiency | Fluent in English | Mandatory |
| Research Criteria | Requirements | Priority |
|---|---|---|
| Decision-Maker | Must be proficient in using software XYZ | Mandatory |
| Technology Adoption | Demonstrated expertise in programming languages A and B | Mandatory |
| Customer Interaction | Should have a history of adopting emerging technologies | Mandatory |
| Financial Authority | Access to substantial financial resources | Nice to have |
| Market Knowledge | Familiarity with industry-specific tech trends | Nice to have |
**The first table talks about the general demographics of the participants. The latter, on the other hand, talks about research-specific criteria. Both are necessary information.
</aside>
<aside> ã°ïļ Project Timeline
To create an effective project timeline, start by defining clear objectives and breaking tasks into manageable steps. Consider available resources, including personnel and materials, and allocate them appropriately. Prioritize tasks based on their impact and dependencies.
Include buffer time for unexpected delays, monitor the critical path closely, and communicate openly with the team and stakeholders. Regularly assess resource availability and adapt the timeline as needed to optimize project management and ensure successful delivery.
Here's a sample 10-day research project timeline
</aside>
â Click through the different database tabs to create and see other views.
Conduct a retrospective meeting with your team. This meeting focuses on reviewing what went well (positives) and what could be improved (negatives) in a project or process.
Successes:
Challenges: