Flow Mapping

Overview

Connect multiple analyzed screenshots into coherent interaction flows by systematically inventorying screens, mapping navigation elements, identifying transitions, and assembling user journeys. Every screen must have defined entry and exit points, every gap must be explicitly noted, and every flow must be organized around user goals.

When to Use

• Multiple screenshots of an app or site have been analyzed and need connecting into flows
• Building a navigation architecture from visual references
• Identifying how users move between screens in an existing product
• Documenting user journeys from screenshot evidence
• Auditing an existing flow for dead ends, orphaned screens, or missing states
• Preparing interaction specifications for implementation

When NOT to Use

• Only a single screenshot is available (use humaninloop:analysis-screenshot instead)
• Designing flows from scratch without reference screenshots