> ## Documentation Index
> Fetch the complete documentation index at: https://docs.figr.design/llms.txt
> Use this file to discover all available pages before exploring further.
# Process User Data
> Transform raw user research and analytics into actionable design insights and requirements.
# Process User Data
Turn user research, analytics, and behavioral data into clear design direction. Figr helps you extract meaningful insights from complex data sources and translate them into specific design requirements.
**Data-driven ideation:** Move beyond assumptions to design solutions grounded in real user behavior and validated insights.
## Data Sources & Input
**Quantitative user behavior:**
* Page views and user flows
* Feature adoption rates
* Conversion funnel analysis
* Time on page metrics
* Bounce rate patterns
* Load time impacts
* Error rate tracking
* Device and browser usage
* Geographic user distribution
* Peak usage patterns
**Qualitative insights:**
```yaml theme={null}
Research types:
✅ User interviews and surveys
✅ Usability testing sessions
✅ Card sorting exercises
✅ Customer support tickets
✅ Feedback and reviews
✅ Social media mentions
✅ Competitive user research
```
**User interaction patterns:**
```yaml theme={null}
Click and attention patterns:
- Where users focus attention
- Most clicked elements
- Ignored interface areas
- Scroll depth analysis
- Mobile vs desktop differences
```
```yaml theme={null}
User journey insights:
- Common task patterns
- Points of confusion
- Error recovery behavior
- Feature discovery paths
- Abandonment triggers
```
## Data Processing Pipeline
**Import and organize data sources:**
**Supported formats:**
```yaml theme={null}
Analytics: CSV exports, API connections
Research: PDF reports, video transcripts
Feedback: Support ticket exports, survey data
Behavioral: Heat map data, session recordings
```
**Identify significant insights:**
```yaml theme={null}
AI-powered insights:
- Anomaly detection in user behavior
- Correlation identification
- Trend analysis over time
- Segmentation opportunities
- Priority issue highlighting
```
```yaml theme={null}
Manual investigation:
- Hypothesis testing
- Specific metric drilling
- Cross-reference data sources
- Custom segmentation
- Comparative analysis
```
**Transform data into design requirements:**
```yaml theme={null}
Output examples:
Data: "Mobile users abandon checkout at shipping step"
Insight: "Shipping costs surprise mobile users"
Design requirement: "Show shipping estimate earlier in flow"
Data: "Help section has 40% bounce rate"
Insight: "Users can't find relevant help content"
Design requirement: "Implement contextual help system"
```
## Insight Categories
**How users actually interact:**
```yaml theme={null}
Common patterns:
- Preferred menu structures
- Search vs browse behavior
- Back button usage patterns
- Deep linking preferences
- Cross-platform consistency needs
```
```yaml theme={null}
User approaches:
- Linear vs exploratory workflows
- Information gathering patterns
- Decision-making processes
- Error recovery methods
- Help-seeking behavior
```
**Obstacles to user success:**
* Confusing navigation
* Unclear labeling
* Visual hierarchy problems
* Interactive element confusion
* Overly complex workflows
* Missing functionality
* Performance bottlenecks
* Information gaps
**What works well for users:**
```yaml theme={null}
Positive patterns:
- High-converting interface elements
- Successful user flow segments
- Well-adopted features
- Positive feedback themes
- Efficient task completion paths
```
## Design Requirement Generation
**Rank insights by impact:**
**Evaluation criteria:**
```yaml theme={null}
User impact: High/Medium/Low
Business value: Revenue, retention, satisfaction
Implementation effort: Technical complexity, time required
Risk assessment: Potential negative consequences
```
**Convert insights to design opportunities:**
```yaml theme={null}
High impact, low effort:
- Copy and labeling improvements
- Color and contrast adjustments
- Micro-interaction enhancements
- Content reorganization
```
```yaml theme={null}
High impact, high effort:
- Information architecture redesign
- New feature development
- Cross-platform consistency
- Accessibility overhauls
```
**Create actionable design briefs:**
```yaml theme={null}
Requirement template:
Problem: User pain point or opportunity
Evidence: Supporting data and research
Success criteria: How to measure improvement
Constraints: Technical, business, timeline limits
Priority: Relative importance ranking
```
## User Persona Development
**Build personas from real user data:**
* Behavioral clustering analysis
* Usage pattern identification
* Goal and motivation mapping
* Pain point documentation
* Demographic correlation
**Update personas as data evolves:**
* Regular data refresh cycles
* Behavior change tracking
* New user segment identification
* Persona validation through research
* Cross-platform behavior mapping
## Advanced Analytics Integration
**Live insight generation:**
```yaml theme={null}
Real-time capabilities:
- Live user behavior monitoring
- Instant anomaly detection
- Dynamic insight updates
- Rapid hypothesis testing
- Immediate design impact measurement
```
**Anticipate user needs:**
```yaml theme={null}
Predictive insights:
- User behavior forecasting
- Churn prediction modeling
- Feature adoption predictions
- Seasonal usage patterns
- Market trend analysis
```
**Understand user evolution:**
```yaml theme={null}
Cohort tracking:
- User onboarding success patterns
- Feature adoption timelines
- Retention curve analysis
- Behavior change over time
- Segmented user journeys
```
## Validation & Testing
**Create testable design hypotheses:**
```yaml theme={null}
Hypothesis structure:
"If we [design change], then [user behavior] will [improve/change]
because [user insight/data evidence]"
Example:
"If we add shipping cost calculator to product pages, then
mobile checkout completion will increase by 15% because
analytics show 60% abandon at shipping cost reveal"
```
**Plan validation approach:**
* A/B testing setup
* Conversion rate measurement
* User behavior tracking
* Statistical significance planning
* User interview planning
* Usability testing design
* Feedback collection strategy
* Observation methodology
**Feed results back into insights:**
```yaml theme={null}
Learning cycle:
- Test results analysis
- Insight validation or revision
- New hypothesis generation
- Design iteration planning
- Knowledge base updates
```
## Best Practices
**Ensure reliable insights:**
✅ Verify data source accuracy
✅ Check for sampling biases
✅ Validate across multiple sources
✅ Consider temporal factors
✅ Account for external influences
**Generate useful design direction:**
✅ Connect data to specific design decisions
✅ Prioritize insights by user impact
✅ Create testable hypotheses
✅ Consider implementation feasibility
✅ Plan success measurement
***
Learn how to systematically analyze competitors and extract design insights for your product.
[Benchmark Competitors →](/designing/ideation/benchmark-competitors)