When 'AutoSweep' Assumed Everyone Spoke Finance
A real-world example of Curse of knowledge in action
Context
A mid-stage fintech startup launched a new feature to automatically move spare cash into investment accounts. The product team — composed of engineers and financial analysts — was excited to ship a feature that reduced decision friction for savvy users.
Situation
The rollout included an in-app toggle labeled 'AutoSweep' and a short setting called 'sweep threshold' with a single-line help link. Product owners assumed the terms were self-explanatory and pushed a lightweight email to announce the change instead of a guided walkthrough.
The bias in action
Team members, who had deep domain knowledge, could not imagine users being unsure what 'sweep' or 'threshold' meant. During design reviews they repeatedly used jargon and skipped step-by-step examples, believing real users would infer intent from context. Customer support and UX researchers flagged potential confusion, but their concerns were downplayed because the team thought the concept was obvious. The marketing copy also mirrored internal language, reinforcing the same assumptions.
Outcome
Within six weeks post-launch, feature activation was far below expectations and support volume rose noticeably. Many users either didn't enable the feature or enabled it with settings that didn't match their cash-flow needs, producing small but repeated bank overdraft disputes and refund requests. The product team had to pause marketing, produce clarifying content, and ship a second release with simpler labels and an onboarding flow.