Versionen im Vergleich

Version Alte Version 5 Neue Version 6
Änderungen wurden vorgenommen von

Zachary Snow

Thorsten Kamann

Gespeichert am

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.
Auszug

Design Customer Journeys with Problem Statements to describe a User Flow for your product. Extend it with Mockups and Prototypes to visualize. Determine functional and non-functional Requirements for a Customer Journey and link it with Jira issues.

Tipp

This template is available in the German and English language.

In the template for initiatives, you will find the section where all customer journeys for an objective are listed. There is also a button there to create a new customer journey. Clicking on this button will open this template for a customer journey.

Adding a customer journey

Image Added

The template starts with a box where you can enter some important metadata (1). To be able to track the implementation progress of a customer journey

, we at enbl.it

use an Epic in Jira. You can link that directly here. Furthermore, you can specify a contact person and link additional documents to the customer journey.

Image Removed

Next, you can formulate the problem statement (2). Here you will find a table with the individual elements of the problem statement.

Image Removed
For some Customer Journeys,

Sometimes it makes sense to include a preparation phase (3) in which possible solutions are worked out, prototypes are created, and a simple proof of concept is run through. You can enter these activities in the table here and even link them to tasks in Jira.

Image Removed

In the next section you can enter the text of the customer journey

. The excerpt macro, which can also be seen in the figure, is used so that the text you enter here can be read on an overview page of all Customer Journeys. Image Removed

(4). This text will shown on the parent initiative page. Later you can mark text parts as requirements in bold letters.

Adding mock-ups and prototypes (5) can help to visualize the text of the customer journey in the product development process. As the saying goes, a picture is worth a thousand words.

After clarifying what the solution to the problem from the problem statement looks like, the next task is to determine the functional and non-functional requirements.
In the functional requirements (6), you describe which functions the product must support and link the appropriate user stories or tasks.

Non-functional requirements (7) describe more general requirements regarding quality, security, etc. Again, you can link the requirements to user stories or tasks as needed.

Image Removed

In this

area

section of the template you can exclude functions or features, which are then not part of the implementation and can be delivered later (8). However, these then require a separate Customer Journey, which only has to describe the delta.

Image Removed

While you are working on the Customer Journey, it will often happen that you have to make decisions. You can document these decisions here (9). This is helpful when looking back to be able to understand the decisions.

Image Removed

The template concludes with a simple question and answer block (10). If any content-related questions arise during filling, you have a central place here where you can deposit them. This way, others who have similar questions can share them.

Image Removed