Map what matters

Workflow, feature, or user journey?

Workflows, features, and user journeys are related, but they are not the same thing.

For product measurement, the distinction matters because each one points to a different level of thinking:

features describe what the product provides
user journeys describe the wider experience
workflows describe the behaviour users perform to complete a task

A feature might be part of a workflow. A workflow might sit within a wider journey. But when a team is deciding what to measure, the workflow is often the most practical starting point.

Quick comparison

Level	Describes	Example	Measurement use
Feature	What the product provides	Registration form	Useful for implementation and product scope
User journey	The wider experience	Becoming a customer	Useful for context across channels and touchpoints
Workflow	The behaviour users perform to complete a task	Register for an account	Usually the best starting point for product measurement

Strong summary: features describe capability, journeys describe context, workflows describe measurable behaviour.

The difference

A feature is part of the product. It is usually named from the organisation’s point of view.

A user journey describes the broader path a user takes before, during, and after interacting with a product.

A workflow describes the sequence of meaningful behaviour a user performs to achieve something.

For example:

“account system” is a feature area
“becoming a registered user” may be part of a user journey
“register for an account” is a workflow

The feature describes the product capability. The journey gives context. The workflow gives the team something measurable.

Why the distinction matters

Measurement becomes weak when these terms are used loosely.

A team might say:

We need to measure onboarding.

That could mean:

the wider onboarding journey across email, product, support, and first use
a set of onboarding screens
an onboarding feature
a workflow such as creating an account, setting preferences, or completing setup

Each interpretation leads to different events, metrics, and decisions.

If the team does not define the level clearly, measurement becomes vague. Events may be added without structure, metrics may describe different behaviours, and dashboards may combine things that should be understood separately.

Features are product capabilities

Features can be measured, but they are not always the best starting point.

A feature might contain several workflows, or support one step within a larger workflow. For example, a payment integration is a feature, but users are usually trying to complete checkout. A document upload feature may support a mortgage application workflow. A recommendations engine may support a home retrofit planning workflow.

A better question is:

What user workflow does this feature help complete?

This keeps measurement connected to behaviour rather than internal product structure.

Journeys give context

User journeys are useful for understanding the wider experience. They can show motivation, touchpoints, channels, expectations, pain points, and what happens before or after product use.

But journeys are often too broad for instrumentation unless they are broken into measurable workflows.

For example, “becoming a customer” may involve:

discovering the product
comparing options
registering for an account
completing setup
making a purchase
receiving support
returning later

That journey may contain several workflows. Each workflow may need its own events, metrics, and decisions.

Workflows sit at the measurement level

A workflow is usually the right level for product measurement because it connects user intent to observable behaviour.

For example:

User journey:
Become a customer

Workflow:
Register for an account

Workflow steps:
View form → enter details → submit form → verify email → access product

Feature examples:
Registration form
Email verification
Account creation

The journey gives context. The features provide functionality. The workflow gives the team a measurable sequence.

How to choose the right level

Before defining events or metrics, label what you are discussing.

Use a feature when talking about what the product provides:

registration form
saved search
payment integration
document upload
recommendation engine

Use a user journey when talking about the wider experience:

becoming a customer
applying for a mortgage
planning a home retrofit
choosing a subscription
preparing for a trip

Use a workflow when talking about measurable behaviour:

register for an account
complete checkout
upload required documents
create a retrofit plan
compare subscription options

If the thing is too broad, break it into workflows. If it is too narrow, connect it back to the task it supports. If it is a feature, ask what user behaviour it enables.

How to apply this

When measurement feels unclear, ask:

What is the user trying to achieve?
Which workflow describes that behaviour?
Which features support the workflow?
What events would show progress?
What metrics would help us understand whether the workflow is working?

This keeps measurement connected to user behaviour, not just product architecture.

What is a workflow?
Workflow steps and user behaviour
Example: mapping a registration workflow

Key takeaway

Features describe what the product provides. User journeys describe the wider experience. Workflows describe the behaviour users perform to complete a task.

For product measurement, start with the workflow. It gives the team a clear, measurable link between user intent, product behaviour, events, metrics, and decisions.