Unexpected after-the-fact rewards harm less than promised ones

What it is

The same reward does different damage depending on timing. A promised reward ("complete this and you'll get X") becomes a precondition of the behavior and creates a controlling expectation; an unexpected reward delivered afterward plays no part in initiating the behavior and barely triggers crowding out. Reward harmfulness tracks whether it enters the decision before the act: expected, behavior-contingent rewards undermine interest; surprises mostly do not.

Why it happens

Self-attribution runs forward in time: in explaining past behavior, people can only use reasons that existed at the time it occurred. A reward arriving afterward cannot serve as the answer to "why did I do it," so "I wanted to" survives intact. A promise does the opposite — it supplies an ample external reason before the act, and the internal one never needs to appear. Contingent promised rewards also carry a control signal, defining the act as "worth buying," whereas a pure surprise gift reads as recognition and gratitude — the informational side of the ledger. The fatal loophole is repetition: surprise rewards that arrive on a pattern are rapidly learned as expectations; the third surprise is already the first promise.

Studying it

• Paradigm: experiments manipulate reward expectancy (whether participants know in advance) and contingency (engagement-contingent, completion-contingent, performance-contingent, or task-non-contingent), then measure residual interest in a free-choice period. Meta-analyses summarize by category: expected completion- and engagement-contingent rewards show the most reliable undermining; unexpected task-non-contingent rewards show essentially none.
• Variables: manipulations are expectancy, contingency, and tangibility; outcomes are free-choice behavior and interest scales.
• Methodological cautions: check that "unexpected" participants truly had no expectation from other channels (word of mouth, past promotions); performance-contingent rewards embed competence information (meeting a standard implies skill), which partially offsets undermining — separate the controlling from the informational component when interpreting.

Where it stops holding

Unexpectedness is a one-time resource: it cannot serve as a long-run incentive architecture, and regularized "surprises" are de facto promises. Performance-standard rewards undermine less even when announced (they carry competence information), so surprise is not the only safety switch. And on tasks with no intrinsic interest, expectancy hardly matters — there is nothing to crowd out, and a clear promise is the reasonable tool.

Applying it

• Place thanks and givebacks after the behavior, unannounced: a surprise thank-you on completion, a year-end achievement retrospective, service recovery beyond expectations — all preserve the "I did it because I wanted to" account.
• Never put surprises on a calendar: no fixed cycle or fixed trigger for the same delightful reward, so it cannot be learned as an expectation.
• When rewards must be announced, anchor them to competence standards (what level was reached) rather than raw behavior counts (how many times), letting the reward carry skill information.
• To validate: compare no-incentive-window retention between an announced group and an after-the-fact surprise group; the gap is the motivational price of promising.

Related

• Same group: P2.01.1 Intrinsic motivation comes from the activity itself · P2.01.2 Extrinsic rewards can crowd out intrinsic motivation · P2.01.3 Behavior often drops after rewards are withdrawn · P2.01.4 Autonomy, competence, and relatedness are the three sources of intrinsic motivation · P2.01.5 Informational feedback does not crowd out; controlling feedback does · P2.01.6 Tasks with no intrinsic interest have no crowding-out problem
• Nearby: P3.01 Variable rewards · P2.14 Reciprocity and social pressure
• Search terms: unexpected rewards · expected tangible rewards · reward contingency