Skip to main content

​
Pre-Design Exploration

Bridge the gap between requirements and design execution. Use Figr’s exploration tools to validate concepts, test assumptions, and establish design direction before detailed interface work.

​
Exploration Methodology

  • Concept Validation
  • Information Architecture
  • Interaction Patterns
Test fundamental design assumptions:
1

Mental Model Testing

Validate that your proposed solution matches user expectations and mental models
2

Flow Feasibility

Ensure user journeys are logical and achievable within technical constraints
3

Value Proposition

Confirm the design approach delivers on promised user and business value

​
Rapid Prototyping Tools

1

Concept Sketching

Quick idea visualization:

Digital Sketching

Fast concept capture:
  • Low-fidelity wireframes
  • User flow diagrams
  • Screen relationship mapping
  • Interaction concept illustration

Collaborative Ideation

Team-based exploration:
  • Real-time collaborative sketching
  • Idea building and iteration
  • Cross-functional input integration
  • Consensus building tools
2

Interactive Prototypes

Concept validation through interaction:
  • Click-Through Prototypes
  • Functional Prototypes
Basic interaction testing:
- Navigation flow validation
- Content hierarchy testing
- User pathway exploration
- Decision point identification
3

Concept Testing

Validate ideas with real users:
Testing approaches:

Concept validation:
- First-click testing
- Tree testing for navigation
- Five-second tests for comprehension
- Preference testing between alternatives

Usability assessment:
- Task completion testing
- Think-aloud protocols
- Time-to-completion measurement
- Error rate analysis

​
Design Direction Establishment

  • Visual Exploration
  • Pattern Selection
  • Technical Validation
Establish aesthetic direction:
Mood board and visual style exploration showing different design directions
Exploration areas:
Visual style:
- Color palette exploration
- Typography direction testing
- Layout approach comparison
- Component style development

Brand expression:
- Brand personality translation
- Visual voice definition
- Emotional tone setting
- Differentiation strategy

​
Stakeholder Alignment

1

Concept Presentation

Communicate design direction effectively:
  • Executive Summary
  • Detailed Walkthrough
High-level communication:
- Problem and solution overview
- Key design decisions rationale
- Expected user and business impact
- Implementation timeline and resources
- Success measurement plan
2

Feedback Integration

Incorporate stakeholder input:

Structured Feedback

Organized input collection:
  • Specific feedback categories
  • Priority level assignment
  • Impact assessment
  • Resolution planning

Collaborative Refinement

Joint improvement process:
  • Real-time concept adjustment
  • Alternative exploration
  • Compromise solution development
  • Consensus building
3

Decision Documentation

Record exploration outcomes:
Documentation capture:

Design decisions:
- Chosen approaches and rationale
- Rejected alternatives and reasons
- Assumption validations
- Constraint acknowledgments

Next steps:
- Detailed design planning
- Implementation roadmap
- Testing and validation schedule
- Success criteria definition

​
Exploration Outputs

Design Brief

Comprehensive design direction:
  • Problem definition
  • Solution approach
  • Success criteria
  • Implementation plan

Prototype Library

Validated concepts:
  • Tested interaction patterns
  • Proven user flows
  • Visual style direction
  • Component foundations

Research Insights

Validated assumptions:
  • User preference data
  • Usability test results
  • Stakeholder alignment
  • Technical feasibility

​
Transition to Detailed Design

1

Design System Preparation

Ready design foundation:
System elements:
- Color palette finalization
- Typography scale definition
- Component pattern specification
- Layout grid establishment
- Icon and imagery direction
2

Implementation Planning

Prepare for development:
Development readiness:
- Technical specification creation
- Component prioritization
- Development phase planning
- Quality assurance preparation
- Launch criteria definition

​
Best Practices

Iterative Exploration

Continuous refinement:✅ Test early and often ✅ Embrace rapid iteration ✅ Document learning progression ✅ Remain open to pivoting ✅ Build on validated insights

Evidence-Based Decisions

Data-driven direction:✅ Validate with real user data ✅ Reference competitive insights ✅ Consider technical constraints ✅ Align with business objectives ✅ Plan measurable outcomes

Start Interface Design

Begin detailed interface design with validated concepts and clear direction.Building on Existing →
⌘I