{"id":533,"date":"2025-12-03T01:05:52","date_gmt":"2025-12-03T01:05:52","guid":{"rendered":"https:\/\/hitchhikersguidetodesign.com\/book\/?page_id=533"},"modified":"2026-09-21T21:49:40","modified_gmt":"2026-09-22T04:49:40","slug":"about","status":"publish","type":"page","link":"https:\/\/hitchhikersguidetodesign.com\/book\/about\/","title":{"rendered":"About"},"content":{"rendered":"\n

A shared language for product teams<\/h2>\n\n\n\n

Product teams have a funny habit of running into the same problems again and again.<\/p>\n\n\n\n

Features keep creeping. Teams keep bikeshedding. Research gets ignored. Designs get polished long after they should have shipped. And somewhere, someone is still paving the cow path.<\/p>\n\n\n\n

The Hitchhiker\u2019s Guide to Design<\/strong> gives those situations names.<\/p>\n\n\n\n

It\u2019s an illustrated collection of design metaphors, behavioral effects, mental traps, idioms, and anti-patterns that help product teams recognize what\u2019s happening, talk about it, and – occasionally – even do something about it.<\/p>\n\n\n\n

Think of it as part field guide, part survival manual, and part collection of things you wish somebody had mentioned before the meeting started.<\/p>\n\n\n\n

Don\u2019t panic. There\u2019s probably a pattern for it.<\/strong><\/p>\n\n\n\n

How the Guide Works<\/h2>\n\n\n\n

Every pattern starts with a recognizable situation and explores:<\/p>\n\n\n\n

WHAT<\/strong> \u2014 What exactly is happening?<\/p>\n\n\n\n

WHY<\/strong> \u2014 Why do smart, well-intentioned teams keep doing this?<\/p>\n\n\n\n

WHEN<\/strong> \u2014 When should you watch out for it?<\/p>\n\n\n\n

HOW<\/strong> \u2014 How can you avoid it, reduce it, or escape it?<\/p>\n\n\n\n

EXAMPLES<\/strong> \u2014 What does it look like in the real world?<\/p>\n\n\n\n

Along the way you’ll encounter psychology, UX principles, product strategy, organizational behavior, research, software development, history, and the occasional dragon.<\/p>\n\n\n\n

The goal isn’t to memorize terminology.<\/p>\n\n\n\n

It’s to recognize the moment when someone around the table says:<\/p>\n\n\n\n

\u201cWait… we’re doing that thing again.\u201d<\/strong><\/p>\n\n\n\n

From 36 Patterns to 78<\/h2>\n\n\n\n

What started as a collection of 36 design patterns<\/strong> became something bigger.<\/p>\n\n\n

\n
\"Cover<\/figure>\n<\/div>\n\n\n

Volume 1<\/h3>\n\n\n\n

Patterns 01 – 36<\/strong><\/p>\n\n\n\n

From Lipstick on a Pig<\/em> and Mullet UI<\/em> to Cargo Cult UX<\/em>, Design Debt<\/em>, HiPPO<\/em>, and Hick’s Law<\/em>. A collection of 36 witty design metaphors, idioms & anti-patterns.<\/p>\n\n\n\n

Buying options from $9.98<\/a><\/p>\n\n\n\n

…don’t panic, there more:<\/p>\n\n\n

\n
\"Cover<\/figure>\n<\/div>\n\n\n

Volume 2<\/h3>\n\n\n\n

Patterns 37 – 72<\/strong><\/p>\n\n\n\n

More cognitive biases. More organizational dysfunction. More questionable product decisions. More things that seemed like a good idea at the time.<\/p>\n\n\n\n

Coming soon – Join the crew and get notified when<\/a><\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

Who Is This For?<\/h2>\n\n\n\n

You don’t need to be a designer to use these patterns.<\/p>\n\n\n\n

In fact, they become considerably more useful when everyone on the team understands them.<\/strong><\/p>\n\n\n\n

The Guide is written for people who make digital products:<\/p>\n\n\n\n

    \n
  • UX & UI designers<\/li>\n\n\n\n
  • Product designers<\/li>\n\n\n\n
  • Product managers<\/li>\n\n\n\n
  • Researchers<\/li>\n\n\n\n
  • Developers & engineers<\/li>\n\n\n\n
  • Design leaders<\/li>\n\n\n\n
  • Students & educators<\/li>\n\n\n\n
  • Stakeholders brave enough to enter a design review<\/li>\n\n\n\n
  • Anyone who has ever heard \u201cIt’s just a small change.\u201d<\/em><\/li>\n<\/ul>\n\n\n\n

    About Michael Gaigg<\/h2>\n\n\n\n

    Hi, I’m Michael.<\/p>\n\n\n\n

    I’m a UX designer, design leader, educator, and longtime collector of the strange things that happen when humans try to build digital products together.<\/p>\n\n\n\n

    Over the years, I’ve noticed that many seemingly complicated design problems aren’t particularly new. Different teams encounter the same behaviors, biases, shortcuts, debates, and spectacularly well-intentioned mistakes.<\/p>\n\n\n\n

    And many of them already have names. So I started collecting them.<\/p>\n\n\n\n

    The Hitchhiker\u2019s Guide to Design<\/strong> is my attempt to turn those ideas into something approachable, memorable, and useful – not another textbook, but a field guide you can actually bring into conversations with your team.<\/p>\n\n\n\n

    If a pattern makes you laugh because you’ve experienced it, that’s good. If it gives your team a name for something you couldn’t quite explain before, even better.<\/p>\n\n\n\n

    And if somebody says \u201cWe’re definitely not doing that\u201d<\/em> while everyone else slowly looks around the room… Well, that’s probably worth investigating.<\/p>\n\n\n\n

    Use of AI Disclaimer<\/h2>\n\n\n\n

    Illustrations <\/strong>were created using ChatGPT Plus (GPT-5 through GPT-5.6). Art direction (prompt engineering) and curation (manual editing) by Michael Gaigg.<\/p>\n\n\n\n

    Proofreading and editing<\/strong> supported by Microsoft Copilot.<\/p>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    A shared language for product teams Product teams have a funny habit of running into the same problems again and again. Features keep creeping. Teams keep bikeshedding. Research gets ignored. Designs get polished long after they should have shipped. And somewhere, someone is still paving the cow path. The Hitchhiker\u2019s Guide to Design gives those […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-533","page","type-page","status-publish","hentry","entry","owp-thumbs-layout-horizontal","owp-btn-big","owp-tabs-layout-horizontal","has-no-thumbnails","has-product-nav"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/pages\/533","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/types\/page"}],"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=533"}],"version-history":[{"count":10,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/pages\/533\/revisions"}],"predecessor-version":[{"id":1052,"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/pages\/533\/revisions\/1052"}],"wp:attachment":[{"href":"https:\/\/hitchhikersguidetodesign.com\/book\/wp-json\/wp\/v2\/media?parent=533"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}