The Diderot Effect describes what happens when an improvement in one part makes everything else feel inconsistent, outdated, or "less than." That initial improvement triggers a cascade of additional changes - not because they were needed, but because now they feel needed. In UX, this is dangerous because it turns focused refinements into sprawling redesigns.
The Iceberg Model is a systems thinking tool that helps uncover the root causes of problems by looking beyond immediate, visible events. It uses the metaphor of an iceberg to illustrate that events (the tip) are driven by deeper layers that are hidden below the surface.
Pogo sticking describes the frustrating user behavior of repeatedly jumping back and forth between a main page and individual items in a list, like bouncing up and down on a pogo stick, because they can’t find what they need or navigate efficiently. It’s a sign of poor information scent, weak previews, or a lack of helpful context.
Whack-a-Mole describes a frustrating pattern where fixing one usability problem seems to create another, often in a different part of the system. It’s what happens when you address symptoms instead of root causes, leaving teams trapped in an endless cycle of reactive fixes.
Design debt is the accumulation of shortcuts, inconsistencies, and outdated patterns in a product’s user experience over time. Like financial debt, it lets you move faster in the short term, but if left unpaid, it compounds into a bigger, messier problem that slows you down and frustrates users.
Paving the cow path happens when you formalize and reinforce an existing user behavior or process, rather than designing a completely new one. In UX, it means observing how users already navigate your product, even if it’s messy, and then improving or streamlining that exact behavior, instead of forcing a “better” way that nobody asked for.
Sandbagging describes the practice of deliberately lowering expectations or under-promising on what a design, feature, or team can deliver, only to exceed those expectations later. It’s a strategy used to create the perception of overperformance, often to impress stakeholders, reduce risk, or buy time.
Rubber ducking is the practice of explaining a problem aloud, often to someone (or something) else, to clarify your own thinking and arrive at a solution. In UX and product work, it’s a simple but effective way to unblock yourself or a teammate by articulating the problem clearly.