Case studies

Labor Perception: Why an Instant Result Can Feel Wrong

+20 XP

Case study

Labor Perception: Why an Instant Result Can Feel Wrong

A huge contact import finishes in a fraction of a second and leaves the user wondering if it worked, while a money transfer feels safe because the app shows the work. You will learn when showing effort builds trust, and when it crosses into manipulation.

3 min read +20 XP when you reach the end

What you will learn

  • Recognize when speed makes people doubt the result
  • Use transition screens after high stakes actions
  • Keep labor effects honest and reassuring

Scroll to follow the story. The screen changes with you.

Based on the learnings from Growth.Design: Labor Perception Bias: Why faster isn't always better, presented in our own format.

A big import screen

Step 1 of 10

  1. A big import screen287,539 contacts

    01

    The setup

    A new HubSpot user is about to import 287,539 contacts.

    Picture a fine restaurant where a complex dish arrives 15 seconds after you order it. You would be suspicious, not impressed. Digital products work the same way. Here, near the end of onboarding, the user selects every contact they have and taps 'Import'.

    TakeawayThe bigger the task, the more people expect it to take some effort.

  2. Are you sure? screenA nervous tap

    02

    The stakes

    A confirmation dialog reminds them how much is at stake.

    'Are you sure?' repeats the number of contacts going into the CRM. This is a moment of real tension: it is their whole customer list, and they are hoping nothing goes wrong.

    TakeawayHigh stakes actions raise expectations about what happens next.

  3. Too fast screenDid it work?

    03

    The problem

    The import finishes almost instantly, and the user is left unsure.

    HubSpot imports every contact in about a hundredth of a second and drops the user straight into the contact list. Technically it is impressive. For the user, it raises a question: did that actually work?

    TakeawayWhen a result arrives faster than people expect, they doubt it.

  4. Original
    Fix: show progress screenAbrupt result
    Suggested
    Fix: show progress corrected screenVisible progress

    04

    Repair

    Add a short importing screen that shows the work being done.

    Growth.Design's suggested version puts a brief screen between the confirmation and the list: an illustration of contacts moving into HubSpot, the count, and a progress bar with a few seconds remaining. Slowing down slightly reassures the user that their data was handled.

    What changed

    • A labor screen appears after the confirmation
    • The contact count is repeated
    • A progress bar shows the import running

    TakeawayA moment of visible effort can turn doubt into confidence.

    Labor perception biasPeople trust and value things more when they can see the work behind them. When expectations are high, as with money, migrations or reports, a wait that is too short makes people skeptical. Growth.Design cites the Nielsen Norman Group on visibility of system status.

  5. Sending money screenBig payment

    05

    Everywhere

    Once you know the bias, you see it in many products, like Wise.

    Here a user sends 3,935.86 US dollars from their Wise account. Sending money is exactly the kind of high stakes action where people need to know it went through.

    TakeawayMoney, data and time are where people most need reassurance.

  6. Abrupt ending screenJust 'Sending'

    06

    The weak version

    Without a transition, the transfer just becomes a line in a list.

    Imagine tapping 'Pay' and landing straight in the activity log, with the transfer shown as 'Sending' among other items. The user is left hoping the money arrives.

    TakeawayDropping people into a list after a big action leaves them to reassure themselves.

  7. In progress
    Fix: the animation screenMoney in motion
    Confirmed
    Fix: the animation corrected screenClear timing

    07

    The good example

    Wise shows the money moving, then confirms when it will arrive.

    A short animation shows money traveling from the USD account to the CAD account with 'Starting your transfer'. Then a confirmation says the transfer has started and should arrive in 5 hours. The user sees the work and knows what to expect.

    What changed

    • An animation replaces the abrupt jump
    • Both accounts and amounts are shown
    • A final screen states when the money will arrive

    TakeawayShow the process, then give a clear promise about the outcome.

  8. The business case screenWorth the pause

    08

    Why it matters

    Transition screens look like decoration, but they change how people value a product.

    It is easy to cut these screens to make an app feel faster. But the feeling of work being done is part of what people pay for, and it affects whether they trust the product enough to come back.

    TakeawayMeasure how valuable a flow feels, not only how fast it is.

    The return on perceived laborGrowth.Design cites a 2011 Harvard study on transparency and perceived value: a well designed labor effect raised perceived value by up to 15 percent. The effect on activation, retention and revenue depends on context, so test it.

  9. The misuse screenConstant jitter

    09

    Be careful

    The same bias can be used to create anxiety instead of trust.

    During the 2016 US presidential election, The New York Times ran a live forecast needle. Staff fed it new data every 15 seconds, and its constant jitter signaled hard work. But the needle moved many times a second, far more often than the data changed.

    TakeawayShowing effort to reassure is helpful. Faking movement to hold attention is manipulation.

    Information versus fearGrowth.Design argues the jitter amplified uncertainty, which drives engagement, page views, time on site and revenue. A more humane design would move the needle only when new data arrives, about every 15 seconds.

  10. Instant
    The takeaway screenLeft guessing
    Shows the work
    The takeaway corrected screenReassured

    10

    The result

    Faster is not always better when people need to trust the result.

    A brief, honest labor screen after an import, payment or migration tells people their request was taken seriously. Used with clear guidelines, the effect builds confidence. Used to stir uncertainty, it erodes it.

    What changed

    • Add labor screens after high stakes actions
    • Keep any delay short and tied to real work
    • Update visuals only when real data changes

    TakeawayUse labor perception to reassure users, never to manipulate them.

Every takeaway, in one place

  1. The setupThe bigger the task, the more people expect it to take some effort.
  2. The stakesHigh stakes actions raise expectations about what happens next.
  3. The problemWhen a result arrives faster than people expect, they doubt it.
  4. RepairA moment of visible effort can turn doubt into confidence.
  5. EverywhereMoney, data and time are where people most need reassurance.
  6. The weak versionDropping people into a list after a big action leaves them to reassure themselves.
  7. The good exampleShow the process, then give a clear promise about the outcome.
  8. Why it mattersMeasure how valuable a flow feels, not only how fast it is.
  9. Be carefulShowing effort to reassure is helpful. Faking movement to hold attention is manipulation.
  10. The resultUse labor perception to reassure users, never to manipulate them.

Source: Growth.Design: Labor Perception Bias: Why faster isn't always better

Make important moments feel as solid as they are.

Imports, payments, migrations and reports are where people most need to trust what just happened. Zyxware can find the moments in your product where users are left unsure, and design clear, honest feedback that shows the work being done.

Build with Zyxware