The full audit lives in Figma

Figma How To

Audit Guide

New to this audit?

This guide shows how the Figma audit is structured and how to navigate it efficiently.

Takes ~1–2 minutes to get oriented

Structure

The audit is composed of three parts.

01Start here

User Journey

  • What the user is trying to do
  • What actually happens
  • Where friction or risk appears
  • Emotional impact (confidence vs stress)

Think of this as the story of the problem.

02System view

App Flow Chart

  • Shows how screens and actions connect
  • Helps you understand how the product is structured
  • Mirrors the same steps shown in the journey

Think of this as the system view of the same story.

03UI breakdown

Screen-Level Audit Notes

  • What works well
  • What needs improvement
  • What needs to be fixed
  • Suggested ideas (when relevant)

Think of this as the specific UI-level breakdown.

How everything connects

Three views, one story.

These three sections are intentionally linked — so you can trace any issue from experience, to system, to UI.

  1. Step 1 · Experience

    User Journey

    Highlights where problems happen.

  2. Step 2 · System

    Flow Chart

    Shows where that happens in the system.

  3. Step 3 · Interface

    Screens

    Show exactly what causes the issue.

How to get value from this quickly

If you're short on time:

  1. 1Start with the Summary Report
  2. 2Skim the User Journey
  3. 3Jump to specific screens if something stands out

If you want full context:

Go through all three sections in order.

What this audit focuses on

Focus areas

  • Clarity during ordering
  • Error prevention before submission
  • Reducing mental load on staff
  • Supporting a smoother service flow