{"id":19715,"date":"2026-02-02T10:00:26","date_gmt":"2026-02-02T09:00:26","guid":{"rendered":"https:\/\/then.agency\/articoli\/design-patterns"},"modified":"2026-10-07T22:34:52","modified_gmt":"2026-10-07T21:34:52","slug":"design-patterns","status":"publish","type":"post","link":"https:\/\/then.agency\/en\/articoli\/design-patterns","title":{"rendered":"Design Patterns: what they are and when to use them"},"content":{"rendered":"<p>Design Patterns are one of the most powerful, and at the same time most misunderstood, resources in Experience Design. They are often treated as ready-to-use solutions, elements to copy or shortcuts to speed up design. In reality, a Design Pattern is never an automatic answer, but <strong>a conscious design decision<\/strong>.<\/p>\n<p>When a pattern is applied correctly, the user does not notice it. When it is used badly, it becomes an invisible obstacle that generates frustration, errors and abandonment. Understanding <strong>when<\/strong> to use a Design Pattern is therefore more important than knowing <strong>which<\/strong> pattern to use.<\/p>\n<h2>What Design Patterns really are<\/h2>\n<p>A <strong>Design Pattern<\/strong> is a recurring solution to an experience problem that shows up in similar contexts and has been validated over time through real use. It is not a rule, it is not a template and it is not a graphic component.<\/p>\n<p>A pattern describes:<\/p>\n<ul>\n<li>an <strong>experience problem<\/strong><\/li>\n<li>the <strong>context<\/strong> in which it appears<\/li>\n<li>an <strong>effective solution<\/strong><\/li>\n<li>the associated <strong>trade-offs<\/strong><\/li>\n<\/ul>\n<blockquote>\n<p><strong><a href=\"https:\/\/www.nngroup.com\/articles\/consistency-and-standards\/\" target=\"_blank\" rel=\"noopener\">Nielsen Norman Group<\/a><\/strong> stresses that patterns work because they reduce cognitive effort and exploit familiarity, one of the main factors of usability.<\/p>\n<\/blockquote>\n<h2>Patterns, UI components and Design Systems<\/h2>\n<p>Confusing these levels is one of the most common mistakes in digital teams.<\/p>\n<ul>\n<li>The <strong>Design Pattern<\/strong> is conceptual<\/li>\n<li>The <strong>UI component<\/strong> is implementational<\/li>\n<li>The <a href=\"https:\/\/then.agency\/en\/articoli\/design-system-implementation\"><strong>Design System<\/strong><\/a> is governing<\/li>\n<\/ul>\n<p>A good Design System does not collect components, but <strong>formalizes behavior patterns<\/strong>. Without patterns, the Design System becomes just a graphic library.<\/p>\n<h2>Why Design Patterns work<\/h2>\n<p>Patterns work when they respond to three fundamental user needs:<\/p>\n<h3>Familiarity<\/h3>\n<p>People prefer interfaces they recognize. Familiarity reduces learning time and increases the perception of control.<\/p>\n<h3>Efficiency<\/h3>\n<p>An effective pattern lets the user complete an action with less effort, fewer errors and fewer pointless decisions.<\/p>\n<h3>Predictability<\/h3>\n<p>The user must be able to anticipate what will happen after an action. Patterns make the interaction legible.<\/p>\n<blockquote>\n<p><strong><a href=\"https:\/\/www.interaction-design.org\/literature\/topics\/design-patterns\" target=\"_blank\" rel=\"noopener\">Interaction Design Foundation<\/a><\/strong> highlights how patterns are fundamental for designing learnable, scalable experiences.<\/p>\n<\/blockquote>\n<h2>The main types of Design Patterns<\/h2>\n<h3>Navigation patterns<\/h3>\n<p>They handle orientation and structure:<\/p>\n<ul>\n<li>menus<\/li>\n<li>breadcrumbs<\/li>\n<li>tabs<\/li>\n<li>navigation drawers<\/li>\n<\/ul>\n<p>Without clear navigation patterns, even the best content becomes inaccessible.<\/p>\n<h3>Input and form patterns<\/h3>\n<p>They reduce errors and abandonment:<\/p>\n<ul>\n<li>inline validation<\/li>\n<li>step forms<\/li>\n<li>smart defaults<\/li>\n<li>autofill<\/li>\n<\/ul>\n<p>Here the impact on the business is direct: small pattern mistakes can generate large conversion losses.<\/p>\n<h3>Feedback and system status patterns<\/h3>\n<p>They make the system understandable:<\/p>\n<ul>\n<li>loading states<\/li>\n<li>contextual error messages<\/li>\n<li>action confirmations<\/li>\n<\/ul>\n<blockquote>\n<p>According to <a href=\"https:\/\/www.nngroup.com\/articles\/ten-usability-heuristics\/\" target=\"_blank\" rel=\"noopener\"><strong>Nielsen Norman Group<\/strong><\/a>, visibility of system status is one of the pillars of usability.<\/p>\n<\/blockquote>\n<h3>Decision-making patterns<\/h3>\n<p>They support choice:<\/p>\n<ul>\n<li>prioritized CTAs<\/li>\n<li>progressive disclosure<\/li>\n<li>guided comparisons<\/li>\n<\/ul>\n<p>Here the line between UX and <a href=\"https:\/\/then.agency\/en\/articoli\/dark-patterns-what-they-are-ux\">dark patterns<\/a> is thin: designing well means <strong>guiding without manipulating<\/strong>.<\/p>\n<h2>When NOT to use a Design Pattern<\/h2>\n<p>A pattern fails when:<\/p>\n<ul>\n<li>it is applied without context<\/li>\n<li>it is not consistent with the target<\/li>\n<li>it is not validated<\/li>\n<li>it conflicts with other patterns<\/li>\n<\/ul>\n<p><strong><a href=\"https:\/\/www.qualtrics.com\/experience-management\/customer\/\" target=\"_blank\" rel=\"noopener\">Qualtrics<\/a><\/strong> stresses that experience must always be evaluated in its real context, through data and continuous feedback.<\/p>\n<h2>Design Patterns and UX research<\/h2>\n<p>Solid patterns come from research:<\/p>\n<ul>\n<li>observation<\/li>\n<li>usability tests<\/li>\n<li>behavioral analysis<\/li>\n<li>quantitative data<\/li>\n<\/ul>\n<p><strong><a href=\"https:\/\/www.medallia.com\/customer-experience\/\" target=\"_blank\" rel=\"noopener\">Medallia<\/a><\/strong> highlights how the continuous use of insights makes it possible to build experiences that are consistent over time.<\/p>\n<h2>Patterns and AI: what changes<\/h2>\n<p>With the introduction of AI:<\/p>\n<ul>\n<li>new conversational patterns emerge<\/li>\n<li>interfaces become adaptive<\/li>\n<li>predictability becomes even more critical<\/li>\n<\/ul>\n<p>In this scenario, patterns do not limit innovation: <strong>they make it understandable<\/strong>.<\/p>\n<h2>The most common mistakes in using Design Patterns<\/h2>\n<ul>\n<li>Copying patterns without understanding them<\/li>\n<li>Using them as rigid constraints<\/li>\n<li>Not testing them<\/li>\n<li>Not documenting them<\/li>\n<\/ul>\n<p>A pattern is never &#8220;right&#8221; in the absolute. It is right <strong>for someone, in a context, with a goal<\/strong>.<\/p>\n<h2>Design Patterns as a strategic asset<\/h2>\n<p>When patterns are:<\/p>\n<ul>\n<li>documented<\/li>\n<li>shared<\/li>\n<li>governed<\/li>\n<\/ul>\n<p>they become an accelerator of quality, consistency and scalability. They are one of the pillars of a mature UX.<\/p>\n<h2>Conclusion: design patterns, don&#8217;t collect them<\/h2>\n<p>Design Patterns are not for designing faster. They are for designing <strong>better<\/strong>. Using them consciously means building experiences that respect people&#8217;s time, attention and expectations.<\/p>\n<p>If you want to understand how to define, validate and govern Design Patterns within your product or your Design System, <a href=\"https:\/\/then.agency\/en\/solutions\"><strong>Then can work alongside you<\/strong><\/a> with <a href=\"https:\/\/then.agency\/en\/solutions\/ux-audit\">UX Audit<\/a>, <a href=\"https:\/\/then.agency\/en\/solutions\/ux-ui-design\">UX research and strategic experience design<\/a> activities.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Not shortcuts to copy: when a pattern helps the user and when it gets in the way.<\/p>\n","protected":false},"author":10,"featured_media":18449,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"UX design patterns: what they are, types and examples","rank_math_description":"What design patterns are in UX, which recurring problems they address and how to recognize when to apply them.","rank_math_focus_keyword":"design pattern","fonti_articolo":"<ul>\n<li data-start=\"7686\" data-end=\"7800\"><a href=\"https:\/\/www.nngroup.com\/articles\/consistency-and-standards\/\">Nielsen Norman Group, \"Consistency and Standards\"<\/a><\/li>\n<li data-start=\"7686\" data-end=\"7800\"><a href=\"https:\/\/www.interaction-design.org\/literature\/topics\/design-patterns\">Interaction Design Foundation, \"Design Patterns in UX Design\"<\/a><\/li>\n<li data-start=\"7686\" data-end=\"7800\"><a href=\"https:\/\/www.qualtrics.com\/experience-management\/customer\/\">Qualtrics, \"Experience Management\"<\/a><\/li>\n<li data-start=\"7686\" data-end=\"7800\"><a href=\"https:\/\/www.medallia.com\/customer-experience\/\">Medallia, \"<em data-start=\"8055\" data-end=\"8085\">Customer Experience Insights\"<\/em><\/a><\/li>\n<\/ul>\n","riassunto":"<p>A design pattern is not an element to copy to save time. It is a solution already validated by real use, with a precise context and trade-offs to accept.<\/p>\n<p>When it works you do not notice it. When it is applied badly it becomes an invisible obstacle that generates errors and abandonment, which is why knowing when to use one matters more than knowing which.<\/p>\n<p>The main families, from navigation to feedback, the difference from components and design systems, and the cases where it is better not to use them.<\/p>","footnotes":""},"categories":[55],"tags":[],"class_list":["post-19715","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ux-and-ui-design"],"_links":{"self":[{"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/posts\/19715","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/comments?post=19715"}],"version-history":[{"count":0,"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/posts\/19715\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/media\/18449"}],"wp:attachment":[{"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/media?parent=19715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/categories?post=19715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/then.agency\/en\/wp-json\/wp\/v2\/tags?post=19715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}