Your first journey

Build one usable journey from the draft, template, or blank journey you chose during Quickstart. By the end, you will have a map your team can review, prioritize from, and update in real work.

​

Outcome

Use this walkthrough to build a first journey around one concrete flow. We will use trial to paid, but the same pattern works for activation, onboarding, retention, or another narrow customer journey.

​

Prerequisites

You do not need a finished map. You do need:

• one narrow flow worth tracking
• a starting point from Quickstart: AI import, template, or blank journey
• one editor who will keep the journey current
• enough evidence for a rough first pass, such as support notes, analytics, or call takeaways

If you have not chosen the starting path yet, go back to Quickstart, Import journey with AI, or Journey templates first.

​

Example journey

​

1. Add the major stages

Start with broad phases. For trial to paid, a practical first pass is:

• Discovery
• Evaluation
• Trial signup
• Setup
• First value
• Upgrade decision

If you are editing an imported draft or template, remove extra stages now. A shorter structure is easier to review than a complete-looking structure that no one trusts.

​

2. Add customer steps inside each stage

Inside each stage, add only the customer moments that matter for this flow. Write from the customer’s point of view. Customer connects Slack is easier to review than Activation workstream.

​

3. Attach the first useful items

Once the structure is readable, add a small set of items. You do not need to fill the whole map. Good first items for this journey: Use Item details and fields if you need the exact field and status reference while you fill items in.

​

4. Link the evidence to the problem and the response

Connect the items so the reasoning stays visible:

• touchpoint: Pricing page
• insight: Plan differences feel unclear to smaller teams
• opportunity: Reduce pricing confusion before signup
• solution: Simplify the comparison section
• metric: Trial signup conversion

If you skip this step, the journey stays a set of notes. Linking keeps the customer moment, the learning, and the follow-up decision together.

​

5. Invite the smallest useful editor group

Invite the people who will actually maintain the map first:

• founder or product lead
• support or customer-facing lead
• one engineering or product partner

Keep broader visibility for later. If people only need to follow the journey, add them as viewers instead of editors. Use Manage your team for role details.

​

6. Review the journey in one real meeting

Run one short review session:

1. Walk the journey from left to right
2. Ask where the biggest friction appears
3. Check which points have real evidence
4. Turn one or two important insights into opportunities
5. Decide one next action

If the team can reach one clear next action from the map, the first journey is already doing its job.

​

Result

After this walkthrough, your first journey should have:

• clear stages
• customer-centered step names
• a few high-signal items
• at least one visible evidence-to-action chain
• one next action the team agreed on

​

Related reference

• Read From mapping to shipping when you are ready to choose what to act on next.
• Read Journey editor for views, filters, permissions, and journey actions.
• Read Items and Item details and fields when you need the item model or exact field behavior.
• Read Weekly workflows when you want a repeatable review rhythm.