Answer to the question no.
1. What is Usability Testing?
Usability testing is a method used in user experience (UX) research to evaluate how easy
and intuitive a product (website, software, or app) is for real users. It involves observing
participants as they interact with the product to identify:
● Ease of use (Can users complete tasks without confusion?)
● Efficiency (How quickly can they perform tasks?)
● Learnability (How easily can new users understand the interface?)
● Errors & Frustrations (Where do users struggle or make mistakes?)
● User Satisfaction (Do they find the experience pleasant?)
The goal is to detect usability issues before launch and improve the product based on real
user feedback.
2. How Usability Testing is Applied to a Product (Website/Software)
● Planning: Define the goals, target users, and key tasks to be tested. Choose the
type of usability testing ( example: remote, in-person, etc.).
● Recruiting Participants: Select representative users from the target audience of the
website or software.
● Test Execution: Ask users to perform common tasks (example: sign up, purchase,
search) while observing their actions, collecting feedback, and noting any difficulties
or confusion.
● Data Collection: Collect both qualitative feedback (example: frustration, confusion)
and quantitative data (example: time on task, success rate, error rate).
● Analysis & Reporting: Analyze the results to identify patterns and usability issues.
Create a report with recommendations for improving the product.
● Iteration: Apply changes based on findings and retest to ensure improvements
address the issues effectively.
Answer to the question no. 2
Usability Test Report for Figma
1. Executive Summary
This report evaluates the usability of Figma, a collaborative design and prototyping tool,
based on feedback from [X] participants. The test focused on key features such as the
interface, collaboration tools, prototyping, and performance.
Usable Features:
1. Intuitive drag-and-drop interface
2. Real-time collaboration
3. Robust prototyping capabilities
4. Easy sharing and commenting
Areas Needing Improvement:
1. Steep learning curve for beginners
2. Performance lag with large files
3. Limited offline functionality
4. Confusing layer management in complex projects
2. Usability Findings
Usable Features
1. Intuitive Drag-and-Drop Interface
● Participants found the toolbar and design elements easy to locate.
● Shapes, text, and basic interactions were straightforward.
2. Real-Time Collaboration
● Users praised the seamless multiplayer editing.
● Comments and mentions improved team communication.
3. Prototyping & Interactive Elements
● Linking frames and adding transitions was smooth.
● Preview mode helped validate interactions quickly.
4. Easy Sharing & Permissions
● Generating shareable links was simple.
● Role-based access (Viewer, Editor) was clear.
Non-Usable or Problematic Features
1. Steep Learning Curve for Beginners
● New users struggled with advanced features (Auto Layout, Components).
● Suggested improvement: Interactive tutorials or guided walkthroughs.
2. Performance Issues with Large Files
● Lag experienced when working with high-fidelity prototypes.
● Suggested improvement: Optimize rendering for complex projects.
3. Limited Offline Functionality
● Users were frustrated by inability to edit offline.
● Suggested improvement: Basic offline mode with sync-on-reconnect.
4. Confusing Layer Management
● Nested layers were hard to track in deep hierarchies.
● Suggested improvement: Better layer grouping/search functionality.
3. Recommendations for Improvement
Issue Suggested Fix
1. Learning Curve 1. Add interactive onboarding tutorials
2. Performance Lag 2. Optimize file handling for large projects
3. Offline Mode Introduce 3. Introduce limited offline editing
4. Layer Management 4. Improve nesting visibility & search
4. Conclusion
Figma excels in collaboration and prototyping but has room for improvement in accessibility
for beginners and performance optimization. Addressing these issues will enhance usability
for a broader range of users.
Answer to the question no. 3
User Story:
A user story is a simple, informal description of a software feature from the perspective of an
end user. For example:
"As a [type of user], I want [an action] so that [a benefit/value]."
User stories help Agile teams focus on delivering value to users rather than just technical
requirements.
Acceptance Criteria:
Acceptance criteria (AC) are conditions that a user story must meet to be considered
complete. They define the boundaries of the story and help testers verify functionality.
Example:
1. Given a user is logged in,
2. When they click the "Logout" button,
3. Then they should be redirected to the login page.
Three Key Elements of a User Story
1. Role (Who) – The user or stakeholder (example: "As a customer").
2. Action (What) – The task or feature (example: "I want to filter products by price").
3. Benefit (Why) – The value or outcome (example: "so that I can find affordable items
quickly").
1. User Story Mapping
User Story Breakdown
Role Action Benefit
As a customer I want to save items so I can purchase them later
to a wishlist
2. Flow Chart (User Story & Acceptance Criteria)
3. Graph (User Story Components)
Key Elements of a User Story
Key Elements of a User Story
Key Elements of a User StoryKey Elements of a User Story
Answer to the question no. 4
Amazon is a leading e-commerce platform with multiple user roles (customers, sellers,
admins). Below are some key user stories identified on the website.
1. User Stories for Customers
User Story Acceptance Criteria
1. As a customer, I want to search for 1. Given I am on the homepage, when I
products so that I can find what I need type a keyword and press "Search," then
quickly. relevant products should appear.
2. As a customer, I want to add items to my 2. Given I view a product, when I click "Add
cart so that I can purchase them later. to Cart," then the item should appear in my
cart.
3. As a customer, I want to apply filters so 3. Given I search for "laptops," when I filter
that I can narrow down search results. by "Brand: Dell," then only Dell laptops
should appear.
2. User Stories for Sellers
User Story Acceptance Criteria
1. As a seller, I want to list a new product so 1. Given I am in Seller Central, when I fill in
that customers can buy it. product details and click "Publish," then the
product should appear in search results.
2. As a seller, I want to track orders so that I 2. Given I am logged in as a seller, when I
can fulfill them on time. check "Orders," then I should see pending
shipments.
3. As a seller, I want to update product 3. Given I edit a product listing, when I
pricing so that I can stay competitive. change the price and save, then the new
price should reflect on the product page.
3. User Stories for Admins
User Story Acceptance Criteria
1. As an admin, I want to remove fraudulent 1. Given I detect a fake product, when I
listings so that customers are protected. click "Remove Listing," then it should
disappear from search results.
2. As an admin, I want to monitor customer 2. Given I access the support dashboard,
complaints so that I can improve service. when I view unresolved tickets, then I can
assign them to agents.
