{"id":1418,"date":"2026-10-21T11:23:27","date_gmt":"2026-10-21T11:23:27","guid":{"rendered":"https:\/\/adhdux.com\/?p=1418"},"modified":"2026-10-27T11:52:56","modified_gmt":"2026-10-27T11:52:56","slug":"you-are-hiring-from-the-wrong-pool","status":"publish","type":"post","link":"https:\/\/adhdux.com\/?p=1418","title":{"rendered":"You Are Hiring From the Wrong Pool"},"content":{"rendered":"\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"572\" src=\"https:\/\/adhdux.com\/wp-content\/uploads\/2026\/10\/talent-1024x572.png\" alt=\"\" class=\"wp-image-1419\" srcset=\"https:\/\/adhdux.com\/wp-content\/uploads\/2026\/10\/talent-1024x572.png 1024w, https:\/\/adhdux.com\/wp-content\/uploads\/2026\/10\/talent-300x167.png 300w, https:\/\/adhdux.com\/wp-content\/uploads\/2026\/10\/talent-767x428.png 767w, https:\/\/adhdux.com\/wp-content\/uploads\/2026\/10\/talent-1536x857.png 1536w, https:\/\/adhdux.com\/wp-content\/uploads\/2026\/10\/talent-2048x1143.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Why the best product people you will ever find have never worked in your industry<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Spotify<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;ve watched a hiring pattern play out at every large organization I have worked in or consulted for, and it produces the same outcome every time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The job description goes up. The recruiter filters the applications. The hiring manager reviews the shortlist. And at some point in that process, usually quietly and without anyone naming it out loud, a decision gets made: we need someone who has done this before. In our space. With our users. In our domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Healthcare organizations hire healthcare designers. Financial services firms hire fintech practitioners. Retail brands pull from retail. And the logic sounds reasonable on the surface. Domain knowledge matters. Regulatory context matters. User behavior in a specific vertical is not always intuitive to someone coming from outside it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But that logic is exactly why most product teams produce work that looks and feels like every other product in their category. They hired from the same pool their competitors hired from. They brought in practitioners whose entire frame of reference is the same set of conventions, the same user expectations, the same design patterns that everyone in the space already uses. And then they wonder why nothing they build feels different.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Problem With Vertical Hiring<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When you hire exclusively from your own industry, you are not hiring experience. You are hiring familiarity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Those are not the same thing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Familiarity means the candidate knows what the existing solutions look like. They know the vocabulary. They know the compliance requirements. They know which stakeholders will push back on what. They can get up to speed faster in the first ninety days, and they will make fewer embarrassing domain-knowledge mistakes in early meetings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Experience is something else. Experience is the accumulation of solved problems across contexts. It is pattern recognition that spans industries, not just depth within one. And when you hire only for familiarity, you are systematically filtering out the practitioners who carry that broader pattern recognition, because their resume does not match the vertical you are in.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The practitioner who spent three years in ecommerce, then two in financial services, then four in healthcare is not a generalist in the pejorative sense. They are someone who has watched conversion optimization, trust-building interfaces, and accessibility constraints play out across three entirely different regulatory and behavioral contexts. That practitioner has a catalog of solved problems that no single-industry hire can match.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where the Best Ideas Actually Come From<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">I have been in healthcare design long enough to have watched the same design problems get solved twice. Once badly, and once correctly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The correct solution almost never originated from within healthcare. It came from someone who had seen a similar friction point in a different context and knew what the resolution looked like before they started the work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Onboarding flows in healthcare products were transformed not by healthcare UX veterans, but by practitioners who had done onboarding in consumer apps where there was zero tolerance for drop-off. Notification architecture in clinical tools was rethought by someone who had spent years managing notification fatigue in media and retail applications. The best progressive disclosure patterns I have seen in enterprise health software were built by a designer who came directly from gaming, where layered information reveal is a first-principle discipline, not an afterthought.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">None of those people would have cleared the typical healthcare hiring filter. Their resumes did not say &#8220;5 years of EHR experience.&#8221; They would have been screened out in round one by a recruiter looking for vertical match.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is not a healthcare-specific problem. It happens in every mature industry. The more established the category, the more calcified the hiring criteria, and the more the domain defaults to reproducing its own conventions rather than borrowing better ones from adjacent fields.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Cross-Industry Practitioners Actually Bring<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The argument for hiring inside your vertical rests on the assumption that domain knowledge is the scarce resource. In most cases, it is not. Domain knowledge can be taught. A designer with strong craft and sharp systems thinking can learn the regulatory constraints of a new industry. They can study the user base. They can absorb the compliance vocabulary. They can do this faster than you expect, because smart practitioners learn domains the same way they learn design problems: by asking the right questions and building their mental model from the ground up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What cannot be easily taught is the cross-contextual pattern library that comes from working across industries. That is earned, not learned in an onboarding module.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cross-industry practitioners bring three things that single-vertical hires rarely carry in the same measure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first is contrast. When you have only ever worked in one industry, you do not know which of its conventions are load-bearing and which are just habits. A practitioner who has worked across multiple verticals knows the difference immediately, because they have seen the same problem solved differently elsewhere. They can tell you which of your patterns are the way things are done in this space and which of them are just the way things have always been done here, which is not the same thing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second is vocabulary transfer. Every industry solves some version of the same core UX problems: trust, onboarding, progressive disclosure, cognitive load, error recovery, navigation, data visualization. The solutions differ by context. A practitioner who has seen multiple solutions to the same category of problem arrives at yours with a larger option set. They are not limited to the solutions your industry has already tried.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The third is resistance to convention capture. Designers who have only ever worked in one vertical tend to accept the conventions of that vertical as natural. They stop questioning why things are done this way and start designing within those constraints as if they were fixed. Cross-industry practitioners have not been inside the convention long enough to stop seeing it. They still ask why, because in their last industry, the answer was different.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Counterargument and Why It Is Mostly Wrong<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The strongest version of the counterargument is that domain knowledge is not just learning material. It is judgment. A healthcare designer who has been through an FDA submission process, a HIPAA audit, and a clinical workflow overhaul has contextual judgment that a talented ecommerce designer simply does not have yet. And that judgment matters when the stakes are high.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is fair. For a very narrow set of roles where regulatory depth is genuinely the primary value driver, vertical experience matters more. A designer leading a clinical decision support product in a hospital system needs to understand clinical workflows in a way that takes real time to build.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But that describes a small fraction of product design roles. Most digital product work, even in regulated industries, is not that narrow. Most of it is building interfaces for people who need to accomplish something. The product has to be trustworthy, understandable, accessible, and efficient. Those are design problems, and design problems respond to craft and cross-contextual experience, not to resume vertical matching.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The other version of the counterargument is about ramp time. Hiring someone from outside the industry means a longer runway before they are fully productive. And in organizations operating under quarterly pressure, that is a real cost.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is a short-term calculation that trades long-term product differentiation for short-term onboarding convenience. The insider hire gets up to speed faster. They also produce work that looks exactly like the rest of the industry, because that is what they have been trained to see as the target.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What I Would Actually Change in the Hiring Process<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The filter should shift from vertical match to problem type match.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of asking whether a candidate has worked in healthcare, ask whether they have designed for high-stakes decisions under uncertainty, because that is the actual design problem in healthcare. Instead of filtering for fintech experience, filter for trust-building interface design in contexts where the user is anxious and the cost of error is high. Those are the real competency requirements, and they can be satisfied by practitioners from a dozen different industries.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second change is to weight the candidate&#8217;s range. A resume that shows three different industries over a ten-year career is not a liability. It is a signal that this person has been asked to adapt their thinking repeatedly and has done it successfully. That adaptability is a core design skill, not a career inconsistency.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The third change is to stop outsourcing domain knowledge transfer to the candidate. If your organization needs a practitioner to come in already knowing your regulatory environment, your user base, and your competitive landscape, you are asking the hire to do work that your onboarding process should do. Build a better onboarding process. Then you can hire for the things that are actually hard to develop: craft, systems thinking, cross-contextual judgment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Real Risk<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The real risk in hiring exclusively from your vertical is not that you will hire someone who makes domain knowledge mistakes. Most of those are correctable. The real risk is that you will spend years hiring exactly the right people with exactly the right industry background and still produce work that looks like everything else in your space, because everyone you hired was trained to see the same solutions as the correct ones.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Differentiated products come from differentiated thinking. Differentiated thinking comes from practitioners who have been exposed to more than one way to solve the same problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The best hire you have passed on probably had a resume that looked like a zigzag. They had worked in industries that had nothing to do with yours. They could not immediately name your regulatory constraints or speak fluently about your user population on day one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And they would have made your product better than anyone you actually hired.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Sources: Nielsen Norman Group, &#8220;Cross-Disciplinary Teams in UX Research,&#8221; 2025; IDEO, &#8220;T-Shaped Skills and Organizational Innovation,&#8221; design research archive; Harvard Business Review, &#8220;Why Your Best Hires May Come From Adjacent Industries,&#8221; 2024; McKinsey &amp; Company, &#8220;The Generalist Advantage,&#8221; 2025.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Why the best product people you will ever find have never worked in your industry Spotify I&#8217;ve watched a hiring pattern play out at every large organization I have worked in or consulted for, and it produces the same outcome every time. The job description goes up. The recruiter filters the applications. The hiring manager<\/p>\n<p><span class=\"more-wrapper\"><a class=\"more-link button\" href=\"https:\/\/adhdux.com\/?p=1418\">Continue reading<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1418","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts\/1418","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1418"}],"version-history":[{"count":1,"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts\/1418\/revisions"}],"predecessor-version":[{"id":1420,"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts\/1418\/revisions\/1420"}],"wp:attachment":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1418"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1418"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1418"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}