Map user journeys

Map user journeys in Notion — 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

+
We need a user journey map for our onboarding flow. Map steps from landing page sign‑up to first…
We need a user journey map for our onboarding flow. Map steps from landing page sign‑up to first value: welcome email sent within 10 minutes, account setup complete within 24 hours task to user, first success metric reached in 7 days. Include touchpoints, responsible teams, and where we measure conversion so PM, growth and support can act.

Improve — make it easier to accept

+
Before I present the user journey to stakeholders, make it easy to act on. Bring conversion drop…
Before I present the user journey to stakeholders, make it easy to act on. Bring conversion drop points to the top, show the metric and current conversion rate for each touchpoint, and flag where ownership is unclear or where instrumented events are missing so the analytics team can prioritize fixes.

Decide — diagnose the stuck moment

+
Our analytics show a 40% drop between signup and the welcome email's link click, and growth is…

Conversion drops at onboarding email step

Our analytics show a 40% drop between signup and the welcome email's link click, and growth is raising alarms. I’m afraid the email is not reaching users or the copy is failing, but I don’t know whether it’s deliverability, content, or timing. What is the most likely diagnosis and the fastest set of tests to run before next Tuesday to find the cause?

Become — change the pattern

+
Across several maps we produce, touchpoints often list no clear owner or missing metrics, so fixes…

User journeys lack clear ownership at touchpoints

Across several maps we produce, touchpoints often list no clear owner or missing metrics, so fixes languish. This slows product improvements and frustrates growth and support. What habit or governance rule should we introduce so every touchpoint has an owner, a success metric, and a review cadence, and how do we implement that without creating heavy bureaucracy?

Next to this one

Other docs and databases work people do in Notion.

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.