Q3 2025
Q2 2025
Q1 2025
Q4 2024
Q3 2024
Q2 2024
Q1 2024
Q4 2023
Search for a command to run...
This library contains actionable insights discovered through user research. Each insight is backed by evidence and includes implications for product development.
An insight is a deep understanding of user behavior, needs, or motivations that goes beyond surface-level observations. It answers the "why" behind user actions and provides direction for product decisions.
These insights are based on multiple research studies and strong evidence.
When documenting an insight, use this structure:
---
title: Insight Title (Clear, Specific Statement)
description: One-sentence summary of the insight
date: 2024-01-15
category: navigation | onboarding | accessibility | mobile | etc.
confidence: high | medium | low
impact: high | medium | low
status: validated | hypothesis | archived
---
# Insight Title
## TL;DR
One or two sentences summarizing the insight and its implications.
## The Insight
Clear, concise statement of what we learned about users.
**In one sentence:** Users do [behavior] because [motivation], which means we should [action].
## Evidence
Data, quotes, and observations that support this insight.
### Quantitative Evidence
- 78% of users (23/30) exhibited this behavior
- Average time to complete task: 45 seconds
- Task success rate: 65%
### Qualitative Evidence
> "Quote from user that illustrates the insight"
> ā Participant 7, Study Name
> "Another supporting quote"
> ā Participant 12, Study Name
### Supporting Studies
- [Study Name 1](/studies/study-1) - Key finding
- [Study Name 2](/studies/study-2) - Key finding
- [Survey Results](/studies/survey) - Relevant data
## Context & Background
When did we discover this? What prompted the research?
- **Discovery Date**: March 2024
- **Research Context**: Usability testing of new navigation
- **Related Problem**: Users were abandoning tasks
## Implications
What does this mean for our products and decisions?
### For Product Teams
How this insight should influence product decisions
### For Design Teams
How this insight should influence design decisions
### For Engineering Teams
Technical considerations or implications
## Recommendations
Specific, actionable steps based on this insight.
### Immediate Actions (Do Now)
1. **Recommendation 1** - Specific action to take
- Owner: Team/Person
- Timeline: 1 week
- Effort: Low
### Short-term Actions (Next Quarter)
2. **Recommendation 2** - Another action
- Owner: Team/Person
- Timeline: 1 month
- Effort: Medium
### Long-term Actions (Future)
3. **Recommendation 3** - Strategic action
- Owner: Team/Person
- Timeline: 3-6 months
- Effort: High
## Actions Taken
What we've done based on this insight and the results.
### Implementation 1
- **What**: Description of change made
- **When**: March 2024
- **Result**: Measurable outcome
- **Impact**: How it affected users
### Implementation 2
- **What**: Another change
- **When**: April 2024
- **Result**: Outcome
- **Impact**: User impact
## Success Metrics
How we measure whether addressing this insight was successful.
- **Metric 1**: Baseline ā Target (Actual)
- **Metric 2**: Baseline ā Target (Actual)
- **Metric 3**: Baseline ā Target (Actual)
## Related Content
Links to related insights, studies, and personas.
- [Related Insight 1](/insights/related-1)
- [Related Study](/studies/study)
- [Related Persona](/personas/persona)
## Confidence Assessment
**Confidence Level:** High
**Why this confidence level?**
- Multiple research methods (triangulation)
- Large sample size (30+ participants)
- Consistent across user segments
- Validated in multiple contexts
**Validation History:**
- Initial finding: Study A (10 participants)
- Confirmed: Study B (15 participants)
- Quantified: Survey (200 responses)
## Future Research
Questions this insight raises or areas needing more research.
- What about [edge case or different context]?
- How does this vary across [different user segment]?
- What are the long-term effects of [intervention]?
---
**Insight Owner:** Researcher Name
**Last Updated:** March 15, 2024
**Next Review:** June 15, 2024
**Status:** ValidatedObservation: Users clicked the back button 5 times before finding settings
Insight: Users expect settings in the navigation menu because that's where other applications place it, not in their profile dropdown
Support your insight with multiple sources:
Bad: "Users struggle with navigation" Good: "Users expect settings in the main menu, not the profile dropdown, because that matches mental models from other applications"
"Based on [Insight Name], we should prioritize..."
"Remember [Insight Name] showed that users expect..."
"This addresses [High Confidence Insight], affecting 75% of users"
"Let's test whether [Insight Name] still holds true"
ā Observation: "Users clicked the wrong button" ā Insight: "Users clicked the CTA button instead of the link because the link looked like body text, not an actionable element"
ā Vague: "Users want better navigation" ā Specific: "Users expect to find account settings in the main navigation menu, not buried in their profile dropdown, because that matches their mental model from banking and email applications"
ā Incomplete: "Users prefer visual layouts" ā Complete: "Users prefer visual card layouts to text lists because they can scan faster and recognize items by thumbnail, reducing time to find items by 40%"
Track the value of your insights:
Remember: Great insights change how teams think about users and lead to better product decisions. Focus on quality over quantity.