Mapping Core User Flows for an AI-Powered App

Documenting key user journeys, decision points, and edge cases to bring clarity and consistency to a complex AI-powered product experience.

Industry

Real Estate

Project Type

User Flow Mapping

Tags

User Flows

AI Product

UX Design

Role

Product Designer

Tool

Figma FigJam

Industry

Real Estate

Role

Product Designer

Project Type

User Flow Mapping

Tool

Figma FigJam

Tags

User Flows

AI Product

UX Design

No headings found on page

This project was completed under NDA. Client details are confidential. The flows shown here are selected examples from a larger end-to-end product design engagement.

Overview

As part of an end-to-end product design engagement for an AI-powered home design platform, I mapped the core user flows to clarify how users move between key actions and product states.

The Challenge

The product involved multiple interconnected features and user decisions. Without clearly mapped flows, it would be harder to identify gaps, account for edge cases, and maintain consistency across the experience.

Design Process

Listing Every Flow First

Before drawing anything, I listed every flow I could think of. Then I tested each one with three questions. Does it have one goal? Does it have a clear start? Does it have a clear end?

Numbering and Grouping

I numbered the flows by group so each one has a short name anyone can point to. The 1.x flows are about the account, the 2.x flows are about finding and saving items, and so on.

Rules for Drawing

To keep every flow consistent, I followed the same rules each time.

  • Start each flow at the first step that belongs only to it

  • Draw the path where everything goes right first. Then add what happens when something goes wrong, like a wrong password, a denied permission, or an empty search

  • Draw anything shared once and link to it

  • Use the same color system

Color System

Pink for the start, purple for a process, green for a decision, red for the finish the user wanted, and yellow for an unexpected finish or a way out.


User Flows

Login

Maps how returning users sign in using their credentials or Google/Meta accounts, including password recovery when needed.


Sign Up

Covers account creation, input validation, email verification, and onboarding before users enter the app.


Forgot Password

Guides users through requesting a password reset, verifying their email, and returning to the login screen.


Change Password

Defines how users verify their current password, set a new one, and complete the password update.


Delete Account

Maps the account deletion process, including email confirmation, resend options, and final deletion.


Searching for an Item

Shows how users search for a specific product, apply sorting or filters, and handle empty results.



Exit Image Generation

Defines how users leave the generation flow, including deciding whether to save their design before exiting.


Reflection

I learned that a flow can look finished and still be wrong. When I reread each one slowly, I found branches with the wrong label, steps that were missing, and boxes that repeated an earlier step.

A flow may looks simple once it is drawn, but the real work is asking what else can happen at each step. Mapping every flow early meant I could answer that question while changes were still easy to make.


This project was completed under NDA. Client details are confidential. The flows shown here are selected examples from a larger end-to-end product design engagement.

Overview

As part of an end-to-end product design engagement for an AI-powered home design platform, I mapped the core user flows to clarify how users move between key actions and product states.

The Challenge

The product involved multiple interconnected features and user decisions. Without clearly mapped flows, it would be harder to identify gaps, account for edge cases, and maintain consistency across the experience.

Design Process

Listing Every Flow First

Before drawing anything, I listed every flow I could think of. Then I tested each one with three questions. Does it have one goal? Does it have a clear start? Does it have a clear end?

Numbering and Grouping

I numbered the flows by group so each one has a short name anyone can point to. The 1.x flows are about the account, the 2.x flows are about finding and saving items, and so on.

Rules for Drawing

To keep every flow consistent, I followed the same rules each time.

  • Start each flow at the first step that belongs only to it

  • Draw the path where everything goes right first. Then add what happens when something goes wrong, like a wrong password, a denied permission, or an empty search

  • Draw anything shared once and link to it

  • Use the same color system

Color System

Pink for the start, purple for a process, green for a decision, red for the finish the user wanted, and yellow for an unexpected finish or a way out.


User Flows

Login

Maps how returning users sign in using their credentials or Google/Meta accounts, including password recovery when needed.


Sign Up

Covers account creation, input validation, email verification, and onboarding before users enter the app.


Forgot Password

Guides users through requesting a password reset, verifying their email, and returning to the login screen.


Change Password

Defines how users verify their current password, set a new one, and complete the password update.


Delete Account

Maps the account deletion process, including email confirmation, resend options, and final deletion.


Searching for an Item

Shows how users search for a specific product, apply sorting or filters, and handle empty results.



Exit Image Generation

Defines how users leave the generation flow, including deciding whether to save their design before exiting.


Reflection

I learned that a flow can look finished and still be wrong. When I reread each one slowly, I found branches with the wrong label, steps that were missing, and boxes that repeated an earlier step.

A flow may looks simple once it is drawn, but the real work is asking what else can happen at each step. Mapping every flow early meant I could answer that question while changes were still easy to make.


Quote

Thank you! That is my work obviously nowhere close to as good as yours so I am definitely missing a lot of screens/the style sucks etc. So also make up whatever screens you think should go there too because you are super smart I think you understand my thinking at this point.

Founder - AI Startup

More Case Study

Designing a Role-Based Investor Portal

Consulting Website Redesign for a Project Management Firm

Create a free website with Framer, the website builder loved by startups, designers and agencies.