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\u2019s a simple but effective way to unblock yourself or a teammate by articulating the problem clearly.<\/p>\n\n\n\n
\nThe term comes from software engineering, popularized by the book The Pragmatic Programmer<\/em>, where a developer keeps a rubber duck on their desk and explains bugs to it. The act of verbalizing the issue forces them to think it through more clearly and often leads to a breakthrough.<\/p>\n<\/blockquote>\n\n\n\n
WHEN<\/h3>\n\n\n\n
You can use rubber ducking when:<\/p>\n\n\n\n
\n
- You\u2019re stuck on a tricky design or usability problem.<\/li>\n\n\n\n
- A teammate comes to you for help but figures it out as they explain it.<\/li>\n\n\n\n
- You need to sanity-check your own assumptions.<\/li>\n\n\n\n
- Writing a design rationale or critique response.<\/li>\n<\/ul>\n\n\n\n
It\u2019s especially helpful when working alone, but just as effective in pair or group settings.<\/p>\n\n\n\n
WHY<\/h3>\n\n\n\n
Explaining a problem aloud engages different parts of your brain and forces you to structure your thoughts. It helps uncover assumptions, gaps, and connections you might not notice in your head.
Plus, sometimes all you really need is an audience, not a solution.<\/p>\n\n\n\nHOW<\/h3>\n\n\n\n
Here\u2019s how to practice rubber ducking:<\/p>\n\n\n\n
\n
- Find an audience.<\/strong> It can be a coworker, a friend, a pet, or even an inanimate object.<\/li>\n\n\n\n
- State the problem.<\/strong> Walk through it step by step, clearly and simply.<\/li>\n\n\n\n
- Listen to yourself.<\/strong> Pay attention to where your own explanation doesn\u2019t make sense.<\/li>\n\n\n\n
- Pause and reflect.<\/strong> Often, you\u2019ll solve it mid-sentence.<\/li>\n\n\n\n
- Thank the duck.<\/strong> Even if it just sat there.<\/li>\n<\/ul>\n\n\n\n
PRO TIP<\/h3>\n\n\n\n
\nWhen a teammate rubber ducks with you, resist the urge to interrupt with solutions. Let them finish, you may not need to say anything at all.<\/p>\n<\/blockquote>\n\n\n\n
EXAMPLES<\/h3>\n\n\n\n
\n
- A designer explains a confusing flow to a teammate and realizes mid-sentence that the extra step can just be removed.<\/li>\n\n\n\n
- A PM walks through user feedback aloud and notices the pattern they missed when reading silently.<\/li>\n\n\n\n
- Talking through a bug with a developer, who suddenly blurts, \u201cOh! I see it now.\u201d<\/li>\n<\/ul>\n\n\n\n
CONCLUSION<\/h3>\n\n\n\n
Rubber ducking reminds us that clarity often comes from articulation. Sometimes all you need to solve a problem is to hear yourself explain it.<\/p>\n\n\n\n
Also known as: Thinking out loud \u2022 Explaining to a teddy bear \u2022 Talking it through<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
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\u2019s a simple but effective way to unblock yourself or a teammate by articulating the problem clearly.<\/p>\n","protected":false},"author":1,"featured_media":329,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[23],"tags":[19,21,20,53,54,39],"class_list":["post-235","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-the-productivity-mirage","tag-design","tag-funny","tag-idiom","tag-productivity","tag-rubber-ducking","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\/13.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/235","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=235"}],"version-history":[{"count":1,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/235\/revisions"}],"predecessor-version":[{"id":236,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/235\/revisions\/236"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media\/329"}],"wp:attachment":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media?parent=235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/categories?post=235"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/tags?post=235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}