Walking on Eggshells means being extremely cautious in one\u2019s actions or words, usually to avoid upsetting someone else. Avoiding conflict becomes more important than improving the product.<\/p>\n\n\n\n
In product design, walking on eggshells means that problems are discussed privately instead of openly, feedback gets softened, and research findings are carefully worded so nobody feels implicated. And that feature requested by the executive? Everyone knows it is questionable but nobody wants to be the person who says so. The team is still communicating – it just isn’t saying what it really thinks.<\/p>\n\n\n\n
\nThe exact origin of the phrase walking on eggshells is uncertain, but the metaphor is surprisingly old. Variations involving walking or treading on eggs appeared in English as early as the 16th century, including descriptions of people proceeding “gingerly” as though afraid of breaking eggs. The familiar eggshell version became established in the 18th century.<\/p>\n\n\n\n
Some people have suggested that the term is based on observation when raising chickens, where hens walk very carefully when getting in and out of their nests.<\/p>\n\n\n\n
Over time, the expression came to describe situations where people carefully control their words and actions to avoid provoking anger, offense, or conflict. In product teams, the eggs are metaphorical, but the careful footsteps are very real. <\/p>\n<\/blockquote>\n\n\n\n
WHEN<\/h2>\n\n\n\n
You’ve encountered Walking on Eggshells when:<\/p>\n\n\n\n
\n
- Feedback becomes suspiciously polite<\/strong>
Everyone has concerns, but the meeting ends with “Looks great!”<\/li>\n<\/ul>\n\n\n\n\n
- Research findings get sanitized<\/strong>
The uncomfortable insight somehow disappears between the research report and the executive presentation.<\/li>\n<\/ul>\n\n\n\n\n
- Certain decisions can’t be questioned<\/strong>
Everyone knows which topics are safe – and which ones are definitely not.<\/li>\n<\/ul>\n\n\n\n\n
- People wait for someone else to speak first<\/strong>
The room has opinions but everyone stays silent.<\/li>\n<\/ul>\n\n\n\n\n
- Problems are discussed after the meeting<\/strong>
The most productive conversation begins five minutes after the person who needed to hear it leaves.<\/li>\n<\/ul>\n\n\n\n\n
- You hear: “Maybe we shouldn’t bring that up.”<\/strong>
Not because it isn’t important, but because of how someone might react.<\/li>\n<\/ul>\n\n\n\nIf everyone is carefully managing the reaction instead of discussing the problem, you’re probably walking on eggshells.<\/p>\n\n\n\n
WHY<\/h2>\n\n\n\n
Walking on Eggshells is usually a symptom of the environment around the team rather than the individuals within it. A strong personality, defensive stakeholder, sensitive designer, or blame-heavy culture can make perfectly reasonable questions feel surprisingly dangerous. The following reasons explain why it may happen:<\/p>\n\n\n\n
\n
- Fear of conflict<\/strong>
Disagreement is treated as confrontation rather than part of good design.<\/li>\n<\/ul>\n\n\n\n\n
- Power imbalance<\/strong>
Challenging a senior stakeholder can feel considerably riskier than challenging a button color.<\/li>\n<\/ul>\n\n\n\n\n
- Defensive ownership<\/strong>
When people become personally attached to ideas, criticism of the work starts feeling like criticism of the person.<\/li>\n<\/ul>\n\n\n\n\n
- Past experience<\/strong>
One badly received piece of feedback can teach an entire team what not to mention next time.<\/li>\n<\/ul>\n\n\n\n\n
- Blame culture<\/strong>
If mistakes are punished rather than examined, people quickly learn that silence is safer than honesty.<\/li>\n<\/ul>\n\n\n\nHOW<\/h2>\n\n\n\n
Walking on Eggshells is solved by making disagreement safe, useful, and focused on the work.<\/p>\n\n\n\n
\n
- Critique the work, not the person<\/strong>
“This flow creates confusion” is different from “You designed this badly.”<\/li>\n<\/ul>\n\n\n\n\n
- Make evidence the common ground<\/strong>
User research, usability testing, analytics, and clearly defined goals help move disagreements away from personal opinion.<\/li>\n<\/ul>\n\n\n\n\n
- Invite dissent deliberately<\/strong>
Ask what might be wrong, what has been overlooked, and who sees the situation differently.<\/li>\n<\/ul>\n\n\n\n\n
- Respond well to uncomfortable feedback<\/strong>
If leaders ask for honesty and then punish it, people learn remarkably quickly which request mattered more.<\/li>\n<\/ul>\n\n\n\n\n
- Separate ideas from ownership<\/strong>
Nobody should have to defend a feature simply because it was originally theirs.<\/li>\n<\/ul>\n\n\n\n\n
- Create smaller, safer channels when necessary<\/strong>
Not every difficult conversation needs to begin in a room full of twenty people.<\/li>\n<\/ul>\n\n\n\nHealthy teams don’t eliminate disagreement. They make it possible to disagree without requiring protective footwear.<\/p>\n\n\n\n
PRO TIP<\/h2>\n\n\n\n
\nIf everyone agrees all the time, check whether they actually feel safe enough to disagree. Watch out for teams self-censoring. As a result, the uncomfortable questions disappear, bad assumptions survive, and consensus becomes remarkably easy to achieve.<\/p>\n<\/blockquote>\n\n\n\n
EXAMPLES<\/h2>\n\n\n\n
\n
- A researcher removes an uncomfortable finding because a stakeholder might take it personally.<\/li>\n\n\n\n
- A designer knows a requested feature will confuse users but implements it without questioning the request.<\/li>\n\n\n\n
- A junior team member notices a serious problem but stays silent because the decision came from leadership.<\/li>\n\n\n\n
- Everyone praises a design during the review, then criticizes it privately afterward.<\/li>\n\n\n\n
- A team spends more time deciding how to present bad news than deciding how to fix the problem.<\/li>\n\n\n\n
- Someone starts a critique with five minutes of compliments before cautiously approaching the thing they actually wanted to discuss.<\/li>\n<\/ul>\n\n\n\n
CONCLUSION<\/h2>\n\n\n\n
Walking on Eggshells may keep meetings comfortable, but it rarely produces better products. When people are afraid to challenge assumptions, question decisions, or deliver inconvenient research findings, problems don’t disappear – they simply become harder to see<\/strong>. Eventually, the organization becomes very good at protecting feelings and surprisingly bad at protecting users.<\/p>\n\n\n\n
Strong product cultures aren’t places where everyone agrees.<\/strong> They’re places where disagreement can happen without fear, evidence can challenge authority, and a bad idea can be called a bad idea without becoming a personal crisis. After all, if your team has to tiptoe around every problem, sooner or later something is going to crack.<\/p>\n","protected":false},"excerpt":{"rendered":"
Walking on Eggshells means being extremely cautious in one\u2019s actions or words, usually to avoid upsetting someone else. Avoiding conflict becomes more important than improving the product.<\/p>\n
In product design, walking on eggshells means that problems are discussed privately instead of openly, feedback gets softened, and research findings are carefully worded so nobody feels implicated. And that feature requested by the executive? Everyone knows it is questionable but nobody wants to be the person who says so. The team is still communicating – it just isn’t saying what it really thinks.<\/p>\n","protected":false},"author":1,"featured_media":960,"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":[196,19,195,192,193,138,194],"class_list":["post-863","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mind-games-mental-traps","tag-challenge","tag-design","tag-disagreement","tag-eggshells","tag-fear","tag-product","tag-silence","entry","has-media","owp-thumbs-layout-horizontal","owp-btn-big","owp-tabs-layout-horizontal","has-no-thumbnails","has-product-nav"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-content\/uploads\/2026\/09\/64.jpg","_links":{"self":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/863","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=863"}],"version-history":[{"count":2,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/863\/revisions"}],"predecessor-version":[{"id":874,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/863\/revisions\/874"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media\/960"}],"wp:attachment":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media?parent=863"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/categories?post=863"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/tags?post=863"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}