Enhance Figr’s product understanding with contextual links and detailed notes. Share references, document decisions, and provide ongoing guidance that shapes every design.
Decision Notes:"We use blue for primary actions because user testing showed 23% better click-through rates vs. green"Constraint Notes:"Mobile layouts must work with one-handed usage - primary actions in thumb reach zone"Pattern Notes:"Error messages appear below form fields, not above, based on eye-tracking studies"
📊 Google Analytics: dashboard.google.com/analytics🎥 User testing videos: loom.com/share/user-research📋 Survey results: typeform.com/results/user-survey📈 Mixpanel dashboard: mixpanel.com/project/insights
Inspiration & Benchmarks
🎨 Design inspiration: dribbble.com/shots/saved🏆 Best practices: nngroup.com/articles/mobile-ux🔍 Competitor analysis: competitor.com/feature-name📱 Mobile patterns: mobbin.design/patterns
2
Contextual Notes
Add detailed context and reasoning:
Note types:
📝 Design Decisions: Why certain choices were made⚠️ Constraints: Technical or business limitations💡 Insights: User research findings🎯 Goals: Success metrics and objectives🔄 Iterations: What was tried and why it changed
3
Smart Tagging
Automatic context organization:
Auto-tags based on content:- #accessibility (WCAG, screen readers)- #mobile-first (responsive, touch)- #performance (load times, optimization)- #conversion (CTAs, funnels)- #enterprise (B2B, admin features)- #onboarding (new user experience)
Write notes that inform future designs:✅ Specific and actionable
“Users expect save button top-right in admin interfaces”✅ Include reasoning
“Single-column mobile layout because 68% of users are one-handed”✅ Reference data
“Blue CTAs convert 15% better than green (A/B test July 2024)”
Context Hierarchy
Organize information by importance:🔴 Critical constraints (must follow)
🟡 Strong preferences (should follow)
🟢 Nice to have (consider when possible)Example:
🔴 “WCAG AA compliance required for government contract”
🟡 “Users prefer minimal form fields”
🟢 “Consider animation to delight users”
When you add: https://competitor.com/dashboardFigr extracts:✅ Visual design patterns✅ Layout structures✅ Color schemes and typography✅ Interactive elements✅ Content organizationApplication:"Referenced competitor uses sidebar navigation with collapsible sections - consider for enterprise users"
Track changes in referenced content:
Update Notifications
Competitor feature changes
Design system updates
Documentation changes
Research report updates
Relevance Scoring
High relevance: Direct feature comparisons
Medium relevance: Similar user flows
Low relevance: General inspiration
Outdated: No longer applicable
Figr suggests relevant links:
When designing checkout flow:"Consider reviewing the Stripe checkout pattern you bookmarked"When creating mobile layout:"Reference the thumb-zone research from NN Group"When adding error states:"Check the error message guidelines in your design system"
Product Manager notes:- Business requirements and constraints- User feedback and feature requests- Market research and competitive insightsDesigner notes:- Visual design decisions and rationale- Usability insights and best practices- Accessibility considerationsEngineer notes:- Technical constraints and possibilities- Performance implications- Implementation complexity
2
Note Threading
Connected conversations:
Discussion flow:
Initial note with context
Team member responses and questions
Resolution and final decision
Reference in future designs
3
Knowledge Building
Cumulative team intelligence:
Month 1: Basic product contextMonth 3: Pattern recognition and preferencesMonth 6: Deep user understanding and edge casesMonth 12: Institutional knowledge and design wisdom
When you mention "mobile navigation" in notes,Figr suggests relevant:- Mobile design pattern links- Competitor mobile examples- Touch interaction guidelines- Accessibility mobile standards
Note Analytics
Understand knowledge usage:
Most referenced notes:1. Mobile interaction guidelines2. Brand color usage rules3. Enterprise user requirements4. Performance constraintsInsight: Mobile guidelines heavily used → Suggests mobile-first design approach
Export & Sharing
Transform notes into documentation:
Export options:✅ Design decision log (PDF)✅ Knowledge base (Markdown)✅ Team wiki pages (HTML)✅ Reference library (JSON)
Note: "Enterprise users need bulk actions"Design output: Tables include checkboxes and bulk operation toolbarLink: Mobile navigation best practicesDesign output: Thumb-friendly navigation with clear touch targets
Automatic compliance checking:
Constraint note: "Buttons must be minimum 44px for accessibility"Figr check: ✅ All buttons meet minimum size requirementReference link: Brand guidelinesFigr check: ✅ Colors match brand palette
Context-aware improvements:
Previous note: "Users confused by icon-only navigation"Design suggestion: Add text labels to navigation iconsResearch link: Form completion studyDesign suggestion: Reduce form fields based on completion data
Explore Screen Sharing
Learn how to share your screen with Figr for the deepest product understanding possible.Screen Sharing →
Discussion flow: