
CUSTOMER UNDERSTANDING
- Market Research & Segmentation
- Contextual User Understanding
- Scenario Gathering & Workflow Analysis
- Customer Modeling & Persona Development

DESIGN CONCEPT VALIDATION
- Feature Validation
- UI Layout Testing
- Visual Design
- Information Architecture
- Design

USER INTERFACE TESTING
- Usability Issues
- Terminology Issues
- Information Architecture
- Refinement

BENCHMARKING
- Baseline Success Metrics
- Satisfaction
WHY WORK WITH US?
vendor management
scalability
work done
vendor budget use
Turnaround
international research
of methodologies
pricing structure
OUR TIMELINE PROCESS

PROJECT DEFINITION
Determine:
- Team and roles
- Goals and scope
- Audience profile(s)
- Research focus
- Methodologies and metrics
- Timeline and milestones

RESEARCH PLANNING
Commence:
- Participant recruiting
- Research plan development
- Test resource setup
- Data collection setup

PRODUCTION
Review & Approve:
- Research plan
- Data collection metrics and tools
- Test resource configuration
- Run-through/pilot

TESTING
Execute:
- Research moderation
- Data collection

ANALYSIS & REPORTING
Deliver:
- Data analysis
- Insights report findings
- Presentation to client

Process Modeling and Information Architecture
Modern products are frequently complex. Process modeling and information architecture take a high-level view to ensure the system always supports the user. Building on user research, personas are developed to capture the needs, behaviors, and pain points for each user group. Process modeling captures how personas perform tasks in a task flow diagram. An information architecture, which is developed to support the requirements described in the personas and task flow diagrams, is a blueprint for how information can be organized to make the whole system easier to understand.

Some of our methods include:
Task flow modeling, Information architecture, hierarchical task analysis, persona development and use case studies.

We help answer questions like:
Do users understand our new navigation scheme?
How could the information in our product be better organized?
Where are breakdowns happening in common user tasks?