---
title: Why Segmented Progress Bars Outperformed Single Progress Bars on a Health and Wellbeing Flow
description: Segmented progress bars and upfront priming cut drop-off in a long health onboarding flow by changing how users perceived effort from the start.
image: https://weareaffective.com/hubfs/learning-centre-images/why-segmented-progress-bars-outperformed-single-progress-bars-on-a-health-and-wellbeing-flow.webp
---

[Skip to content](https://weareaffective.com/learning-centre/why-segmented-progress-bars-outperformed-single-progress-bars-on-a-health-and-we#main-content)

[![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com)

- [Home](https://weareaffective.com)
- About Us 
  
    - [Our Story](https://weareaffective.com/about)
    - [How We Work](https://weareaffective.com/how-we-work)
- Our Services 
  
    - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy)
    - [App Design](https://weareaffective.com/app-design-agency)
    - [App UX Design](https://weareaffective.com/app-ux-design)
    - [App UI Design](https://weareaffective.com/app-ui-design)
    - [App Technical Architecture](https://weareaffective.com/app-architecture)
    - [Existing App Audits](https://weareaffective.com/app-audit)
- [Case Studies](https://weareaffective.com/case-studies)
- [Pricing](https://weareaffective.com/pricing)
- [Learning Centre](https://weareaffective.com/learning-centre)

- [Get Started](https://weareaffective.com/get-started)

Expert Guide Series

# Why Segmented Progress Bars Outperformed Single Progress Bars on a Health and Wellbeing Flow

 Table of Contents

A health and wellbeing onboarding flow was losing most of its users before they reached question five. Drop-off rates were sitting somewhere between 80 and 85 percent, and almost all of it happened in the first three or four questions. The progress bar was working, it was moving, it was visible, it was technically accurate. And yet users were leaving anyway.

> A single continuous bar makes the distance ahead feel fixed and large.

The bar was not the only problem, as it turned out. But it was part of one. A single continuous bar across a long multi-step flow does something users feel before they consciously register it: it makes the distance ahead feel fixed and large. Every small step forward produces a tiny movement. The bar barely shifts. And for a user who arrived with no clear sense of how long this would take, that tiny movement reads as a signal to stop.

What we found on that project, and on an OTA travel checkout we redesigned separately, is that progress indicators are not neutral information displays. They shape how users read effort, and [effort perception is what drives completion](https://weareaffective.com/user-psychology-app-design). The design of the bar, what it breaks into, and what you tell users before they even start: these are the variables that matter.

## What a Progress Bar Actually Communicates to a User

A progress bar carries two messages simultaneously. The first is positional: you are here, and the end is there. The second is emotional: this is worth continuing. Most designers focus entirely on the first. The second is the one that determines whether the user stays.

Effort perception is not the same as actual effort. A user completing ten questions across a well-structured segmented flow and a user completing ten questions across one continuous bar face identical objective effort. Their subjective experience of that effort differs, sometimes substantially. The bar shapes what the work feels like, not just what it measures.

Progress indicators also communicate something about the product itself. A bar that moves in tiny, barely perceptible increments signals a long, undifferentiated process. It says: all of this is one thing, and you are not very far through it. For a health and wellbeing flow where users are being asked personal questions before they have any established relationship with the product, that signal lands as friction rather than guidance.

What a well-designed indicator communicates instead is proximity to the next small win. [Behavioural psychology has established that people](https://weareaffective.com/learning-centre/how-to-redesign-an-onboarding-flow-for-the-emotional-state-the-user-actually-arr) are more motivated by progress within a visible sub-goal than by distance from a distant overall goal. The bar needs to give users something close enough to feel achievable, not just a faithful representation of where they sit in a 25-step process.

## Why Single Progress Bars Fail in Long Multi-Step Flows

A single incremental bar across a long flow creates what might be described as a flat reward curve. Each step produces roughly the same visual movement, the same small shift in position. In a five-step flow, that is fine: each step feels like genuine progress. In a 20 or 25-step flow, each step feels like almost nothing.

The problem compounds early. A user at question three of 25 sees the bar at around 12 percent. That 12 percent is accurate. It is also demoralising, because the work required to get there felt real and the progress shown feels negligible. The gap between effort invested and progress displayed creates a mismatch that, for many users, becomes a reason to leave.

Analytics data can reveal this clearly: [drop-off tends to concentrate at exactly](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl) the points where the bar moves least relative to the user's recent effort. On the health and wellbeing product, the 80-85 percent drop-off we were seeing happened in those first three or four questions. Users had already committed to starting, had already answered something personal, and were already leaving. The bar's failure to reflect meaningful progress was a factor.

There is also the problem of unpredictability. Without section breaks, a user cannot easily judge whether the remaining distance is five questions or fifteen. That uncertainty makes it harder to commit to continuing, because the cost of continuing is unknown. A segmented bar solves this by making each section a bounded, comprehensible unit.

## UX/UI design built around *real* psychology

We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package.

[See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started)

No commitment

## How Segmented Bars Change the Way Users Read Effort

A segmented progress bar reorganises the same total effort into a series of smaller, visible completions. Instead of one long bar inching forward, the user sees a bar divided into named or numbered sections, with progress tracked within each section independently. Completing a section feels like finishing something, even though the overall process continues.

On the health and wellbeing product we worked on, we replaced the single overall bar with a segmented view that showed progress within each section. The total number of steps did not change. What changed was how those steps were grouped and displayed. Users could see that they were almost through one section, even when they were not very far through the overall process. That proximity to a small completion had a measurable effect on how far they continued.

> Users could see they were almost through one section, even when far from the overall completion.

The psychology behind this maps to the [goal-gradient effect: people accelerate their effort](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you) as they approach a goal. Segmented bars create multiple such approach moments within a single flow. Each section end is a mini-goal, and the user experiences several instances of near-completion and achievement rather than one distant, slowly approaching one.

It also changes what the bar asks of the user cognitively. Rather than holding a vague sense of "I'm not very far through this", the user can make a specific, accurate judgement: "I'm nearly done with this section." That clarity reduces the uncertainty that makes abandonment feel like a reasonable choice.

## The Health and Wellbeing Case: What We Changed and What Happened

On the health and wellbeing onboarding flow, we made two structural changes. The first was replacing the single progress bar with a segmented one. The second was introducing [upfront priming before the flow began](https://weareaffective.com/learning-centre/5-user-testing-methods-that-will-save-your-app-from-failure). The segmented bar produced an uplift of around 20-25 percent in completion rates compared to the original single-bar configuration.

The mechanics of the segmented bar were straightforward. We grouped the existing questions into thematic sections, named each section, and gave users a view of progress within the current section alongside a visual overview of how many sections remained. By aggregating steps into subsections, users had a more granular sense of where they were and a more accurate ability to judge how much further they had to go, rather than interpreting one long bar that moved by a tiny amount per question.

Group the questions in your multi-step flow into thematic sections before you design the progress indicator. The grouping logic should come first, and the bar should reflect it, not the other way around.

The improvement came from two things working together. Users could see imminent completion of each section, which gave them a reason to push through to the end of that unit. And the sections made the remaining effort legible: you are in section two of four, and section two has three questions left. That is a specific, manageable piece of information. A single bar at 28 percent is not.

Completion going from around 15-20 percent to something in the 40-45 percent range from bar redesign alone represents a real change in user behaviour, driven entirely by how progress was displayed rather than by what the user was being asked to do.

## Upfront Priming: The Variable That Mattered Even More

The segmented bar improved completion by 20-25 percent. Upfront priming did something bigger. On the same health and wellbeing flow, we tested two versions: one that told users what to expect before they began, and one that showed a progress bar with no prior context. Without priming, drop-off was sitting at 80-85 percent, mostly in the first few questions. After we introduced an upfront explanation of what the process involved and approximately how long it would take, completion rates rose to around 95 percent.

That is a near-complete reversal of the abandonment pattern. And it happened before the user had answered a single question. The priming screen arrived before any progress bar became relevant, which is partly why it had such a pronounced effect.

What priming does is reframe the user's relationship to the unknown ahead. Without it, each new question is an ambiguous signal: is there more of this? How much more? That ambiguity is a form of [cognitive tax, and it accumulates with each step](https://weareaffective.com/learning-centre/how-to-structure-a-behavioural-risk-register-before-you-write-a-single-user-stor). With priming, the user enters the flow knowing roughly what is coming. The progress bar then confirms and tracks something the user was already expecting, rather than revealing something they were not sure was going to end.

Before any multi-step flow begins, tell the user what sections they will move through, roughly how long each takes, and what they will need to have ready. A 30-second read at the start saves the drop-off you would otherwise diagnose six questions in.

Setting expectations before a process starts can be more powerful than any in-flow design change, because the user's orientation to the task is set at the beginning and colours everything that follows.

## The Cumulative Effect: Priming and Segmentation Together

The full picture on the health and wellbeing flow was a combination of both changes operating together. Priming brought completion from around 15-20 percent up to approximately 95 percent on its own. The segmented bar contributed a further 20-25 percent uplift when measured against the unprimed, single-bar baseline. Run together, the two interventions produced a flow where nearly all users who started also finished.

The reason the combination works better than either element alone is that they address different failure points. Priming handles the front end: the user arrives with clear expectations and a sense of what they are committing to. The segmented bar handles the middle: as the flow progresses and fatigue becomes a factor, the structure of the bar gives users repeated small reasons to continue rather than a single large reason to persist.

| Configuration | Completion rate | Primary failure point addressed |
| --- | --- | --- |
| Single bar, no priming | ~15-20% | Neither entry nor mid-flow |
| Single bar, with priming | ~95% | Entry expectation only |
| Segmented bar, no priming | ~35-45% | Mid-flow effort perception only |
| Segmented bar, with priming | ~95%+ | Both entry and mid-flow |

The table above is an approximation from the work on that project, not a controlled trial with statistically isolated variables. But the directional pattern held across the testing we ran. Drop-off happened at entry when there was no priming, and in the middle when there was no segmentation. Remove both failure points, and completion becomes the default rather than the exception.

## What the OTA Checkout Taught Us About Interactive Progress

On an OTA travel checkout we redesigned, the challenge was structurally different from the health and wellbeing flow. The checkout covered accommodation, flights, transfers, and extras, with integration across multiple third-party providers. The total information required from users was high: traveller details, passport numbers, room sharing, ticket distribution, and payment across a process that could not easily be shortened.

We found users were entering information partway through and then dropping off. The problem was not the quantity of information required; it was the opacity of the process. Users did not know how much remained, how the sections related to each other, or whether they could pause and return. The standard segmented bar was not enough here, because the sections were not equivalent in effort or time required.

Our solution was to make the progress indicator interactive. Users could see each section of the checkout laid out, with an estimated time per section and an overall time estimate for the whole process. They could jump between sections rather than moving linearly, which meant they could complete easier sections first or return to something they had left incomplete. This gave users a navigable map of the booking journey rather than a position marker on an undifferentiated path.

For complex, multi-section flows with variable effort per section, replace a standard progress bar with an interactive section map showing estimated time per section. Users who can see and choose their route through a process are less likely to abandon it when a single section feels demanding.

The lesson from the OTA project is that interactive progress indicators give users a form of agency that passive bars cannot. Agency over the process reduces the feeling that the process is happening to them, which is where a lot of mid-flow abandonment begins.

## Designing Progress Indicators for Emotional State, Not Just Position

A progress bar's job is to tell users how they should feel about where they are. Position is the input. Emotional state is the output. A bar that accurately reports position but produces the wrong emotional response has not succeeded.

The emotional state that drives completion is a sense of manageable, imminent progress. Users need to feel that what is immediately ahead is achievable, and that completing it will produce a perceptible reward. This is why the segmented approach works: it creates a close horizon, not just an accurate one. Each section end is genuinely close, and reaching it feels like finishing something.

Designing for emotional state also means matching the complexity of what you show to where the user is in the process. Early in a flow, users need simplicity and reassurance. A screen that opens with six sections, twenty sub-steps, and a time estimate for each can feel as daunting as a single bar at 5 percent. Showing just the current section and a simple overall section count in the early stages and expanding the view as users move deeper is a way of layering information as confidence grows.

Research supports the baseline: [users shown a moving progress indicator during waiting are willing to wait around three times as long as those shown nothing](https://www.nngroup.com/articles/progress-indicators/), and report higher satisfaction. The indicator itself changes the experience. The form it takes changes it further.

## What This Means for Any Multi-Step Product Flow

The principles from the health and wellbeing flow and the OTA checkout apply across any product that asks users to move through a structured sequence of steps. Beauty and skincare brands running skin diagnostic questionnaires, fitness products running initial assessment flows, hospitality products running booking processes: all of them are asking users to invest effort before experiencing any return, and all of them carry mid-flow abandonment risk.

The key design decisions reduce to a short set:

1. Prime users before the flow begins. Tell them what sections they will move through and approximately how long the whole process takes. This is the highest-leverage single change you can make.
2. Segment the progress indicator by logical groupings of the content. Named sections with internal progress tracking give users a close, achievable target at every point in the flow.
3. Match what the bar shows to the user's current emotional state. Early in the flow, keep it simple. As users move further in, more detail becomes useful rather than daunting.
4. For high-complexity or variable-effort flows, consider making the progress indicator interactive so users can navigate sections rather than being moved through them linearly.
5. Track drop-off points in your analytics at the question or screen level, not just the section level. Where users leave tells you where the bar is failing, not just where the content is difficult.

What runs through all of these is a shift from designing the indicator as an information display to [designing it as an emotional tool](https://weareaffective.com/learning-centre/why-your-social-media-app-needs-more-than-just-pretty-design). The bar is there to sustain the motivation to continue.

## Conclusion

The health and wellbeing project made the case clearly. The same questions, asked in the same order, produced dramatically different completion rates depending on two things: whether users knew what was coming before they started, and whether the progress indicator gave them a close, achievable goal at every point along the way. Neither change required rewriting the content. Both required rethinking what the bar was for.

A single continuous bar treats progress as a measurement. A segmented bar with upfront priming treats progress as an experience. The measurement and the experience produce different results because they create different emotional conditions. One asks users to persist against a slowly moving total. The other gives users something to finish, and then something else to finish, until the overall flow is complete.

The 20-25 percent uplift from segmentation and the near-complete completion rates when priming was added show that the design of progress indicators is a structural decision with real consequences for how many users complete the things you ask them to do. The OTA checkout reinforced this from a different angle: interactivity and section-level time estimates gave users agency over a complex process, and agency changes how demanding a process feels.

Progress indicators deserve the same attention as the copy and the visual design of a product flow, because they are doing the same work: managing how users feel at every step, not just reporting where they are. If your flow is losing users before they see value, the bar is worth examining before the questions are.

[Let's talk about your onboarding flow](https://weareaffective.com/get-started).

## Frequently Asked Questions

Why did users drop off so early in the health and wellbeing onboarding flow?

Most users were leaving before question five because the single continuous progress bar made the journey ahead feel long and fixed. Even though the bar was technically accurate, each small step produced barely any visible movement, which signalled to users that the process was not worth continuing.

What is the difference between actual effort and effort perception?

Actual effort refers to the objective number of steps or questions a user must complete, which stays the same regardless of how the interface is designed. Effort perception is how difficult or lengthy that process feels subjectively, and this can be shaped significantly by how progress indicators are designed.

Why do single progress bars struggle in long multi-step flows?

In a flow with 20 or more steps, each completed step produces only a tiny visual shift in a single continuous bar, which creates a flat reward curve. A user at question three of 25 sees the bar at roughly 12 percent, and the mismatch between the effort they have invested and the progress shown becomes a reason to leave.

What does a progress bar actually communicate beyond just position?

A progress bar carries two simultaneous messages. The first is positional, telling users where they are relative to the end. The second is emotional, signalling whether continuing is worth their time, and it is this second message that most determines whether users stay or leave.

How does segmenting a progress bar improve completion rates?

Breaking a long flow into visible segments gives users a series of closer, more achievable sub-goals rather than one distant overall target. Behavioural psychology supports this approach, as people are more motivated by progress within a visible sub-goal than by how far they are from a remote finishing point.

Does this principle apply only to health and wellbeing flows?

No, the article notes that similar findings emerged during the redesign of an online travel agency checkout flow. Progress indicators shape effort perception across many product types, and the principles around segmentation and sub-goals are broadly applicable.

What should designers communicate to users before a long flow even begins?

The article identifies what you tell users before they start as one of the key variables in completion rates. Setting clear expectations about the structure and length of a flow upfront helps users arrive with a realistic sense of what is ahead, reducing the chance that early progress feels disappointing.

How can analytics help identify progress bar problems in an onboarding flow?

Drop-off data can reveal patterns that point clearly to a progress indicator problem, particularly when most abandonment clusters in the first few steps. When users leave consistently at the same early point, it often reflects a mismatch between the effort they have invested and the progress the bar appears to show.

## Related Articles

[![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com)

20-22 Wenlock Road  
London, N1 7GU  
United Kingdom

+44 20 4572 8062  
[hello@weareaffective.com](mailto:hello@weareaffective.com)

<https://linkedin.com/company/weareaffective> <https://instagram.com/weareaffective> <https://facebook.com/weareaffective>

Services

[App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit)

Legal

[Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70)

Case studies

[TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift)

About us

[Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work)

Guides

[Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth)

 Copyright © 2026, weareaffective.com. All rights reserved.