Inside MyNordstrom, one of the most common reactions when checking hours or pay is:
“That doesn’t look right.”
Not completely wrong.
Not obviously broken.
Just… off.
And almost always, the reason isn’t a system issue.
It’s something much more subtle:
expectation bias.
What users expect vs what actually happens
| Situation | User expectation | Actual behavior |
|---|---|---|
| Check hours | Matches mental calculation | Reflects processed system data |
| Recent work | Already included | May still be pending |
| Pay estimate | Simple math | Complex calculation + timing |
The key problem is this:
Users don’t compare numbers to reality.
They compare numbers to what they expected to see.
And expectations are rarely accurate.
Where expectation bias comes from
| Source | How it distorts perception |
|---|---|
| Rounded memory | “About 8 hours” instead of exact |
| Simplified math | Ignoring small time differences |
| Immediate assumption | Expecting instant updates |
| Selective recall | Remembering only main shifts |
A real scenario explains this perfectly.
You work:
- 7h 42m
- plus a shorter shift earlier
Your brain simplifies it:
→ “about 8 hours”
You check MyNordstrom:
→ shows exact processed number
Now it feels wrong.
Not because it is wrong—
but because it doesn’t match your expectation.
Behavioral loop that creates confusion
- work shifts
- estimate mentally
- check system
- see different number
- assume issue
What’s actually happening underneath
| Stage | User perception | System reality |
|---|---|---|
| Work completed | “I know my hours” | Time recorded precisely |
| Early check | “That’s too low” | Not all time processed |
| Later update | “Now it’s closer” | More data finalized |
Another important factor is timing misalignment.
Users expect:
→ instant reflection
System works in:
→ stages and updates
So you’re often comparing:
- expected total
vs - incomplete system state
Why this feels like a system problem
Because expectations feel accurate.
Your brain says:
“I worked this amount”
So when the number differs, it feels like:
“The system is wrong”
But in reality:
- your estimate is approximate
- the system is precise
- and timing isn’t aligned
What actually helps in real usage
1. Stop trusting rough estimates
They’re almost always off.
2. Expect delay in updates
Hours don’t finalize instantly.
3. Compare only after full processing
Early checks are incomplete.
4. Think in exact time, not rounded hours
Minutes matter more than you think.
5. Let the system be the source of truth
Not your memory.
FAQ
Why do my hours feel wrong in MyNordstrom?
Because they don’t match your expectation—not because they’re incorrect.
Why are numbers lower at first?
Because not all time is processed yet.
How do I avoid confusion?
Check later and rely on finalized data.
The key insight
The number isn’t wrong.
Your expectation is just not aligned with the system yet.
Final thought
MyNordstrom doesn’t confuse users—expectations do. The gap between what you think you earned and what the system shows is usually just timing + estimation bias. Once you stop comparing early numbers to mental math, everything becomes much clearer.