Practice area 1

Out of 9

Mapping journeys dynamically


Mapping dynamic journeys includes the activities, methods and tools that build an interconnected information system across an enterprise. It is the practice of converting static journey maps into dynamic ones that can be managed on-goingly. This practice area combines a range of mapping tools, such as Journeys, Service Blueprints and Systems Architecture and technology maps. It includes dynamic elements, including the creation of map hierarchies, metrics, tags and linking of related information assets.

What activities, methods and tools make up this practice?

Survey respondents first rated the relevance of each practice (0–5, from 'not relevant at all' to 'very relevant'). For practices scoring 3 or higher, respondents scored their organisation's effectiveness in applying them (0–5, from 'not effective at all' to 'very effective'). The chart above shows both the range and average scores for relevance and effectiveness across each practice.

Avg relevance 2.01–3.98 · Avg effectiveness 2.67–3.72
12345
Journey mapping
Service blueprinting
Journey hierarchy
Experience framework
Journey metrics
Linking, tagging & filtering information
Integrating journey assets
Utilising AI tools
RelevanceEffectivenessAverage

Insight

Organisations demonstrate robust mapping capabilities but are less proficient in building and managing dynamic elements

Between 54% and 71% of respondents rate foundational mapping practices, such as evidence-grounded Journey Mapping, Service Blueprinting, Journey Hierarchies, and the integration of historical journey assets, as very or extremely relevant. These practices show the narrowest gap between perceived relevance and effectiveness across all practices, which means that organisations not only value them, but are good at applying them. Conversely, applying dynamic elements and data-centric capabilities remain underused, as only about a quarter of respondents consider journey metrics, linking, or tagging highly relevant or effective.

Insight

Organisations demonstrate robust mapping capabilities but are less proficient in building and managing dynamic elements

Between 54% and 71% of respondents rate foundational mapping practices, such as evidence-grounded Journey Mapping, Service Blueprinting, Journey Hierarchies, and the integration of historical journey assets, as very or extremely relevant. These practices show the narrowest gap between perceived relevance and effectiveness across all practices, which means that organisations not only value them, but are good at applying them. Conversely, applying dynamic elements and data-centric capabilities remain underused, as only about a quarter of respondents consider journey metrics, linking, or tagging highly relevant or effective.

Insight

Organisations demonstrate robust mapping capabilities but are less proficient in building and managing dynamic elements

Between 54% and 71% of respondents rate foundational mapping practices, such as evidence-grounded Journey Mapping, Service Blueprinting, Journey Hierarchies, and the integration of historical journey assets, as very or extremely relevant. These practices show the narrowest gap between perceived relevance and effectiveness across all practices, which means that organisations not only value them, but are good at applying them. Conversely, applying dynamic elements and data-centric capabilities remain underused, as only about a quarter of respondents consider journey metrics, linking, or tagging highly relevant or effective.

Insight

Architecting Journey hierarchies and integrating metrics is an iterative process, and these elements can change over time or as the practice scales

Journey hierarchies, frameworks, linking elements and establishing metrics take time to get right. Effectiveness in applying them increases as practices evolve, whereas Evidence-based mapping and Service Blueprinting work well from the start. Low effectiveness in applying dynamic elements presents as a generalised weakening of all other practice Areas. Those that are less effective in dynamic elements are less effective across all other practice areas. It especially impacts an organisation’s ability to apply Data Visualisation (Practice Area 4).

Insight

Architecting Journey hierarchies and integrating metrics is an iterative process, and these elements can change over time or as the practice scales

Journey hierarchies, frameworks, linking elements and establishing metrics take time to get right. Effectiveness in applying them increases as practices evolve, whereas Evidence-based mapping and Service Blueprinting work well from the start. Low effectiveness in applying dynamic elements presents as a generalised weakening of all other practice Areas. Those that are less effective in dynamic elements are less effective across all other practice areas. It especially impacts an organisation’s ability to apply Data Visualisation (Practice Area 4).

Insight

Architecting Journey hierarchies and integrating metrics is an iterative process, and these elements can change over time or as the practice scales

Journey hierarchies, frameworks, linking elements and establishing metrics take time to get right. Effectiveness in applying them increases as practices evolve, whereas Evidence-based mapping and Service Blueprinting work well from the start. Low effectiveness in applying dynamic elements presents as a generalised weakening of all other practice Areas. Those that are less effective in dynamic elements are less effective across all other practice areas. It especially impacts an organisation’s ability to apply Data Visualisation (Practice Area 4).

Methods, tools and activities that make up this practice area

Grounding journeys in evidence

Building maps based on customer research, behavioural analytics and transactional data rather than primarily by internal assumptions (or where assumptions are used, these are labelled on maps)

Service blueprinting

Using Journeys to develop current-state service blueprints, including business processes, enterprise system touchpoints, business architecture and specifying what teams are responsible for

Experience framework

Identifying high-level lifecycle stages that define the end-to-end experience across the organisation, which journeys are organised within

Journey metrics

Defining and collecting a range of user and performance metrics at each journey level and connecting them with live data feeds to maintain automated regular updates, or establishing a regular rhythm to update them manually

Linking, tagging and filtering information

Linking research assets across journeys, using visual tags to separate insights from assumptions, and or to filter by different users, segments or personas

Leverage historical journey assets

Utilise existing journey map assets, updating and validating them over time

Utilising AI tools

Utilising AI tools to map journeys, synthesise research insights or connect journey information

What challenges do organisations experience when mapping dynamic journeys?

The following challenges summarise the core themes identified across participant interviews. Survey participants rated the frequency of each challenge from 1-5. The graph below compares average scores by different stages of practice:

EmergingEstablishedLeading
Assumption-biasQuantitative gapInconsistent terminology,templates or conceptsData provenance,integrity and metricsMapping scopeand intentConflict overjourney assets

Insight

Linking data to maps is a core problem for many organisations

The top two challenges are both about data. Teams lack the quantitative evidence to complement research and lack clarity on what to measure and where the data comes from. Fewer than 10% rarely or never face data provenance problems.

Insight

Linking data to maps is a core problem for many organisations

The top two challenges are both about data. Teams lack the quantitative evidence to complement research and lack clarity on what to measure and where the data comes from. Fewer than 10% rarely or never face data provenance problems.

Insight

Linking data to maps is a core problem for many organisations

The top two challenges are both about data. Teams lack the quantitative evidence to complement research and lack clarity on what to measure and where the data comes from. Fewer than 10% rarely or never face data provenance problems.

Insight

Establishing evidence is the greatest hurdle for organisations in the early stages of their practice

55% of respondents in their early stages of their journey management practice face challenges associated with assumption bias (journey maps based solely on high-level stakeholder hypotheses and internal consensus, without the inclusion of direct customer or user research)s often or very often. Challenges associated with quantitative gap (constructing journey frameworks without behavioural analytics or transactional data) are also high 49%.

Insight

Establishing evidence is the greatest hurdle for organisations in the early stages of their practice

55% of respondents in their early stages of their journey management practice face challenges associated with assumption bias (journey maps based solely on high-level stakeholder hypotheses and internal consensus, without the inclusion of direct customer or user research)s often or very often. Challenges associated with quantitative gap (constructing journey frameworks without behavioural analytics or transactional data) are also high 49%.

Insight

Establishing evidence is the greatest hurdle for organisations in the early stages of their practice

55% of respondents in their early stages of their journey management practice face challenges associated with assumption bias (journey maps based solely on high-level stakeholder hypotheses and internal consensus, without the inclusion of direct customer or user research)s often or very often. Challenges associated with quantitative gap (constructing journey frameworks without behavioural analytics or transactional data) are also high 49%.

Insight

As an organisation’s practice stage changes, challenges shift from ‘establishing evidence’ to ‘data provenance, integrity and metrics’.

For advanced-stage practices, assumption bias remains minimal and largely resolved. This means that over time, organisations typically overcome organisational resistance to evidence-based Journey Mapping methods. Instead, governance and data challenges, such as questions of data provenance, metric integrity, mapping scope, and asset ownership, become more frequent. These issues naturally emerge as organisations manage expanding map portfolios and strive to maintain accuracy as data sources, performance metrics, and evidence thresholds change.

Insight

As an organisation’s practice stage changes, challenges shift from ‘establishing evidence’ to ‘data provenance, integrity and metrics’.

For advanced-stage practices, assumption bias remains minimal and largely resolved. This means that over time, organisations typically overcome organisational resistance to evidence-based Journey Mapping methods. Instead, governance and data challenges, such as questions of data provenance, metric integrity, mapping scope, and asset ownership, become more frequent. These issues naturally emerge as organisations manage expanding map portfolios and strive to maintain accuracy as data sources, performance metrics, and evidence thresholds change.

Insight

As an organisation’s practice stage changes, challenges shift from ‘establishing evidence’ to ‘data provenance, integrity and metrics’.

For advanced-stage practices, assumption bias remains minimal and largely resolved. This means that over time, organisations typically overcome organisational resistance to evidence-based Journey Mapping methods. Instead, governance and data challenges, such as questions of data provenance, metric integrity, mapping scope, and asset ownership, become more frequent. These issues naturally emerge as organisations manage expanding map portfolios and strive to maintain accuracy as data sources, performance metrics, and evidence thresholds change.

Challenges that organisations experience

Assumption-bias

Developing journey maps based solely on high-level stakeholder hypotheses and internal consensus, without the inclusion of direct customer or user research.

Quantitative Gap

Constructing journey frameworks without behavioural analytics or transactional data, leading to a lack of proportional representation

Inconsistent terminology, templates or concepts

Describing pain points, opportunities or solutions inconsistently across maps or teams, resulting in quality issues.

Data provenance, integrity and metrics

Uncertainty regarding what to measure and track across the journey, and a lack of clarity on where that data is housed, or a lack of transparency of data sources

Mapping scope and intent

Mapping too many journeys at once, over-engineering maps, mapping the wrong state (current vs. future) or mapping without clear business goals to manage towards

Conflict over journey assets

Ambiguity over whether to invest in remapping journeys or to leverage existing internal assets of varying quality.

Get new findings
& report updates

By subscribing, you agree to receive communications about the State of Journey Management report.

© 2026 Stickdorn Service Design GmbH

Made with Framer by Sayali Bharambe