Journey map common security workflow(s)
Overview
My spidey-sense is telling me we are having an issue seeing the forest through the trees on the secure-team. What better way to gain an understanding of how our users are interacting with security products than a journey map!
Let's get a better understanding of the journey user's take while interacting with ~Secure products.
Why journey maps?
From the nngroup:
The benefits of journey maps (and most other UX mappings) are two-fold. First, the process of creating a map forces conversation and an aligned mental model for the whole team. Fragmented understanding is a widespread problem in organizations because success metrics are siloed; it is no one’s responsibility to look at the entire experience from the user’s standpoint. This shared vision is a critical goal of journey mapping, because, without it, agreement on how to improve customer experience would never take place.
Second, the shared artifact resulting from the mapping can be used to communicate an understanding of your user or service to all involved. Journey maps are effective mechanisms for conveying information in a way that is memorable, concise, and that creates a shared vision. The maps can also become the basis for decision making as the team moves forward.
Proposal
Working with UX research we will create journey maps that document the security workflow(s) through interviews with users.
Personas to include in the exercise
Value added and potential outcomes from the exercise
Security Journey maps will set a baseline on the experience we have today and help highlight any gaps that may be present in the application.
Journey maps can answer:
- How and to what degree are users interacting with security tools within the application?
- Are there any gaps in the journey that we need to address?
- Specifically, are users bouncing back and forth between pages to complete a task?
- Specifically, are users taking more steps/actions than necessary to complete a task?
- Are any features or functionality missing from the workflow?
- Are users using other security products to supplement a lack of features/functionality?
Let's target Q1
for this exercise