Unit - II User Requirements and its Analysis
2.2 2.1 Introduction to research and analysis tool (freeware) such as FigJam:-
FigJam – A Research & Analysis Tool (Freeware)
What is FigJam?
FigJam is an online collaborative whiteboard tool by Figma, mainly used during the research and
ideation phase of UI/UX design.
It is widely used for:
Brainstorming and ideation
User research analysis
Requirement gathering
Team collaboration
Templates and plugins
Visual mapping for research
- Flowchart
- Diagrams
Import and integration
## How FigJam Supports Research and Analysis (Deep Explanation)
FigJam is not just a whiteboard — it is research thinking tool.
It supports every critical step of UX research and analysis, from raw data collection to structured
insights.
Below is a clear, deep, exam-ready explanation.
Why FigJam is Powerful for Research & Analysis
Aspect How FigJam Helps
Data Collection Sticky notes, free text
Data Organization Affinity mapping
Pattern Discovery Visual clustering
User Understanding Personas, journeys
Team Alignment Real-time collaboration
Decision Making Voting & prioritization
Aspect How FigJam Helps
2.2 User Requirements :-
Defination:-
User requirements define the specific needs, preferences, and expectations that users have from a
system product, or service. They are essential to ensure the final design aligns with the actual needs
of its users, improving satisfaction and functionality.
Types of User Research
User research is classified based on purpose, data type, and research stage.
Below is a clear, exam-oriented explanation suitable for teaching.
1. Qualitative User Research
Focuses on understanding user behaviour, feelings, motivations, and problems.
🔹 Answers: Why users behave in a certain way
Methods:
User interviews
Observation
Contextual inquiry
Focus groups
Example:
Asking users why they find an app confusing.
📌 Data is descriptive, not numerical.
2. 2. Quantitative Research
Definition: - Involves gathering numerical data that can be measured and statistically analysed. It is
useful for identifying trends and patterns across a larger user base specific need.
Purpose: To validate about user behaviour and preferences and to measure the extent of
Common Techniques:
Surveys and Questionnaires: Structured questions to gather data from a large sample, providing
insights into user preferences and satisfaction levels.
Analytics and Metrics: Tracking data on how users interact with the system (e.g., click rates, time
spent on tasks) to identify usage patterns and common challenges.
Difference Between Qualitative & Quantitative Research
Qualitative Research Quantitative Research
Focus on why Focus on how many
Descriptive data Numerical data
Small user group Large user group
Interviews, observation Surveys, questionnaires
2. Tools to Collect User Requirements
User requirements are collected using direct and indirect methods.
A. Personal Observation
Definition
Observing users while they perform tasks without interrupting them.
Purpose
Understand real user behavior
Identify difficulties users don’t mention
Example
Watching users struggle to find a button.
📌 Very effective for behavioral research.
B. Interviews
Definition
Direct conversation with users to understand their needs, expectations, and problems.
Types
Structured interviews
Semi-structured interviews
Unstructured interviews
Advantages
Deep insights
Clarification possible
Rich qualitative data
📌 Best for qualitative research.
C. Questionnaire
Definition
A set of written questions answered by users.
Purpose
Collect data from many users
Get measurable responses
Examples
Yes/No questions
Multiple choice
Rating scales
📌 Best for quantitative research.
D. User Reviews
Definition
Feedback given by actual users based on real usage.
Sources
App reviews
Feedback forms
Support tickets
Benefits
Real problems
Honest opinions
📌 Shows real-world issues.
E. Expert Reviews
Definition
Evaluation done by domain experts or UX experts.
Purpose
Identify usability problems
Ensure standards and best practices
Examples
Heuristic evaluation
UI/UX audit
📌 Faster than user testing, but based on expert knowledge.
Summary Table (Exam-Friendly)
Tool Type of Research Purpose
Personal Observation Qualitative Study real behavior
Interviews Qualitative Understand user needs
Questionnaire Quantitative Collect numeric data
User Reviews Qualitative Identify real issues
Expert Reviews Qualitative Usability evaluatio
2.3 User Requirement Analysis
User Requirement Analysis is the process of studying, organizing, and interpreting user data to
clearly understand who the users are, what they need, and what problems must be solved before
designing a product.
It ensures the product is user-centered, competitive, and aligned with client goals.
1. Understanding Target Audience and Client Requirements
A. Understanding Target Audience
Definition
Target audience refers to the specific group of users for whom the product is being designed.
Why it is important
Different users have different needs
Helps design suitable features and UI
Improves usability and satisfaction
Factors to Analyze
Age group
Education level
Technical knowledge
User goals
User problems (pain points)
Example:
A banking app for senior citizens must have large text and simple navigation.
B. Understanding Client Requirements
Definition
Client requirements are the business goals and expectations provided by the client or stakeholder.
Examples
Increase sales
Improve customer retention
Reduce support calls
Launch product within budget
📌 A good product balances user needs + client goals.
2. Competitive Analysis
Definition
Competitive analysis is the process of studying competitor products to understand their strengths,
weaknesses, features, and UX patterns.
Purpose
Identify market standards
Learn what works and what fails
Avoid repeating competitors’ mistakes
Find opportunities for improvement
What is Analyzed
Features
User interface
User experience
Pricing
User reviews
Example:
Comparing Swiggy vs Zomato to understand food delivery UX.
📌 Helps create a better and unique product.
Competitors Studied
Instagram
ShareChat
Moj
Findings
App Strength Weakness
Instagram High quality UI High data usage
ShareChat Strong local language UI looks crowded
Moj Easy short videos Limited community features
3. Affinity Mapping
Definition
Affinity mapping is a technique used to group similar user research data to identify patterns and
common problems.
Process
1. Write user feedback on sticky notes
2. Group similar feedback together
3. Name each group (theme)
Purpose
Convert raw data into meaningful insights
Identify major user pain points
Support decision making
Example Groups
Navigation issues
Payment problems
Performance issues
📌 Commonly done using tools like FigJam or Miro.
Example
3. Affinity Mapping (From User Research)
Collected User Feedback
“Videos take too much data”
“English language is confusing”
“Too many buttons on screen”
“App becomes slow on my phone”
Affinity Groups
Group Name Feedback
App slow, high data
Performance Issues
usage
Need regional
Language Issues
languages
UI Complexity Too many buttons
Hard to find local
Content Discovery
content
Step 1: Raw User Research Data (Sticky Notes)
Each statement is written on one sticky note.
“App consumes too much mobile data”
“Videos load very slowly on my phone”
“English language is difficult to understand”
“I want Marathi language option”
“Too many buttons on the home screen”
“App feels confusing for first-time users”
“Phone hangs when using the app”
👉 At this stage, data is unstructured and messy.
Group Name Feedback
Step 2: Grouping Similar Data (Affinity Mapping)
Now, we group similar feedback together.
Group 1: Performance & Data Issues
App consumes too much mobile data
Videos load slowly
Phone hangs while using the app
Group 2: Language Issues
English language is difficult
Need Marathi language option
Group 3: UI & Usability Issues
Too many buttons on home screen
App is confusing for first-time users
Step 3: Naming the Groups (Themes)
Each group is given a clear name.
Group Name Identified Problem
Performance Issues Slow app, high data usage
Language Problems Need regional languages
Usability Issues Complex UI
Step 4: Insights from Affinity Mapping
After grouping, we identify patterns:
Most users face performance problems
Regional language support is critical
UI is too complex for new users
📌 These insights directly guide design decisions.
Group Name Feedback
Final Outcome (Requirements Derived)
Insight Requirement
High data usage Low-data mode
Language difficulty Marathi/Hindi options
Complex UI Simple, minimal layout
One-Line Exam Answer
Affinity mapping groups similar user feedback to identify patterns, major
issues, and user requirements.
4. Defining User Persona
Definition
A user persona is a fictional representation of a real user, created using research data.
Purpose
Keep design user-focused
Avoid designing for assumptions
Help team understand user behavior
Attributes of user Persona
Name & photo (fictional)
Age & occupation
Goals
Frustrations
Technical skills
Example:
Ramesh, 45, shop owner, wants fast and simple digital payments.
📌 Personas guide design decisions throughout the project.
Relationship Between These Activities
Step Purpose
Target audience analysis Know who the users are
Client requirements Understand business goals
Competitive analysis Study market & competitors
Affinity mapping Organize research insights
User persona Represent real users
One-Line Exam Answers
User Requirement Analysis:
It is the process of understanding user needs and analyzing research data to define clear
product requirements.
Competitive Analysis:
Study of competitor products to identify strengths, weaknesses, and opportunities.
Affinity Mapping:
Technique of grouping similar user research data to identify patterns.
User Persona:
A fictional user profile created from research to represent target users.