> ## 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. # Product Context > Leverage Figr's deep product understanding to create interfaces that perfectly fit your specific users, constraints, and business objectives. # Product Context Figr's product context awareness is what makes AI-generated designs feel native to your specific product. Learn how to leverage this deep understanding for better design outcomes. **Context-aware design:** Every design decision informed by your specific users, business constraints, technical limitations, and product history. ## How Product Context Works **Multi-layered product understanding:** Diagram showing layers of product context from user data to technical constraints **Context layers:** ```yaml theme={null} User context: - Persona characteristics and behaviors - Skill levels and technical proficiency - Device and platform preferences - Geographic and cultural considerations Business context: - Strategic objectives and KPIs - Market positioning and differentiation - Revenue models and monetization - Compliance and regulatory requirements Technical context: - Platform capabilities and limitations - Performance requirements and constraints - Integration points and dependencies - Security and privacy requirements Design context: - Existing design system and patterns - Brand guidelines and visual identity - Accessibility standards and requirements - Cross-platform consistency needs ``` **How context influences design decisions:** ```yaml theme={null} Context-driven layout choices: Mobile-first users → Vertical layouts prioritized Data-heavy workflows → Table-dense interfaces Creative professionals → Visual-first layouts Enterprise users → Information-dense designs Accessibility needs → Clear hierarchy and contrast ``` ```yaml theme={null} Context-informed interactions: Touch-primary users → Larger touch targets Keyboard-heavy workflows → Shortcut integration Multi-tasking contexts → Efficient state management Error-prone processes → Extensive validation Time-critical tasks → Streamlined interactions ``` ```yaml theme={null} Context-aware content decisions: Technical users → Detailed specifications Business users → High-level summaries International users → Localization considerations Compliance-heavy industries → Audit trail emphasis Fast-paced environments → Scannable information ``` **Context evolves with your product:** **Continuous context refinement:** * User behavior pattern analysis * Feature adoption tracking * Performance metric monitoring * Feedback sentiment analysis **Keeping context current:** * Product evolution tracking * Market condition changes * User base evolution * Technology advancement impact ## Context Categories **Understanding your specific users:** ```yaml theme={null} Detailed user understanding: Primary persona: Marketing Manager - Technical proficiency: Intermediate - Primary tasks: Campaign creation, performance analysis - Pain points: Complex reporting, time-consuming setup - Success metrics: Campaign ROI, time to launch - Device usage: 60% desktop, 40% mobile Secondary persona: Campaign Specialist - Technical proficiency: Advanced - Primary tasks: Detail optimization, A/B testing - Pain points: Limited automation, manual processes - Success metrics: Conversion optimization, efficiency - Device usage: 90% desktop, 10% mobile ``` ```yaml theme={null} User behavior insights: Navigation preferences: - 70% use search vs 30% browse menus - Average session: 15 minutes - Multi-tab usage: 85% of power users - Mobile sessions: Shorter, task-focused Task completion patterns: - Prefer saving drafts frequently - Complete complex tasks in multiple sessions - Heavy use of keyboard shortcuts - Collaborate via shared links and comments ``` ```yaml theme={null} Multi-context usage: Work environments: - Office: Large screens, keyboard+mouse - Remote: Varied setups, video calls - Travel: Mobile-first, limited time - Commute: Quick checks, mobile only Urgency levels: - Routine tasks: Efficiency-focused - Urgent issues: Error-prevention critical - Exploratory work: Discovery-friendly - Presentations: Visual clarity essential ``` **Aligning design with business objectives:** ```yaml theme={null} Business goal influence on design: Revenue growth → Conversion optimization focus User retention → Engagement feature emphasis Market expansion → Localization considerations Competitive differentiation → Unique feature highlighting Cost reduction → Efficiency workflow prioritization ``` ```yaml theme={null} Brand positioning impact: Premium positioning → Sophisticated, clean design Value positioning → Efficiency and functionality focus Innovation leader → Cutting-edge interaction patterns Trust-focused → Conservative, reliable patterns Accessibility leader → Inclusive design prioritization ``` ```yaml theme={null} Compliance requirements: Healthcare (HIPAA) → Privacy-first design patterns Finance (SOX) → Audit trail emphasis Education (FERPA) → Student data protection European markets (GDPR) → Consent management Accessibility (WCAG) → Inclusive interaction design ``` **Design within technical reality:** ```yaml theme={null} Technical limitation awareness: Mobile performance → Lightweight interactions Legacy browser support → Progressive enhancement Slow networks → Offline-first design Limited bandwidth → Image optimization priority Battery life → Animation and processing limits ``` ```yaml theme={null} Platform-specific optimizations: Web application → Rich interactions, keyboard shortcuts iOS app → Native gestures, system integration Android app → Material design patterns Desktop app → Window management, file system Progressive web app → Offline capability, installation ``` ```yaml theme={null} System connectivity needs: CRM integration → Contact data synchronization Analytics platform → Event tracking design Payment systems → Security pattern compliance Email services → Template and automation design API limitations → Rate limiting consideration ``` ## Context-Driven Design Examples **Context shapes dashboard priorities:** Two dashboard designs showing how different user contexts create different layouts **Executive user context:** ```yaml theme={null} Design implications: - High-level metrics prominently displayed - Trend visualization over detailed data - One-click drill-down capabilities - Mobile-optimized for on-the-go access - Clean, presentation-ready layouts ``` **Analyst user context:** ```yaml theme={null} Design implications: - Detailed data tables with sorting/filtering - Advanced chart customization options - Export functionality in multiple formats - Real-time data refresh controls - Desktop-optimized for extended sessions ``` **Purchase context variations:** ```yaml theme={null} Business purchase considerations: - Multi-step approval workflow design - Purchase order number integration - Tax exemption handling - Bulk quantity optimization - Invoice and payment term options ``` ```yaml theme={null} Consumer purchase optimization: - Guest checkout prioritization - Social login integration - Mobile payment method support - Shipping option clarity - Trust signal prominence ``` ```yaml theme={null} Recurring payment design: - Trial period clarity - Cancellation policy transparency - Billing cycle visualization - Plan comparison integration - Upgrade/downgrade pathways ``` **Administrative context adaptation:** ```yaml theme={null} Context-aware admin design: Small team context: - Simplified role management - Quick configuration options - Essential features prioritized - Minimal training requirements Enterprise context: - Advanced permission systems - Bulk operation capabilities - Audit log prominence - Integration management tools - Compliance reporting features ``` ## Leveraging Context for Better Designs **Ask better questions to get better results:** **Less effective:** "Create a user settings page" **Result:** Generic settings layout **More effective:** "Create user settings for marketing managers who need quick access to notification preferences and team collaboration settings" **Result:** Prioritized layout with relevant features **Ensure context accuracy:** ```yaml theme={null} Context verification methods: User research validation: - Interview findings alignment - Survey data correlation - Usability testing confirmation - Analytics pattern verification Business requirement checking: - Strategic objective alignment - KPI impact assessment - Stakeholder expectation matching - Market positioning consistency Technical constraint verification: - Performance requirement feasibility - Integration capability confirmation - Security standard compliance - Platform limitation acknowledgment ``` **Keep context current and relevant:** ```yaml theme={null} Context maintenance schedule: - Quarterly user research integration - Monthly analytics review - Weekly feedback incorporation - Daily usage pattern monitoring ``` ```yaml theme={null} Context drift indicators: - User behavior pattern changes - Business objective shifts - Technical capability evolution - Market condition changes - Competitive landscape shifts ``` ## Advanced Context Features **Anticipate future needs:** * User behavior prediction * Seasonal usage pattern awareness * Growth-stage design adaptation * Market trend incorporation * Technology evolution preparation **Handle complex context combinations:** * Cross-persona design optimization * Multi-platform context balancing * Regional variation management * Industry-specific customization * Accessibility context integration ## Best Practices **Maintain high-quality context:** ``` ✅ Validate context with real user research ✅ Update context regularly as product evolves ✅ Consider edge cases and minority users ✅ Balance multiple context sources ✅ Document context assumptions clearly ``` **Use context effectively in design:** ``` ✅ Reference specific context in design requests ✅ Validate design decisions against context ✅ Consider context trade-offs explicitly ✅ Test designs with contextual users ✅ Iterate based on context-specific feedback ``` *** Learn how to set up and manage design tokens for consistent, scalable design systems in Figr. [Setting Tokens →](/designing/design-system/setting-tokens)