{"id":284,"date":"2025-09-09T20:37:50","date_gmt":"2025-09-09T20:37:50","guid":{"rendered":"https:\/\/hitchhikersguidetodesign.com\/book\/?p=284"},"modified":"2025-09-11T00:15:50","modified_gmt":"2025-09-11T00:15:50","slug":"sunk-cost-fallacy","status":"publish","type":"post","link":"https:\/\/hitchhikersguidetodesign.com\/book\/sunk-cost-fallacy\/","title":{"rendered":"31 \u2022 Sunk Cost Fallacy"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Sunk cost fallacy is the tendency to keep investing time, effort, or money into something, just because you\u2019ve already invested so much, even when it\u2019s clear it\u2019s not working. In UX, this shows up when teams cling to flawed designs, failed features, or outdated systems simply because they don\u2019t want to \u201cwaste\u201d what\u2019s already been spent.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">ORIGIN<\/h3>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">The concept comes from economics and behavioral psychology. Rationally, past costs (sunk costs) should not affect current decisions since they can\u2019t be recovered. But humans hate waste, and we\u2019re wired to double down to \u201cjustify\u201d past effort.<br>In design, this means that teams keep polishing or defending something that should have been scrapped or rethought long ago.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">WHEN<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You\u2019ll see the sunk cost fallacy in UX when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A clunky feature lingers because \u201cwe already built it.\u201d<\/li>\n\n\n\n<li>Redesigns keep patching a broken flow instead of replacing it.<\/li>\n\n\n\n<li>A legacy system continues draining resources because \u201cmigrating would mean wasting past work.\u201d<\/li>\n\n\n\n<li>Designers defend bad ideas because they spent weeks perfecting the pixels.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">WHY<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The sunk cost fallacy happens because:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>People feel emotionally attached to their past work.<\/li>\n\n\n\n<li>Organizations measure effort by input (time, money) rather than outcomes.<\/li>\n\n\n\n<li>Admitting something isn\u2019t working feels like admitting failure.<\/li>\n\n\n\n<li>Hope that \u201cjust one more tweak\u201d will turn things around.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">But clinging to sunk costs often means throwing away more time and money, at the expense of users.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">HOW<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s how to escape the sunk cost trap:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Focus on outcomes.<\/strong> Ask: \u201cDoes this solve user problems today?\u201d not \u201cHow much have we spent?\u201d<\/li>\n\n\n\n<li><strong>Create kill criteria.<\/strong> Define clear rules for when to pivot or stop a project.<\/li>\n\n\n\n<li><strong>Celebrate learning.<\/strong> Frame abandoned work as insight gained, not effort wasted.<\/li>\n\n\n\n<li><strong>Use small bets.<\/strong> Prototype and test before heavy investment to reduce sunk costs in the first place.<\/li>\n\n\n\n<li><strong>Invite fresh eyes.<\/strong> New team members can question attachments that others are no longer able see.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">PRO TIP<\/h3>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">When you hear \u201cwe\u2019ve already put too much into this to quit,\u201d that\u2019s your red flag. Challenge the team to reframe: <em>\u201cIf we were starting today, would we still choose this path?\u201d<\/em><\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">EXAMPLES<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A mobile app feature that is barely used but keeps getting design tweaks because it took three sprints to build.<\/li>\n\n\n\n<li>A navigation redesign that\u2019s been iterated on for months, even though user tests show the structure is fundamentally broken.<\/li>\n\n\n\n<li>A legacy enterprise tool that\u2019s expensive to maintain but sticks around because rewriting it feels like \u201cthrowing away years of work.\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">CONCLUSION<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The sunk cost fallacy reminds us that good UX isn\u2019t about defending yesterday\u2019s work, it\u2019s about serving today\u2019s users. Sometimes, the bravest design move is to abandon and \u201cpaddle\u201d away completely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Also Known As: Escalation of commitment \u2022 Throwing good money after bad \u2022 Cost trap<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sunk cost fallacy is the tendency to keep investing time, effort, or money into something, just because you\u2019ve already invested so much, even when it\u2019s clear it\u2019s not working. In UX, this shows up when teams cling to flawed designs, failed features, or outdated systems simply because they don\u2019t want to \u201cwaste\u201d what\u2019s already been spent.<\/p>\n","protected":false},"author":1,"featured_media":347,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[25],"tags":[81,19,21,20,76,39],"class_list":["post-284","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mind-games-mental-traps","tag-cost","tag-design","tag-funny","tag-idiom","tag-mind","tag-ux","entry","has-media","owp-thumbs-layout-horizontal","owp-btn-big","owp-tabs-layout-horizontal","has-no-thumbnails","has-product-nav"],"jetpack_featured_media_url":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-content\/uploads\/2025\/09\/31.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/284","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/comments?post=284"}],"version-history":[{"count":1,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/284\/revisions"}],"predecessor-version":[{"id":286,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/284\/revisions\/286"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media\/347"}],"wp:attachment":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media?parent=284"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/categories?post=284"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/tags?post=284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}