Honeymoon Cliff: Hype Raises Expectation—Retention Pays It Back
Expectation-confirmation theory: satisfaction equals experience minus expectation. Play the gacha to see “demo is P99, users get P50,” drag the hype slider to watch signup conversion and 30-day retention trade off, then flip three levers on the expectation-curve editor
THE QUESTION THIS PAGE ANSWERS
ANSWER FIRSTWhat is the key idea behind “Honeymoon Cliff: Hype Raises Expectation—Retention Pays It Back”?
Expectation-confirmation theory: satisfaction equals experience minus expectation. Play the gacha to see “demo is P99, users get P50,” drag the hype slider to watch signup conversion and 30-day retention trade off, then flip three levers on the expectation-curve editor
Turn taste into a behavior the product can repeat. The useful outcome is not a nice opinion. It is a visible rule, a small example, and a way to tell when the experience falls below the bar.
Capture one before-and-after example that shows the quality bar without extra explanation.
Polish that improves the surface while leaving the user's uncertainty untouched.
Experience is built with fixed cost; expectation is lifted by one marketing line. Raising expectation is free; paying it back is costly.
AI products are born behind on this subtraction problem, and the reason hides in probability. Left is the keynote demo slot; right is real user use. Both hit the same model—tap Generate five times and see what each side draws.
If expectation is lifted by marketing, how high becomes a product decision. Left is your landing page—drag the slider through five copy tiers; right, three metrics move live. Find the tier where conversion × retention peaks.
Even with expectation managed, another drop awaits: novelty fades on its own. Ed-tech research calls it the novelty effect: a new tool looks strong when it first enters the classroom, then falls back in weeks—because part of the gain was “new” itself. AI honeymoons are especially short: first poem is magic, tenth is a feature, hundredth is owed, one miss is garbage.
This is the 30-day satisfaction curve after signup. Current state: hype maxed, day-one capability fully lit, improvements dripped quietly—classic honeymoon cliff. Flip the three levers on the right one by one and watch the curve get caught, segment by segment.
Satisfaction = experience − expectation: raising expectation is free; paying it back is costly. Forty years of expectation-confirmation theory haven’t been overturned.
Demos cherry-pick the distribution’s tip: marketing shows P99, users get P50—probabilistic-good marketing carries an expectation bubble by nature, and the gap all lands on the product.
Magic is a consumable: novelty fades on its own; propping retention on first-wow is heating with fireworks.
Three levers catch the curve: promise one notch below (copy writes P50), unlock capability gradually (advanced features schedule-unlock), bank improvements into felt releases (changelog is a free second honeymoon).
Source: Original to Xiaoshan Academy's AI Product Psychology series; expectation-confirmation theory from Oliver, A Cognitive Model of the Antecedents and Consequences of Satisfaction Decisions (1980); novelty effect is a standard finding in educational-technology research.
Turn the feeling in “One formula · Satisfaction is subtraction” into a judgment
“AI products are born behind on this subtraction problem, and the reason hides in probability.” points out that AI has lowered the bar for making something usable. The skill readers need is noticing what is wrong and turning that feeling into an actionable requirement.
Watch the user's next action, not just the surface
Turn “If expectation is lifted by marketing, how high becomes a product decision.” into observable questions: does the user know what happened, what to do next, and how to recover from an empty or failed state? Does the hierarchy make the important information visible first?
Pretty is not the same as usable
Apply “Three levers catch the curve: promise one notch below (copy writes P50), unlock capability gradually (advanced features schedule-unlock), bank improvements into felt releases (chan…” to a second screen or flow. Record one moment of hesitation and the user action after the change; observable behavior is stronger evidence than polish alone.
From “One formula · Satisfaction is subtraction” to “Hands-on · Gacha: demo slot vs. real use—where’s the gap”
“One formula · Satisfaction is subtraction” grounds the problem in “Satisfaction = actual experience − prior expectation Expectation-confirmation theory (Oliver, 1980)—forty years of consumer-satisfaction research stand on it. Experience is built with fixed cost; expectation is…”. “Hands-on · Gacha: demo slot vs. real use—where’s the gap” then moves it toward “AI products are born behind on this subtraction problem, and the reason hides in probability. Left is the keynote demo slot; right is real user use. Both hit the same model —tap Generate five times and see what…”. Together, they show that the lesson is not just a conclusion to remember, but a claim with conditions.
Carry the judgment into the next situation
For experience work, turn abstract impressions into user actions: did the person understand the state, find the next step, recover from an error, and want to continue?
- “One formula · Satisfaction is subtraction”: Satisfaction = actual experience − prior expectation Expectation-confirmation theory (Oliver, 1980)—forty years of consumer-satisfaction research stand on it. Experience is built with fixed cost; expectation is…
- “Hands-on · Gacha: demo slot vs. real use—where’s the gap”: AI products are born behind on this subtraction problem, and the reason hides in probability. Left is the keynote demo slot; right is real user use. Both hit the same model —tap Generate five times and see what…
- “The closing point”: Three levers catch the curve: promise one notch below (copy writes P50), unlock capability gradually (advanced features schedule-unlock), bank improvements into felt releases (changelog is a free second honeymo…
The final “The closing point” brings the discussion to “Three levers catch the curve: promise one notch below (copy writes P50), unlock capability gradually (advanced features schedule-unlock), bank improvements into felt releases (changelog is a free second honeymo…”. The useful thing to carry forward is knowing which judgments must be revisited when input, scale, or risk changes.
I turned one judgment from this article into a small experiment I could run today. Knowing what to observe next is more useful than simply remembering the conclusion.
After reading this, I first looked for the conditions behind the idea instead of copying the method into a project. That order made the later trade-offs much clearer.
When this judgment reaches real work, which constraint should be added first? I am curious which step matters most between reading and the first practical attempt.
No discussion on this article yet.