--- title: What 'Emotional Pacing' Means and Why It Decides Whether Users Finish a Multi-Step Flow description: Learn what emotional pacing means in UX, why it determines whether users finish multi-step flows, and how to apply it to your own onboarding design. image: https://weareaffective.com/hubfs/learning-centre-images/what-emotional-pacing-means-and-why-it-decides-whether-users-finish-a-multi-step-flow.webp --- [Skip to content](https://weareaffective.com/learning-centre/what-emotional-pacing-means-and-why-it-decides-whether-users-finish-a-multi-step#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 # What 'Emotional Pacing' Means and Why It Decides Whether Users Finish a Multi-Step Flow Table of Contents On a health and wellbeing product we worked on, four out of five people walked away from the onboarding questions before they got anywhere near the end. Drop-off sat at around 80 to 85%, and almost all of it happened within the first three or four screens. The questions were short and sensible. The flow worked exactly as it had been built to work. People still left. > People abandon a flow because of how the steps feel, long before they run out of patience with the content. We tested a second version that told people upfront what was about to happen and roughly how long it takes. Same questions, same order, same screens. Completion rose to about 95%. Nothing in the flow got shorter. What changed was how the flow felt before anyone touched it. That gap between what a process costs and what it feels like to go through is emotional pacing. It is the rhythm of effort and reassurance across a multi-step journey, matched to how a person feels at each point rather than to how the data model is organised. Get the rhythm wrong and people leave perfectly good flows. Get it right and they finish longer ones than you expected them to tolerate. ## Defining Emotional Pacing Emotional pacing is the rate at which a product asks for effort and gives something back. Every step in a flow takes something from the user, which is attention, personal information, a decision, or patience. Every step also has the chance to give something back, which is reassurance, a sense of movement, a small reward, or a clearer idea of what happens next. Pacing is the balance of those two things over time. Information architecture asks what order the content should go in. Emotional pacing asks a different question, which is how the person feels at step four and whether the product has earned the right to ask what it is about to ask. #### Matched to the emotional state As Simon puts it, "every step of that process that they go through needs to be [matched to where they are emotionally](https://weareaffective.com/user-psychology-app-design) at that point in time and as they get more confident and more comfortable with the product we can increase the complexity." Confidence builds. Complexity follows it. The default in building management apps is to hand over the whole directory the moment someone signs in. On the concierge app we worked on, that felt wrong for people who had just moved home and were somewhere between excited and overwhelmed. We treated the timing and sequencing of information as an emotional design problem rather than a filing one. ## Why Progress Feels Different From Progress Made A single long progress bar across a twenty-step flow tells the truth and still feels like standing still. Each step moves it by five per cent, which the eye barely registers. The person has genuinely made progress. They do not feel it, so the honest indicator produces a dishonest emotional result. Felt progress is what keeps people moving. It comes from three things working together, which are a sense that the last action changed something, a readable idea of how much is left, and a belief that the remaining steps are of the same size as the ones already done. Break any of those and people start doing sums in their head about whether finishing is worth it. Progress indicators do real work here. Research from the University of Nebraska-Lincoln, reported by [Nielsen Norman Group](https://www.nngroup.com/articles/progress-indicators/), found people waited around three times longer when they saw a moving progress bar than when they saw nothing at all, and felt better about the wait. That study looked at waiting for a page to load rather than filling in a form, so treat it as a signal about how people read movement, not as a rule about onboarding. The lesson we take from our own flows is narrower and more useful. Movement has to be visible at the scale a person is working at. ## 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 ## The Three Questions Users Ask Mid-Flow Somewhere around step three, people start running a quiet internal commentary. They rarely type it into a feedback box, and it shapes whether they carry on. 1. How much longer is this going to take? 2. Why do you need this from me? 3. What do I actually get at the end? Each question has a point in the flow where it gets loudest. The first arrives early, usually at the moment the novelty of a new product wears off. The second arrives whenever the questions get personal, which in [health, fitness and beauty products happens fast](https://weareaffective.com/learning-centre/fitness-app-trends-2026-what-users-really-want-from-their-workout-apps). The third arrives in the final third, when the finish line is close enough to be worth pricing up. > A person mid-flow is quietly asking how much longer and why you need this from me. You can see these questions in behaviour before anyone tells you about them. Simon describes [watching for "time on screen, time with people](https://weareaffective.com/learning-centre/research-findings-from-our-own-work-where-lifestyle-brand-reorder-flows-break-do) going into a screen, coming back out, going back into it" and for repeated scrolling up and down through a block of text. That pattern signals either a lack of comprehension or a lack of trust, and both of them are an unanswered question. On the health and wellness genetics app we worked on, the third question never got a good answer. The brand had promised transformation in its packaging and marketing, then the app delivered results in flat, clinical language. The reward at the end of the flow was colder than the invitation at the start. ## Setting Expectations Before the First Step The cheapest pacing change we have made cost almost nothing to build. On a fitness product we worked on, people had to go through a handful of orientation questions before they got to anything that felt like fitness. Early abandonment was high. The change we made was to tell people how long those questions take, framed before they started. In Simon's words, "just framing how long that was going to take, really super simple, not a technical thing, but just [telling people what to expect suddenly](https://weareaffective.com/learning-centre/how-to-redesign-an-onboarding-flow-for-the-emotional-state-the-user-actually-arr), they would go into that in a much more prepared way." We ran a cleaner version of that test on the health and wellbeing product described at the start. One version primed people with what was coming and how long it takes. The other simply showed a progress bar once they were inside. The primed version took completion from around 80 to 85% drop-off to roughly 95% completion. Priming works because it moves the decision. Without it, every screen is a fresh chance to ask whether this is worth continuing. With it, the person has already agreed to a known cost, so each screen is part of something they signed up for. Write your expectation-setting line as a sentence a person says out loud. "Six quick questions, about two minutes" beats "complete your profile to continue". ## Segmenting the Progress Bar: What Changed and What It Lifted On the same health and wellbeing product, onboarding used one long progress bar that crept forward with every answer. We replaced it with a segmented bar that showed progress inside each section as well as across the whole flow. The number of steps stayed the same. People answered the same questions in the same order. Simon described what the change did: "it gave them a much more granular view of where they were in the process, and it was easier for them to ascertain how much further they had to go rather than just one long bar that's just moving a small amount each time." Completion rose by around 20 to 25% against the single bar. | What the user experiences | Single bar | Segmented bar | | --- | --- | --- | | Movement after one answer | Barely visible | Clear jump within the section | | Judging what is left | Guesswork | Sections remaining | | Natural stopping points | None | End of each section | | Completion effect | Baseline | Around 20 to 25% higher | Stack that on top of the upfront priming and the combined effect on completion was large. Two changes, neither of them touching the questions themselves, both of them changing how the same work feels to do. ## Chunking Steps Into Sections Users Recognise A segmented bar only helps when the segments mean something to the person looking at them. Splitting twenty questions into four groups of five does very little if the groups are named after your database tables. The sections have to match how someone already thinks about the task. On a health and wellness product we worked on, we built the layering around reducing anxiety rather than around product logic. The top level used simple, easy to understand metaphors about the human body. More science-based detail sat underneath, available to people who went looking for it once they felt steady. That same principle governs how you group steps, so the first section should be the one people find easiest to answer and least exposing. #### Naming sections in the user's language Good section names tell a small story about the journey. In a skincare consultation, "about your skin", "what you have tried" and "what you want to change" give a person a map before they start. Each name sets up the kind of thinking the next few questions need, which lowers the effort of switching between them. Read your section names in order, on their own, with nothing else on the page. If they do not describe a sensible journey, your chunking is organisational rather than emotional. ## Effort, Reward and the Rhythm Between Them Pacing has a rhythm to it, which is ask, give, ask, give. The ask is the question or the action. The give is whatever the product hands back, which might be a calculation, a piece of personalisation, [a moment of recognition, or simply the sense](https://weareaffective.com/learning-centre/10-micro-interactions-that-will-transform-your-apps-user-experience) that something has been understood. Long runs of asking with nothing in between are where flows go quiet. On a fitness product we redesigned, people were self-conscious about their bodies and quick to switch off if they felt judged. We built everything around personal pace and the idea that everything is better than nothing. Two minutes a day got celebrated over zero. Simon's framing was "really celebrating just turning up and behaviour change rather than necessarily the level at which you're doing a particular thing." > Effort with no return feels like paperwork, and reward with no effort feels like nothing earned. That principle holds inside a multi-step flow. The reward for answering five questions about your routine should be something that recognises the person who answered them, in their language. A spinner followed by another five questions reads as a product that takes and takes. Where the ask is heaviest, put the clearest give directly after it. Personal questions, body measurements, payment details and anything medical all deserve a visible return. ## Adapting the Pace to Different Users Two people in the same flow are often having different experiences, and the product can tell which is which from behaviour. On a travel app we worked on, we [adapted the gamification to emotional state](https://weareaffective.com/learning-centre/why-a-charity-reorder-flow-should-feel-different-from-a-beauty-reorder-flow). Where people were dwelling on screens and moving slowly, we limited the visibility of rewards and badges to the next achievable goal and perhaps one or two beyond it. For people breezing through, we opened the window up so they could see the full set of rewards and track what they had earned against what remained. Simon's reasoning is simple enough. "Someone who's stressed needs a very different kind of strategy for gamification than someone who is confident and happy." Showing an anxious person twelve locked achievements adds weight. Showing a confident person one next step takes the game away. The behavioural signals we watch for are the ones that are already in the data, if the tracking is granular enough: - Time on screen compared with the flow average - Entering a screen, leaving, and coming back to it - Repeated scrolling up and down through the same block of text - Pauses before answering personal questions - Speed across the first three steps, which predicts the rest Adaptive pacing does not need machine learning to start. Two modes, triggered by speed through the opening section, covers most of the value. ## Where Pacing Goes Wrong: Common Mistakes The most common failure is handing over everything at once because the information exists. The concierge app we worked on started as a directory and a maintenance logger, with the whole lot available on day one. Our focus groups showed that people who had just moved in wanted connection and reassurance first. We put a social feed at the heart of the product, where residents post, ask neighbours for help and follow the concierge team, with the building management features sitting behind that as a second layer. The second failure is a [mismatch between the emotional pitch and the product](https://weareaffective.com/learning-centre/why-your-social-media-app-needs-more-than-just-pretty-design). On the health and wellness genetics app, the packaging and online presence were luxurious and aspirational, all about becoming a better version of yourself. The app was cold and clinical. Simon called it "a very jarring experience", because the journey from marketing, to ordering a kit, to doing the test, to opening the results simply stopped carrying the same feeling. #### Smaller mistakes that add up - Asking the most personal question first, before any trust exists - Progress indicators that jump backwards when a branch adds steps - Sections of wildly different lengths under equal-sized segments - Celebrating completion of an admin step as though it were an achievement - Saving all the reassurance for a confirmation screen nobody reaches Each one is small. Together they tell a person this process was built for the organisation, not for them. ## What to Measure to Know Your Pacing Is Working [Funnel completion tells you something went wrong](https://weareaffective.com/learning-centre/how-to-tell-whether-your-digital-problem-is-a-format-problem-or-a-brief-problem) and almost nothing about where or why. The measurement has to be granular enough to see hesitation, which is the thing that sits just before abandonment. Teams that never capture it are left guessing at the cause of a number they can see clearly. Track these per step rather than per flow: 1. Drop-off by step, with branches separated out 2. Median time on screen, and the spread around it 3. Re-entry counts, meaning people who leave a screen and come back 4. Repeated scrolling through terms, explanations or disclaimers 5. Completion by section, so you can see which chunk breaks the rhythm 6. Return completion, meaning people who come back later and finish Two patterns matter most. A spike in time on screen with high completion usually means a hard question people are willing to answer. A spike in time on screen with re-entry and scrolling means comprehension or trust has gone, and that is where to spend your next sprint. Before you change anything, record a baseline for every step. The segmented bar result on our health and wellbeing product was only readable because the single bar version had been measured step by step first. ## Applying Emotional Pacing to Your Own Flow Start by writing your flow out as a list of steps on one page, then mark how each step feels to the person doing it rather than what it collects. Simon's approach to this is to find the genuine high points and lift them higher, then take the low points and either improve them or give them context so people understand why that bit feels uncomfortable. From there, the sequence we follow is fairly consistent. 1. Add upfront priming that states what happens and how long it takes 2. Group steps into sections a user already has a name for 3. Show progress within sections as well as across the whole flow 4. Put a visible return directly after your heaviest ask 5. Instrument every step before you test, then change one thing at a time Run the priming change first. It is usually the smallest build and the clearest read, and on both the fitness product and the health and wellbeing product it moved more than anything we did inside the flow itself. Then look at whether the pace suits different emotional states. One flow that adapts between a cautious mode and a confident mode handles far more of your audience than a single average pace ever will. ## Conclusion Emotional pacing decides completion because people measure your flow in how it feels to be three screens in, slightly unsure, with no clear idea of how much is left. A twenty-step process with good pacing finishes more often than an eight-step process that asks for personal information in silence and gives nothing back. The changes that moved our numbers were unglamorous. Telling people how long the fitness orientation questions take. Splitting one long bar into sections on the health and wellbeing product, which lifted completion by around 20 to 25%. Priming people before the first question, which took drop-off from roughly 80 to 85% down to about 95% completion. Putting a social feed at the heart of the concierge app instead of a directory. None of them required new technology, and all of them came from asking what the person felt at that exact moment. If you have a multi-step flow losing people in the first few screens, the fix is usually sitting in the pacing rather than the content. We are happy to look at where yours breaks and what to change first. [Let's talk about the pacing of your onboarding flow](https://weareaffective.com/get-started) ## Frequently Asked Questions What exactly is emotional pacing? Emotional pacing is the rhythm of effort and reassurance across a multi-step journey, matched to how a person feels at each point rather than to how your data model is arranged. Every step takes something from the user, such as attention, personal information or a decision, and every step has a chance to give something back, such as reassurance or a sense of movement. Pacing is the balance of those two things over time. How is emotional pacing different from information architecture? Information architecture asks what order the content should go in and how it should be grouped. Emotional pacing asks how the person actually feels at step four, and whether the product has earned the right to ask what it is about to ask. The two work together, but a logically ordered flow can still feel exhausting if the pacing is wrong. Can telling people what to expect really improve completion that much? In the health and wellbeing onboarding described in the article, completion moved from roughly 15 to 20% to around 95% simply by telling people upfront what was coming and roughly how long it would take. The questions, the order and the screens were identical. What changed was how the flow felt before anyone touched it. Why do users abandon flows that seem perfectly well built? People abandon a flow because of how the steps feel, long before they run out of patience with the content. A flow can work exactly as designed, with short and sensible questions, and still lose most of its users in the first three or four screens. The problem is the gap between what a process costs and what it feels like to go through. What is the difference between progress made and felt progress? Progress made is the objective distance travelled through a flow. Felt progress is whether the user senses that movement, and it depends on three things working together, which are a sense that the last action changed something, a readable idea of how much is left, and a belief that the remaining steps are the same size as the ones already completed. Break any of those and people start calculating whether finishing is worth it. Why can an honest progress bar still feel discouraging? A single long bar across a twenty-step flow moves by about five per cent per step, which the eye barely registers. The indicator is telling the truth, but it produces a dishonest emotional result because the user feels as though they are standing still. Breaking the journey into smaller, visibly completed sections usually feels better than one long bar. Does the research on progress indicators apply directly to onboarding forms? Not directly. The University of Nebraska-Lincoln research reported by Nielsen Norman Group found people waited around three times longer when they saw a moving progress bar, but that study looked at waiting for a page to load rather than filling in a form. Treat it as a signal about how people read movement, not as a rule you can transplant into onboarding. How should complexity be introduced across a flow? Start simple and let complexity follow confidence. As Simon puts it, each step needs to be matched to where the user is emotionally at that point, and as they grow more comfortable with the product you can increase the complexity. On the concierge app, that meant resisting the default of handing over the entire directory the moment someone signed in. ## 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) 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.