> ## Documentation Index
> Fetch the complete documentation index at: https://docs.figr.design/llms.txt
> Use this file to discover all available pages before exploring further.

# Turn research and walkthroughs into journeys and flows

Before anyone designs, someone has to pull the context together: interview notes in one doc, a walkthrough on a drive, analytics in another tool. Product teams have to get everything into one place by hand every time.

Figr does that gathering for you, then turns it into the journeys and flows your team designs from.

![Image](https://mintcdn.com/figr-1af7ae64/MWugUlEIv8OG0sG0/images/image-8.png?fit=max\&auto=format\&n=MWugUlEIv8OG0sG0\&q=85\&s=df34082c0bfe801c3784f5891eba16d2)

> [!TIP]
>
> **The short version:** Drop in interviews, walkthroughs and notes. Figr reads them together and produces a journey map and the user flows behind it, connected on one canvas, so the team starts design from shared evidence.

**Example on this page:** FreshFold, a laundry pickup and delivery app. Customers book a pickup in the app, a rider collects the bag, and clean clothes come back within 24 hours.

## How it works

**1. Give Figr your research**

Attach interview notes, a walkthrough recording or research docs, or connect the tools where they live. In the FreshFold example: two interviews with customers who book weekly pickups, and a recording of the booking flow.

![Screenshot 2026 10 20 At 11 27 31 PM](https://mintcdn.com/figr-1af7ae64/IKsR7_SNlON40_qL/images/Screenshot-2026-10-20-at-11.27.31-PM.png?fit=max\&auto=format\&n=IKsR7_SNlON40_qL\&q=85\&s=e689ad198c53588c4474c80b123446b4)

**2. Figr finds the patterns**

Figr reads every source together and pulls out the goals, steps and pain points that repeat across people.

**3. Figr maps the journey**

You get a journey map of the experience end to end, with each pain point traced back to where it came from.

![Image](https://mintcdn.com/figr-1af7ae64/6fNHqiw94uTEs_lh/images/image-11.png?fit=max\&auto=format\&n=6fNHqiw94uTEs_lh\&q=85\&s=817ce51dacd9f7ec91c19af870275b05)

**4. Figr turns it into flows**

Ask for the flows behind any stage, and Figr maps them step by step, ready to design from.

**5. Figr writes the PRD**

Ask for a PRD, and Figr writes the problem, goals, user stories, requirements and edge cases from the same research, with each requirement linked back to the evidence behind it.

![Image](https://mintcdn.com/figr-1af7ae64/6fNHqiw94uTEs_lh/images/image-12.png?fit=max\&auto=format\&n=6fNHqiw94uTEs_lh\&q=85\&s=f00de68e71a81a87a8b75bcdc29eb808)

## What changes for your team

* **Researchers** see their findings used, not filed away.
* **PMs** get a journey the whole team agrees on before scoping.
* **Designers** start from real user steps instead of assumptions.

## Go further

Want Figr to read more of your context? See every source you can bring in.

> **[Files and research](/input-research/files-research)**
>
> Bring in PRDs, research docs and screenshots.

## Related

> **[Screen recordings](/input-research/screen-recording)**
>
> Record a walkthrough Figr can learn from.

> **[Many directions, one decision](/what-figr-does/explore-and-sign-off)**
>
> Next step: explore real options and get sign-off.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.