{"id":900,"date":"2026-11-16T12:50:47","date_gmt":"2026-11-16T20:50:47","guid":{"rendered":"https:\/\/hitchhikersguidetodesign.com\/book\/?p=900"},"modified":"2026-11-16T12:50:50","modified_gmt":"2026-11-16T20:50:50","slug":"here-be-dragons","status":"publish","type":"post","link":"https:\/\/hitchhikersguidetodesign.com\/book\/here-be-dragons\/","title":{"rendered":"69 \u2022 Here Be Dragons"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Here Be Dragons is a popular phrase to depict dangerous or unexplored territory. Everyone knows it&#8217;s there yet nobody quite understands it. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In product design, it refers to uncharted, complex, or risky areas of a product or system. So the team draws an imaginary border around that part of the product. Beyond that line lie unknown dependencies, mysterious design decisions, legacy code, forgotten business rules, or angry customers. The dragons may or may not be real. Nobody particularly wants to find out.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">ORIGIN<\/h2>\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 phrase <em>Here be dragons<\/em> is famously associated with old maps and the idea that medieval cartographers marked unknown or dangerous territories with dragons, sea monsters, and other fantastical creatures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The reality is a little less dramatic. Historic maps certainly featured strange creatures in distant and poorly understood regions, but <em>here be dragons<\/em> was never a common cartographic warning. One of the few known examples appears on the Hunt-Lenox Globe, dating from around 1508, where the Latin inscription <em>HC SVNT DRACONES<\/em> &#8211; \u201cHere are dragons\u201d &#8211; appears near the eastern coast of Asia.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">More commonly, cartographers used ideas such as <em>terra incognita<\/em>: unknown land. Where reliable knowledge ended, so did the map.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Over time, <em>Here Be Dragons<\/em> became a metaphor for exactly that boundary: the point where knowledge gives way to uncertainty, speculation, and potential danger. Software developers adopted the expression too, using it to warn others about obscure, complicated, or particularly hazardous areas of code.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">WHEN<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Product teams have their own maps &#8211; and plenty of places where someone has drawn a dragon. Places you may encounter Here Be Dragons include the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Nobody knows why something works the way it does<\/strong><br>\u201cIt&#8217;s always been like that\u201d is the closest thing available to documentation.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Certain parts of the product are carefully avoided<\/strong><br>Everyone agrees the workflow is terrible. Changing it, however, is apparently forbidden by the <a href=\"https:\/\/hitchhikersguidetodesign.com\/book\/hippo\/\">HiPPO<\/a>.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Assumptions have quietly become facts<\/strong><br>\u201cUsers need this\u201d has been repeated for three years. Nobody remembers asking them.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Knowledge has turned into folklore<\/strong><br>Someone remembers that somebody once tried changing it and \u201csomething bad happened.\u201d<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Success is assumed rather than demonstrated<\/strong><br>The team shipped the redesign and moved on without finding out whether it actually improved anything.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>You hear: \u201cWe don&#8217;t touch that.\u201d<\/strong><br>No further explanation is considered necessary.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If a part of your product is governed more by assumptions, warnings, and stories than evidence, you&#8217;ve reached the part of the map marked <strong>Here Be Dragons<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WHY<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dragons thrive where knowledge disappears. Following are some of the reasons this may happen:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Complexity accumulates<\/strong><br>Features, exceptions, integrations, workarounds, and business rules pile up until nobody understands the entire system.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Knowledge leaves<\/strong><br>Designers change teams. Engineers leave. Product managers move on. What was once common knowledge becomes organizational archaeology.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Decisions lose their context<\/strong><br>Teams document what was built but not why. Years later, intentional constraints and historical accidents become indistinguishable.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Team lacks understanding<\/strong><br>It takes time and courage to explore the unknown. <\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Unknown becomes synonymous with dangerous<\/strong><br>When evidence is missing, imagination fills the gap &#8211; and imagination has excellent dragons.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">HOW<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Key to avoiding dragons is to turn unknowns into things that can be explored, tested, and measured. Follow these steps to map the uncharted:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Acknowledge <em>\u201cwe don&#8217;t know\u201d<\/em><\/strong><br>Recognize the unknown rather than pretending the territory isn&#8217;t there.<\/li>\n\n\n\n<li><strong>Map what you don&#8217;t know<\/strong><br>Identify undocumented workflows, uncertain dependencies, unanswered research questions, and assumptions nobody has verified. <\/li>\n\n\n\n<li><strong>Test old assumptions<\/strong><br>Technology changes. Business rules change. Users change. A constraint from five years ago may no longer exist. Show your dragons.<\/li>\n\n\n\n<li><strong>Separate dragons from drawings of dragons<\/strong><br>\u201cChanging this will break billing\u201d is a claim that can be investigated. \u201cWe must not change that\u201d is folklore.<\/li>\n\n\n\n<li><strong>Define what success looks like<\/strong><br>Decide what outcome you expect and how you will recognize and measure it.<\/li>\n\n\n\n<li><strong>Explore incrementally<\/strong><br>Use research, prototypes, technical spikes, experiments, feature flags, and small releases to learn without betting the entire kingdom.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><strong>Document the expedition and update the map<\/strong><\/strong><br>Once territory is understood, replace the dragon. Don&#8217;t make the next team rediscover the continent.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The goal is to replace imaginary monsters with actual knowledge &#8211; but it requires determination and courage.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">PRO TIP<\/h2>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">As designers, we must measure our assumptions and make the outputs understandable to the business. Otherwise we are part of the folklore.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">EXAMPLES<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A checkout flow nobody wants to redesign because its business rules aren&#8217;t documented.<\/li>\n\n\n\n<li>A legacy feature that research consistently identifies as confusing but the team considers too risky to change.<\/li>\n\n\n\n<li>An old component everyone continues copying because nobody knows why it was designed that way.<\/li>\n\n\n\n<li>A team insists users need a feature despite having no research or behavioral data supporting the assumption.<\/li>\n\n\n\n<li>A product area previously owned by someone who left years ago, taking most of its institutional knowledge with them.<\/li>\n\n\n\n<li>A designer asks why a strange field is mandatory and receives the historically significant answer: <em>\u201cJust don&#8217;t remove that.\u201d<\/em><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">CONCLUSION<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Every mature product has unexplored territory. Systems become complicated, people leave, decisions lose their context, assumptions escape from research decks and somehow become facts, and yesterday&#8217;s perfectly sensible workaround becomes today&#8217;s mysterious dropdown with seventeen options.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There&#8217;s nothing inherently wrong with having blank spaces on the map. Design always involves uncertainty. In fact, <strong>acknowledging those blank spaces is considerably healthier than pretending we already understand them<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The danger begins when <em>\u201cwe don&#8217;t know\u201d<\/em> quietly turns into <em>\u201cwe don&#8217;t go there.\u201d<\/em> That&#8217;s when assumptions become warnings, warnings become folklore, and teams stop asking whether the monsters drawn on their maps actually exist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Good product teams don&#8217;t pretend there are no dragons, they show their dragons<\/strong> &#8211; the risks, assumptions, uncertainties, and unexplored territory &#8211; and then systematically go looking for evidence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Here Be Dragons is a popular phrase to depict dangerous or unexplored territory. Everyone knows it&#8217;s there yet nobody quite understands it. <\/p>\n<p>In product design, it refers to uncharted, complex, or risky areas of a product or system. So the team draws an imaginary border around that part of the product. Beyond that line lie unknown dependencies, mysterious design decisions, legacy code, forgotten business rules, or angry customers. The dragons may or may not be real. Nobody particularly wants to find out.<\/p>\n","protected":false},"author":1,"featured_media":965,"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_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[25],"tags":[232,19,231,236,193,233,234,235,39],"class_list":["post-900","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mind-games-mental-traps","tag-business-rules","tag-design","tag-dragons","tag-facts","tag-fear","tag-product-team","tag-trap","tag-uncertainty","tag-ux","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\/69.jpg","_links":{"self":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/900","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=900"}],"version-history":[{"count":3,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/900\/revisions"}],"predecessor-version":[{"id":1177,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/posts\/900\/revisions\/1177"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media\/965"}],"wp:attachment":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media?parent=900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/categories?post=900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/tags?post=900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}