Story mapping is a practice that can be applied to many verticals to organize and visualize a new project, including (but not limited to); customer or product journey, go-forward plans, or basic project management. The process is useful when collaborating with multiple stakeholders to understand key objectives, communicate on workflow, and visualize progress.
Story maps are most prevalent in software development, especially among teams practicing agile methodology. However, they can be a valuable tool for any industry. Of course, the specifics of a map will differ based on the vertical and project. Follow these steps to use a story map for any new initiative.
1. Define Your Vision and Goals
What is the overall objective of your project? Are you creating a new internal system, working with an outside client to develop a service, building a website, visualizing your customer journey? Whatever it may be, identify the main goal of your project so that you can work backward from there, to start your story map.
Once you identify your end target, the next step is to outline your vision. Think of this step as telling the initial story. Here are a few examples of initial stories:
E-commerce site– walk through the customer journey. Customer searches for an item, finds your website, views products, selects a specific product, looks at images, puts a product in the cart, enters payment information, enters shipping information, confirms the order.
Planning an event– walkthrough a guest’s experience. The guest arrives, valets their car, checks their coat, finds their table, has cocktails, participates in the silent auction, enjoys their meal, watches live entertainments, departs with their thank-you bag.
Developing a job board– outline the job seeker’s journey. The applicant uploads a resume, applicant browses open jobs, the applicant finds an appropriate job and applies, the employer is notified of the new applicant and can choose to engage or not, communication is established.
The key with this step is to understand your end game (goal), and the ideal storyline (vision) you would like to happen to get there.
2. How to Establish Your Strategy
Knowing where to start when creating a strategy can be tricky. Take each step of the initial story and group and define activities from there. Ask yourself; what needs to be ideated or created to make that step occur? You might need to break down each step further if the process is complex.
After you establish what needs to happen, make a list of specific activities or tasks to complete. Intuitively group activities into stages. For example, what are the tasks that need to be done first? In many software-related story maps, these individual tasks are referred to as the backlog.
Assign each task to a person or team, ensure they understand the task, and set a firm deadline. Communication plays a crucial role in story mapping, no matter if you have a team of five or two-hundred. Each stakeholder in the story map should have a point person they can turn to for issues; this will help you avoid roadblocks.
3. Determine the Best Way to Visualize your Roadmap
This is the step of actually putting together a physical story map (often referred to as a roadmap) for your project. Original practices used a white-board or a large open wall space, with colored post-its or index cards to outline the roadmap. The main concept being that everyone could visualize steps and assignments, and physically move cards as they progress.
Traditional roadmaps generally have the following stages; backlog (unassigned tasks), in progress (assigned tasks), testing (testing the first iteration), and completed.
If you don’t have all employees or stakeholders in one physical office space, or you would prefer a digital alternative, there are many story-mapping programs. These platforms allow for interactive, usually cloud-based, story maps, accessible from any location, with real-time updates. A few popular options include:
Cardboard– takes the post-it format and makes it digital, very customizable, offers integrations with other software and programs, with free and paid versions available.
Realtime Board– also uses the digital post-it format for their visual story maps. Realtime offers multiple story-board templates to choose from, a benefit to new story-mappers. The platform is customizable, with third-party integrations, and free or paid subscriptions.
Trello– a digital project management system that you can also use for story mapping. Trello uses lists and boards to organize information, but is very interactive, and can integrate popular programs like GoogleDocs, Dropbox, or Microsoft OneDrive, as well as the Atlassian suite products.
4. Pro-Tip: Translate Software-Specific Principles for All Story Maps
While every story map will differ depending on the industry, company, and campaign, there are main software and agile principles that apply to any project.
Deliver important requirements first.
If you’re working on a large project with many moving parts, determine the must-haves. Then move those to the front of your story map, to work on and deliver them first. Items that are non-essential, but would be nice to have, should be given second or third priority. This way, if the project takes longer than expected—which it often does—you can cut those tasks.
Break down complex requirements.
If there’s a large requirement or task, break it up into smaller more manageable pieces. Even though you might not physically be working off of post-its or index cards, break down updates or tasks as if you are. If the task description can’t fit on a post-it, divide it into multiple tasks. This can also help you divide less critical components, to move them to a later time frame.
Focus on communication and progress documentation.
Agile software teams have daily or weekly stand-up meetings, where they quickly go over all of the need-to-know information, give progress reports and discuss roadblocks or issues. From here, if further meetings need to happen, they break off into to one-on-ones. While you might not need to have frequent meetings, communication should be key. Further, make sure to document the progress of each task, whether that be on an actual board or the digital story map. Each stakeholder should be able to see progress and understand the current stage of each assignment.
Ready to Create Your Story Map?
Story maps offer a dynamic process to organize any type of project with multiple stakeholders, stages, and tasks. If you’re facing a challenging new campaign, try creating a story map to set progress in motion.
Here at FeedOtter, something that’s usually on our minds is how to streamline the process of creating routine, content emails and newsletters that you can easily push to your email sending platform. And what better way to automate content emails than adding an RSS feed into Pardot? Let’s look at the need for an RSS […]
When it comes to marketing, emailing your clients and prospects is a great touchpoint for interaction with customers. Using Marketo’s A/B Subject line test will help you ensure you have the perfect attention-grabber for your emails. When emailing, many emails go straight to the trash or unread. How can this be reduced? According to Yes […]
Working with email automation and customers sending website content to their subscribers, we see lots of questions about high unsubscribe rates and what our best tips for reducing unsubscribes on routine content emails are. Gaining lead subscribers is one thing, keeping them can be just as difficult for marketers. Reducing Unsubscribes The first step to […]