◆ Figma

Create user journey maps

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI 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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I show this journey to the product team, make the map easy for someone in support or…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe launched the new signup flow and 40% of people abandon at email verification. The…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the last three releases we consistently lose users between welcome and first successful…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Figma's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.