Type at work.

Five types, one schedule.

Five energy types operate at work in genuinely different ways. The cost of treating them as interchangeable — same schedule, same expectations, same metrics — is structural underperformance plus persistent burnout for the types that do not fit the dominant work pattern, which in most modern organizations is Generator on a Monday-to-Friday cadence with quarterly outputs.

About thirty percent of any well-mixed team is something other than that, and most of them have spent their adult lives wondering why they keep ending up exhausted, unrecognized, or quietly underperforming despite being competent. They are not failing. They are operating against their design, in a system built for someone else's design.

This chapter is the practical translation. How to deploy each type, what kind of work fits, what kind crushes, and what to ask of (and not to ask of) people on your team. We will hold a hard line on the ethical question at the end: this is decision-support, never determinative, especially in hiring contexts.

Manifestor — catalytic, in bursts.

About eight percent of the population. Manifestors are built to initiate. Energy comes in catalytic bursts followed by recovery. They are not built for sustained daily output, and pushing a Manifestor to deliver Generator-pace consistency produces burnout faster than almost any other configuration.

Roles that fit. Founder or first-mover work, where the value is in starting things from nothing. Strategy lead. Head of new initiatives. Executive sponsor of new ventures. Creative director, anyone who frames the vision and steps back. Crisis intervention, where the move is to set direction fast.

Roles that crush. Pure execution and operational maintenance. Daily-grind production work without bursts of new initiation. Roles where the Manifestor has to ask permission constantly and cannot inform-and-act.

Operational implication. Their impact is non-linear. Measure in initiations and direction-changes, not hours logged. Do not calendar them like builders. The Manifestor must be allowed to inform without seeking approval — this is structural, not a personality preference, and treating it as one is the most reliable way to lose a Manifestor's contribution permanently.

Generator — sustainable life-force.

About thirty-seven percent of the population. The most common type and the daily-execution engine of any team. Sustainable energy that can run for years on the right work, but turns to chronic frustration on the wrong work. The trick: Generators must respond rather than initiate. They do not pick the work; the work appears, and the body responds yes or no.

Roles that fit. Builders, makers, craftspeople — anything where the work is concrete and the body responds yes to it. Most operational roles, when the role's daily texture matches what the Generator actually wants to do. Long-haul ownership of products, codebases, customer relationships.

Roles that crush. Roles where they have to manufacture initiative out of nothing. Cross-functional figure out what we should do next roles without concrete inputs to respond to. Cold-outreach sales without warm response signals.

Operational implication. Present Generators with concrete options and let their body respond. Do not ask them to brainstorm in a vacuum. The difference between a Generator working on the right thing and the wrong thing is enormous — productivity ratios of three to five times are not unusual, and the difference between a satisfied Generator and a frustrated one is mostly a question of whether the daily work was the right thing to begin with.

Manifesting Generator — multi-track builder.

About thirty-three percent of the population. Hybrid — the Manifestor's speed on top of the Generator's response mechanic. MGs run multiple tracks simultaneously, pivot fast, and skip steps that pure Generators have to complete in order. They also have to inform when they pivot, otherwise their team is constantly out of sync with where they actually are.

Roles that fit. Multi-product founders. Roles with high parallelism and frequent pivots. Generalist operator roles where the role itself spans multiple domains. High-velocity build roles — startups, R&D teams, fast iteration cycles.

Roles that crush. Pure-specialist deep-focus roles where one track is the whole job. Hierarchical environments where pivots require committee approval. Anywhere the speed of pivot is treated as a liability rather than an asset.

Operational implication. Do not expect linear progress. MGs leap. They also drop tracks they were on yesterday and pick them up again next week. The protocol: require explicit informing on pivots, do not mistake their multi-track motion for attention deficit, and structure their work in parallel streams rather than serial dependencies wherever possible.

Projector — strategic outside-eye.

About twenty percent of the population. Projectors see the system from outside in a way the people inside it cannot. They are not built for high-output execution; their energy is shorter-burst, focused, and amplifies whatever defined energy is around them. The unlock: recognition before output. Projectors need to be specifically asked for their perspective, given a clear seat at the table, not expected to volunteer and grind.

Roles that fit. Consultant, advisor, fractional executive, executive coach. Head of strategy, head of org design, internal advisor roles. Editor, critic, taste-maker — roles that read others' work. Often hired part-time; the four-day workweek was practically invented for Projectors.

Roles that crush. Generator-pace execution roles. They will burn out repeatedly. Hustle-culture environments where output is the only metric. Roles where their gift is expected to flow without explicit invitation.

Operational implication. The Projector's shadow is bitterness, and it arrives when they are contributing without recognition or running at Generator pace. Hire Projectors and explicitly invite them. Pay them well for smaller scopes. Do not expect them to grind. The Projector who has been recognized produces work nobody else on the team could have produced; the Projector who has been ground produces resentment.

Reflector — mirror energy.

About one percent of the population. Reflectors are rare and unique. They have no internally defined centers; their energy is fully open, and they read the health of the team, organization, or environment they are inside. Decisions move on a twenty-eight-day lunar cycle.

Roles that fit. Cultural advisor, organizational health roles, ombudsperson positions. Long-cycle strategic positions where decisions can wait. External board roles, nonprofit governance, roles where the read on the broader field is the contribution.

Roles that crush. Anything requiring same-week material commitments. High-volume operational roles. Hostile or frenetic environments — Reflectors absorb the field they are in, and the cost of placing one inside a chronically dysfunctional environment is high.

Operational implication. Do not ask Reflectors for fast decisions. Honor the lunar cadence. Their read on team health is unusually accurate; listen when they share it, especially when what they share is uncomfortable. Environment matters more for Reflectors than for any other type; build the right room.

The honest line on hiring.

PRISM's ethical guardrail is non-negotiable: Human Design output cannot be the sole basis for hiring, firing, promotion, or compensation decisions. Type can inform how you structure the role you are hiring for — the rhythm, the recognition, the kind of output expectation — but it cannot tell you whether to hire any specific candidate.

The legitimate use of the framework at work is decision-support. Better language for understanding why a particular team member is thriving or struggling. Better protocols for how to deploy people once they are on the team. Better empathy for why someone does not fit the dominant pattern. Use it for that.

Do not use it as a candidate filter. Do not screen for type. Do not ask candidates for their birth data. The framework can help you operate the team you have; it cannot decide who should be on the team. Those decisions remain yours, supported by all the conventional inputs (work history, references, demonstrated capability, fit with the role as defined) plus, where the candidate volunteers it, the framework's interpretive layer.

The line is firm because the cost of crossing it is high. Discrimination claims aside, the practical truth is that the framework is not designed to make hiring calls, and using it that way produces both bad hiring and bad uses of the framework.