Hiring through an HD lens.

The two lanes.

Human Design at the hiring desk is one of the framework's highest-leverage business applications, and one of its most ethically loaded. There is a clear line between using the framework as decision-support — legitimate, useful, structurally sound — and using it as a candidate filter — illegitimate, often illegal, definitely against PRISM's ground rules.

This chapter walks the line carefully. The framework can be a real asset to a thoughtful operator who wants to design roles that fit the people they hire, recognize structural mismatch when it shows up, and offboard with structural language rather than personal blame. It cannot be a substitute for actually evaluating whether a candidate can do the work, and any attempt to use it as one is a misuse the framework itself does not authorize.

We hold this line firmly because the cost of crossing it is high — legal, ethical, and practical — and because the legitimate uses of the framework in hiring are enough to justify learning it. You do not need the illegitimate use to get value.

The hard line.

Human Design output cannot be the sole basis for hiring, firing, promotion, or compensation. This is non-negotiable in PRISM, and it is the single most important sentence in this chapter.

Filtering candidates by type, by authority, or by any other chart property is discrimination dressed in framework language. Do not do it. Asking candidates for their birth data before an offer is selection-stage filtering, and is not legitimate. Stereotyping the canonical patterns — I do not want to hire a Reflector for this; we need a Projector here — as a decision shortcut is also not legitimate, because it short-circuits the actual evaluation of the actual person in front of you.

PRISM's product surfaces are designed to make this kind of misuse structurally awkward. We do not expose chart filtering on candidate pools. We do not provide tooling that supports selection-by-chart. Operators who attempt it are misusing the tool, and the framework itself does not endorse the misuse.

The reason for the firmness is not just the ethical and legal exposure, although both are real. The deeper reason is that the framework is not designed to predict job performance. Two candidates with similar type and authority can perform radically differently in the same role; experience, skill, motivation, fit with the specific team, and a hundred other factors the chart cannot see all matter more for actual outcomes. Using Human Design as a hiring filter is structurally incorrect even before it is ethically problematic.

Where the framework legitimately helps.

The legitimate uses cluster around structuring the role and deploying the person you have hired, not around picking the person to hire.

Designing the role's rhythm. A role you have decided requires Generator-pace daily output is going to crush a Projector who takes it. The right move is not to filter Projectors out of the pool; the right move is to be honest with yourself and the candidates about what the role's actual cadence is. The Projector who reads the job description and self-selects out is operating with full information, which is the goal.

Calibrating expected outputs. Manifestor roles measure differently than Generator roles. Do not apply Generator key-performance-indicators to a Manifestor seat once you have hired one. The Manifestor's contribution is non-linear; if the role's incentive structure does not understand that, the design will fail predictably regardless of who is in the seat.

Designing onboarding for the person you actually hired. Once a candidate has accepted, started, and voluntarily shared their chart with the team, structure their first ninety days around how they are built to operate. The new Projector hire benefits from explicit invitations into the rooms where their gift can be used. The new Manifestor hire benefits from clear domain ownership and inform-protocols rather than approval-seeking. The new Reflector hire benefits from being told, plainly, that material decisions in their lane will be expected on a slower cadence than the surrounding culture might suggest.

Composite read for fit with the existing team. Once a candidate is far along in the hiring process and the framework is part of how the team already operates, an authority-cadence read on the dyad of the candidate with their direct manager can be useful as a structuring input — how should the relationship be designed? — not as a selection filter. The distinction matters and should be held visibly.

Offboarding language. When a role is not working, structural language often serves the conversation better than personal language. This role required someone built for daily-grind production; you are built for catalytic bursts; this is not a failing on either side and we both knew the role's shape was unusually narrow is a more honest and more humane framing than you have not been performing. The first allows both parties to part with dignity; the second tends to leave one or both feeling shame that the situation does not warrant.

Where the framework damages hiring.

The patterns to recognize and avoid.

Asking candidates for birth data before offer. This is selection-stage filtering and should not happen. The framework's role in hiring begins after the offer is accepted, when the candidate has voluntarily entered the framework's terms.

Treating chart properties as credentials. The Manifestor is not a better candidate than the Projector for the founder seat. They are different. Whichever person actually fits the role — with their actual experience, actual skill, actual judgment — wins the seat. The chart layer does not override the basic evaluation.

Stereotyping. I do not want to hire a Reflector for this and its variants. The candidate in front of you is not a stereotype of their type; they are a specific person whose specific fit you are evaluating. The framework's general claims about types are useful as broad orientation; they do not describe individuals well enough to make selection calls.

Public discussion of someone's chart without their consent. PRISM enforces this with team-membership controls and audit logging. The principle applies outside the product as well. A team member's chart is theirs to share; the team is responsible for not discussing it as if it were public information.

The legal layer.

Most jurisdictions have employment-discrimination law that does not contemplate Human Design specifically but does cover the general pattern of selecting candidates based on personal-identity properties they did not choose. Even if Human-Design-based filtering does not fall under a protected class in your particular jurisdiction, the general principle — decisions based on chart properties rather than on ability to do the work — is on shaky legal ground and is going to look bad in any subsequent dispute.

PRISM's position: keep the framework in the help me structure this role lane, not the help me pick this candidate lane. The first is decision-support and lawful. The second is discrimination and exposes the operator and the company to real risk.

The honest commercial frame.

The right way to use the framework in hiring is as a frame for empathy and structural design once you have hired someone for legitimate reasons. Their chart helps you deploy them well. Their chart helps you understand why a particular pattern of friction is showing up. Their chart helps you offboard humanely if the role is not working out.

The chart should not have been a selection input. The framework does not need to be used at the selection stage to deliver real value at every other stage. Operators who restrict its use to the legitimate lanes get the value without the exposure.

This is one of the framework's quietest commercial gifts: applied carefully, it improves the operating layer of a company significantly without ever needing to touch the hiring decision in a way that would damage the candidate or the company. The line is not a constraint; it is the position from which the framework actually works.