Create user journey maps

Create user journey maps in Figma — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need a clear user journey map for new customers onboarding to our subscription product. Start…
I need a clear user journey map for new customers onboarding to our subscription product. Start with the first marketing touch (LinkedIn post on Tuesday) through account activation and first successful task completion. Include the emotional state at each touchpoint, the business metric we care about (activation rate, time-to-first-success), and the single next action we should take at each stage to improve the metric. Deliver as a single-page diagram I can paste into our product review on Friday.

Improve — make it easier to accept

+
Before I show this journey to the product team, make the map easy for someone in support or sales…
Before I show this journey to the product team, make the map easy for someone in support or sales to act on: surface the biggest drop-off between touchpoints, label which stage a support rep should intervene, and flag two hypotheses that would explain the drop. Highlight the one metric to track on the dashboard for 30 days.

Decide — diagnose the stuck moment

+
We launched the new signup flow and 40% of people abandon at email verification. The stakeholders…

We launched the new signup flow and saw a 40% drop at the email verification step.

We launched the new signup flow and 40% of people abandon at email verification. The stakeholders are the growth PM, the support lead Maya, and our CTO. I am worried this will tank week-one activation and that the verification email is going to spam for some domains. I cannot tell whether this is deliverability, confusing copy, or a UI bug. Diagnose the most likely cause and recommend the one A/B test or investigation to run first, with the minimal tracking to add.

Become — change the pattern

+
Over the last three releases we consistently lose users between welcome and first successful use of…

We keep losing people between welcome and first success event.

Over the last three releases we consistently lose users between welcome and first successful use of the product. The pattern shows low time-to-first-success and repeated support tickets about missing guidance. I want habitual changes to stop this bleed. Recommend the single process change and the one content pattern designers should embed into every onboarding screen to raise first-success rate, plus how to measure it for 60 days.

Next to this one

Other interface design work people do in Figma.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.