Process: Journey Mapping

UXmatters has published 7 articles on the topic Journey Mapping.

Top 3 Trending Articles on Journey Mapping

  1. Envisioning Experience Outcomes

    Leadership Matters

    Leading UX transformation

    April 20, 2015

    When your organization’s goal is to differentiate on the experience, you must start every product-development project by defining the experience that you want people to have with your product or service. Companies that differentiate on the experience do not begin by defining feature sets. They first define a vision for the experience outcome that they intend to deliver to their users and customers. Only once your team fully understands the experience outcomes that you want users to have can you make good decisions about what features and technologies would optimally support that vision.

    This is the fourth column in our series about what companies must do if they want to stop producing average user experiences and instead design great experiences. As we have already stated in our previous columns, great UX teams focus on differentiating their companies through design. If that’s your goal, you need to work for a company that shares your aspirations. Read More

  2. Mapping Experiences

    September 26, 2016

    This is a sample chapter from the book Mapping Experiences: A Complete Guide to Creating Value Through Journeys, Blueprints, & Diagrams, by Jim Kalbach, which O’Reilly Media published in May 2016. UXmatters is publishing this chapter with O’Reilly’s permission. Copyright © 2016 O’Reilly Media. All rights reserved.

    Chapter 4: Initiate: Starting a Mapping Project

    Mapping Experiences CoverOne of the most common questions I get in my workshops on mapping is, “How do I begin?” Aspiring mapmakers may see the immediate value in these techniques, yet they have barriers getting started.

    Getting stakeholder buy-in is a common challenge. I’ve been fortunate to have had opportunities to create diagrams of all kinds and have found that stakeholders see the value in mapping only after the process is complete. As a result, initiating an effort requires convincing them up front. Read More

  3. Book Review: User Story Mapping

    April 10, 2017

    User Story Mapping CoverAuthor: Jeff Patton, with Peter Economy

    Publisher: O’Reilly Media

    Publication date: September 2014

    Formats: Paperback, ebook, and Safari Books Online. 324 pages in print.

    Print ISBN: 978-1-4919-0490-9 and 10:1-4919-0490-9

    Ebook ISBN: 978-1-4919-0485-5 and 10:1-4919-0485-2

    List Price: Paperback, $34.99; ebook, $29.99


    If you are or soon will be working in an agile development environment, User Story Mapping: Discover the Whole Story, Build the Right Product, by Jeff Patton is a must read for you. This book details story-mapping techniques and explains why they are important for teams that create products to meet user needs. According to Patton, user story mapping is not about creating set of written requirements, but a way of thinking. Telling stories through words and pictures builds understanding and helps solve problems for organizations, customers, and users.

    The most important job we have is to focus on the outcome and the impact of the products we are creating. Taking a slightly philosophical view of the importance of project outcomes, Patton writes, “The truth is, your job is to change the world.” Read More

Champion Advertisement
Continue Reading…

New on UXmatters