Fabricated progress destroys trust
Aliases: fake progress bar · deceptive progress indicator
What it is
Progress feedback works only while progress is true. Fabricated progress — bars that advance on a script, percentages unrelated to actual remaining work, indicators slowed or pulsed for retention — manufactures gradient and completion feeling in the short run, but once spotted the cost exceeds the single task: progress display is part of what the product asserts, and a caught fabrication announces "we will lie to keep you here."
Why it happens
Users' trust in progress is not all-or-nothing; it is continuously calibrated. While real progress tracks felt workload over time, the indicator is treated as a reliable instrument. Once systematic misalignment appears — installers stuck at 90%, processing bars that lurch and stall — users reclassify the indicator as theater, and the motivational value of all progress feedback zeros out, because nobody accelerates toward a fake goal. The heavier secondary loss is at the attribution layer: progress fabrication sits in the easiest-to-detect class of manipulation (the comparison standard is the user's own experience of waiting), handing users a concrete, repeatable example supporting "this product manipulates people" — after which even honest retention prompts get read as tactics.
Where it stops holding
Not all imprecision is fabrication: honest uncertainty (fluctuating download rates, queue estimates) can be labeled as such, and "about 2 minutes left" beats fake precision. Smoothing jitter for readability (avoiding numbers that bounce backward) is legitimate so long as remaining work is not systematically distorted. The test is the intent structure: progress reflecting real state is the floor; progress reflecting retention targets crosses the line.
Applying it
- Bind indicators to real units of work: every percentage point corresponds to an actual completed fragment; when precision is impossible, show ranges and the estimation basis ("at current speed").
- For long waits, structure rather than fake progress: name the real stages (extracting, verifying, writing) — verifiable stages are both honest and easier to wait through than a constant-speed counterfeit bar.
- Show a stalled state when work stalls, not a frozen percentage, and let users inspect details to verify the system is working.
- Audit every scripted indicator (fixed-duration animations posing as processing, endings slowed to hold attention) and replace with real signals or clearly decorative animation.
- To validate: sample and reconcile indicator readings against actual completion times (screen-recording comparison), and watch community channels for "the progress bar is fake" threads — once such threads appear, the trust loss is already externalized.