Avion Knowledge Base
avion.ioSign inSign up
  • 👋Introduction
  • 👉Getting started
    • What is Avion?
    • Define your product backbone
    • Scoping and prioritizing your product
    • Creating your release plan
    • Aligning the team
    • Integrating with backlog tools
  • Docs
    • 👏Core concepts
      • Projects
        • Project team
        • Migrating to projects
      • Organizations
        • Invite a member
        • Remove a member
        • Roles
        • Transfer ownership
        • Configure your path
        • Delete your organization
    • 🚀Story map
      • Story map anatomy
      • Journeys and steps
      • Stories
      • Releases
      • Attachments
      • Tags
      • Personas
      • Labels
      • Dependencies
      • Search and filter
      • Sharing
        • Restricted links
        • Public links
      • Workflow
      • Importing data
        • Import from Excel
          • XLSX import template
        • Import from StoriesOnBoard
      • Exporting data
        • Export to PDF
        • Export to image
        • Export to CSV
        • Export to Excel
      • Rich text editor
        • Keyboard shortcuts
        • Known limitations
      • Keyboard shortcuts
      • Tips
    • 🤝Integrations
      • Backlog tools
        • Set up an integration
          • Authentication
          • Project / board selection
          • Backbone syncing
          • Map story states
          • Additional syncing options
          • Importing data
        • Sync data
          • Pushing
          • Importing
          • Attachments
          • Deleting data
        • Configuration
        • Pause an integration
        • Re-authenticate
        • Remove an integration
        • Maintenance
          • Removing stale webhooks
        • FAQs and troubleshooting
        • Services
          • Jira Cloud
            • Features
            • Set up
            • Permissions required
            • Mapping options
              • Mapping fix versions
            • Epics ~ our thoughts
            • Additional data syncing
              • Mapping custom fields
                • Company-managed projects
                • Team-managed projects
            • Migrating to epic hierarchies
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Verify webhooks
              • JQL import issues
              • Workflow issues
              • Ghost cards (cards with a dashed border)
              • Limitations
              • Jira Cloud or Jira Server
          • Jira Data Center (Server)
            • Features
            • Set up
              • Creating an application link
            • Permissions required
            • Mapping options
            • Additional data syncing
              • Mapping custom fields
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Ghost cards (card with a dashed border)
              • Jira Cloud or Jira Server
              • JQL import issues
          • Azure DevOps
            • Features
            • Set up
            • Permissions required
            • Import using WIQL
            • FAQs and troubleshooting
              • Verify webhooks
              • No Azure DevOps accounts were found for your user
              • Problems communicating with Azure DevOps
              • Work items couldn't be imported
              • Show epics in Azure DevOps backlog
              • Import limits
          • Trello
            • Features
            • Set up
            • FAQs and troubleshooting
          • GitHub
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
              • What types of GitHub Projects are supported?
          • Linear
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
      • Notifications
        • Slack
          • Set up
          • Configure notification settings
          • Remove Slack
      • Design tools and media
        • Figma
        • Adobe XD
        • Axure
        • Framer X
        • Invision Web & Studio
        • YouTube & Vimeo
      • Embed Avion
        • Confluence
        • Confluence Server
        • Notion
        • Coda
    • 🔒Security
      • Single Sign-On (SSO)
        • Setup & Configure SSO
        • Azure AD
        • Google Workspace
        • Okta
        • OpenID Connect
      • Two-factor authentication (2FA)
    • ❓FAQs
      • Attachment file types
    • 💳Billing
      • Plans and pricing
      • Legacy plans
      • Free trials
      • Billing and payments
      • Change your plan
      • Cancel your plan
      • Refunds
      • Startup, student and educational discount
  • Story Mapping Guides
    • How To Story Map — A Simple Example
    • Advantages of Story Mapping
    • A Recommended Workflow
Powered by GitBook
On this page
  • Journeys
  • Steps
  • Stories
  1. Story Mapping Guides

How To Story Map — A Simple Example

Last updated 6 years ago

Journeys

To start with, we need to define the core user journeys in our product. It's important to truly think in terms of user journeys and not technical features. So, examples of some typical user journeys are as follows:

  • Buy a product

  • Register an account

  • Contact the business

  • Top up my balance

  • Learn about the brand

  • Request a call back

  • Download a book

Notice that these all begin with a verb, and they're all written from the user's perspective. This is not a hard and fast rule, but it really helps to get inside the mind of your user. Let's take "Buy a product" as our example. We need to to write this down, either on a post-it, or electronically — like so:

Steps

Once you have a user journey established, you need to define the steps required to achieve the journey. Think of this as all the things the user will need to do from start to finish, at a fairly high level. So, in order to buy a product, the user might need to:

  • Select a product

  • Review product selection

  • Enter delivery details

  • Enter payment details

  • Purchase selection

This can be quite specific to your product. For example, if we had a particularly unique checkout process, this flow should be captured here. However — don't feel tempted to capture the smaller details like "address lookup" or "promo code", as this will all be picked up in user stories. Verbs work well here to, but feel free to tailor this to your own terminology and workflows.

Once you have your steps defined, you write them under the journey the sequence from left to right. In our example this will look like:

Awesome 😎— now we have a really clear outline of the user journey and how they can get from start to finish. Now is the fun part...

Stories

Our task is to now create placeholder user stories that fit into any one of the steps outlined above. The beauty here is that we are not committing to actually develop any of these stories yet, we are merely gathering ideas and requirements. This is a perfect time for stakeholder engagement. This exercise will raise collaborative discussions about how you can innovate along your journey. Some stories might be simple and obvious like:

  • Add to cart button

  • Change item quantity

  • Remove from cart button

  • Pay with debit/credit card

  • Order confirmation email notification

But, make sure you're open to innovation here and jot down more left-field ideas. For example:

  • Pay with Bitcoin/Ethereum

  • Scan item barcode from catalogue / in-store

  • View product on Oculus Rift / HTC Vive

  • Request live demo with hangouts

Story titles should be short and to the point, but not so short that they are not descriptive. There is no need to add story descriptions right now. We need to place the stories that we come up with in the column of the step that they relate to. In our case, that might look like this:

Our single journey. Simple so far, right?
Steps from left to right