01Overview
Weber–Fechner law describes psychophysics: the just-noticeable difference between stimuli is proportional to the baseline, not fixed. Double the brightness of a dim light and users notice; double an already bright light requires a larger jump. The same logarithmic intuition applies to price increases, loading time, gamification points, and slider granularity.
Designers often scale interfaces linearly — equal steps on a slider, equal pound increments on tiers, equal milliseconds on progress. Perception does not. Users experience diminishing sensitivity as magnitude grows and hypersensitivity near zero. Misaligned scaling produces "nothing happens" dead zones and "sudden shock" jumps — both feel like product bugs, both are perceptual law.
02Detailed explanation
Weber–Fechner mismatches appear in everyday product decisions:
- Price rise from £9 to £12 feels massive; from £900 to £903 invisible — same absolute £3, different ratio.
- Progress bars linear by file size stall visually at 90% on large uploads — log-scaled progress feels honest.
- Volume and brightness sliders with linear mapping — coarse control at low end, hair-trigger at high.
- Loyalty points with linear earn — early rewards feel meaningful; later grind without log-scaled milestones.
Design for perceived change means mapping controls and communications to how users notice difference — often logarithmic or stepped. Legal and financial reality stays linear; experience layer may need perceptual correction to communicate fairly.
03Why it exists
Sensory systems compress wide physical ranges into manageable perception — ratio detection prevents overload.
Digital products inherit linear engineering defaults (bytes, milliseconds, currency) without perceptual translation layer.
Equal steps in your UI are not equal steps in user experience. Scale for noticeability.
04Effects on users
Users tolerate small absolute fees on large purchases but rage at same fee on small — ratio, not amount.
Users misread linear progress on long tasks as "broken" when early movement is slow — perceptual mismatch drives support tickets.
05Effects on designers & teams
Teams ship linear defaults:
- Uniform price increments across tiers. Shock at low end, numbness at high.
- Linear loading indicators. Apparent stall near completion.
- Equal slider steps for wide ranges. Unusable precision at extremes.
- Feature scoring without perceptual calibration. 4.0 to 4.1 stars invisible; 3.2 to 3.7 invisible on same display.
6Extrospective view
Look outward. Users notice relative, not absolute, change, informing pricing steps, sizing and progress scaling.
From an extrospective perspective, Weber–Fechner Law is a property of the product experience itself — visible in pricing, copy, defaults, layout, and the moments where users decide whether to continue, convert, or leave.
What users compare against
On a pricing page, Weber–Fechner Law shapes which tier feels like the obvious choice — order, reference prices, and highlighted plans all set the comparison point. Users notice relative, not absolute, change, informing pricing steps, sizing and progress scaling.
What the eye meets first
Size, colour, and motion direct attention — and Weber–Fechner Law means users overweight what was salient, even if quieter elements matter more for the task. Users notice relative, not absolute, change, informing pricing steps, sizing and progress scaling.
How far along it feels
Progress bars and step counts change behaviour through Weber–Fechner Law — users treat sunk steps as a reason to continue, or misread how much work remains. Users notice relative, not absolute, change, informing pricing steps, sizing and progress scaling.
Presentation over substance
Packaging, comparison pricing, and premium framing lean on Weber–Fechner Law to make the same offer feel more valuable — sometimes without changing the offer at all. Users notice relative, not absolute, change, informing pricing steps, sizing and progress scaling.
07Practical takeaways
- Map controls to perceived difference. Log or stepped sliders for wide ranges.
- Frame price changes by ratio. Small bases need careful communication.
- Calibrate progress to user-noticeable milestones. Not raw backend proportion.
- Test sensitivity at low and high magnitude. Same absolute change, both ends.
- Accessibility: don't rely on tiny absolute differences. Contrast and size jumps must exceed threshold.
- Explain non-linear UX honestly. Users forgive perceptual design when labelled.
08Design examples
Three pounds
Subscription rises £9→£12. Churn spikes. Enterprise tier rises £900→£903. Silence. Same absolute change — Weber–Fechner predicts outrage asymmetry; comms team treats as irrational.
Stuck at ninety
Linear bar by bytes stalls final 10%. Users force-quit. Log-scaled presentation reduces "frozen" perception without changing actual process.
Linear volume
Slider unusable at low volumes, jumpy at high. Perceptual (log) curve ships — support tickets on "broken slider" drop.
Points inflation
Early levels fast; later linear grind feels empty. Log-scaled level thresholds restore sense of progress — engagement recovers without changing total work.
09Ethical risks
Exploiting ratio blindness — hiding fees in large transactions, micro-charges on small — is perceptual manipulation.
Linear progress misrepresentation causes users to abandon long necessary processes (updates, transfers) — harm from perceptual neglect.
Self-test: Where does your UI change in equal absolute steps while user perception treats those steps as unequal — and is that helping or hiding?
10Suggested reading
Suggested reading is temporarily unavailable. Please check back later.