Journey editor

Use the journey editor when the team needs to review the customer story, clean up item details, narrow a large map, and decide what to do next from one place. The editor is one work surface with several views and controls. You are changing the lens on the same journey, not creating separate copies of the work.

​

Editor structure

The journey editor combines:

• the journey canvas
• stage and step structure
• item group and persona tabs
• grid, table, and matrix views
• search and filters
• visible property controls
• command and action menus
• collaboration cues
• access to version history and settings

Add screenshot of the journey editor header, item group tabs, and main canvas here

​

Add and organize stages and steps

Stages and steps are the structure of the journey. Use stages for broad phases such as discovery, evaluation, setup, first value, or renewal. Use steps for specific customer moments inside those stages, such as:

• Customer reads pricing page
• Customer connects Slack
• Customer invites teammate
• Customer receives failed-payment email

Good step names are written from the customer’s point of view. That makes the journey easier to review, search, and improve. When editing structure:

1. Add the major stages first.
2. Add only the customer steps that matter for the journey’s decision.
3. Keep internal team work out of the customer path unless the customer experiences it.
4. Attach items to the step where the evidence or decision belongs.
5. Reorder stages or steps when the flow changes.

​

Grid view

Use grid view when you need to understand the customer experience in order. Grid view is best for:

• reviewing the end-to-end path
• explaining the flow to teammates
• spotting where friction builds across stages
• running planning sessions or workshops
• placing items close to the customer moment they support

Start with the customer path, then inspect the items attached to the moments that matter most.

​

Table view

Use table view when you need a field-level scan of the journey. Table view is useful for:

• sorting by priority, owner, status, or updated date
• finding stale items
• cleaning up incomplete fields
• auditing what changed recently
• reviewing many items without moving through the whole map

Table view is often the fastest way to keep a mature map tidy.

​

Matrix view

Use matrix view when the team is deciding what to work on next. Matrix view is best for:

• comparing candidate opportunities
• comparing possible solutions
• discussing impact and effort tradeoffs
• separating quick wins from expensive bets

The goal is not to replace judgment. It is to make prioritization easier to see and discuss. Read Prioritize with customer context for the full decision workflow.

​

Item group and persona tabs

Use item group tabs to focus the editor on one kind of context, such as touchpoints, insights, opportunities, solutions, or metrics. Use personas when the customer type matters to the journey. Personas can be reviewed in grid or table view. Tabs help the team avoid scanning every item type when the current job is narrower.

​

Search

Use search when you know the problem or theme, but not where it lives. Good search cases:

• you remember the customer problem but not the item title
• you want all references to one concept across the journey
• you want to jump to the right stage or step indirectly

Custory uses a hybrid search model in the journey editor and table views:

• exact-text search for direct matches
• semantic search for meaning-based matches

That means a query like setup friction can still surface an item titled Teams stall before first integration even when the wording is different. Keyword search can match against:

• item title
• item description
• item status
• item type or property values
• owner names
• stage name
• step name

Search works best when items are written in plain, specific customer language.

​

Filters

Use filters when you want to narrow the working surface on purpose. Common filter cases:

• show only one item group
• show only items owned by one person
• show only high-priority opportunities
• show only stale assumptions or missing metrics
• focus on one stage or step

Depending on the surface and item group, you can filter by fields such as:

• group
• status
• owner
• type
• priority
• impact
• effort
• created date
• updated date
• stage or step context

Filters work as a temporary lens, not a report export. In the current editor flow, active filters combine with AND logic. Every condition must be true for an item to appear. Example:

• Group is Opportunities
• Priority is High
• Owner is Founder

Only items that match all three conditions remain visible. Use search and filters together when the journey is large.

​

Visible properties

Use visible properties when the journey has many fields but the current review only needs a smaller surface. Examples:

• show owner and status during cleanup
• show impact and effort during prioritization
• show target and direction while reviewing metrics

Property visibility is a working preference. It helps the current review stay focused without changing the underlying item data.

​

Saved working preferences

Custory remembers your editor setup for each journey in your browser, including view, filter, and visible-property preferences. That is useful when different people reopen the same map for different jobs:

• one person may keep a regular priority-review view
• another may keep an owner-based cleanup view
• another may focus on one item group repeatedly

Some entry points open the editor with a temporary group focus. That temporary focus helps the current visit but does not overwrite your saved setup.

​

Command menu

Use the command menu when you want to jump quickly without scanning the whole map. Press Cmd+K or Ctrl+K to open it. From there, you can:

• search matching items
• add a new item
• open AI chat
• open guide mode

​

Action menus and exports

The editor settings or action menu includes common journey-level actions such as:

• Journey Settings
• Version History
• Export CSV
• Duplicate
• Delete

Use Export CSV when you need a lightweight offline review, handoff, or audit outside Custory. Use Journey settings for journey-specific configuration. Use Version history when you need to inspect earlier snapshots, label important states, or restore a prior version safely.

​

Undo and redo

Use undo and redo when a cleanup pass or structural change goes too far. The usual shortcuts are:

• Cmd/Ctrl + Z for undo
• Cmd/Ctrl + Shift + Z for redo

For larger recovery needs, use Version history instead of trying to manually reverse a long editing session.

​

Basic collaboration

The editor supports live collaboration with:

• presence avatars
• cursor and editing cues
• shared comments on items
• immediate visibility into ongoing work

Live visibility helps people coordinate, but it does not replace ownership. In live sessions, agree on which part of the journey each person is touching, narrow the surface with views or filters, and say when a larger change is about to happen. Cursor tracking depends on teammate presence. If you are the only person in the journey, you may not see live cursor activity because there is no one else to display. Use comments for the reasoning that should stay attached to the journey or item. Use Version history for recovery and snapshot review.

​

AI in the editor

AI as a workspace member is available directly where the work happens. Use it to:

• draft or improve content
• review the current journey
• summarize evidence
• help create follow-up work
• work against connected integrations

​

Practical review patterns

​

Weekly priority review

Use:

• search for a theme such as activation, pricing, or handoff
• filter to opportunities
• narrow to high priority
• show impact, effort, confidence, and owner

This gives you a short list of what deserves attention now.

​

Delivery follow-up

Use:

• table view
• filter to solutions
• narrow by owner
• sort by updated date

This gives you a quick view of what is moving, what is stuck, and what looks stale.

​

Validation sweep

Use:

• filter to insights
• narrow to assumptions
• search for a product area such as onboarding or billing

This helps the team separate what it knows from what it still needs to confirm.

​

Common mistakes

​

Advanced editor workflows

Keep these pages separate because they cover deeper workflows:

• Version history for snapshots, labels, preview, and restore
• Journey templates for reusable starting structures
• Nested journeys for parent-child journey structure
• Building blocks for reusable items across journeys
• Journey settings for journey-specific configuration

​

What good looks like

A healthy editing habit lets the team:

• review the customer story clearly
• find important items quickly
• keep fields and ownership current
• compare priorities from real evidence
• collaborate without overwriting each other’s work
• recover safely when a larger change goes wrong

​

Next step

Read Version history if your next concern is recovery. Read Prioritize with customer context if you are using the editor to decide what to work on next.