Unit -V

What Is a Problem Statement in UI/UX?

• A problem statement describes a user’s pain
point or challenge that your product or design
is trying to solve.
• A Good Problem Statement Should:
• Focus on the user, not the business alone
• Be based on research, not assumptions
• Highlight the impact of the problem
• Be specific, not vague or too broad
 Steps to Identify and Write One
• 1. Gather User Insights
• Use research methods like:
• Interviews
• Surveys
• Usability testing
• Analytics
• 2. Define the User & Context
• Who’s experiencing the problem?
What’s the context (device, environment, task,
etc.)?
• 3. Describe the Problem Clearly
• Focus on:
• What the user is trying to do
• What’s preventing them from doing it
• Why this matters to them
• 4. Write the Statement
• Use the formula, or try alternatives like:
• Our [type of user] struggles with [problem]
when [context], which causes [consequence].
 Identifying Appropriate Research Methods

• Define Your Goal First

• Understand user needs or behaviors?
• Evaluate an existing design or prototype?
• Explore new design directions?
• Validate a design decision?
 Common UI/UX Research Methods by
Design Phase
• Discovery Phase (Understanding Users & Context)
• Goal: Learn user needs, pain points, and behaviors
• User Interviews – In-depth, qualitative data from users
• Surveys/Questionnaires – Quick way to gather
quantitative data
• Contextual Inquiry – Observe users in their
environment
• Diary Studies – Understand long-term user behavior
• Ideation & Design Phase
• Goal: Test concepts and get early feedback
• Card Sorting – Helps structure navigation or
content
• Tree Testing – Tests information architecture
• Wireframe Testing – Get feedback on low-
fidelity designs
• Focus Groups – Explore opinions or preferences
• Testing & Validation Phase
• Goal: Validate usability and experience
• Usability Testing – Identify usability issues in designs
• A/B Testing – Compare two versions to see which
performs better
• Heatmaps & Analytics – Understand user
interactions and drop-offs
• First-click Testing – Test where users would click first
to complete a task
• Quantitative vs Qualitative Methods
• Quantitative: Numbers, trends (e.g., surveys,
A/B testing, analytics)
• Qualitative: Deeper insights, reasons behind
behaviors (e.g., interviews, usability testing)
 Creating Personas

• Step-by-Step: How to Create Personas

• 1. Conduct User Research
• Collect data through:
• User interviews
• Surveys
• Analytics
• Customer support feedback
• Observation/field studies
• 2. Identify Key Patterns
• Group users by:
• Goals/motivations
• Behavior patterns
• Demographics (age, job role, tech savviness,
etc.)
• Needs and pain points
• Environment/context of use
• 4. Validate (If Possible)
• Share with stakeholders and, if feasible, test
with real users to make sure personas feel
realistic and representative.
• 👥 Example Persona
• Name: Sarah, "The Multitasking Manager"
Age: 34
Job: Project Manager at a tech startup
Tech Comfort: High
Goals:
• Keep team tasks organized
• Track project progress quickly
Pain Points:
• Hates cluttered dashboards
• Gets overwhelmed with notifications
 Solution Ideation

• What Is Solution Ideation?

• A process of brainstorming and exploring
potential design solutions based on user
needs, goals, and pain points. It focuses on
quantity first, then quality.
• Solution Ideation Process (Step-by-Step)
• 1. Define the Problem Clearly
• Use a concise problem statement or How
Might We (HMW) question.
• 2. Gather Insights
• Review key user needs, personas, and journey
maps. Keep the user front and center.
• 4. Sketch & Explore Concepts
• Low-fidelity sketches or wireframes help
visualize ideas fast.
• 5. Group & Prioritize Ideas
• Use methods like:
• Affinity Diagrams – Group similar ideas
together
• Impact/Effort Matrix – Prioritize based on value
and feasibility
• 6. Select Ideas to Prototype
• Choose the most promising ideas to turn into
wireframes or prototypes for usability testing.
 Creating User Stories

• What Is a User Story?

• A user story captures who the user is, what
they want to do, and why they want to do it —
all in one sentence.
• What Are User Stories?
• A user story captures a feature or function from
the user’s point of view, usually in this format:
• As a [type of user], I want to [do something] so
that [goal].
• Example:
• As a project manager, I want to assign tasks to
team members so that I can track
responsibilities.
• How to Create User Stories
• 1. Start with User Research
• Use your:
• Personas
• User interviews
• Journey maps
• Observed behaviors and needs
• 2. Identify Key User Goals
• What is the user trying to accomplish with
your product? List out the core tasks and
motivations.
• 3. Use the Story Format
• Stick to the format to ensure clarity:
• As a [user role],
• I want to [action],
• So that [goal/benefit].
• 4. Group by Features or Functions
• Group stories around features, e.g. search,
account management, task creation, etc.
 Creating Scenarios

• What Is a UX Scenario?
• A scenario is a short narrative that describes:
• A specific user (based on your persona)
• Their goal
• The context or situation
• The steps they take to achieve that goal using
your product
• Structure of a UX Scenario
• Persona: Who is the user? (e.g., Sarah, the
multitasking manager)
• Goal: What does the user want to achieve?
• Context: Where and when is this happening?
• Interaction: How does the user engage with
your product?
• Example UX Scenario
• Persona: Sarah, the multitasking manager
Scenario: Sarah is preparing for her team’s morning stand-up. She’s
commuting and wants to quickly check what tasks are pending.
• Story:
• Sarah opens the project management app on her phone while
waiting for coffee. She taps into the dashboard to view today’s
tasks. The UI clearly separates overdue, current, and upcoming
items. She quickly checks off two completed items and adds a note
for her team. All within 2 minutes, without needing her laptop.
• Goal: Stay updated and productive on the go
Context: On mobile, limited time, in a real-world setting (coffee
shop)
• Why Scenarios Are Useful
• Connect features with real-life use
• Expose gaps in the user flow
• Fuel ideation and prototyping
• Aid stakeholder communication
• Guide test scripts for usability testing
 Flow Diagrams

• What Are Flow Diagrams in UI/UX?

• A flow diagram shows:
• Screens/pages the user visits
• Actions the user can take (click, tap, submit,
etc.)
• Decision points (if/else logic)
• Outcomes or end states
• When to Use Flow Diagrams
• During early planning & ideation
• Before wireframing or prototyping
• To explain the experience to stakeholders or
developers
• To identify pain points or unnecessary steps
 Example Flow: Sign-Up Process
• [Start]
• ↓
• [Open App]
• ↓
• [Click 'Sign Up']
• ↓
• [Enter Email & Password]
• ↓
• <Is email valid?>
• ↙ ↘
• [Error] [Continue]
• ↓
• [Verify Email]
• ↓
• [End]
 Flow Mapping

• What Is Flow Mapping in UI/UX?

• Flow mapping is the process of outlining:
• Entry points (where users start)
• Actions (clicks, scrolls, form inputs)
• Decisions (yes/no, if/else)
• Pathways (what happens next)
• Outcomes (goal achieved, error, exit, etc.)
• Why Use Flow Mapping?
• Clarify complex processes (e.g., onboarding,
checkout)
• Spot dead ends, redundancies, or UX friction
• Align teams on how a feature should behave
• Improve usability by streamlining flows
 Example: Flow Map for E-commerce Checkout
css
CopyEdit

• [Start: Cart Page]

• ↓
• [Click "Checkout"]
• ↓
• [Enter Shipping Info]
• ↓
• [Enter Payment Info]
• ↓
• <Is payment valid?>
• ↙ ↘
• [Error] [Order Review]
• ↓
• [Confirm Order]
• ↓
• [Thank You Page]
• ↓
• [End]
 Information Architecture

• What Is Information Architecture in UI/UX?

• Information Architecture is:
• The practice of organizing content in a logical, user-
friendly way to support usability and findability.
• It answers questions like:
• What content do users need?
• Where should that content live?
• How should it be grouped or categorized?
• How do users move between content?
• Core Elements of IA
• Organization Systems
How information is grouped (e.g., by topic, task,
audience)
• Labeling Systems
What things are called (e.g., “Support” vs. “Help”)
• Navigation Systems
How users move around (e.g., menus, breadcrumbs)
• Search Systems
How users find content directly (e.g., site search, filters)
• IA Design Process
• User Research: Understand user needs & behaviors
• Content Inventory: Audit existing content
• Card Sorting: Let users organize content into
categories
• Sitemap Creation: Visualize content structure
• Navigation Design: Design how users access content
• Usability Testing: Validate structure with real users
 Example Sitemap (for a SaaS Dashboard)
• Home
• ├── Dashboard
• ├── Projects
• │ ├── Active
• │ ├── Archived
• ├── Reports
• │ ├── Usage
• │ ├── Billing
• ├── Settings
• │ ├── Profile
• │ ├── Notifications
• │ ├── Security
THANK YOU