Map what matters

Entry points, exits, and completion

Every workflow needs a clear start, a clear end, and a way to understand what happens between them.

Entry points show where users begin. Exits show where they leave, pause, abandon, or fail to continue. Completion shows whether the workflow reached its intended outcome.

For product measurement, these definitions set the boundary of the workflow. Without them, a team may know that a workflow is underperforming, but not whether users are failing to start, leaving part-way through, or completing something that does not reflect the intended outcome.

Boundary comparison

Measurement choice	Entry point	Completion point	What the metric means
Narrow setup view	View registration form	Verify email	Measures whether users complete account setup
Product access view	Start account creation	Access product for the first time	Measures whether registration gets users into the product
Form-only view	View registration form	Submit form	Measures form completion, not registration completion

The boundary is not a technical detail. It changes the meaning of the metric.

Entry points show where users begin

An entry point is where a user starts a workflow.

For account registration, entry points might include:

clicking “create account”
opening a registration link from an email
arriving from a marketing page
selecting registration during checkout
being invited by an organisation

Entry points matter because users may arrive with different intent and context. A user required to register during checkout may behave differently from someone creating an account from the homepage.

If the team treats all entry points as the same, the measurement may hide useful differences.

Exits show where users leave

An exit is where a user leaves, pauses, abandons, or fails to continue the workflow.

For registration, users might exit when they:

view the form but do not enter details
enter details but do not submit
encounter a validation error
submit the form but do not verify their email
verify their email but do not access the product

Not every exit is a failure. A user may pause because they need information, switch device, wait for an email, or return later.

The point is to make exits visible enough for the team to understand where the workflow loses momentum.

Completion defines the outcome

Completion is the point where the workflow has achieved its intended outcome.

For account registration, completion might mean:

the account has been created
the email has been verified
the user has accessed the product for the first time

Each definition produces a different metric. If completion means “account created”, the workflow may look healthier than it is. Users may have accounts, but still not reach the product.

Completion should reflect the outcome the team cares about, not just the easiest event to track.

The boundary changes the metric

The way a team defines entry and completion changes what the metric means.

For example:

Entry:
User views registration form

Completion:
User verifies email

This measures whether people complete account setup.

A different boundary measures something else:

Entry:
User clicks “create account”

Completion:
User accesses the product for the first time

This gives a fuller view of whether registration helped the user reach the product.

Neither definition is automatically right or wrong. The right definition depends on the decision the team needs to support.

Use exits to diagnose problems

The same completion rate can hide different problems.

For example:

View form
↓
Enter details
↓
Submit form
↓
Verify email
↓
Access product

If many users exit before submitting the form, the team may investigate the form design, required fields, error handling, or perceived effort.

If many users submit the form but do not verify their email, the team may investigate the confirmation screen, email content, deliverability, resend behaviour, or user expectations.

Exit points help the team find the part of the workflow that needs attention.

How to apply this

When defining a workflow, ask:

where does the workflow begin?
what signals that the user intended to start?
where can the user pause, abandon, or fail?
what counts as completion?
does completion reflect the user outcome or only a system state?
what decision will this definition support?

Once the entry point, exits, and completion point are clear, the team can decide what events to capture and what metrics to create.

Common mistakes

Common mistakes include:

defining completion too early, such as treating “form submitted” as registration completion
ignoring entry points and combining users who arrive with different intent
treating all exits as failures, even when some are temporary pauses or expected behaviour
choosing the easiest event to track rather than the outcome the team cares about

These mistakes make workflow metrics harder to interpret and easier to misuse.

Metric quality and confidence
Example: mapping a registration workflow
Workflow catalogue template

Key takeaway

Entry points, exits, and completion define the boundary of a workflow.

That boundary changes what the metric means.

Define the boundary before deciding what events to capture or what metrics to report. Otherwise, teams may compare numbers that appear similar but describe different behaviours. Entry points, exits, and completion define the boundary of a workflow.

They help teams understand where users begin, where they leave, and whether the workflow achieved its intended outcome.

Define these boundaries before deciding what events to capture or what metrics to report.