Unit Bias

The tendency to consume or complete one 'unit' of something regardless of how the unit is defined—eating a full plate regardless of plate size, completing a full project regardless of project scope, watching a full episode regardless of episode length. The mechanism: the brain uses the unit boundary as a natural stopping point, so larger units produce larger consumption and smaller units produce smaller consumption. Restaurants that increase portion sizes increase consumption without increasing hunger. Projects defined in large chunks get completed in large chunks; the same work broken into smaller units gets evaluated (and potentially abandoned) at each boundary.

When to use it

When consumption patterns need to be reshaped (food, time, resources); when projects continue past the point of value because there's no natural stopping point; when designing products, portions, or processes where unit size affects behavior; when large commitments need to be made interruptible.

How it can help

Design units strategically to shape behavior. For consumption reduction: use smaller plates, smaller packages, smaller default serving sizes. For project management: break large projects into small milestones—each milestone creates a natural evaluation point where continuation is a deliberate choice rather than an automatic continuation of the current unit. For productivity: define 'done' in small increments (the Pomodoro Technique exploits unit bias by making 25 minutes the unit of work). The unit boundary is where behavior gets evaluated and choices get made—so place boundaries where you want evaluation to happen.