Use Journeys to group and show related (or totally unrelated, it’s your call, go wild!) Appcues experiences, and add notes for context and detail. Maybe you’ve encountered this scenario before: you and your team created 5 flows, 10 pins, and 1 banner–all related to one specific project. You need to know (at a glance), document, share the experiences for this project with context. How do you do that right now? A mishmash of whiteboards, screenshots, and docs?

That stuff is time-consuming and boring, so let Journeys help you stop that nasty busy work! We shared one example of creating a journey around a project/goal, but here are a few others:

1. Team: Pull together everything a department or team has created
2. Goal or project: Show what content is live or on deck for a project or singular goal
3. Page: See everything currently live and/or drafted to specific pages
4. Lifecycle: Create journeys for different messages across your user lifecycle (trial, post-purchase, renewal, etc)

Here’s how to do it, using an example from a project we’ve done at Appcues related to encouraging the setup of new integrations (that was a goal or project!). 

Build Guide

Step 1: Add all relevant experiences to the canvas

You can add multiple flows to the same canvas by clicking on the flow button, searching for the related flow, and adding it to the Journey. 

Step 2: Organize, arrange, and add context

Next up, rearrange the content to flow in the way that makes the most sense for what you are trying to showcase.

Then, use notes to add helpful context, notes, and even open questions to the Journey. Some of the top things that are great to include are: 
 

• The goal of these experiences
• Target audience
• Messaging
• Related workflows (like notes for things that are happening outside of Appcues such as emails or notifications to Slack)

Step 3: Share with key stakeholders 

Lastly, be sure to share the experience with others using the Share button to send a link or by grabbing a screenshot. It’s a great way to give an overview to people not directly involved in crafting your user experiences.

For us, we have this pinned on our project team’s notion page and also include it in our weekly progress update so that key team members can quickly see and understand what’s live in our product related to this project. 
 

Happy Building!