Standard onboarding is designed by HR departments for the average new hire. The problem is that there is no average new hire. A D-type who is handed a 200-page employee handbook and told to "take the first week to settle in" is going to be climbing the walls by Wednesday. An S-type who is thrown into a high-stakes project on day one with no relationship context is going to be silently panicking.
Onboarding by Type
D-type new hires want to contribute immediately. Skip the lengthy orientation and get them into real work by day two. Give them a clear goal for their first 30 days with measurable outcomes. Assign them a challenging early project that lets them demonstrate capability. D-types onboard by doing. Extended observation periods feel like punishment.
I-type new hires want to connect. Their first week should be heavy on introductions, team lunches, and social context. Who are the key people? What are the unwritten rules? Where does the team get together informally? I-types onboard through relationships. They will figure out the processes later. What they need first is to feel part of the group.
S-type new hires want predictability. Give them a detailed schedule for the first two weeks. Introduce them to a reliable buddy who is available for questions. Walk them through every system, every tool, and every recurring process. S-types onboard through structure. Uncertainty is exhausting for them, and a well-organized first week builds the safety foundation for months of strong performance.
C-type new hires want documentation. Give them access to wikis, process docs, and system architectures. Let them read and learn before expecting output. Schedule one-on-ones with key stakeholders to ask detailed questions. C-types onboard through understanding. They will be slow to contribute initially, but once they understand the system, their output will be remarkably high quality from the start.
Key Takeaways
- D-types: real work by day two. Give them a 30-day goal.
- I-types: introductions first. Relationships before processes.
- S-types: detailed schedule and a reliable buddy. Structure builds safety.
- C-types: documentation access and time to learn. Understanding before output.

